× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes, this is a known problem in WDSC.  I posted it at developerWorks and
my response from an IBMer with the name "shahall" was:

"This forum is a best effort support forum for middleware. Product
specific support and development teams do not monitor the forum. I am
not aware of an evaluation copy of WDSC, if I am not mistaken the
software is iSeries specific and you should have an IBM support contract
for this software."

Lots of help, eh?

However, another WDSC user with the same problem pointed me to a
solution.

"As a default, WSAD includes the webservices.jar from
WAS_50_PLUGINDIR/lib. Check the properties of your Client Project. If
you find that the reference for webservice.jar points to
...\runtimes\base_v50_stub\lib\webservices.jar (under properties - Java
Build Path - Libraries) - bingo you're halfway there ;-)

Simply delete that library reference and add an external jar instead
that points to ...\runtimes\base_v51\lib\webservices.jar."

HTH

Joe

> From: SamL
> 
> I'm running WebSphere Development Studio Client for iSeries Version:
> 5.1.2.4
> Build id: 20050104_2139. 2.4GHZ PC, 1 GB memory.
> 
> >>#{pc_WSProxy.doGetTempAction}: javax.faces.el.EvaluationException:
> >>java.lang.Error: Unresolved compilation problem:
> >>    The constructor ParameterDesc(QName, byte, QName, Class,
> >>boolean,
> >>boolean, boolean, boolean) is undefined


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.