× 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.



JAX-RPC is an old standard as is Apache Axis, which was based on JAX-RPC.
The JAX-RPC web services standard has been replaced by JAX-WS. I suggest
looking at Apache Axis2:
http://ws.apache.org/axis2/

The downside is that you won't have the wizards but Axis2 does provide a
command-line WSDL2Java command for creating code stubs from the WSDL.
There may be a bit of a learning curve but you won't find any new
development going on for Axis and thus no support in the forums and/or
mailing lists.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx




Dhanushka Manjula
<dhanuxp@xxxxxxxx
m> To
Sent by: java400-l@xxxxxxxxxxxx
java400-l-bounces cc
@midrange.com
Subject
JAX-RPC & Apache Axis Web Service
2009-12-08 10:16 problem on WAS 6.0


Please respond to
Java Programming
on and around the
iSeries / AS400
<java400-l@midran
ge.com>






Hi All,



Scenario 1:



Iâm using RAD 7.0 and created the Top-Down Java beans Web service from
given WSDL,

Set Web Service Runtime = JAX-RPC

No Errors!! Iâm happy!! Wrote a business logic & Deployed on WAS 6.0



I can see the web service from dotNet side & Can be accessed the service
through Test Web Service Explorer as well.

The WebServices Explorer however does not work & always returning an error:
(even in donNet side gives error)



IWAB0135E An unexpected error has occurred.404 Not Found

500

Internal Server Error



Then I tried to create Web Service client & Client Creating wizard end up
with this error
-----------------------------------------------------------------------------------------------------------------------------

IWAB0639E Error in generating Java files and deployment descritpors from
WSDL file

WSWS3574E:
GENERATION OF ARTIFACTS HAS BEEN SUSPENDED.

See messages to follow for more details.

WSWS3549E: Error: WSDL2Java could not discover a suitable StubWriter for
null.

Error: FATAL ERRORS encountered by WSDL2Java tool.

java.io.IOException: FATAL ERRORS encountered by WSDL2Java tool.

at com.ibm.ws.webservices.wsdl.Parser.generate(Unknown Source)

at com.ibm.ws.webservices.wsdl.Pa.....
--------------------------------------------------------------------------------------------------------------------------------


Bad Luck !!!



Scenario 2:



Using same WSDL file, I created a Top-down web service & this time set the

Web Service runtime = Apache Axis

Wrote the logic & Deployed it on WAS 6.0



Create a Client for above service (runtime is Apache Axis), Wow!!
everything fine!!!!!!

But I need to create JAX-RPC web service !

What is the issue with JAX-RPC ?

Any Idea Please ..

Thanks
dhanuxp


This communication and any transmitted documents are intended to be confidential. If there is a problem with this transmission, please contact the sender. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.


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.