Re: WSA Action = null for endpoint...
If you have a SOAP-based endpoint (i.e., either SOAP 1.1 or 1.2 binding) then you just can't invoke the service using your browser. The service expects a well-formed SOAP input, while your browser only sends a simple HTTP GET request. If you have deployed your service using Axis2 and the standard configuration then you should automatically have a REST endpoint (besides the two SOAP endpoints mentioned before). Unlike the SOAP ones you should be able to invoke this service using your browser (at least if it is simple enough and does not require input). /philipp silver17 schrieb: Hi guys, I'm relatively newb to the world of web services and i've come accross something else. I built a web service and put it in it's own war file, and it works, sort of. When I use my java client to hit the endpoint (eg: http://server/path/services/publish) it works great, but when i load my browser with that same URL I get an error indicating there is no Endpoint because WSA Action is null, can someone explain this to me? Here is my wsdl. ?xml version=1.0 encoding=UTF-8? wsdl:definitions name=RegistryPublish targetNamespace=http://services.registry.agr.gc.ca/publish/; xmlns:tns=http://services.registry.agr.gc.ca/publish/; xmlns:axis2=http://services.registry.agr.gc.ca/publish/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:ows=http://www.opengis.net/ows/1.1; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; xmlns:csw=http://www.opengis.net/cat/csw/2.0.2; wsdl:documentation WSDL Description for the Registry Publishing Service. /wsdl:documentation wsdl:types xsd:schema xsd:import namespace=http://www.opengis.net/cat/csw/2.0.2; schemaLocation=csw-Publication.xsd/ xsd:import namespace=http://www.opengis.net/ows/1.1; schemaLocation=owsExceptionReport.xsd/ /xsd:schema /wsdl:types wsdl:message name=msgTransactionFailedFault wsdl:part name=fault element=ows:ExceptionReport /wsdl:part /wsdl:message wsdl:message name=msgTransaction wsdl:part name=part1 element=csw:Transaction /wsdl:part /wsdl:message wsdl:message name=msgTransactionResponse wsdl:part name=part1 element=csw:TransactionResponse /wsdl:part /wsdl:message wsdl:message name=msgInvalidRequestFault wsdl:part name=fault element=ows:ExceptionReport /wsdl:part /wsdl:message wsdl:portType name=RegistryPublish_portType wsdl:operation name=Transaction wsdl:input message=tns:msgTransaction /wsdl:input wsdl:output message=tns:msgTransactionResponse /wsdl:output wsdl:fault name=InvalidRequestFault message=tns:msgInvalidRequestFault /wsdl:fault wsdl:fault name=TransactionFailedFault message=tns:msgTransactionFailedFault /wsdl:fault /wsdl:operation /wsdl:portType wsdl:binding name=RegistryPublishSOAP11_binding type=tns:RegistryPublish_portType soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ wsdl:operation name=Transaction soap:operation soapAction=urn:Transaction style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output wsdl:fault name=InvalidRequestFault soap:fault name=InvalidRequestFault use=literal/ /wsdl:fault wsdl:fault name=TransactionFailedFault soap:fault name=TransactionFailedFault use=literal/ /wsdl:fault /wsdl:operation /wsdl:binding wsdl:service name=RegistryPublish wsdl:port name=RegistryPublishSOAP11port_http binding=tns:RegistryPublishSOAP11_binding soap:address location=http://localhost:8080/RegistryPublishServiceHibernate/services/RegistryPublish/ /wsdl:port /wsdl:service /wsdl:definitions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] No xsi:type in the response elements
can you please try with a nighly build. Now axis2 directly use the xmlbeans serialization. thanks, Amila. On Jan 9, 2008 1:16 PM, Gaurav Lall [EMAIL PROTECTED] wrote: Hi all , We are doing migration to axis2 from axis1, we are using xmlnbeans as data binding. mechanism.I am using axis 2 version 1.3 We are observing difference in the responses 1. there is no xsi:type coming out for the response 2. Also the namespaces are coming for each element in axis 2 response ? I would idealy like to use the prefixes to reduce the size of the payload 3. Is there a configuration parameter which controls the emission of xsi:type Any direction or pointers would be of great help ? ---AXIS 1 off:productCategory off:controlTypemultiSelect/off:controlType off:categoryType xsi:type=*xs:string* alaCarteResidential.alaCarteResidential/off:categoryType off:categoryNameODUSelection.ODUSelection/off:categoryName ent:description xsi:type=*xs:string*ODU Selection/ent:description Axis2 productCategory xmlns= http://ei.com/schemas/wsdl/orderServices/v3_0/offer;http://ei.com/schemas/wsdl/orderServices/v3_0/offer controlType xmlns=http://ei.com/schemas/wsdl/orderServices/v3_0/offer;http://ei.com/schemas/wsdl/orderServices/v3_0/offermultiSelect/controlType categoryType xmlns= http://ei.com/schemas/wsdl/orderServices/v3_0/offer;http://ei.com/schemas/wsdl/orderServices/v3_0/offer alaCarteResidential.alaCarteResidential/categoryType categoryName xmlns= http://ei.com/schemas/wsdl/orderServices/v3_0/offer;http://ei.com/schemas/wsdl/orderServices/v3_0/offer ODUSelection.ODUSelectionl/categoryName description xmlns=http://ei.com/schemas/entities/v3_1;http://ei.com/schemas/entities/v3_1A La Carte Programming/description Thanks for the help Gaurav -- Amila Suriarachchi, WSO2 Inc.
Re: Error while invoking the axis service through PHP NUSoap
Hi.
I see this in stack trace:
org.apache.axis2.AxisFault: Please implement
org.presci.echo.service.EchoServiceSkeleton#echo_operation
This seems axis default empty skeleton message. Did you generate the service
aar with the correct code, perhaps you generated the aar with an old code...
Bye.
Antonio.
2008/1/10, prasad c iyer [EMAIL PROTECTED]:
Got it I messed up the Ant file so the generated code was always
overwriting
the implemented class.
Thanks for the help
- Original Message -
From: prasad c iyer [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Wednesday, January 09, 2008 3:44 PM
Subject: Re: Error while invoking the axis service through PHP NUSoap
Following are my wsdl file, php file and soap request
wsdl file
?xml version=1.0 encoding=UTF-8?
definitions xmlns:tns=
http://localhost:8080/my-app/services/EchoService;
xmlns=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:ns1=http://localhost:8080/my-app/services/EchoService/types;
name=EchoService
targetNamespace=http://localhost:8080/my-app/services/EchoService;
types
xsd:schema
targetNamespace=http://localhost:8080/my-app/services/EchoService/types
xsd:element name=request_element type=xsd:string/
xsd:element name=response_element type=xsd:string/
/xsd:schema
xsd:schema
targetNamespace=
http://localhost:8080/my-app/services/EchoService/types:0;
xsd:element name=request_element type=xsd:string/
xsd:element name=response_element type=xsd:string/
/xsd:schema
/types
message name=echo_request
part name=parameters element=ns1:request_element/
/message
message name=echo_response
part name=result element=ns1:response_element/
/message
portType name=echo_portType
operation name=echo_operation
input name=echo_request message=tns:echo_request/
output name=echo_response message=tns:echo_response/
/operation
/portType
binding name=echo_binding type=tns:echo_portType
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
operation name=echo_operation
soap:operation soapAction=echo_operation/
input name=echo_request
soap:body use=literal/
/input
output name=echo_response
soap:body use=literal/
/output
/operation
/binding
service name=EchoService
port name=EchoPort binding=tns:echo_binding
soap:address
location=http://localhost:8080/my-app/services/EchoService/
/port
/service
/definitions
--
php code:
?php
/**
* echo php
*
*
*/
require_once('nusoap.php');
$client=new
nusoap_client('http://localhost:8080/my-app/services/EchoService?wsdl',
'wsdl');
$err=$client-getError();
if($err){
echo 'constructor error : '. $err ;
die;
}
$proxy=$client-getProxy();
$err=$client-getError();
if($err){
echo 'got error : '.$err;
}
$client-loadWSDL();
$err=$client-getError();
if($err){
echo 'got error : '.$err;
}
echo 'WSDLnamespace'.$client-wsdl-namespaces;
foreach($client-wsdl-namespaces as $key=$value){
echo $key. ' ' . $value . 'br/';
}
$param['parameters']=array('hello world');
$client-call('echo_operation', $param);
echo 'h2Request/h2pre' . htmlspecialchars($client-request,
ENT_QUOTES) . '/pre';
echo 'h2Response/h2pre' . htmlspecialchars($client-response,
ENT_QUOTES) . '/pre';
echo 'h2Debug/h2pre' . htmlspecialchars($client-debug_str,
ENT_QUOTES) . '/pre';
?
--
request message
?xml version=1.0 encoding=ISO-8859-1?
SOAP-ENV:Envelope
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:ns4861=http://tempuri.org;
SOAP-ENV:Body
m:request_element
xmlns:m=http://localhost:8080/my-app/services/EchoService/types;hello
world/m:request_element
/SOAP-ENV:Body
/SOAP-ENV:Envelope
- Original Message -
From: Martin Gainty
To: axis-user@ws.apache.org
Sent: Wednesday, January 09, 2008 3:30 PM
Subject: RE: Error while invoking the axis service through PHP NUSoap
Please display php client code and service wsdl
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission.
Wrom:
RE: [axis2] empty xmlns
Hello, Thanks for you reply. I already have an elementFormDefault=qualified defined at the beginning of my xsd file. But it still doesn't work. Should this attribute be put somewhere else in my xsd file ? Thx Date: Wed, 9 Jan 2008 12:13:22 -0500 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: [axis2] empty xmlns According to your schema, the compteAncre element must be unqualified, therefore the generated response is correct. If you want the compteAncre element to be qualified, then add this attribute to the http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0 schema: elementFormDefault=qualified Anne On Jan 7, 2008 3:45 AM, Henry Duc de Cagade de Branlou [EMAIL PROTECTED] wrote:Hi,I have created an axis2 web service (release 1.2). I used the top bottom approach with xmlbeans (used the axis2 generator tool). The problem I have is that I have an empty xmlns tag (related to compteAncre tag) in my soap web service response : ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body findByResponse xmlns=http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0; compteAncre xmlns= CodeOrganisme xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;390/CodeOrganisme CodeExoneration xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/ OrigineExoneration xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/ NumeroInterneCompte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;60767/NumeroInterneCompte NumeroExterneCompte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3940109656/NumeroExterneCompte Categorie xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;1/Categorie SousCategorie xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/ EtatCpte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3/EtatCpte NoPersonne xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;9514/NoPersonne DateEtatCpte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;2000-01-15+01:00/DateEtatCpte I don't understand why. Attached are my wsdl, xsd files and soap response. I also tried release 1.3 of axis2 but it didn't help. Help will be greatly appreciated. Thank you in advance. Express yourself instantly with MSN Messenger! MSN Messenger Express yourself instantly with MSN Messenger! MSN Messenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: [axis2] empty xmlns
Hello, is the operation you are invoking RPC? Greetings, Angel Henry Duc de Cagade de Branlou wrote: Hello, Thanks for you reply. I already have an elementFormDefault=qualified defined at the beginning of my xsd file. But it still doesn't work. Should this attribute be put somewhere else in my xsd file ? Thx Date: Wed, 9 Jan 2008 12:13:22 -0500 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: [axis2] empty xmlns According to your schema, the compteAncre element must be unqualified, therefore the generated response is correct. If you want the compteAncre element to be qualified, then add this attribute to the http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0 schema: elementFormDefault=qualified Anne On Jan 7, 2008 3:45 AM, Henry Duc de Cagade de Branlou [EMAIL PROTECTED] wrote: Hi, I have created an axis2 web service (release 1.2). I used the top bottom approach with xmlbeans (used the axis2 generator tool). The problem I have is that I have an empty xmlns tag (related to compteAncre tag) in my soap web service response : ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body findByResponse xmlns=http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0; compteAncre xmlns= CodeOrganisme xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;390/CodeOrganisme CodeExoneration xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/ OrigineExoneration xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/ NumeroInterneCompte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;60767/NumeroInterneCompte NumeroExterneCompte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3940109656/NumeroExterneCompte Categorie xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;1/Categorie SousCategorie xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/ EtatCpte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3/EtatCpte NoPersonne xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;9514/NoPersonne DateEtatCpte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;2000-01-15+01:00/DateEtatCpte I don't understand why. Attached are my wsdl, xsd files and soap response. I also tried release 1.3 of axis2 but it didn't help. Help will be greatly appreciated. Thank you in advance. Express yourself instantly with MSN Messenger! MSN Messenger Express yourself instantly with MSN Messenger! MSN Messenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Express yourself instantly with MSN Messenger! MSN Messenger http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/ No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.17.13/1212 - Release Date: 1/6/2008 10:55 PM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Example code for WS-SecureConversation implementation using Rampart in Axis2
Hi Bhushan, Rampart distribution has a sample which demonstrate the secure conversation usage. It has a complete service and client implementation which you can run using a ant script. Source can be found here [1] . And please post any questions you have in the Rampart mailing list [2]. Thanks, Nandana [1] - https://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/policy/sample04/ [2] - [EMAIL PROTECTED] ( to subscribe : [EMAIL PROTECTED]) On Jan 9, 2008 10:17 PM, Bhushan Gupte [EMAIL PROTECTED] wrote: Hi, I am looking for documentation and examples related to WS-SecureConversationhttp://specs.xmlsoap.org/ws/2005/02/sc/WS-SecureConversation.pdfusage in our project. I am using axis2 with rampart module(for Ws-Security and WS-SecureConversation). I was able to implement WS-Security using Rampart module but am not finding examples to use WS-SecureConversation. Can you please direct me or provide me the information with some examples. I have already looked at these documents but still not getting good examples to use Rampart and Rahas(for WS-Trust) : http://specs.xmlsoap.org/ws/2005/02/sc/WS-SecureConversation.pdf http://wso2.org/search/node/WS-SecureConversation http://schemas.xmlsoap.org/ws/2005/02/sc/ http://msdn2.microsoft.com/en-us/library/ms996521.aspx Thanks
[Axis2] NPE in HttpCoreNIOSender
Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError (HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed (HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed (SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSessi onRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute (DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEngine (HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000 (HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run (HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to remove mustUnderstand attribute?!
What a hell is mustUnderstand attribute?! I'm creating client to 3d party server and after migrating from axis1.4 to axis2 I found this strange attrib added to the header elements of my SOAP request. How to get rid of it? -- View this message in context: http://www.nabble.com/How-to-remove-mustUnderstand-attribute-%21-tp14731994p14731994.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 Writing Custom Phase Handlers
Hi, I am using IBM Websphere Application Server and Web Service Feature Pack version 6.1. I want to write a custom handler which I have to inject it in Axis2 Soap Engine Phases. I could get some material but they were not helpful enough since i don't want to use the module approach, i just need to write a plain handler. It would be very helpful if i can get some pointers and concrete information on how to achieve this with respect to websphere. Thanks in advance for your help. Deepak. - Now you can chat without downloading messenger. Click here to know how.
Re: [Axis2] NPE in HttpCoreNIOSender
Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError(HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed(HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed(SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute(DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEngine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000(HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run(HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Writing Custom Phase Handlers
Deepak, if you can get a reference to the configuration context you can do something like this: AxisService service = Utils.createSimpleService(new QName(EchoXml), new RawXMLINOutMessageReceiver(), EchoXML.class.getName(), new QName(echo)); service.setScope(Constants.SCOPE_REQUEST); // service.setEnableAllTransports(true); final AxisConfiguration axisConfiguration = this.configurationContext .getAxisConfiguration(); axisConfiguration.addService(service); HandlerDescription description = new HandlerDescription(MyHandler); description.setHandler(new MyHandler()); ArrayListPhase phasesList = axisConfiguration.getOutFlowPhases(); Phase myPhase = new Phase(MyPhase); myPhase.addHandler(description); phasesList.add(0, myPhase); axisConfiguration.setOutFaultPhases(phasesList); HTH, Michele On 10 Jan 2008, at 12:53, Deepak Vishwakarma wrote: Hi, I am using IBM Websphere Application Server and Web Service Feature Pack version 6.1. I want to write a custom handler which I have to inject it in Axis2 Soap Engine Phases. I could get some material but they were not helpful enough since i don't want to use the module approach, i just need to write a plain handler. It would be very helpful if i can get some pointers and concrete information on how to achieve this with respect to websphere. Thanks in advance for your help. Deepak. Now you can chat without downloading messenger. Click here to know how. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] NPE in HttpCoreNIOSender
Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError (HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed (HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed (SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSe ssionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute (DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEngin e(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000 (HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run (HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Writing Custom Phase Handlers
You can use org.apache.axis2.dispatchers.AddressingBasedDispatcher.java as a model then in axis2.xml configure the handler as in handler name=AddressingBasedDispatcher class=org.apache.axis2.dispatchers.AddressingBasedDispatcher/ where the handler is configured into the engine as a Phase as in this example phase name=Dispatch class=org.apache.axis2.engine.DispatchPhase which is then configured in phaseOrder of InFault,OutFault,InFaultFlow or OutFaultFlow HTH/ M-- - Original Message - From: Deepak Vishwakarma To: [EMAIL PROTECTED] ; axis-user@ws.apache.org Sent: Thursday, January 10, 2008 7:53 AM Subject: Axis2 Writing Custom Phase Handlers Hi, I am using IBM Websphere Application Server and Web Service Feature Pack version 6.1. I want to write a custom handler which I have to inject it in Axis2 Soap Engine Phases. I could get some material but they were not helpful enough since i don't want to use the module approach, i just need to write a plain handler. It would be very helpful if i can get some pointers and concrete information on how to achieve this with respect to websphere. Thanks in advance for your help. Deepak. -- Now you can chat without downloading messenger. Click here to know how.
Re: [Axis2] No xsi:type in the response elements
Hi Amila Thanks will try with nightly build and let you know. Just want to check with you not sure how the nightly works should i be taking the build which is out there with modified date 10-Jan-2008 11:50 (http://people.apache.org/dist/axis2/nightly/) or do i need to wait for the build to happen Thanks Gaurav Amila Suriarachchi wrote: can you please try with a nighly build. Now axis2 directly use the xmlbeans serialization. thanks, Amila. On Jan 9, 2008 1:16 PM, Gaurav Lall [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all , We are doing migration to axis2 from axis1, we are using xmlnbeans as data binding. mechanism.I am using axis 2 version 1.3 We are observing difference in the responses 1. there is no xsi:type coming out for the response 2. Also the namespaces are coming for each element in axis 2 response ? I would idealy like to use the prefixes to reduce the size of the payload 3. Is there a configuration parameter which controls the emission of xsi:type Any direction or pointers would be of great help ? ---AXIS 1 off:productCategory off:controlTypemultiSelect/off:controlType off:categoryType xsi:type=*xs:string*alaCarteResidential.alaCarteResidential/off:categoryType off:categoryNameODUSelection.ODUSelection/off:categoryName ent:description xsi:type=*xs:string*ODU Selection/ent:description Axis2 productCategory xmlns=http://ei.com/schemas/wsdl/orderServices/v3_0/offer; http://ei.com/schemas/wsdl/orderServices/v3_0/offer controlType xmlns=http://ei.com/schemas/wsdl/orderServices/v3_0/offer; http://ei.com/schemas/wsdl/orderServices/v3_0/offermultiSelect/controlType categoryType xmlns=http://ei.com/schemas/wsdl/orderServices/v3_0/offer; http://ei.com/schemas/wsdl/orderServices/v3_0/offeralaCarteResidential.alaCarteResidential/categoryType categoryName xmlns=http://ei.com/schemas/wsdl/orderServices/v3_0/offer; http://ei.com/schemas/wsdl/orderServices/v3_0/offerODUSelection.ODUSelectionl/categoryName description xmlns=http://ei.com/schemas/entities/v3_1; http://ei.com/schemas/entities/v3_1A La Carte Programming/description Thanks for the help Gaurav -- Amila Suriarachchi, WSO2 Inc.
Re: How to remove mustUnderstand attribute?!
re-submit your inquiry using the king's english Regards - Original Message - From: westpine [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Thursday, January 10, 2008 7:54 AM Subject: How to remove mustUnderstand attribute?! What a hell is mustUnderstand attribute?! I'm creating client to 3d party server and after migrating from axis1.4 to axis2 I found this strange attrib added to the header elements of my SOAP request. How to get rid of it? -- View this message in context: http://www.nabble.com/How-to-remove-mustUnderstand-attribute-%21-tp14731994p 14731994.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] NPE in HttpCoreNIOSender
Michele You might want to check the latest Synapse code from the QA 1.1.1 build. I know that Asankha usually prototypes his improvements in Synapse first and then ports them over to Axis2. Paul On Jan 10, 2008 1:57 PM, Michele Mazzucco [EMAIL PROTECTED] wrote: Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError (HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed (HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed (SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSe ssionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute (DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEngin e(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000 (HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run (HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] RuntimeException when using SOAPMonitor
Hi Axis2 users, i have implemented a very simple Axis2 webservice (request-response), which works correct as long as i don't use SOAPMonitor. When I integrate SOAPMonitor into my Axis2 web-application, i get the following RuntimeException (mapped to an axis2fault) at the webservice response: java.lang.RuntimeException: Element namespace from data source is http://my.company.com, not the expected I assume i configured SOAPMonitor correct. I can use the SOAPMonitor applet, it shows the correct request message and the above-named fault-message. SOAPMonitor also works fine for me with one-way webservices. So why do i get an error at the response when using SOAPMonitor? Has anyone an idea or a similar problem? Version: Axis2-1.3 SOAPMonitor applet classes taken from Axis2-1.3/lib/soapmonitor-1.3.jar The RuntimeException stacktrace is attached. Thanks in advance, Andi Stacktrace (part of): java.lang.RuntimeException: Element namespace from data source is http://my.company.com, not the expected at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(OMSourcedElementImpl.java:184) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:568) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:210) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) at org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) at org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:913) at org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(SOAPMonitorHandler.java:101) at org.apache.axis2.engine.Phase.invoke(Phase.java:292) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:45) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL XSD Schema Importing...
To answer your first question, yes it was a typo. I can also validate the wsdl and xsd's fine in eclipse, and when i set up the web service I can hit it and return a response using SOAPUI. Mauro Molinari wrote: silver17 ha scritto: http://localhost:8080/app/services'.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd xsd:import namespace=http://www.opengis.net/cat/csw/2.0.2; schemaLocation=RegistryPublish?xsd=csw-Publication.xsd/ http://www.nabble.com/file/p14722764/csw-Publication.xsd csw-Publication.xsd Is the first a copy 'n' paste problem or does Axis2 really says it can't find http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd? Because your file name seems to start with csw-, not cs-... Anyway, I can make Axis2 1.3 work with schema imports, except when trying to do some more complex things like sharing a schema between multiple services (please see https://issues.apache.org/jira/browse/AXIS2-3354). Does Eclipse give you any validation error on your WSDL and/or XSDs? (try right-click = Validate)? -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14734904.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis2] empty xmlns
Hi,
No, the operation is Document/Literal...
Why?
Date: Thu, 10 Jan 2008 11:13:58 +0200 From: [EMAIL PROTECTED] To:
axis-user@ws.apache.org Subject: Re: [axis2] empty xmlns Hello, is the
operation you are invoking RPC? Greetings, Angel Henry Duc de Cagade
de Branlou wrote: Hello,Thanks for you reply.I already
have an elementFormDefault=qualified defined at the beginning of my xsd
file.But it still doesn't work.Should this attribute be put
somewhere else in my xsd file ?Thx
Date: Wed, 9 Jan 2008 12:13:22 -0500 From: [EMAIL PROTECTED] To:
axis-user@ws.apache.org Subject: Re: [axis2] empty xmlns
According to your schema, the compteAncre element must be unqualified,
therefore the generated response is correct. If you want the compteAncre
element to be qualified, then add this attribute to the
http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0 schema:
elementFormDefault=qualified Anne On Jan 7, 2008 3:45
AM, Henry Duc de Cagade de Branlou [EMAIL PROTECTED] wrote:
Hi, I have created an axis2 web service
(release 1.2). I used the top bottomapproach with xmlbeans (used
the axis2 generator tool).The problem I have is that I have an empty
xmlns tag (related to compteAncretag) in my soap web service
response :?xml version=1.0 encoding=UTF-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:BodyfindByResponse
xmlns=http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0;
compteAncre xmlns=CodeOrganisme
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;390/CodeOrganisme
CodeExoneration
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;
xsi:nil=true/OrigineExoneration
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;
xsi:nil=true/NumeroInterneCompte
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;60767/NumeroInterneCompte
NumeroExterneCompte
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3940109656/NumeroExterneCompte
Categorie
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;1/Categorie
SousCategorie xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;
xsi:nil=true/EtatCpte
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3/EtatCpte
NoPersonne
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;9514/NoPersonne
DateEtatCpte
xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;2000-01-15+01:00/DateEtatCpte
I don't understand why. Attached are my wsdl, xsd files
and soap response.I also tried release 1.3 of axis2 but it didn't
help.Help will be greatly appreciated. Thank you in
advance. Express
yourself instantly with MSN Messenger! MSN Messenger
Express yourself instantly with MSN
Messenger! MSN Messenger
-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands,
e-mail: [EMAIL PROTECTED]
- To
unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
[EMAIL PROTECTED]
Express yourself instantly with MSN Messenger! MSN Messenger
http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/
No virus found in this incoming message. Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.13/1212 - Release Date: 1/6/2008
10:55 PM
- To
unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
[EMAIL PROTECTED]
_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: [Axis2] RuntimeException when using SOAPMonitor
What SOAP version (1.1 or 1.2) and databinding are you using? You seem
to missing a uri in your envelope. All the soap monitor does is
convert the soap envelope to a string, and this error seems to be deep
into axiom. Seems to be failing around this code:
http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMSourcedElementImpl.java?view=markup
String readerURI = readerFromDS.getNamespaceURI();
readerURI = (readerURI == null) ? : readerURI;
String uri = getNamespace().getNamespaceURI();
if (!readerURI.equals(uri)) {
log.error(forceExpand: expected element namespace +
getLocalName() + , found + uri);
throw new RuntimeException(Element namespace from
data source is +
readerURI + , not the expected + uri);
}
Post your envelope and maybe we can help. It also would help if you
post the logs that are printed on this line:
log.error(forceExpand: expected element namespace +
getLocalName() + , found + uri);
So you need a uri and it doesn't appear you have one for some reason.
You could try a nightly release or use TCPMon instead of the soapmonitor.
HTH,
Robert
On Jan 10, 2008 12:00 PM, [EMAIL PROTECTED] wrote:
Hi Axis2 users,
i have implemented a very simple Axis2 webservice (request-response), which
works correct as long as i don't use SOAPMonitor.
When I integrate SOAPMonitor into my Axis2 web-application, i get the
following RuntimeException (mapped to an axis2fault) at the webservice
response:
java.lang.RuntimeException: Element namespace from data source is
http://my.company.com, not the expected
I assume i configured SOAPMonitor correct. I can use the SOAPMonitor applet,
it shows the correct request message and the above-named fault-message.
SOAPMonitor also works fine for me with one-way webservices.
So why do i get an error at the response when using SOAPMonitor?
Has anyone an idea or a similar problem?
Version:
Axis2-1.3
SOAPMonitor applet classes taken from Axis2-1.3/lib/soapmonitor-1.3.jar
The RuntimeException stacktrace is attached.
Thanks in advance,
Andi
Stacktrace (part of):
java.lang.RuntimeException: Element namespace from data source is
http://my.company.com, not the expected
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(OMSourcedElementImpl.java:184)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:568)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:210)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:913)
at
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(SOAPMonitorHandler.java:101)
at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:45)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
--
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Complex type problem
I'm having the same problem also when I deserialize. The string field all contains the same value from the first attribute. Vasilis wrote: Anna, Thank you a lot for your help. I tried it and i get another error :-). The client can't deserialize correctly the response. I send a request with a RequestData object with this data (x = Hello, y=User , num = 10). In the client the object has these values: x=Hello y=Hello' num=10 I tried with 3 and four strings and i get the same results (All string variables get the value of the first String). In the monitor i can see that the request has the right values for each string var. Do you know why this is happening? Thank you, Roy Anne Thomas Manes [EMAIL PROTECTED] wrote: Roy, The problem is that the ns namespace declaration is not in scope for the parameter element. Change the parameter definition to this and see if it works: parameter qname=pns:reqData xmlns:pns= http://test.com/ejb/; type= pns:RequestData xmlns:tns=http://www.w3.org/2001/XMLSchema / Anne On 5/29/06, Roy [EMAIL PROTECTED] wrote: Dear Anne, I think that i have declared it here: beanMapping xmlns:ns= http://ejb.test.com/rd; qname=ns:RequestData languageSpecificType=java:com.test.ejb.rd.RequestData/ I tried to set my complex type only with a String ant an int var. It worked. I tried it with 2 Strings and both Strings take the same value (the value of the first string) when i call the service. In the Soap monitor i can see that both string are sent with different values. Have you ever any similar problems? Anne Thomas Manes [EMAIL PROTECTED] έγραψε: Roy, You have an error in your WSDD: parameter qname=pns:reqData xmlns:pns= http://test.com/ejb/; type=ns:RequestData xmlns:tns= http://www.w3.org/2001/XMLSchema / You have not declared the ns namespace. Anne On 5/26/06, Suyog Gandhi [EMAIL PROTECTED] wrote:Check out the issue AXIS2-770 , may be it is realted to this. I faced problems about serialization of complex types. 2nd level of nesting is not working. Once I re-structure wsdl for only 1 level of nesting, it started working. e.g following complex type does NOT work: ( Gives null for Name and Value for the attributes. ) WMemberInfo ---|- ID ---|- Attrbutes [] -|- Name -|- Value Following complex type works. WMemberInfo |- ID |- Attr1Name |- Attr1 Value |- Attr2 Name |- Attr2 Value But this is a crude workaround till the time problem is fixed. Hope this helps. Suyog -Original Message- From: robert lazarski [mailto: [EMAIL PROTECTED] Sent: Friday, May 26, 2006 9:36 AM To: axis-user@ws.apache.org Subject: Re: Complex type problem The other thing is make sure your vendor supports wsdl2java -jboss does not, for example (although they run a modified version of axis 1.2 internally). The problem I had was similair, although IIRC correctly I was getting ser / deser errors, not null. It was working on simple types but failing on complex ones. HTH, Robert http://www.braziloutsource.com/ On 5/26/06, Roy[EMAIL PROTECTED] wrote: I think that this is not exactly my problem. I can call normally the service from my client when i use simple types. When i try to pass complex types i face the problem. robert lazarski [EMAIL PROTECTED] έγραψε: You'retrying to use a non-ejb client to connect to a Web Service that implementsimplements SessionBean, is that correct? The only way I got that to work -using jboss - was something like... // remote ejb / webservice private CallCentreWebEndpointendpoint; String wsdl_loc = http://localhost:8080/CallCentreWebServiceJAR?wsdl;; // generated by JSWDP wscompile, which jboss insists onusing URL mappinglocation = ClassLoader.getSystemResource(CallCentreWeb_Mapping.xml); assertNotNull(mappinglocation); // bean mapping URL ws4eeMetaData = ClassLoader.getSystemResource(ws4ee-deploy.xml); assertNotNull(ws4eeMetaData); QName qname = new QName( http://localhost/callcentreweb;, CallCentreWebService); URL url = newURL(wsdl_loc); org.jboss.webservice.client.ServiceFactoryImpl factory= (org.jboss.webservice.client.ServiceFactoryImpl) ServiceFactoryImpl.newInstance(); javax.xml.rpc.Service service = factory.createService(url,mappinglocation, ws4eeMetaData, qname, null); endpoint =
Re: WSDL XSD Schema Importing...
As an addition to this discussion, if instead of trying to reference the http://localhost/app/services/RegistryPublish.wsdl i get the following error: http://www.nabble.com/file/p14736457/serviceError.jpg silver17 wrote: Hi Guys, I've searched a lot of these forum posts and haven't been able to find a resolution to my problem. Currently I am using Axis 2.1.3 and Eclipse Europa with the Apache Codegen wizard plugins. I created a WSDL that imports a couple of schemas and I'm having problems. When I attempt to use the wizards to generate the client stubs using a URL like: http://localhost:8080/app/services/RegistryPublish?wsdl I get the following error: An error occured while completing process - java.lang.InterruptedException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred while trying to resolve schema referenced at 'RegistryPublish?xsd=csw-Publication.xsd, relative to http://localhost:8080/app/services'.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd And I don't know why it's doing that. Here's a sample of that wsdl: wsdl:definitions name=RegistryPublish targetNamespace=http://services.registry.company.com/publish/; wsdl:documentation WSDL Description for the Registry Publishing Service. /wsdl:documentation wsdl:types xsd:schema xsd:import namespace=http://www.opengis.net/cat/csw/2.0.2; schemaLocation=RegistryPublish?xsd=csw-Publication.xsd/ xsd:import namespace=http://www.opengis.net/ows/1.1; schemaLocation=RegistryPublish?xsd=owsExceptionReport.xsd/ /xsd:schema /wsdl:types ... My web app directory structure is: app-web-inf-services-RegistryPublish-META-INF ... csw-Publication.xsd owsExceptionReport.xsd RegistryPublish.wsdl services.xml I tried using a program called SOAPUI to run a test request to that same url as above and it returned a successful result. Any thoughts? I've attached the files. http://www.nabble.com/file/p14722764/RegistryPublish.wsdl RegistryPublish.wsdl http://www.nabble.com/file/p14722764/services.xml services.xml http://www.nabble.com/file/p14722764/owsExceptionReport.xsd owsExceptionReport.xsd http://www.nabble.com/file/p14722764/csw-Publication.xsd csw-Publication.xsd -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14736457.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] NPE in HttpCoreNIOSender
Hi Mechele, This issue is indeed strictly related to connection timeouts. I remember that there were other issues with NPEs in HTTPCoreNIOSender. These were resolved in the meantime, but probably those corrections have not yet been propagated to Axis2. It would be interesting to know which variable is actually null in the handleError method. Do you think that you will be able to check this? Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError(HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed(HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed(SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute(DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEngine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000(HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run(HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Does wsdl2java delete toString method?
Hi, I'm trying to override the toString method in beans re-generated by wsdl2java and it seems to be deleting this code. Is it an expected behaviour or there is something wrong with my code? Thanks in advance for your help! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] RuntimeException when using SOAPMonitor
Hi Robert,
I'm using SOAP 1.1 and JAXB-RI data binding.
The correct soap envelope for the response should look like this:
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Bodyns1:RESPONSE
xmlns:ns1=http://my.company.com;../ns1:RESPONSE
/soapenv:Body/soapenv:Envelope
But i'm not 100% sure if it does because i can't monitor the correct response
due to the Exception.
The log statement before the Exception prints the following (RESPONSE is the
Element name in the Response Message):
[OMSourcedElementImpl] forceExpand: expected element namespace RESPONSE, found
The fact that the service works normal when SOAPMonitor is *NOT* used confuses
me a bit,
because the exception is thrown deep into axiom, as you mentioned.
Greets,
Andi
Original-Nachricht
Datum: Thu, 10 Jan 2008 12:33:48 -0200
Von: robert lazarski [EMAIL PROTECTED]
An: axis-user@ws.apache.org
Betreff: Re: [Axis2] RuntimeException when using SOAPMonitor
What SOAP version (1.1 or 1.2) and databinding are you using? You seem
to missing a uri in your envelope. All the soap monitor does is
convert the soap envelope to a string, and this error seems to be deep
into axiom. Seems to be failing around this code:
http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMSourcedElementImpl.java?view=markup
String readerURI = readerFromDS.getNamespaceURI();
readerURI = (readerURI == null) ? : readerURI;
String uri = getNamespace().getNamespaceURI();
if (!readerURI.equals(uri)) {
log.error(forceExpand: expected element namespace +
getLocalName() + , found + uri);
throw new RuntimeException(Element namespace from
data source is +
readerURI + , not the expected + uri);
}
Post your envelope and maybe we can help. It also would help if you
post the logs that are printed on this line:
log.error(forceExpand: expected element namespace +
getLocalName() + , found + uri);
So you need a uri and it doesn't appear you have one for some reason.
You could try a nightly release or use TCPMon instead of the soapmonitor.
HTH,
Robert
On Jan 10, 2008 12:00 PM, [EMAIL PROTECTED] wrote:
Hi Axis2 users,
i have implemented a very simple Axis2 webservice (request-response),
which works correct as long as i don't use SOAPMonitor.
When I integrate SOAPMonitor into my Axis2 web-application, i get the
following RuntimeException (mapped to an axis2fault) at the webservice
response:
java.lang.RuntimeException: Element namespace from data source is
http://my.company.com, not the expected
I assume i configured SOAPMonitor correct. I can use the SOAPMonitor
applet, it shows the correct request message and the above-named
fault-message. SOAPMonitor also works fine for me with one-way webservices.
So why do i get an error at the response when using SOAPMonitor?
Has anyone an idea or a similar problem?
Version:
Axis2-1.3
SOAPMonitor applet classes taken from Axis2-1.3/lib/soapmonitor-1.3.jar
The RuntimeException stacktrace is attached.
Thanks in advance,
Andi
Stacktrace (part of):
java.lang.RuntimeException: Element namespace from data source is
http://my.company.com, not the expected
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(OMSourcedElementImpl.java:184)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:568)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:210)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:913)
at
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(SOAPMonitorHandler.java:101)
at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
at
org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:45)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
Re: [Axis2] NPE in HttpCoreNIOSender
On 10 Jan 2008, at 14:59, Andreas Veithen wrote: It would be interesting to know which variable is actually null in the handleError method. Do you think that you will be able to check this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] NPE in HttpCoreNIOSender
Andreas, it must be a concurrency-related problem because I cannot reproduce it when I execute instructions step-by-step with the debugger. Michele On 10 Jan 2008, at 14:59, Andreas Veithen wrote: Hi Mechele, This issue is indeed strictly related to connection timeouts. I remember that there were other issues with NPEs in HTTPCoreNIOSender. These were resolved in the meantime, but probably those corrections have not yet been propagated to Axis2. It would be interesting to know which variable is actually null in the handleError method. Do you think that you will be able to check this? Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError (HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed (HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed (SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.process SessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute (DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEng ine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000 (HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run (HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis2] empty xmlns
Hi, By adding elementFormDefault=qualified into my wsdl file, I eventually get the empty namespace disappear (see compteAncre attribute) : ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body findByArrayResponse xmlns=http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0; compteAncre CodeOrganisme xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;980/CodeOrganisme I expected the namespace to be filled with value though... Do you think it is correct this way? Thx Date: Thu, 10 Jan 2008 08:09:54 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [axis2] empty xmlns You also need it in the inline schema in your WSDL file. Anne On Jan 10, 2008 4:04 AM, Henry Duc de Cagade de Branlou [EMAIL PROTECTED] wrote: Hello, Thanks for you reply. I already have an elementFormDefault=qualified defined at the beginning of my xsd file. But it still doesn't work. Should this attribute be put somewhere else in my xsd file ? Thx Date: Wed, 9 Jan 2008 12:13:22 -0500 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Subject: Re: [axis2] empty xmlns According to your schema, the compteAncre element must be unqualified, therefore the generated response is correct. If you want the compteAncre element to be qualified, then add this attribute to the http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0 schema: elementFormDefault=qualified Anne On Jan 7, 2008 3:45 AM, Henry Duc de Cagade de Branlou [EMAIL PROTECTED] wrote: Hi, I have created an axis2 web service (release 1.2). I used the top bottomapproach with xmlbeans (used the axis2 generator tool).The problem I have is that I have an empty xmlns tag (related to compteAncretag) in my soap web service response :?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:BodyfindByResponse xmlns=http://findby.wsdocument.dao.acces.ancre.acoss.fr/1.0; compteAncre xmlns=CodeOrganisme xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;390/CodeOrganisme CodeExoneration xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/OrigineExoneration xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/NumeroInterneCompte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;60767/NumeroInterneCompte NumeroExterneCompte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3940109656/NumeroExterneCompte Categorie xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;1/Categorie SousCategorie xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0; xsi:nil=true/EtatCpte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;3/EtatCpte NoPersonne xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;9514/NoPersonne DateEtatCpte xmlns=http://datamodel.wsdocument.dao.acces.ancre.acoss.fr/1.0;2000-01-15+01:00/DateEtatCpte I don't understand why. Attached are my wsdl, xsd files and soap response.I also tried release 1.3 of axis2 but it didn't help.Help will be greatly appreciated. Thank you in advance. Express yourself instantly with MSN Messenger! MSN Messenger Express yourself instantly with MSN Messenger! MSN Messenger - To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Express yourself instantly with MSN Messenger! MSN Messenger _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: [Axis2] NPE in HttpCoreNIOSender
Michele, Can you post the code at line 442 in HttpCoreNIOSender.java that triggers the error? Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, it must be a concurrency-related problem because I cannot reproduce it when I execute instructions step-by-step with the debugger. Michele On 10 Jan 2008, at 14:59, Andreas Veithen wrote: Hi Mechele, This issue is indeed strictly related to connection timeouts. I remember that there were other issues with NPEs in HTTPCoreNIOSender. These were resolved in the meantime, but probably those corrections have not yet been propagated to Axis2. It would be interesting to know which variable is actually null in the handleError method. Do you think that you will be able to check this? Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError(HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed(HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed(SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute(DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEngine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000(HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run(HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 JMS Transport to WebSphere MQ
Hi, We are currently using axis2 in a standalone server. I have been trying to configure axis2 to hook up with websphereMQ. However i am unsure of how to configure axis2 for this as all the examples i have found are for activeMQ. Could anyone tell me how this can be done? My main area of concern is the definition of a jms transportReciever for websphereMQ. Any advice would be much appriciated. My attempts so far have left me here, using the definition below. However this currently does not work. The first issue is that the initial context factory being used is based in websphere not websphereMQ. Secondly how do i configure this jndi resource in websphereMQ, i.e configure jms/QueueConnectionFactory transportReceiver name=jms class=org.apache.axis2.transport.jms.JMSListener parameter name=default parameter name=java.naming.factory.initialcom.ibm.mq.jms.context.WMQInitialContextFactory/parameter parameter name=java.naming.provider.urllocalhost:1414/parameter parameter name=transport.jms.ConnectionFactoryJNDINamejms/QueueConnectionFactory/parameter /parameter /transportReceiver Thanks, Cathal -- View this message in context: http://www.nabble.com/Axis2-JMS-Transport-to-WebSphere-MQ-tp14738492p14738492.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDL location
I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the message receiver class. Axis2 is auto generating the wsdl. Can I know where I can find the physical location of the file on my file system??
Re: Axis2 JMS Transport to WebSphere MQ
Hi, I don't have any specific suggestions, but I am aware that someone has worked on this before. I suggest searching the Axis2 user and dev archives for the following JIRA (which is the context in which is was discussed previously): https://issues.apache.org/jira/browse/AXIS2-2816 Cheers, David On Jan 10, 2008 4:45 PM, callagc4 [EMAIL PROTECTED] wrote: Hi, We are currently using axis2 in a standalone server. I have been trying to configure axis2 to hook up with websphereMQ. However i am unsure of how to configure axis2 for this as all the examples i have found are for activeMQ. Could anyone tell me how this can be done? My main area of concern is the definition of a jms transportReciever for websphereMQ. Any advice would be much appriciated. My attempts so far have left me here, using the definition below. However this currently does not work. The first issue is that the initial context factory being used is based in websphere not websphereMQ. Secondly how do i configure this jndi resource in websphereMQ, i.e configure jms/QueueConnectionFactory transportReceiver name=jms class=org.apache.axis2.transport.jms.JMSListener parameter name=default parameter name=java.naming.factory.initialcom.ibm.mq.jms.context.WMQInitialContextFactory/parameter parameter name=java.naming.provider.urllocalhost:1414/parameter parameter name=transport.jms.ConnectionFactoryJNDINamejms/QueueConnectionFactory/parameter /parameter /transportReceiver Thanks, Cathal -- View this message in context: http://www.nabble.com/Axis2-JMS-Transport-to-WebSphere-MQ-tp14738492p14738492.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 JMS Transport to WebSphere MQ
I have some previous advice on using MQ. In fact this was done with Synapse, but the advice might help: Websphere MQ 6 on Windows XP QM_upul = default queue manager MQ_HOME\bin\runmqsc.bat QM_upul (Enter commands in sub-shell.) define qlocal(Q1) end Using the file system based JNDI for this time. Changed MQ_HOME\Java\bin\JMSAdmin.config. INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory PROVIDER_URL=file:/C:/JNDI-Directory MQ_HOME\Java\bin\JMSAdmin.bat -cfg JMSAdmin.config (Enter commands in sub-shell.) def qcf(ConnectionFactory) qmgr(QM_upul) def q(StockQuoteProxy) qmgr(QM_upul) queue(Q1) end Added in Synapse axis2.xml transportReceiver name=jms class=org.apache.axis2.transport.jms.JMSListener parameter name=default parameter name=java.naming.factory.initialcom.sun.jndi.fscontext.RefFSContextFa ctory/parameter parameter name=java.naming.provider.urlfile:/C:/JNDI-Directory/parameter parameter name=transport.jms.ConnectionFactoryJNDINameConnectionFactory/parame ter /parameter /transportReceiver Copy from MQ_HOME\Java\lib to Synapse lib com.ibm.mq.jar com.ibm.mqjms.jar connector.jar dhbcore.jar fscontext.jar providerutil.jar Paul On Jan 10, 2008 4:45 PM, callagc4 [EMAIL PROTECTED] wrote: Hi, We are currently using axis2 in a standalone server. I have been trying to configure axis2 to hook up with websphereMQ. However i am unsure of how to configure axis2 for this as all the examples i have found are for activeMQ. Could anyone tell me how this can be done? My main area of concern is the definition of a jms transportReciever for websphereMQ. Any advice would be much appriciated. My attempts so far have left me here, using the definition below. However this currently does not work. The first issue is that the initial context factory being used is based in websphere not websphereMQ. Secondly how do i configure this jndi resource in websphereMQ, i.e configure jms/QueueConnectionFactory transportReceiver name=jms class=org.apache.axis2.transport.jms.JMSListener parameter name=default parameter name=java.naming.factory.initialcom.ibm.mq.jms.context.WMQInitialContextFactory/parameter parameter name=java.naming.provider.urllocalhost:1414/parameter parameter name=transport.jms.ConnectionFactoryJNDINamejms/QueueConnectionFactory/parameter /parameter /transportReceiver Thanks, Cathal -- View this message in context: http://www.nabble.com/Axis2-JMS-Transport-to-WebSphere-MQ-tp14738492p14738492.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL location
The WSDL is generated on-demand... it isn't stored. If you want to store it you can use a browser (Save As...) or wget to grab it. Paul On Jan 10, 2008 4:47 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote: I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the message receiver class. Axis2 is auto generating the wsdl. Can I know where I can find the physical location of the file on my file system?? -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL location
So is there no way I can change the wsdl file??I am unable to hit the service because it complains that WSA action is nullI have not specified the SOAP action in my clientIs there a way out??? Anjana Kandalam Private Client Group - AIG Work: 908-679-2608 Cell: 908-596-0424 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Thursday, January 10, 2008 11:57 AM To: axis-user@ws.apache.org Subject: Re: WSDL location The WSDL is generated on-demand... it isn't stored. If you want to store it you can use a browser (Save As...) or wget to grab it. Paul On Jan 10, 2008 4:47 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote: I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the message receiver class. Axis2 is auto generating the wsdl. Can I know where I can find the physical location of the file on my file system?? -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL location
Anjana I'm not clear changing the WSDL file is the right solution here, but you can do it. You save the WSDL, add it into the service archive, and then set a flag called useOriginalWSDL. However Does the WSDL define SOAPAction or wsa:action settings? And what client are you using. Basically the client should automatically pick those actions up from the WSDL and Axis2 sets actions into the WSDL. If Axis2 isn't setting actions into the WSDL then its probably easier to get it to do that: In the services.xml set operation name=doSmt actionMappinghttp://foo.org/myAction/actionMapping /operation If you want more info about the settings in services.xml (including useOriginalWSDL) see this article by deepal http://wso2.org/library/2060 Paul On Jan 10, 2008 5:11 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote: So is there no way I can change the wsdl file??I am unable to hit the service because it complains that WSA action is nullI have not specified the SOAP action in my clientIs there a way out??? Anjana Kandalam Private Client Group - AIG Work: 908-679-2608 Cell: 908-596-0424 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Thursday, January 10, 2008 11:57 AM To: axis-user@ws.apache.org Subject: Re: WSDL location The WSDL is generated on-demand... it isn't stored. If you want to store it you can use a browser (Save As...) or wget to grab it. Paul On Jan 10, 2008 4:47 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote: I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the message receiver class. Axis2 is auto generating the wsdl. Can I know where I can find the physical location of the file on my file system?? -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] NPE in HttpCoreNIOSender
mr.receive(nioFaultMessageContext); On 10 Jan 2008, at 16:45, Andreas Veithen wrote: Michele, Can you post the code at line 442 in HttpCoreNIOSender.java that triggers the error? Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, it must be a concurrency-related problem because I cannot reproduce it when I execute instructions step-by-step with the debugger. Michele On 10 Jan 2008, at 14:59, Andreas Veithen wrote: Hi Mechele, This issue is indeed strictly related to connection timeouts. I remember that there were other issues with NPEs in HTTPCoreNIOSender. These were resolved in the meantime, but probably those corrections have not yet been propagated to Axis2. It would be interesting to know which variable is actually null in the handleError method. Do you think that you will be able to check this? Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender $2.handleError(HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed (HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed (SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.proce ssSessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execu te(DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientE ngine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000 (HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run (HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Exception doesnt contain ObjectFactory.class or jaxb.index
Hello,
I have a service which is exposing some classes which are mapped to an
external xml file with jaxb2. I want to use jaxb2 for getting/writting values
to my xml but when I send data on http for webservice I want to use the axis2
adb binding. My method that is exposing xml with jaxb2 is working outside axis2.
But when I deploy this method as a web service and I call the web service I get
javax.xml.bind.JAXBException: burster.generated.jaxb2 doesnt contain
ObjectFactory.class or jaxb.index.
What is this exception? What is jaxb.index? I want to use ADB as binding over
the htpp.
Thank you,
Virgil
- Original Message
From: andreas netter [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Thursday, January 10, 2008 5:35:46 PM
Subject: Re: [Axis2] RuntimeException when using SOAPMonitor
Hi Robert,
I'm using SOAP 1.1 and JAXB-RI data binding.
The correct soap envelope for the response should look like this:
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Bodyns1:RESPONSE
xmlns:ns1=http://my.company.com;../ns1:RESPONSE
/soapenv:Body/soapenv:Envelope
But i'm not 100% sure if it does because i can't monitor the correct
response due to the Exception.
The log statement before the Exception prints the following (RESPONSE
is the Element name in the Response Message):
[OMSourcedElementImpl] forceExpand: expected element namespace
RESPONSE, found
The fact that the service works normal when SOAPMonitor is *NOT* used
confuses me a bit,
because the exception is thrown deep into axiom, as you mentioned.
Greets,
Andi
Original-Nachricht
Datum: Thu, 10 Jan 2008 12:33:48 -0200
Von: robert lazarski [EMAIL PROTECTED]
An: axis-user@ws.apache.org
Betreff: Re: [Axis2] RuntimeException when using SOAPMonitor
What SOAP version (1.1 or 1.2) and databinding are you using? You
seem
to missing a uri in your envelope. All the soap monitor does is
convert the soap envelope to a string, and this error seems to be
deep
into axiom. Seems to be failing around this code:
http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-impl/src/main/java/org/apache/axiom/om/impl/llom/OMSourcedElementImpl.java?view=markup
String readerURI = readerFromDS.getNamespaceURI();
readerURI = (readerURI == null) ? : readerURI;
String uri = getNamespace().getNamespaceURI();
if (!readerURI.equals(uri)) {
log.error(forceExpand: expected element namespace +
getLocalName() + , found + uri);
throw new RuntimeException(Element namespace from
data source is +
readerURI + , not the expected + uri);
}
Post your envelope and maybe we can help. It also would help if you
post the logs that are printed on this line:
log.error(forceExpand: expected element namespace +
getLocalName() + , found + uri);
So you need a uri and it doesn't appear you have one for some reason.
You could try a nightly release or use TCPMon instead of the
soapmonitor.
HTH,
Robert
On Jan 10, 2008 12:00 PM, [EMAIL PROTECTED] wrote:
Hi Axis2 users,
i have implemented a very simple Axis2 webservice
(request-response),
which works correct as long as i don't use SOAPMonitor.
When I integrate SOAPMonitor into my Axis2 web-application, i get
the
following RuntimeException (mapped to an axis2fault) at the
webservice
response:
java.lang.RuntimeException: Element namespace from data source is
http://my.company.com, not the expected
I assume i configured SOAPMonitor correct. I can use the
SOAPMonitor
applet, it shows the correct request message and the above-named
fault-message. SOAPMonitor also works fine for me with one-way
webservices.
So why do i get an error at the response when using SOAPMonitor?
Has anyone an idea or a similar problem?
Version:
Axis2-1.3
SOAPMonitor applet classes taken from
Axis2-1.3/lib/soapmonitor-1.3.jar
The RuntimeException stacktrace is attached.
Thanks in advance,
Andi
Stacktrace (part of):
java.lang.RuntimeException: Element namespace from data source is
http://my.company.com, not the expected
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(OMSourcedElementImpl.java:184)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:568)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:210)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at
Re: Exception doesnt contain ObjectFactory.class or jaxb.index
Virgil, Both the ObjectFactory class and the jaxb.index file are generated by JAXB 2. They are required by JAXB to load the generated classes at runtime. So, the message basically tells you that the generated classes are not available in the classpath. Andreas On 10 Jan 2008, at 19:33, Trasca Virgil wrote: Hello, I have a service which is exposing some classes which are mapped to an external xml file with jaxb2. I want to use jaxb2 for getting/ writting values to my xml but when I send data on http for webservice I want to use the axis2 adb binding. My method that is exposing xml with jaxb2 is working outside axis2. But when I deploy this method as a web service and I call the web service I get javax.xml.bind.JAXBException: burster.generated.jaxb2 doesnt contain ObjectFactory.class or jaxb.index. What is this exception? What is jaxb.index? I want to use ADB as binding over the htpp. Thank you, Virgil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to set SimpleSessionHandler session timeout in Axis 1.4
Hi, I have a web service that uses SimpleSessionHandler to maintain sessions. I had the following lines in my service description in server-config.wsdd. requestFlow handler type=soapmonitor/ handler type=java:org.apache.axis.handlers.SimpleSessionHandler/ /requestFlow responseFlow handler type=soapmonitor/ handler type=java:org.apache.axis.handlers.SimpleSessionHandler/ /responseFlow I also created the client-wsdd like following lines in it. transport name=http pivot=java:org.apache.axis.transport.http.HTTPSender requestFlow handler type=java:org.apache.axis.handlers.SimpleSessionHandler / /requestFlow responseFlow handler type=java:org.apache.axis.handlers.SimpleSessionHandler / /responseFlow /transport Session handling is working fine. I get the MessageContext.getCurrentContext and get session from it and storing session stuff in the session. My problem is how do I set the session time out? Can some please let me know?. Is it some thing can be specified in the web.xml? or server-config.wsdd? What is default timeout it uses (axis servlet's timeout in web.xml)? Thanks Yuva
Re: [Axis2] NPE in HttpCoreNIOSender
Andreas, it's very odd indeed -- the exception does not occur every time (it suggests me that is a concurrency problem). I'm not testing a deployed service, so I really don't know what getMessageReceiver() should return. Michele On 10 Jan 2008, at 19:32, Andreas Veithen wrote: Michele, This would mean that mc.getAxisOperation().getMessageReceiver() returns null. I don't know the code very well, but this seems indeed strange. Can you also post your unit test? Andreas On 10 Jan 2008, at 19:14, Michele Mazzucco wrote: mr.receive(nioFaultMessageContext); On 10 Jan 2008, at 16:45, Andreas Veithen wrote: Michele, Can you post the code at line 442 in HttpCoreNIOSender.java that triggers the error? Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, it must be a concurrency-related problem because I cannot reproduce it when I execute instructions step-by-step with the debugger. Michele On 10 Jan 2008, at 14:59, Andreas Veithen wrote: Hi Mechele, This issue is indeed strictly related to connection timeouts. I remember that there were other issues with NPEs in HTTPCoreNIOSender. These were resolved in the meantime, but probably those corrections have not yet been propagated to Axis2. It would be interesting to know which variable is actually null in the handleError method. Do you think that you will be able to check this? Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender $2.handleError(HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed (HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed (SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.pro cessSessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.exe cute(DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClien tEngine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000 (HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run (HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] NPE in HttpCoreNIOSender
Andreas, it's very odd indeed -- the exception does not occur every time (it suggests me that is a concurrency problem). I'm not testing a deployed service, so I really don't know what getMessageReceiver() should return. Michele On 10 Jan 2008, at 19:32, Andreas Veithen wrote: Michele, This would mean that mc.getAxisOperation().getMessageReceiver() returns null. I don't know the code very well, but this seems indeed strange. Can you also post your unit test? Andreas On 10 Jan 2008, at 19:14, Michele Mazzucco wrote: mr.receive(nioFaultMessageContext); On 10 Jan 2008, at 16:45, Andreas Veithen wrote: Michele, Can you post the code at line 442 in HttpCoreNIOSender.java that triggers the error? Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, it must be a concurrency-related problem because I cannot reproduce it when I execute instructions step-by-step with the debugger. Michele On 10 Jan 2008, at 14:59, Andreas Veithen wrote: Hi Mechele, This issue is indeed strictly related to connection timeouts. I remember that there were other issues with NPEs in HTTPCoreNIOSender. These were resolved in the meantime, but probably those corrections have not yet been propagated to Axis2. It would be interesting to know which variable is actually null in the handleError method. Do you think that you will be able to check this? Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Andreas, my problem looks quite similar to JIRA Synapse-205 [1], the difference is that the second row of the stack trace is failed and not timeout. Michele [1] http://issues.apache.org/jira/browse/SYNAPSE-205 On 10 Jan 2008, at 13:23, Andreas Veithen wrote: Hi Michele! I think the NIO HTTP code in Axis2 actually comes from the Apache Synapse project. There were several issues about NPEs reported for Synapse. Maybe you can search the JIRA issues to see if your particular issue has already been solved in Synapse. Regards, Andreas Quoting Michele Mazzucco [EMAIL PROTECTED]: Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender $2.handleError(HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed (HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed (SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.pro cessSessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.exe cute(DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClien tEngine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000 (HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run (HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exception doesnt contain ObjectFactory.class or jaxb.index
Hi Andreas, Thanks for help. I am generating jaxb2 code with XJC ant task. This is generating ObjectFactory.java but not jaxb.index file. Is this file from jaxb2 or it is from old jaxb1? If I am googling for this file I get so few references and no clear documentation for jaxb.index. I putted the generated classes including ObjectFactory.java as a jar in WEB-INF\lib folder of the Axis2 web-app in order to be in the classpath but still the same error. What do you think I am doing wrong? Thanks, Virgil - Original Message From: Andreas Veithen [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Thursday, January 10, 2008 8:53:46 PM Subject: Re: Exception doesnt contain ObjectFactory.class or jaxb.index Virgil, Both the ObjectFactory class and the jaxb.index file are generated by JAXB 2. They are required by JAXB to load the generated classes at runtime. So, the message basically tells you that the generated classes are not available in the classpath. Andreas On 10 Jan 2008, at 19:33, Trasca Virgil wrote: Hello, I have a service which is exposing some classes which are mapped to an external xml file with jaxb2. I want to use jaxb2 for getting/ writting values to my xml but when I send data on http for webservice I want to use the axis2 adb binding. My method that is exposing xml with jaxb2 is working outside axis2. But when I deploy this method as a web service and I call the web service I get javax.xml.bind.JAXBException: burster.generated.jaxb2 doesnt contain ObjectFactory.class or jaxb.index. What is this exception? What is jaxb.index? I want to use ADB as binding over the htpp. Thank you, Virgil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL location
Hi , The client Im using is Axis 1.4 in java. The wsdl defines both SOAPAction and wsaw:action settings. In the client if I add the line call.setSOAPActionURI( operation name) then I am able to hit the service. Is there a way to avoid making this change?? Anjana -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Thursday, January 10, 2008 12:19 PM To: axis-user@ws.apache.org Subject: Re: WSDL location Anjana I'm not clear changing the WSDL file is the right solution here, but you can do it. You save the WSDL, add it into the service archive, and then set a flag called useOriginalWSDL. However Does the WSDL define SOAPAction or wsa:action settings? And what client are you using. Basically the client should automatically pick those actions up from the WSDL and Axis2 sets actions into the WSDL. If Axis2 isn't setting actions into the WSDL then its probably easier to get it to do that: In the services.xml set operation name=doSmt actionMappinghttp://foo.org/myAction/actionMapping /operation If you want more info about the settings in services.xml (including useOriginalWSDL) see this article by deepal http://wso2.org/library/2060 Paul On Jan 10, 2008 5:11 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote: So is there no way I can change the wsdl file??I am unable to hit the service because it complains that WSA action is nullI have not specified the SOAP action in my clientIs there a way out??? Anjana -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Thursday, January 10, 2008 11:57 AM To: axis-user@ws.apache.org Subject: Re: WSDL location The WSDL is generated on-demand... it isn't stored. If you want to store it you can use a browser (Save As...) or wget to grab it. Paul On Jan 10, 2008 4:47 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote: I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the message receiver class. Axis2 is auto generating the wsdl. Can I know where I can find the physical location of the file on my file system?? -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL XSD Schema Importing...
Hi Amila, Your solution was correct; I replaced the Axis2 v1.3 libs with the nightly build (snapshot) libs and everything works fine. The Eclipse plugins don't work, but if I use the WSDL2Java in the nightly build it works as I expected it to. Amila Suriarachchi wrote: can you please try with a nightly build? If you still getting the problem please send your wsdl. thanks, Amila. On Jan 10, 2008 3:33 AM, silver17 [EMAIL PROTECTED] wrote: Hi Guys, I've searched a lot of these forum posts and haven't been able to find a resolution to my problem. Currently I am using Axis 2.1.3 and Eclipse Europa with the Apache Codegen wizard plugins. I created a WSDL that imports a couple of schemas and I'm having problems. When I attempt to use the wizards to generate the client stubs using a URL like: http://localhost:8080/app/services/RegistryPublish?wsdl I get the following error: An error occured while completing process - java.lang.InterruptedException : WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred while trying to resolve schema referenced at 'RegistryPublish?xsd=csw-Publication.xsd, relative to http://localhost:8080/app/services'http://localhost:8080/app/services%27.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd And I don't know why it's doing that. Here's a sample of that wsdl: wsdl:definitions name=RegistryPublish targetNamespace=http://services.registry.company.com/publish/; wsdl:documentation WSDL Description for the Registry Publishing Service. /wsdl:documentation wsdl:types xsd:schema xsd:import namespace=http://www.opengis.net/cat/csw/2.0.2; schemaLocation=RegistryPublish?xsd=csw-Publication.xsd/ xsd:import namespace=http://www.opengis.net/ows/1.1; schemaLocation=RegistryPublish?xsd=owsExceptionReport.xsd/ /xsd:schema /wsdl:types ... My web app directory structure is: app-web-inf-services-RegistryPublish-META-INF ... csw-Publication.xsd owsExceptionReport.xsd RegistryPublish.wsdl services.xml I tried using a program called SOAPUI to run a test request to that same url as above and it returned a successful result. Any thoughts? I've attached the files. http://www.nabble.com/file/p14722764/RegistryPublish.wsdl RegistryPublish.wsdl http://www.nabble.com/file/p14722764/services.xml services.xml http://www.nabble.com/file/p14722764/owsExceptionReport.xsd owsExceptionReport.xsd http://www.nabble.com/file/p14722764/csw-Publication.xsd csw-Publication.xsd -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14722764.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14744671.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL XSD Schema Importing...
Hi, are you trying to create an ebRIM CSW server, that is interesting - sorry I missed your earlier emails - I have already run wsdl2java on the ebrim wsdl files, I also tried doing this with Apache Tuscany - works with Axis, not with Tuscany. I don't think this is right forum for a discussion so perhaps we can take this offline, but if your server solution is public domain then that is interesting and I would like to know more Just f.y.i. (again apologies since this is the wrong forum) omar is spatial enabled - http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc. Norman On Jan 10, 2008 2:53 PM, silver17 [EMAIL PROTECTED] wrote: Hi Amila, Your solution was correct; I replaced the Axis2 v1.3 libs with the nightly build (snapshot) libs and everything works fine. The Eclipse plugins don't work, but if I use the WSDL2Java in the nightly build it works as I expected it to. Amila Suriarachchi wrote: can you please try with a nightly build? If you still getting the problem please send your wsdl. thanks, Amila. On Jan 10, 2008 3:33 AM, silver17 [EMAIL PROTECTED] wrote: Hi Guys, I've searched a lot of these forum posts and haven't been able to find a resolution to my problem. Currently I am using Axis 2.1.3 and Eclipse Europa with the Apache Codegen wizard plugins. I created a WSDL that imports a couple of schemas and I'm having problems. When I attempt to use the wizards to generate the client stubs using a URL like: http://localhost:8080/app/services/RegistryPublish?wsdl I get the following error: An error occured while completing process - java.lang.InterruptedException : WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred while trying to resolve schema referenced at 'RegistryPublish?xsd=csw-Publication.xsd, relative to http://localhost:8080/app/services'http://localhost:8080/app/services%27.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd And I don't know why it's doing that. Here's a sample of that wsdl: wsdl:definitions name=RegistryPublish targetNamespace=http://services.registry.company.com/publish/; wsdl:documentation WSDL Description for the Registry Publishing Service. /wsdl:documentation wsdl:types xsd:schema xsd:import namespace=http://www.opengis.net/cat/csw/2.0.2; schemaLocation=RegistryPublish?xsd=csw-Publication.xsd/ xsd:import namespace=http://www.opengis.net/ows/1.1; schemaLocation=RegistryPublish?xsd=owsExceptionReport.xsd/ /xsd:schema /wsdl:types ... My web app directory structure is: app-web-inf-services-RegistryPublish-META-INF ... csw-Publication.xsd owsExceptionReport.xsd RegistryPublish.wsdl services.xml I tried using a program called SOAPUI to run a test request to that same url as above and it returned a successful result. Any thoughts? I've attached the files. http://www.nabble.com/file/p14722764/RegistryPublish.wsdl RegistryPublish.wsdl http://www.nabble.com/file/p14722764/services.xml services.xml http://www.nabble.com/file/p14722764/owsExceptionReport.xsd owsExceptionReport.xsd http://www.nabble.com/file/p14722764/csw-Publication.xsd csw-Publication.xsd -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14722764.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. -- View this message in context: http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14744671.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Calling BeanDeserializer ?
I have a problem trying to use the BeanDeserializer outside of the standard SOAP message processing. I wonder if this is possible. I have an object that is normally transmitted via Web Services that I want to persist as an XML file, and then re-use it at a later date as an Object. This Object was generated with WSDL2Java, and has both a getSerializer() and a getDeserializer() method. I can serialize the Object to XML easily like this: StringWriter output = new StringWriter(); QName qn = new QName(urn...,Item); Serializer serial = Item.getSerializer(Constants.AXIS_SAX, Item.class, item); SerializationContext ctx = new SerializationContext(output); Attributes attribs = new AttributesImpl(); serial.serialize(qn , attribs, item, ctx); return output.toString(); What I cannot figure out how to do is deserialize the XML back to the Object. I've seen this question asked a couple of times in the archives, but never any answer. Any suggestions most welcome Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Difficulty Generating a JSP Test Client with Eclipse's Web Service Client Wizard
Hello all, I've been creating web services based on WSDL files, using Eclipse's Web Service wizard and deploying on Axis2 without much difficulty. At first, I tested my services by using the Web Services Explorer within Eclipse. Now, I'd like to build my own client to access the web services sitting in my Tomcat6/Axis2 server. Looking over the Web Service Client wizard's documentation, it appears that this wizard should be able to automatically generate JSP as a test-client. Unfortunately, I can't seem to access this functionality. So my questions: 1) Has the functionality been deprecated? 2) Is there something that would cause this functionality (i.e. generating a JSP test client) to be unavailable? 3) Is this functionality only available on Axis1 (I'm using Axis2), or would the version even be an issue on the client side? 4) Currently, I specify the client project to be an existing Dynamic Web Project. Is there another project type that I should be using? Side note: Aside from the wsdl2java and associated Eclipse Web Service Client wizard, are there any tutorials on building web clients that can interface with a web service? I'd like to steer clear of proprietary (e.g. Microsoft) solutions, and stick with stuff like JSP, JavaScript, Java, PHP, etc. Currently, I've got two books on the subject (ISBNs: 0672326418 and 0321396855), but they rely on the wsdl2java tool or the wizard mentioned above. Thanks! Matt
Re: Axis2 logging question
Hi all, I have a service exposed in an war which has aar inside. This service is failing when it is called even if calling just the business from POJO in eclipse is working.So I feel it is a deployment issue/class path etc. How can I enable/see all the logging on the Apache Axis2 java server? My war with aar inside is deployed on Jetty. If you can access the web application , then you browse on that you will see your service as a faulty service , and when you click on the link you would see the reason behind the faulty service. The log file should be there in the current directory , please see whether the log file there in the current directory or sometime you may see the error in the application console as well. -Deepal Thank you, Virgil - Original Message From: kokie [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, January 8, 2008 4:57:22 AM Subject: [Axis2]About WS-Policy support Dear, Axis2's great project! I'm using it developing web service with policy support. You metioned in the document http://ws.apache.org/axis2/1_3/WS_policy.html that axis2 *fully supports WS Policy at client-side,* so could axis give an example like codegen a stub against a WSLD which contains policies or else? Thanks in advance. Best wishes. -- 绯村剑心 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to hit AXIS2 service
Kevin, Thanks for your response. My client is Axis 1.4. When I try to hit the Axis2 service, I get the following exception The endpoint reference (EPR) for the Operation not found is http://localhost:9082/axis2/services/AcordWinsRateService and the WSA Action = Where my EPR is http://localhost:9082/axis2/services/AcordWinsRateService. When I use the Axis2.0 client and hit the 2.0 service I am able to hit it and get the response. Why is this? Hmm , as I can see the issue is you are not sending the soap action , please look at the wsdl (as Keith suggested) if the wsdl has a soap action then you need to send that in the request, -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] NPE in HttpCoreNIOSender
Hi Michele , Will you be able to contribute that test case to Axis2 , may be you could create a JIRA and attach the test case :) -Deepal Hi all, I'm unit testing some code and I see a NPE in the HTTPCoreNIOSender. The stack trace is the following: Exception in thread HttpCoreNIOSender java.lang.NullPointerException at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.handleError(HttpCoreNIOSender.java:442) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$2.failed(HttpCoreNIOSender.java:412) at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed(SessionRequestImpl.java:139) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processSessionRequests(DefaultConnectingIOReactor.java:249) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.execute(DefaultConnectingIOReactor.java:109) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.executeClientEngine(HttpCoreNIOSender.java:127) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender.access$000(HttpCoreNIOSender.java:69) at org.apache.axis2.transport.nhttp.HttpCoreNIOSender$1.run(HttpCoreNIOSender.java:102) at java.lang.Thread.run(Thread.java:613) Any idea? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mininal set of maven dependencies
This is the minimum set of dependencies you want to , write a and invoke a service ;-) activation-1.1.jar annogen-0.1.0.jar backport-util-concurrent-2.2.jar commons-codec-1.3.jar commons-fileupload-1.1.1.jar commons-httpclient-3.0.1.jar httpcore-4.0-alpha5.jar httpcore-nio-4.0-alpha5.jar httpcore-niossl-4.0-alpha5.jar log4j-1.2.jar neethi-2.0.2.jar wsdl4j-1.6.2.jar XmlSchema-1.3.2.jar axiom-api-1.2.5.jar axiom-impl-1.2.5.jar commons-logging-1.1.jar stax-api-1.0.1.jar wstx-asl-3.2.1.jar jaxen-1.1.1.jar -Deepal Somebody could tell me the minimal set of maven dependencies for a Axis2 Service project? Thanks. Antonio. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: WSDL problem 'Didn't find specified return QName' error
Hi folks,
*Please* spend some time reading this fully. I am tired of trying to solve
this problem for more than a week now.
I have to write a webservice client using Axis 1.4. The webservice is very
old, written using servlets and apache-soap. I do not even have the WSDL for
it. So I wrote WSDL by myself, by analyzing request and response soap
messages. I am using the types and stubs generated for this service by
WSDL2Java tool, in my client application.
GetServerStatusResponse response = *mappService*.getServerStatus
(getServerStatusRequest);
System.* out*.println(response.getCode());
System.* out*.println(response.getDescription());
System.* out*.println(response.getTrackingCode());
The above code executes normally without any exceptions, but its prints only
null values.
Can anybody tell me what the problem with my WSDL is?
Following is the Response *soap-message* that the webservice sends.
?xml version=1.0 encoding=ISO-8859-1?
SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/
SOAP-ENV:Body
getServerStatus xmlns=urn:sampleURN
serviceStatus
code0/code
descriptiongetServerStatus OK!/description
trackingCodeAABBMMCOEED/trackingCode
/serviceStatus
statusServer xyz alive at Thu Jan 10 11:33:35 CET
2008%BUILDTAG%Build date amp; time: %DEPLOYDATE%/status
/getServerStatus
/SOAP-ENV:Body
/SOAP-ENV:Envelope
Here is the *WSDL* definition I've written for above message:
xsd:element name=getServerStatusResponse
xsd:complexType
xsd:sequence
xsd:element name=getServerStatusReturn
type=impl:GetServerStatusResponse/
/xsd:sequence
/xsd:complexType
/xsd:element
xsd:complexType name=GetServerStatusResponse
xsd:complexContent
xsd:extension base=impl:ServiceStatus
xsd:sequence
xsd:element name=status type=xsd:string/
/xsd:sequence
/xsd:extension
/xsd:complexContent
/xsd:complexType
xsd:complexType name=ServiceStatus
xsd:sequence
xsd:element name=code nillable=true type=xsd:string/
xsd:element name=description nillable=true type=xsd:string/
xsd:element name=trackingCode nillable=true type=xsd:string/
/xsd:sequence
/xsd:complexType
wsdl:message name=getServerStatusRequest
wsdl:part element=impl:getServerStatus name=parameters/
/wsdl:message
wsdl:message name=getServerStatusResponse
wsdl:part element=impl:getServerStatusResponse name=parameters/
/wsdl:message
wsdl:portType name=samplePortName
wsdl:operation name=getServerStatus
wsdl:input message=impl:getServerStatusRequest
name=getServerStatusRequest/
wsdl:output message=impl:getServerStatusResponse
name=getServerStatusResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=sampleBindingName type=impl:samplePortName
wsdlsoap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http
/
wsdl:operation name=getServerStatus
wsdlsoap:operation soapAction=/
wsdl:input name=getServerStatusRequest
wsdlsoap:body use=literal/
/wsdl:input
wsdl:output name=getServerStatusResponse
wsdlsoap:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
If I add the following 4 lines in _initOperationsDesc1() method of the
WebService Stub, then I get the following error .
Error: Didn't find specified return QName {
http://aaa.ccc.com}getServerStatus!;
param = *new* org.apache.axis.description.ParameterDesc(*new*
javax.xml.namespace.QName( urn:sampleURN, serviceStatus),
org.apache.axis.description.ParameterDesc.* OUT*, *new*
javax.xml.namespace.QName( http://bbb.dummycomp.com; , ServiceStatus ),
com.dummycomp.bbb.webservice.ServiceStatus.*class* , *false*, *false*
);
oper.addParameter(param);
param = *new* org.apache.axis.description.ParameterDesc(*new*
javax.xml.namespace.QName( urn:sampleURN, status),
org.apache.axis.description.ParameterDesc.* OUT*, *new*
javax.xml.namespace.QName( http://bbb.dummycomp.com; , Status ),
java.lang.String.*class* , *false*, *false*);
oper.addParameter(param);
--
Kindly suggest the solution as soon as possible, as I'm stuck here for more
than a week now.
Regards,
Rushikesh S. Thakkar
