[ANN]Apache Axis2C 0.9 released
Hi All, We are proud to announce the release of Apache Axis2C version 0.90. You can download this release from http://ws.apache.org/axis2/c/download.cgi Key Features 1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 Messages. This has complete XML infoset support. 2. Support for One-Way Messaging (In-Only) and Request Response Messaging (In-Out) 3. Module Architecture, mechanism to extend the SOAP Processing Model 4. Content hierarchy 5. Directory based deployment model 6. Raw XML providers 7. WS-Addressing, both the submission (2004/08) and final (2005/08) versions 8. Transports supports: HTTP * Both simple axis server and Apache2 httpd module Experimental Features 1. WSDL Object Model support New * Dynamic invocation Other notes 1. Interoperability tested with Axis2/Java for XML in/out client and services 2. Addressing interoperability on client side Major changes since last release 1. Minimal memory leaks 2. Apache2 module working in Windows 3. More samples and tests 4. WSDL Object Model built based on the proposed WSDL 2.0 Component model. 5. Dynamic Invocation 6. Numerous bug fixes since last release What is stii to do 1. Module version support 2. Archive based deployment Model 3. Improved and user friendly Client API 4. Support for MTOM/ MIME/ SwA 5. Sessions scoping for Application, SOAP, Transport and Request levels 6. Service Groups 7. Different character encoding support 8. WSDL Code Generation Tool for Stub and skeletons (based on Java tool) 9. Security module 10. REST (REpresentational State Transfer) Support 11. Server side Web Service Policy support 12. Axis2 Web Application (Web App) We welcome your early feedback on this implementation. Thanks for your interest in Axis2C -- Apache Axis2C Team --
documentation in axis2?
One last question for axis2 and I got all the information I need ;-) Thank you all for the very important and interesting information you gave me the last weeks. Is the documentation tag supported in axis2? Axis was the only framework I knew which supported the metadata information to be generated into the resulting wsdl. Is there a way to specifiy the information (f.e. by adding documentation tags to the entries in service.xml)? thx a lot Dominik ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
[Axis2 0.95] NullpointerException invoking .NET webService
Hi,
I'm writting a dynamic webservice invoker with Axis2. I'm testing .NET
interroperability and Axis2 give me a nullpointerexception with a sample
.NET webservice parsing the response.
This is stack trace:
The 2 first lines show message is sent to the ..NET server and
invokation response is received (I'have tried this web service with
SOAPUI and I'heve same response than second line), so
NullpointerException is throw when Axis2 parse the response.
This web service works perfectly with a dynamic axis based client. I'd
prefered to base my implementation on Axis2 than Axis
An Idea ?
Thanks,
Arnaud
httpclient.wire.content - DEBUG - ?xml version='1.0'
encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:BodyGetDrawings
xmlns=http://lottoexchange.net/LottoDrawings;EndDate2006-11-05/EndDateStateAlaska/StateStartDate2005-11-05/StartDateGameTest/Game/GetDrawings/soapenv:Body/soapenv:Envelope
httpclient.wire.content - DEBUG - ?xml version=1.0
encoding=ISO-8859-1?SOAP-ENV:Envelope
SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:si=http://soapinterop.org/xsd;SOAP-ENV:BodyGetDrawingsResponsevalue
xsi:type=xsd:stringlt;Drawingsgt;lt;/Drawingsgt;/value/GetDrawingsResponse/SOAP-ENV:Body/SOAP-ENV:Envelope!--[\n]
httpclient.wire.content - DEBUG - soap_server: entering
parseRequest() on 00:49 2006-03-31[\n]
httpclient.wire.content - DEBUG - soap_server: method name:
GetDrawings[\n]
httpclient.wire.content - DEBUG - soap_server: method 'GetDrawings'
exists[\n]
httpclient.wire.content - DEBUG - soap_server: calling
parser-get_response()[\n]
httpclient.wire.content - DEBUG - soap_server: parser debug: [\n]
httpclient.wire.content - DEBUG - soap_parser: Entering
soap_parser()[\n]
httpclient.wire.content - DEBUG - soap_parser: found root struct
GetDrawings, pos 3[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value EndDate of value 2006-11-05[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value State of value Alaska[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value StartDate of value 2005-11-05[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value Game of value Test[\n]
httpclient.wire.content - DEBUG - soap_parser: inside buildVal() for
GetDrawings(pos 3) of type struct[\n]
httpclient.wire.content - DEBUG - soap_parser: parsed successfully,
found root struct: 3 of name GetDrawings[\n]
httpclient.wire.content - DEBUG - [\n]
httpclient.wire.content - DEBUG - soap_server: params var dump
array(4) {[\n]
httpclient.wire.content - DEBUG -[EndDate]=[\n]
httpclient.wire.content - DEBUG -string(10) 2006-11-05[\n]
httpclient.wire.content - DEBUG -[State]=[\n]
httpclient.wire.content - DEBUG -string(6) Alaska[\n]
httpclient.wire.content - DEBUG -[StartDate]=[\n]
httpclient.wire.content - DEBUG -string(10) 2005-11-05[\n]
httpclient.wire.content - DEBUG -[Game
org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:124)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:65)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:352)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:267)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:445)
Caused by: java.lang.NullPointerException
at
com.ctc.wstx.io.ReaderBootstrapper.verifyXmlEncoding(ReaderBootstrapper.java:213)
at
com.ctc.wstx.io.ReaderBootstrapper.bootstrapInput(ReaderBootstrapper.java:143)
at
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:503)
at
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:558)
at
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:578)
at
com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputFactory.java:284)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:115)
Encoding Style
Hi, I'have same problem, I'have compared Axis 1.3 and Axis2 0.95 soap request generation (dynamic invocation) Axis 1.3 (OK): soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;soapenv:Bodyns1:getAnagramWithLetters soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=xletters xsi:type=xsd:stringDEFAIRE/lettersnbLetters href=#id0//ns1:getAnagramWithLettersmultiRef id=id0 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=xsd:int xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;7/multiRef/soapenv:Body/soapenv:Envelope Axis2 (KO : org.apache.axis2.AxisFault: this is a soap-encoded endpoint) soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header /soapenv:BodygetAnagramWithLetters xmlns=http://www.webmethods.com/wsdl/AnagramImpl/;lettersDEFAIRE/lettersnbLetters7/nbLetters/getAnagramWithLetters/soapenv:Body/soapenv:Envelope Is it possible to use some Axis2 option to have encoding style attribute ? Arnaud Dharminder Singh Wed, 26 Feb 2003 12:26:41 -0800 Hi all, I have a question about the encoding style attribute. I'm using axis as a client to a glue server and I'm setting the encoding style attribute on both the rpc element aswell as the body element in the request soap message. It seems that glue expects the encoding style attribute to be on the envelope or body elements. If the encoding style attribute is not on this level glue throws a this is a soap encoded endpoint exception. I looked at the axis code specifically SOAPEnvelope.java and SOAPBody.java and I see that attributes on the body element are never serialized. Is this correct or am I doing something wrong? I appreciate any help. Thanks Dharminder Singh
Distinguish axis engine(s) in Tomcat
Hi, I'm new to Axis. I'll like to find out if i have 2 servlets (both extending AxisServlet) deployed under same webapp, will there be 2 separate engines or both of them sharing 1 Axis engine? Is there anyway of distinguishing them? Another question: If i have a subclass of AxisServlet in a webapp and AxisServlet in another webapp, it'll be 2 Axis Engine i suppose? Is there anyway of letting them share 1 engine across different webapp? The reason i asked is because I'm trying to get ActiveBPEL to work with WSRF (deployed in Tomcat). Thanks, Larry Tan -- The University of Stirling is a university established in Scotland by charter at Stirling, FK9 4LA. Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not disclose, copy or deliver this message to anyone and any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind.
Re: [Axis2 0.95] NullpointerException invoking .NET webService
Hmm..
Seems the woodstox parser caused an error due to some encoding issue!
Could be the ISO encoding (ISO-8859-1) !
On 3/31/06, Arnaud MERGEY [EMAIL PROTECTED] wrote:
Hi,
I'm writting a dynamic webservice invoker with Axis2. I'm testing .NET
interroperability and Axis2 give me a nullpointerexception with a sample
.NET webservice parsing the response.
This is stack trace:
The 2 first lines show message is sent to the ..NET server and
invokation response is received (I'have tried this web service with
SOAPUI and I'heve same response than second line), so
NullpointerException is throw when Axis2 parse the response.
This web service works perfectly with a dynamic axis based client. I'd
prefered to base my implementation on Axis2 than Axis
An Idea ?
Thanks,
Arnaud
httpclient.wire.content - DEBUG - ?xml version='1.0'
encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header
/soapenv:BodyGetDrawings
xmlns=http://lottoexchange.net/LottoDrawings;EndDate2006-11-05/EndDateStateAlaska/StateStartDate2005-11-05/StartDateGameTest/Game/GetDrawings/soapenv:Body/soapenv:Envelope
httpclient.wire.content - DEBUG - ?xml version=1.0
encoding=ISO-8859-1?SOAP-ENV:Envelope
SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:si=http://soapinterop.org/xsd;SOAP-ENV:BodyGetDrawingsResponsevalue
xsi:type=xsd:stringlt;Drawingsgt;lt;/Drawingsgt;/value/GetDrawingsResponse/SOAP-ENV:Body/SOAP-ENV:Envelope!--[\n]
httpclient.wire.content - DEBUG - soap_server: entering
parseRequest() on 00:49 2006-03-31[\n]
httpclient.wire.content - DEBUG - soap_server: method name:
GetDrawings[\n]
httpclient.wire.content - DEBUG - soap_server: method 'GetDrawings'
exists[\n]
httpclient.wire.content - DEBUG - soap_server: calling
parser-get_response()[\n]
httpclient.wire.content - DEBUG - soap_server: parser debug: [\n]
httpclient.wire.content - DEBUG - soap_parser: Entering
soap_parser()[\n]
httpclient.wire.content - DEBUG - soap_parser: found root struct
GetDrawings, pos 3[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value EndDate of value 2006-11-05[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value State of value Alaska[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value StartDate of value 2005-11-05[\n]
httpclient.wire.content - DEBUG - soap_parser: adding data for
scalar value Game of value Test[\n]
httpclient.wire.content - DEBUG - soap_parser: inside buildVal() for
GetDrawings(pos 3) of type struct[\n]
httpclient.wire.content - DEBUG - soap_parser: parsed successfully,
found root struct: 3 of name GetDrawings[\n]
httpclient.wire.content - DEBUG - [\n]
httpclient.wire.content - DEBUG - soap_server: params var dump
array(4) {[\n]
httpclient.wire.content - DEBUG -[EndDate]=[\n]
httpclient.wire.content - DEBUG -string(10) 2006-11-05[\n]
httpclient.wire.content - DEBUG -[State]=[\n]
httpclient.wire.content - DEBUG -string(6) Alaska[\n]
httpclient.wire.content - DEBUG -[StartDate]=[\n]
httpclient.wire.content - DEBUG -string(10) 2005-11-05[\n]
httpclient.wire.content - DEBUG -[Game
org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:124)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:65)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:352)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:267)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:445)
Caused by: java.lang.NullPointerException
at
com.ctc.wstx.io.ReaderBootstrapper.verifyXmlEncoding(ReaderBootstrapper.java:213)
at
com.ctc.wstx.io.ReaderBootstrapper.bootstrapInput(ReaderBootstrapper.java:143)
at
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:503)
at
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:558)
at
com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:578)
at
com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputFactory.java:284)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:115)
--
Ajith Ranabahu
Re: How to reproduce WSDL2Java okay+uncompilable code generated
Hi,Eclipse Web Tools Platform (WTP) comes with XSD and WSDL editors which are able to validate.For more information please visit http://www.eclipse.org/webtools/Regards,Ali Sadik KumlaliAnne Thomas Manes [EMAIL PROTECTED] wrote: There are other problems with this WSDL besides the wrong qnames in your message parts. (Note that they aren't unqualified because there is a default namespace (the wsdl namespace); but these elements are in the xsd1 namespace.) When using RPC style, your message parts must reference types, not elements. To fix the WSDL, either change the style to "document" (and remove the namespace attributes from the soap:body definitions) or change the message parts to reference types rather than elements. I disagree with you that wsdl2java should have a
built-in WSDL validator and should be able to catch all WSDL errors. As a best practice, you should validate your WSDL before running wsdl2java. Many WSDL editors provide WSDL validators. I'm not aware of an open source WSDL validator, though. (Perhaps someone would like to volunteer to build one?) I do think that wsdl2java should generate an error when it encounters an unresolvable reference, though. e.g.,"http://schemas.xmlsoap.org/wsdl/}echoStringParam is referenced but not defined"Anne On 3/30/06, Morten Mortensen [EMAIL PROTECTED] wrote: I can now directly provoke, what I said yesterday: WSDL2Java
runningsmoothly, but the generated coded in an uncompilable state!To reproduce, take the "Axis2SampleDocLit.wsdl" from the 0.95distribution, make the error like I did in my own WSDL by removing the qualification from the message-elements like this (see the attachedfile; slightly modified variant of the original sample):Change e.g. -message name="echoString"part element="xsd1:echoStringParam" name="a"/- remove "xsd1"/message- into -message name="echoString"part element="echoStringParam" name="a"/ - no "xsd1" /messageNow the WSDL2Java runs without any errors, but the compilation failssince the code shown in my original message below
is produced.I think, that there ought to be a negative test-case for WSDL2Java with this type of WSDL!It is very good, that given correct WSDL, then all is fine - but in reallife, we fiddle with WSDL for a long time, maybe do not get it right forthe first number of times and then it is important to have tools like WSDL2Java do some aggressive verification of the WSDL...Having to track down the cause of generated, uncompilable code is tootough.Developers - are you listening?Regards,Morten Sabroe Mortensen -Oprindelig meddelelse-Fra: Morten MortensenSendt: 29. marts 2006 17:38Til: axis-user@ws.apache.orgEmne: Mode "Document/literal" vs. "Document/literal wrapped" Hi allWith the 0.95 version, how come I can use WSDL2Java to generate*un-compilable* code?Apparently, when I write WSDL as "Document/literal wrapped",
thegenerated "XXXReceiverInOut" has bad "toOM()", "fromOM()" and "toEnvelope()" (for an example, see the below "toOM()"-implementation;the parameter does not have the right type!).Why does this happen? What to do?Regards,Morten Sabroe Mortensen --- ...privateorg.apache.ws.commons.om.OMElementtoOM(org.apache.ws.commons.om.OMElement param){if (param instanceoforg.apache.axis2.databinding.ADBBean ){org.apache.ws.commons.om.impl.builder.StAXOMBuilder builder = neworg.apache.ws.commons.om.impl.builder.StAXOMBuilder(org.apache.ws.commons.om.OMAbstractFactory.getOMFactory(),param.getPullParser(
org.apache.ws.commons.om.OMElement.MY_QNAME));org.apache.ws.commons.om.OMElementdocumentElement = builder.getDocumentElement();((org.apache.ws.commons.om.impl.OMNodeEx )documentElement).setParent(null); // remove the parent linkreturn
documentElement;}else{ //todo finish this onece the bean serializer has the necessary methodsreturn null;}} ...---
New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.
[Axis2] Correct location for third party lib(s)
What is the correct location for third party libraries within an Axis 2 service? Should these be packaged within the .aar file? I seem to remember reading this information somewhere in the documentation but was unable to find it today. If it does in fact exist could someone please point me in the correct direction? This e-mail and any files transmitted with it are intended solely for the use of the entity or individual(s) to whom they are addressed and not for reliance upon by unintended recipients. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail and any files transmitted are strictly prohibited. If you have received this e-mail in error please delete the entire email and immediately notify us by email to the sender or by telephone to the AOC main office number, (404) 656-5171. Thank you.
Which Axis for WebLogic 9.1?
Title: Which Axis for WebLogic 9.1? Hey, We are currently upgrading from WebLogic 8.1 to 9.1 and one of the things that stopped working is Axis 1.1. We are seeing the following NullPointerException in the Call class: java.lang.NullPointerException at org.apache.axis.client.Call.invoke(Call.java:1768) at com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReportClient.java:738) at com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient.java:255) ... Apparently this is linked to WebLogic prefering its own saaj classes. In fact when we prepend the saaj jar that comes with Axis 1.1 to the WebLogic classpath, things work out. However, that is unfortunately not an option for us. So what I was wondering is the following: - Has anyone figured out what's the best way to get Axis (preferably 1.1) to run with WebLogic 9.1? - Is there a version of Axis that works smoothly with WebLogic 9.1? - Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3? Thanks for your help! -hendrik
Re: Which Axis for WebLogic 9.1?
Maybe you have a similar problem compared to http://ws.apache.org/axis/java/install.html#WebLogic8.1 WebLogic 8.1 ships with webservices.jar that conflicts with Axis' saaj.jar and prevents Axis 1.2 from working right out of the box. This conflict exists because WebLogic uses an older definition of javax.xml.soap.* package from Java Web Services Developer Pack Version 1.0 http://java.sun.com/webservices/docs/1.0/api/javax/xml/soap, whereas Axis uses a newer revision from J2EE 1.4. Hendrik Schreiber wrote: Hey, We are currently upgrading from WebLogic 8.1 to 9.1 and one of the things that stopped working is Axis 1.1. We are seeing the following NullPointerException in the Call class: java.lang.NullPointerException at org.apache.axis.client.Call.invoke(Call.java:1768) at com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReportClient.java:738) at com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient.java:255) ... Apparently this is linked to WebLogic prefering its own saaj classes. In fact when we prepend the saaj jar that comes with Axis 1.1 to the WebLogic classpath, things work out. However, that is unfortunately not an option for us. So what I was wondering is the following: - Has anyone figured out what's the best way to get Axis (preferably 1.1) to run with WebLogic 9.1? - Is there a version of Axis that works smoothly with WebLogic 9.1? - Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3? Thanks for your help! -hendrik
RE: Which Axis for WebLogic 9.1?
Lars, Yeah - the problem is definitely similar, which is why I'd like to find 'matching' versions. I.e. which version of Axis does play well with WebLogic 9.1 - if there is one at all that does that. We compared filesizes etc and concluded that the webservices.jar that ships with 9.1 is a different one than the one shipping with 8.1. So the problem is similar, but not the same. -hendrik -Original Message- From: Lars Torunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 4:19 PM To: axis-user@ws.apache.org Subject: Re: Which Axis for WebLogic 9.1? Maybe you have a similar problem compared to http://ws.apache.org/axis/java/install.html#WebLogic8.1 WebLogic 8.1 ships with webservices.jar that conflicts with Axis' saaj.jar and prevents Axis 1.2 from working right out of the box. This conflict exists because WebLogic uses an older definition of javax.xml.soap.* package from Java Web Services Developer Pack Version 1.0 http://java.sun.com/webservices/docs/1.0/api/javax/xml/soap, whereas Axis uses a newer revision from J2EE 1.4. Hendrik Schreiber wrote: Hey, We are currently upgrading from WebLogic 8.1 to 9.1 and one of the things that stopped working is Axis 1.1. We are seeing the following NullPointerException in the Call class: java.lang.NullPointerException at org.apache.axis.client.Call.invoke(Call.java:1768) at com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReport Client.java:738) at com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient .java:255) ... Apparently this is linked to WebLogic prefering its own saaj classes. In fact when we prepend the saaj jar that comes with Axis 1.1 to the WebLogic classpath, things work out. However, that is unfortunately not an option for us. So what I was wondering is the following: - Has anyone figured out what's the best way to get Axis (preferably 1.1) to run with WebLogic 9.1? - Is there a version of Axis that works smoothly with WebLogic 9.1? - Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3? Thanks for your help! -hendrik
RE: Which Axis for WebLogic 9.1?
Supposedly WebLogic 9.0/9.1 fully support J2EE 1.4. -Original Message- From: Hendrik Schreiber [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 4:23 PM To: axis-user@ws.apache.org Cc: David Ingbretsen Subject: RE: Which Axis for WebLogic 9.1? Lars, Yeah - the problem is definitely similar, which is why I'd like to find 'matching' versions. I.e. which version of Axis does play well with WebLogic 9.1 - if there is one at all that does that. We compared filesizes etc and concluded that the webservices.jar that ships with 9.1 is a different one than the one shipping with 8.1. So the problem is similar, but not the same. -hendrik -Original Message- From: Lars Torunski [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 4:19 PM To: axis-user@ws.apache.org Subject: Re: Which Axis for WebLogic 9.1? Maybe you have a similar problem compared to http://ws.apache.org/axis/java/install.html#WebLogic8.1 WebLogic 8.1 ships with webservices.jar that conflicts with Axis' saaj.jar and prevents Axis 1.2 from working right out of the box. This conflict exists because WebLogic uses an older definition of javax.xml.soap.* package from Java Web Services Developer Pack Version 1.0 http://java.sun.com/webservices/docs/1.0/api/javax/xml/soap, whereas Axis uses a newer revision from J2EE 1.4. Hendrik Schreiber wrote: Hey, We are currently upgrading from WebLogic 8.1 to 9.1 and one of the things that stopped working is Axis 1.1. We are seeing the following NullPointerException in the Call class: java.lang.NullPointerException at org.apache.axis.client.Call.invoke(Call.java:1768) at com.dstm.mp.businessprocess.base.AdvReportClient.sendMessage(AdvReport Client.java:738) at com.dstm.mp.businessprocess.base.AdvReportClient.logon(AdvReportClient .java:255) ... Apparently this is linked to WebLogic prefering its own saaj classes. In fact when we prepend the saaj jar that comes with Axis 1.1 to the WebLogic classpath, things work out. However, that is unfortunately not an option for us. So what I was wondering is the following: - Has anyone figured out what's the best way to get Axis (preferably 1.1) to run with WebLogic 9.1? - Is there a version of Axis that works smoothly with WebLogic 9.1? - Which saaj version comes with Axis 1.1, 1.2, 1.2.1 and 1.3? Thanks for your help! -hendrik
choice problems for Axis 1.3
Hi, We're having problems with the choice tag using Axis 1.3. xsd:choice xsd:sequence xsd:element name=Value1 type=ns:Value1/ xsd:element name=Value2 type=ns:Value2 minOccurs=0/ /xsd:sequence xsd:element name=Value2 type=ns:Value2/ /xsd:choice Basically, we wanted to implmeent non-exclusive or. So either value 1 and value 2 are present, or one of either, but not neither. If we only set value2, then Axis complains about value 1 not being present. Has anyone ever seen something like this before? thanks, Jordan.
unable to get soap header in Axis2
Hi, I have custom wsdl with just an echo service which contain soap header as input for action but when I view my wsdl from browser it does not show up the soap header part?? Any help ??, let me if anything wrong in wsdl it self Thanks Gopal my wsdl file ?xml version=1.0 encoding=UTF-8? definitions name=keystone targetNamespace=http://org.apache.axis2/ xmlns:tns=http://org.apache.axis2/ xmlns:ns1=http://org.apache.axis2/xsd xmlns:xs=http://www.w3.org/2001/XMLSchema xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/ xmlns=http://schemas.xmlsoap.org/wsdl/ xmlns:plnk=http://schemas.xmlsoap.org/ws/2003/05/partner-link/ xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing types xs:schema attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://schemas.xmlsoap.org/wsdl/ xmlns=http://www.w3.org/2001/XMLSchema import namespace=http://schemas.xmlsoap.org/ws/2004/08/addressing schemaLocation=http://schemas.xmlsoap.org/ws/2004/08/addressing / /xs:schema xs:schema elementFormDefault=qualified xmlns=http://www.w3.org/2001/XMLSchema targetNamespace=http://org.apache.axis2/xsd xs:complexType name=echoAsyncRequest xs:sequence xs:element name=param1 type=xs:string/ /xs:sequence /xs:complexType xs:complexType name=echoAsyncResponse xs:sequence xs:element name=return type=xs:string/ /xs:sequence /xs:complexType xs:element name=EchoAsyncRequest type=ns1:echoAsyncRequest/ xs:element name=EchoAsyncResponse type=ns1:echoAsyncResponse/ /xs:schema /types message name=StartHeader part name=MessageID element=wsa:MessageID / part name=ReplyTo element=wsa:ReplyTo / /message message name=ContinueHeader part name=RelatesTo element=wsa:RelatesTo/ /message message name=echoAsyncRequestMessage part name=part1 element=ns1:EchoAsyncRequest/ /message message name=echoAsyncResponseMessage part name=part2 element=ns1:EchoAsyncResponse/ /message portType name=keystonePort operation name=echoAsync input message=tns:echoAsyncRequestMessage / /operation /portType portType name=keystonePortCallBack operation name=onResult input message=tns:echoAsyncResponseMessage / /operation /portType plnk:partnerLinkType name=keystone plnk:role name=keystoneServiceProvider plnk:portType name=tns:keystone/ /plnk:role plnk:role name=keystoneServiceRequester plnk:portType name=tns:keystoneCallBack/ /plnk:role /plnk:partnerLinkType binding name=keystoneBinding type=tns:keystonePort soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http / operation name=echoAsync soap:operation soapAction=echoAsync style=document/ input soap:body use=literal/ soap:header message=tns:StartHeader part=MessageID use=literal/ soap:header message=tns:StartHeader part=ReplyTo use=literal/ /input /operation /binding binding name=keystoneCallBackBinding type=tns:keystonePortCallBack soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http / operation name=onResult soap:operation soapAction=onResult style=document/ input soap:body use=literal/ soap:header message=tns:ContinueHeader part=RelatesTo use=literal/ /input /operation /binding service name=keystone port name=keystonePort0 binding=tns:keystoneBinding soap:address location=http://localhost:8080/axis2/services/keystone/ /port /service service name=keystoneCallBack port name=keystonePort0CallBack binding=tns:keystoneCallBackBinding soap:address location=http://set.by.caller/ /port /service /definitions
[Axis2] [AXIOM] Whre is the SVN?
The Source Code link on http://ws.apache.org/commons/axiom/index.html does not work :-( How can I get the latest svn co? Thanks, Samisa...
Re: [Axis2] Correct location for third party lib(s)
yes , with third party lib can locate inside .Saar file and with them that will be like as follows few.Saar MATA-INF services.ml Borg apache . lib my lib1.jar my lib2.jar (http://www.developer.com/open/article.php/3557741) Michael Robinson wrote: What is the correct location for third party libraries within an Axis 2 service? Should these be packaged within the .aar file? I seem to remember reading this information somewhere in the documentation but was unable to find it today. If it does in fact exist could someone please point me in the correct direction? * This e-mail and any files transmitted with it are intended solely for the use of the entity or individual(s) to whom they are addressed and not for reliance upon by unintended recipients. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail and any files transmitted are strictly prohibited. If you have received this e-mail in error please delete the entire email and immediately notify us by email to the sender or by telephone to the AOC main office number, (404) 656-5171. Thank you. * -- Thanks, Deepal ~Future is Open~
