generate WSDL with implicit headers
Hello all, I am trying to find out, is it possible to use Axis to generate a WSDL that includes implicit headers? thanks a lot -- Stanimir Stanev (Stanley) Senior Java Developer www.stanev.com
[Axis2] RE: Client-within-server problems
Finally solved my own problem, the system at the other end was not a proper Web Service and wasn't actually running anything resembling the WSDL I'd been given. It was more of an HTTP listener that someone had set up to monitor the traffic. I created a dummy web service to simulate the other end and my AxisService immediately cheered up and started working great! Hi, I'm trying to develop a request-reply web service, rather like in Figure 4 on this website: http://www-128.ibm.com/developerworks/library/ws-asynch2/ To do this I'm essentially writing a synchronous web service to do the first request-ack interaction. During the processing I launch a new thread that is effectively a client for the other end. I want to send the response document (which may have taken some time to obtain) back to the other end. I have the WSDL of the other end and used it to create a client stub. I can send my response document to the other end and get the ack back from it. However, my Stub ALWAYS crashes within the _operationClient.execute(true); With a NullPointerException. I've dug around a bit and it seems to be caused by the createSOAPMessage() method of the TransportUtils class - the inStream is always null. I'm guessing there is something clever I have to do with message/operation/configuration contexts, but I can't figure it out! The really weird thing is that despite the AxisFault being thrown, the document still gets sent! Can anyone advise what I have to do to be able to behave like a client within an AxisService? Thanks for any light you can shed, John M.
[axis2] mail transport - is it functional
Hi, Some more question about the mail transport in axis2. 1. Is it considered to be stable for use in a production system or is there more work to do? (I have looked a the src and seem to be finding a few //todo comments, and things like More details need to be explained here. in the Javadoc for service client which do not inspire comfort). 2. Has anyone actually successfully used the mail transport in axis2? If so do anyone have an actual working example (not the example from the user-guide which I still cannot get to work)? -- Cheers Jack... The claim natural is not synonymous with safe.
Re: WSDL2Java variable name syntax error
Hello,yes you are right but something is not work.When i am sending soap request message with uppercase variable i got the that soap response mesage :soapenv:Body soapenv:Faultfaultcodesoapenv: Server.userException/faultcodefaultstringorg.xml.sax.SAXException: Invalid element in otapax.requestclasses.OTA_AirAvailRQ - OriginDestinationInformation /faultstringdetailns1:hostname xmlns:ns1=http://xml.apache.org/axis/recepayaz/ns1:hostname/detail /soapenv:Fault /soapenv:Body*** and this my wdl file (too long. i'm sorry):*** ?xml version=1.0 encoding=UTF-8?wsdl:definitions targetNamespace=http://localhost:8080/axis/services/OTA xmlns:apachesoap= http://xml.apache.org/xml-soap xmlns:impl=http://localhost:8080/axis/services/OTA xmlns:intf= http://localhost:8080/axis/services/OTA xmlns:tns1=http://www.hititcs.com/TestRecep xmlns:tns2=http://requestclasses.otapax xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/ xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/ xmlns:xsd=http://www.w3.org/2001/XMLSchema!--WSDL created by Apache Axis version: 1.3Built on Oct 05, 2005 (05:23:37 EDT)--wsdl:types schema elementFormDefault=qualified targetNamespace=http://www.hititcs.com/TestRecep xmlns= http://www.w3.org/2001/XMLSchema import namespace=http://localhost:8080/axis/services/OTA/ complexType name=LocationType sequence/ attribute name=LocationCode type=xsd:string/ /complexType complexType name=OriginDestinationInformationType sequence element name=DepartureDateTime nillable=true type=xsd:string/ element name=OriginLocation nillable=true type=tns1:LocationType/ element name=DestinationLocation nillable=true type=tns1:LocationType/ /sequence /complexType complexType name=FlightTypePrefType sequence/ attribute name=FlightType type=xsd:string/ attribute name=PreferLevel type=xsd:string/ /complexType complexType name=EquipPrefType sequence/ attribute name=AirEquipType type=xsd:string/ /complexType complexType name=CabinPrefType sequence/ attribute name=Cabin type=xsd:string/ attribute name=PreferLevel type=xsd:string/ /complexType complexType name=TicketDistribPrefType sequence/ attribute name=DistribType type=xsd:int/ attribute name=PreferLevel type=xsd:string/ /complexType complexType name=TravelPreferencesType sequence element name=FlightTypePref nillable=true type=tns1:FlightTypePrefType/ element name=EquipPref nillable=true type=tns1:EquipPrefType/ element name=CabinPref nillable=true type=tns1:CabinPrefType/ element name=TicketDistribPref nillable=true type=tns1:TicketDistribPrefType/ /sequence attribute name=MaxStopsQuantity type=xsd:int/ attribute name=SmokingAllowed type=xsd:string/ /complexType complexType name=TravelerInfoSummaryType sequence element name=AirTravelerAvail nillable=true type=impl:ArrayOfPassengerTypeQuantityType/ /sequence /complexType /schema schema elementFormDefault=qualified targetNamespace=http://localhost:8080/axis/services/OTA xmlns=http://www.w3.org/2001/XMLSchema import namespace=http://www.hititcs.com/TestRecep / complexType name=PassengerTypeQuantityType sequence/ attribute name=Code type=xsd:string/ attribute name=Quantity type=xsd:int/ /complexType complexType name=ArrayOfPassengerTypeQuantityType sequence element maxOccurs=unbounded minOccurs=0 name=item type=impl:PassengerTypeQuantityType/ /sequence /complexType complexType name=OTA_AirAvailRQ sequence element name=OriginDestinationInformation nillable=true type=tns1:OriginDestinationInformationType/ element name=TravelPreferences nillable=true type=tns1:TravelPreferencesType/ element name=TravelerInfoSummary nillable=true type=tns1:TravelerInfoSummaryType/ /sequence attribute name=DirectFlightsOnly type=xsd:boolean/ attribute name=MaxResponses type=xsd:int/ attribute name=PrimaryLangID type=xsd:string/ attribute name=SequenceNmbr type=xsd:int/ /complexType element name=myJavaWebServiceReturn type=xsd:string/ /schema schema elementFormDefault=qualified targetNamespace= http://requestclasses.otapax xmlns=http://www.w3.org/2001/XMLSchema import namespace= http://localhost:8080/axis/services/OTA/ import namespace=http://www.hititcs.com/TestRecep/ element name=RQ type=impl:OTA_AirAvailRQ/ /schema/wsdl:types wsdl:message name=myJavaWebServiceResponse wsdl:part element=impl:myJavaWebServiceReturn name=myJavaWebServiceReturn/ /wsdl:message wsdl:message name=myJavaWebServiceRequest wsdl:part element=tns2:RQ name=RQ/ /wsdl:message wsdl:portType name=Class2 wsdl:operation name=myJavaWebService parameterOrder=RQ wsdl:input message=impl:myJavaWebServiceRequest name=myJavaWebServiceRequest/ wsdl:output message=impl:myJavaWebServiceResponse name=myJavaWebServiceResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=OTASoapBinding type=impl:Class2 wsdlsoap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ wsdl:operation name=myJavaWebService wsdlsoap:operation
Re: CalClient problem: Classpath
Well I didn't noticed that its an Axis1. Perhaps in axis1 what I remember the lib jars and server side code should be in classpath. I tried in old version, may be in new version it might have been changed. On 4/26/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Kensky; This is Axis1 sampple not an Axis2 sample , so Axis1 does not support .aar based deployemnt , so it will not help that if you drop .aar file into classpath. But if you put .jar file it may work (btw I am not the right person to answer Axis1 q :) ) Kensky Schulz wrote: You have to place the server side .aar in your class path. Remember the server side code you generated as serverapp.aar for classpath reference should be renamed as serverapp.jar before placing into classpath. On 4/24/06, Askar Zaidi [EMAIL PROTECTED] wrote: Hi, When I try to run the CalClient example, I get the following exception: Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/utils/Options at samples.userguide.example2.CalcClient.main(CalcClient.java:29) If this is a CLASSPATH trouble, please tell me how to solve this. I have set AXIS_HOME and AXIS_LIB. this is my directory structure: /home/tintin/apache/ /home/tintin/axis/ PLEASE ! this is urgent !! -- thanks, Askar -- Thanks, Deepal ~Future is Open~
unsubscribe me
Re: [axis2] services.xml problems
Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) at org.apache.axis2.AxisFault.init(AxisFault.java:159) ... 4 more where BlockSingleGetQuote.java:42 is OMElement result = sender.sendReceive(payload); while by pointing the browser to http://localhost:8080/axis2/services/StockQuoteService?wsdl I get an HTTP Status 500: javax.servlet.ServletException: null; nested exception is: java.lang.NullPointerException org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:105) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause org.apache.axis2.AxisFault: null; nested exception is: java.lang.NullPointerException org.apache.axis2.description.AxisService.getWSDL(AxisService.java:479) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:468) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:82) org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:45) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:103) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Any idea? Thanks in advance, Michele Deepal Jayasinghe wrote: Hi Michele; I found the problem, each service element in a servicegroup have to have name attribute so if you apply my changes it will work Michele Mazzucco wrote: Hi all, I'm using Axis2 1.0 RC2 and I'm having troubles with services.xml when I include more that one service. In particular, the services.xml below doesn't work (the .aar file is shown as faulty service) ?xml version=1.0 encoding=UTF-8? serviceGroup service *service name=StockQuoteService* description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter
Re: [axis2] services.xml problems
Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) at org.apache.axis2.AxisFault.init(AxisFault.java:159) ... 4 more where BlockSingleGetQuote.java:42 is OMElement result = sender.sendReceive(payload); while by pointing the browser to http://localhost:8080/axis2/services/StockQuoteService?wsdl I get an HTTP Status 500: javax.servlet.ServletException: null; nested exception is: java.lang.NullPointerException org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:105) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause org.apache.axis2.AxisFault: null; nested exception is: java.lang.NullPointerException org.apache.axis2.description.AxisService.getWSDL(AxisService.java:479) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:468) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:82) org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:45) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:103) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Any idea? Thanks in advance, Michele Deepal Jayasinghe wrote: Hi Michele; I found the problem, each service element in a servicegroup have to have name attribute so if you apply my changes it will work Michele Mazzucco wrote: Hi all, I'm using Axis2 1.0 RC2 and I'm having troubles with services.xml when I include more that one service. In particular, the services.xml below doesn't work (the .aar file is
Re: CalClient problem: Classpath
Hi Deepal, I set my variable like this for (linux); and tried couple of examples, working fine. AXIS_HOME=/usr/local/axis-1_3 AXIS_LIB=$AXIS_HOME/lib AXISCLASSPATH=$AXIS_LIB/axis.jar:$AXIS_LIB/commons-discovery-0.2.jar:$AXIS_LIB/commons-logging-1.0.4.jar:$AXIS_LIB/jaxrpc.jar:$AXIS_LIB/saaj.jar:$AXIS_LIB/log4j-1.2.8.jar:$AXIS_LIB/wsdl4j-1.5.1.jar:$AXIS_LIB/xml-apis.jar:$AXIS_LIB/xercesImpl.jar export AXIS_HOME; export AXIS_LIB; export AXISCLASSPATH Hope this is useful. Bharathi. Kensky Schulz wrote: Well I didn't noticed that its an Axis1. Perhaps in axis1 what I remember the lib jars and server side code should be in classpath. I tried in old version, may be in new version it might have been changed. On 4/26/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Kensky; This is Axis1 sampple not an Axis2 sample , so Axis1 does not support .aar based deployemnt , so it will not help that if you drop .aar file into classpath. But if you put .jar file it may work (btw I am not the right person to answer Axis1 q :) ) Kensky Schulz wrote: You have to place the server side .aar in your class path. Remember the server side code you generated as serverapp.aar for classpath reference should be renamed as serverapp.jar before placing into classpath. On 4/24/06, Askar Zaidi [EMAIL PROTECTED] wrote: Hi, When I try to run the CalClient example, I get the following exception: Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis/utils/Options at samples.userguide.example2.CalcClient.main(CalcClient.java:29) If this is a CLASSPATH trouble, please tell me how to solve this. I have set AXIS_HOME and AXIS_LIB. this is my directory structure: /home/tintin/apache/ /home/tintin/axis/ PLEASE ! this is urgent !! -- thanks, Askar -- Thanks, Deepal ~Future is Open~
Re: [axis2] services.xml problems
Yes: serviceGroup service name=OMElement description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter operation name=getQuote messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service service name=CustomObjects descriptionSecond/description parameter name=serviceClass locked=xsd:falsestock.service.SchemaQuoteService/parameter operation name=getQuote1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service /serviceGroup Deepal Jayasinghe wrote: Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) at org.apache.axis2.AxisFault.init(AxisFault.java:159) ... 4 more where BlockSingleGetQuote.java:42 is OMElement result = sender.sendReceive(payload); while by pointing the browser to http://localhost:8080/axis2/services/StockQuoteService?wsdl I get an HTTP Status 500: javax.servlet.ServletException: null; nested exception is: java.lang.NullPointerException org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:105)
Re: [axis2] services.xml problems
Rename serviceClass to ServiceClass Michele Mazzucco wrote: Yes: serviceGroup service name=OMElement description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter operation name=getQuote messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service service name=CustomObjects descriptionSecond/description parameter name=serviceClass locked=xsd:falsestock.service.SchemaQuoteService/parameter operation name=getQuote1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service /serviceGroup Deepal Jayasinghe wrote: Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) at org.apache.axis2.AxisFault.init(AxisFault.java:159) ... 4 more where BlockSingleGetQuote.java:42 is OMElement result = sender.sendReceive(payload); while by pointing the browser to http://localhost:8080/axis2/services/StockQuoteService?wsdl I get an HTTP Status 500: javax.servlet.ServletException: null; nested exception is: java.lang.NullPointerException org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:105)
Problem deploying axis
Hi there, I am facing a problem deploying Axis on a linux server having a dual IP address. This is due to Axis's restriction of only allowing deployment from localhost. The server, I am trying to deploy on has 2 IP addresses and this is confusing AXIS into thinking that its a remote deployment. Has anyone faced this issue and if could let me know a probably solution. Thanks in advance, Santunu This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.
Re: [axis2] services.xml problems
Deepal, unfortunately it still doesn't work. Deepal Jayasinghe wrote: Rename serviceClass to ServiceClass Michele Mazzucco wrote: Yes: serviceGroup service name=OMElement description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter operation name=getQuote messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service service name=CustomObjects descriptionSecond/description parameter name=serviceClass locked=xsd:falsestock.service.SchemaQuoteService/parameter operation name=getQuote1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service /serviceGroup Deepal Jayasinghe wrote: Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) at org.apache.axis2.AxisFault.init(AxisFault.java:159) ... 4 more where BlockSingleGetQuote.java:42 is OMElement result = sender.sendReceive(payload); while by pointing the browser to http://localhost:8080/axis2/services/StockQuoteService?wsdl I get an HTTP Status 500: javax.servlet.ServletException: null; nested exception is: java.lang.NullPointerException
Re: [axis2] services.xml problems
I forget to add that now the problem is visible from the web admin tool (the service il listed as faulty) and (of course) if you try to run the client you get the following error org.apache.axis2.AxisFault: Service not found operation terminated !! Michele Mazzucco wrote: Deepal, unfortunately it still doesn't work. Deepal Jayasinghe wrote: Rename serviceClass to ServiceClass Michele Mazzucco wrote: Yes: serviceGroup service name=OMElement description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter operation name=getQuote messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service service name=CustomObjects descriptionSecond/description parameter name=serviceClass locked=xsd:falsestock.service.SchemaQuoteService/parameter operation name=getQuote1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service /serviceGroup Deepal Jayasinghe wrote: Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) at org.apache.axis2.AxisFault.init(AxisFault.java:159) ... 4 more where BlockSingleGetQuote.java:42 is OMElement result = sender.sendReceive(payload); while by pointing the
Re: [axis2] services.xml problems
Wt was the exception , when you click on fault service link you can get it Michele Mazzucco wrote: I forget to add that now the problem is visible from the web admin tool (the service il listed as faulty) and (of course) if you try to run the client you get the following error org.apache.axis2.AxisFault: Service not found operation terminated !! Michele Mazzucco wrote: Deepal, unfortunately it still doesn't work. Deepal Jayasinghe wrote: Rename serviceClass to ServiceClass Michele Mazzucco wrote: Yes: serviceGroup service name=OMElement description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter operation name=getQuote messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service service name=CustomObjects descriptionSecond/description parameter name=serviceClass locked=xsd:falsestock.service.SchemaQuoteService/parameter operation name=getQuote1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service /serviceGroup Deepal Jayasinghe wrote: Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) at org.apache.axis2.AxisFault.init(AxisFault.java:159) ... 4 more where BlockSingleGetQuote.java:42 is OMElement result = sender.sendReceive(payload); while by
RE: help on java2wsdl and parameter types
Thanks Dies, That indeed made it work as I wanted. -Original Message- From: Dies Koper [mailto:[EMAIL PROTECTED] Sent: Thursday, April 27, 2006 2:38 AM To: axis-user@ws.apache.org Subject: Re: help on java2wsdl and parameter types Hello Mati, Use the option -u LITERAL. As far as I understood, the SOAP spec was being written when the XMLSchema spec was not finished yet. The SOAP spec defines a way to describe data types, so does the XMLSchema. Java2WSDL uses ENCODED (SOAP encoding) by default, but you can change it to use XMLSchema data types. Some SOAP engines (.NET?) do not support SOAP encoded data types. Regards, Dies Mati David wrote: Hi, I'm running java2wsdl (axis1.3) in rpc style on my java source files. In the generated wsdl I see that the messages arguments types have the 'soapenc' namespace i.e., wsdl:part name=in0 type=soapenc:string/. Yet, when I look at automatically generated wsdl from the axis engine on my web server I see that those types are defined with the xsd namespace - xsd:string. How can I cause the java2wsdl tool to generate a wsdl using the xsd namespace for parameter types (and what is actually the difference between those two namespaces?)? Thanks, Mati David,
RE: help on java2wsdl and parameter types
Guys, Any idea how to get the maxoccurs and minoccurs attributes using java2wsdl ? Regards, Santunu Mati David [EMAIL PROTECTED] 27/04/2006 12:11 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject RE: help on java2wsdl and parameter types Thanks Dies, That indeed made it work as I wanted. -Original Message- From: Dies Koper [mailto:[EMAIL PROTECTED] Sent: Thursday, April 27, 2006 2:38 AM To: axis-user@ws.apache.org Subject: Re: help on java2wsdl and parameter types Hello Mati, Use the option -u LITERAL. As far as I understood, the SOAP spec was being written when the XMLSchema spec was not finished yet. The SOAP spec defines a way to describe data types, so does the XMLSchema. Java2WSDL uses ENCODED (SOAP encoding) by default, but you can change it to use XMLSchema data types. Some SOAP engines (.NET?) do not support SOAP encoded data types. Regards, Dies Mati David wrote: Hi, I'm running java2wsdl (axis1.3) in rpc style on my java source files. In the generated wsdl I see that the messages arguments types have the 'soapenc' namespace i.e., wsdl:part name=in0 type=soapenc:string/. Yet, when I look at automatically generated wsdl from the axis engine on my web server I see that those types are defined with the xsd namespace - xsd:string. How can I cause the java2wsdl tool to generate a wsdl using the xsd namespace for parameter types (and what is actually the difference between those two namespaces?)? Thanks, Mati David, This email has been scanned for all viruses by the MessageLabs SkyScan service. This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.
Re: WSDL-File incompatible with Axis1 Axis2
Hi, Try the XMLBeans databinding with the -d xmlbeans On 4/27/06, Koelle, Christian [EMAIL PROTECTED] wrote: Hi, would someone please mind taking a glimpse on the following wsdl-file regarding axis1 and axis2 compatibility? Thanks in advance. All new for me, and I don't know where to look first. Seems that the first wsdl-file I got is not a good start. Background: I can run axis 1.2.1 WSDL2Java on the wsdl without problem, i.e. generate stubs, but get an runtime error, if I execute a method on my stubs. The response returned is exactly how it should be, but there seems to be a problem in the object mapping. I get a similar error for stubs generated with axis 1.3 WSDL2Java. I cannot run axis 2 WSDL2Java on the the file via ant or provided script as I am getting a Unsupported content Simple Content Extension ! All at all, I assume that the WSDL-File is not optimized for Axis. I appreciate all of your comments, as I do not know exactly where to start to look first. It is fairly new for me. I will get into all this but it is far to much to assess the situation now. Thanks in advance Regards Chris Below: WSDL2-Java error Axis2 0.95 Runtime-error Axis 1.2.1 Soap Request Soap Response WSDL-file provided ### Error while running Axis 2 0.95-WSDL2Java Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: org.apache.axis2.schema.SchemaCompilationException : Unsupported content Simple Content Extension ! at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:146) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: org.apache.axis2.schema.SchemaCompilation Exception: Unsupported content Simple Content Extension ! at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp leDBExtension.java:162) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:101) ... 2 more Caused by: org.apache.axis2.schema.SchemaCompilationException: Unsupported content Simple Content Extension ! at org.apache.axis2.schema.SchemaCompiler.processSimpleContent(SchemaCompiler.java:803) at org.apache.axis2.schema.SchemaCompiler.processContentModel(SchemaCompiler.java:672) at org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:654) at org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:604) at org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:569) at org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:360) at org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:338) at org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:220) at org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:179) at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:115) ... 3 more Error with Axis 1.2.1-generated stubs during runtime when calling: StaticAttributeProfileService service = new StaticAttributeProfileServiceLocator(); StaticAttributeProfile myStub = service.getStaticAttributeProfileSOAPPort(); Stub axisStub2 = (Stub) myStub; [...] myStub.getDocumentTypes(epc); 2006-04-27 10:22:47,410 DEBUG [main] org.apache.axis.encoding.DeserializationContext: Popped element stack to org.apache.axis.message.RPCElement:schemaList 2006-04-27 10:22:47,410 DEBUG [main] org.apache.axis.encoding.DeserializationContext: Exit: DeserializationContext::endElement() 2006-04-27 10:22:47,410 DEBUG [main] org.apache.axis.i18n.ProjectResourceBundle: org.apache.axis.i18n.resource::handleGetObject(exception00) 2006-04-27 10:22:47,410 ERROR [main] org.apache.axis.client.Call: Exception: org.apache.axis.types.URI$MalformedURIException: No scheme found in URI. at org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:180) at org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) at org.apache.axis.client.Call.invoke(Call.java:2448) at
Re: [axis2] services.xml problems
It just says Requested resource not found! Deepal Jayasinghe wrote: Wt was the exception , when you click on fault service link you can get it Michele Mazzucco wrote: I forget to add that now the problem is visible from the web admin tool (the service il listed as faulty) and (of course) if you try to run the client you get the following error org.apache.axis2.AxisFault: Service not found operation terminated !! Michele Mazzucco wrote: Deepal, unfortunately it still doesn't work. Deepal Jayasinghe wrote: Rename serviceClass to ServiceClass Michele Mazzucco wrote: Yes: serviceGroup service name=OMElement description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter operation name=getQuote messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service service name=CustomObjects descriptionSecond/description parameter name=serviceClass locked=xsd:falsestock.service.SchemaQuoteService/parameter operation name=getQuote1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service /serviceGroup Deepal Jayasinghe wrote: Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at
Re: [axis2] services.xml problems
psl send me your service archive file , there should be some problem with that. Michele Mazzucco wrote: It just says Requested resource not found! Deepal Jayasinghe wrote: Wt was the exception , when you click on fault service link you can get it Michele Mazzucco wrote: I forget to add that now the problem is visible from the web admin tool (the service il listed as faulty) and (of course) if you try to run the client you get the following error org.apache.axis2.AxisFault: Service not found operation terminated !! Michele Mazzucco wrote: Deepal, unfortunately it still doesn't work. Deepal Jayasinghe wrote: Rename serviceClass to ServiceClass Michele Mazzucco wrote: Yes: serviceGroup service name=OMElement description First /description parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter operation name=getQuote messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service service name=CustomObjects descriptionSecond/description parameter name=serviceClass locked=xsd:falsestock.service.SchemaQuoteService/parameter operation name=getQuote1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation operation name=subscribe1 messageReceiver class=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver/ /operation /service /serviceGroup Deepal Jayasinghe wrote: Do you have the serviceClass parameter in both service elements serviceGroup service name=service1 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService/parameter /service service name=service2 parameter name=serviceClass locked=xsd:falsestock.service.StockQuoteService2/parameter /service serviceGroup Michele Mazzucco wrote: Hi Deepal, thanks very much for your help. Now that problem has been fixed, however at runtime the web service doesn't work any more (while if you provide a services.xml with a single service it does). On the client side I get the following exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:286) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:452) at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:394) at client.BlockSingleGetQuote.main(BlockSingleGetQuote.java:42) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: SERVICE_CLASS parameter is not specified at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:57) at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:90) at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:450) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:283) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at
Attempt to get an attribute on an invalidated session
HI, I am trying to run Axis 1.2.1 on ATG Dynamo 6.0. The service works absolutely fine except that after running the service, I get the following errors after some time on my application servers logs: Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionData.getAttribute(SessionData.java:1099) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at org.apache.axis.transport.http.AxisHTTPSessionListener.destroySession(AxisHTTPSessionListener.java:43) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at org.apache.axis.transport.http.AxisHTTPSessionListener.sessionDestroyed(AxisHTTPSessionListener.java:72) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at atg.servlet.container.WebApplication.handleHttpSessionLifecycleEvent(WebApplication.java:1613) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionData.invalidate(SessionData.java:883) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.ParentSessionData.invalidate(ParentSessionData.java:133) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionData.invalidate(SessionData.java:898) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionManager.performInvalidation(SessionManager.java:729) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionManagerService.performScheduledTask(SessionManagerService.java:1315) Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler stack trace CROPPED after 10 lines. Error Thu Apr 27 08:34:12 BST 2006 1146123252958 /atg/dynamo/service/Scheduler info Thu Apr 27 08:35:03 BST 2006 1146123303258 /atg/dynamo/server/ServerMonitor Sampling request information for DrpServer. Number of requests since last sample=0 info Thu Apr 27 08:35:03 BST 2006 1146123303259 /atg/dynamo/server/ServerMonitor Sampling resource pool information for /atg/dynamo/service/jdbc/JTDataSource Number of checked out resources is 0 info Thu Apr 27 08:35:03 BST 2006 1146123303260 /atg/dynamo/server/ServerMonitor Sampling session and memory information. Number of sessions=6. Total memory=1264582656, free memory=995729200 (78.74%). Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler Error while handling scheduled job invalidationCheck java.lang.IllegalStateException: Attempt to get an attribute on an invalidated session Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionData.getAttribute(SessionData.java:1099) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at org.apache.axis.transport.http.AxisHTTPSessionListener.destroySession(AxisHTTPSessionListener.java:43) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at org.apache.axis.transport.http.AxisHTTPSessionListener.sessionDestroyed(AxisHTTPSessionListener.java:72) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at atg.servlet.container.WebApplication.handleHttpSessionLifecycleEvent(WebApplication.java:1613) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionData.invalidate(SessionData.java:883) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.ParentSessionData.invalidate(ParentSessionData.java:133) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionData.invalidate(SessionData.java:898) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionManager.performInvalidation(SessionManager.java:729) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler at atg.servlet.sessiontracking.SessionManagerService.performScheduledTask(SessionManagerService.java:1315) Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler stack trace CROPPED after 10 lines. Error Thu Apr 27 08:35:12 BST 2006 1146123312958 /atg/dynamo/service/Scheduler I have tried to change the scope of all the handlers ( I have not introduced any new handlers in the pipeline) to request as well as to application scope but the errors keep on coming. Sometimes, even on user logout on the portal, the same errors throw up in the form of a Servlet Exception. Is there a way out .. L Thanks, Nikhil Saini
String, which is not a simple type
Hello,I have a problem. I can deploy my web service to axis 1.3 (Tomcat 4.1).If I try to get the wsdl description, i gave that error meesage AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - Bean attribute URL is of type java.lang.String, which is not a simple typeAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: Bean attribute URL is of type java.lang.String, which is not a simple type faultActor: faultNode: faultDetail: {
http://xml.apache.org/axis/}hostname:recepayaz*And this is a part of my java class:***
public class RequestorIDType implements java.io.Serializable {private java.lang.String URL; // attributeprivate java.lang.String type; // attribute...}please someone help me ?
i am really stuck at this problem.regards.Recep Ayaz
[Axis2] Good way of notifying the clients to say results are ready in asynchronous messaging
Hi all, I want to send a notification message to my clients when their requests are processed and the results are ready. Then I expect them to call a service to acquire the results. Here is the sample scenario: server.wsdl - OpenAccount - input: OpenAccountMsg - GetOpenAccountResult - input: GetOpenAccountResultMsg - output: GetOpenAccountResultResponseMsg client.wsdl - ResultIsReady (input only) - input: ResultIsReadyMsg OpenAccountMsg (MessageId: A) Client - Server ResultIsReadyMsg (MessageId: B, RelatesTo: A) Client - Server GetOpenAccountResultMsg (MessageId: C, RelatesTo: A) Client - Server - GetOpenAccountResultResponseMsg (MessageId: D, RelatesTo: A) Here are the questions: 1) Do you see any flaw in this scenario? Or is there a common and standards based way to accomplish this kind of asynchronous communication? 2) I haven't found a good way to say my clients which service do they need to call for getting the results. I'm planning to put the name of result service name (GetOpenAccountResultMsg) in notification message (ResultIsReadyMsg). Could you please enlighten me? Any help would be great! Ali Sadik Kumlali __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [Axis2] Good way of notifying the clients to say results are ready in asynchronous messaging
WS-Addressing.On 4/27/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote: Hi all,I want to send a notification message to my clients when their requestsare processed and the results are ready. Then I expect them to call aservice to acquire the results. Here is the sample scenario: server.wsdl - OpenAccount- input: OpenAccountMsg - GetOpenAccountResult- input: GetOpenAccountResultMsg- output: GetOpenAccountResultResponseMsgclient.wsdl - ResultIsReady (input only)- input: ResultIsReadyMsgOpenAccountMsg (MessageId: A)Client - Server ResultIsReadyMsg (MessageId: B, RelatesTo: A)Client - ServerGetOpenAccountResultMsg (MessageId: C, RelatesTo: A)Client - Server -GetOpenAccountResultResponseMsg (MessageId: D, RelatesTo: A)Here are the questions:1) Do you see any flaw in this scenario? Or is there a common and standards based way to accomplish this kind of asynchronouscommunication?2) I haven't found a good way to say my clients which service do theyneed to call for getting the results. I'm planning to put the name of result service name (GetOpenAccountResultMsg) in notification message(ResultIsReadyMsg).Could you please enlighten me? Any help would be great!Ali Sadik Kumlali__ Do You Yahoo!?Tired of spam?Yahoo! Mail has the best spam protection aroundhttp://mail.yahoo.com
wsdl schema - parse 'form' attribute for an element
Hi, I have this scenario wherein I am trying to construct the input/output soap-message structures and since I need to display them also, I am preparing some internal models for representing them. I am also required to store additional information like node-occurrence and node-qualification (whether qualified or unqualified). I have been able to retrieve schema-level qualification through SchemaImport. However, I would also need to get the qualification specified at the element declaration level as form attribute in schema. Is this possible using axis APIs (I am using axis 1.2.1)? Or do I need to resort to any schema-parsing utility like JaxME or Castor? But herein I must press the fact that primarily I am parsing a WSDL so axis API is my best resort. Note: I may use getNode method on a TypeEntry instance but what about derived-simple schema types? Appreciate any help in this regard, Prashanto
Re: WSDL-File incompatible with Axis1 Axis2
Thanks for your quick response. Good: The axis2 WSDL2Java runs without error and generates the required java files if -d xmlbeans is used. Notes: Then I sticked to the Axis2 manual: The input parameter are to be created by factories on the Interfaces of input parameter types. Bad: I cannot use any factory on any type, as I am always getting an error like the following. Please note that the generated ,xsb-Files are on the classpath. Question: What would you suggest do next? Is it more expected to be a misusage issue of xmlbeans or more like to get fixed by getting deeper into wsdl-definitions? thx Christian ### Exception in thread main java.lang.ExceptionInInitializerError at _1.schema.xml.authentication.epcis.interchange.specification.epc.UserTokenType$Factory.newInstance(UserTokenType.java:69) at de.fhg.fokus.sensors.epcglob.WebServiceUtilsAxis2.main(WebServiceUtilsAxis2.java:47) Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.sE8D74C43B4CA14DB64488CB73633D6D3.TypeSystemHolder. Make sure the generated binary files are on the classpath. at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:781) at _1.schema.xml.authentication.epcis.interchange.specification.epc.UserTokenType.clinit(UserTokenType.java:19) ... 2 more Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.sE8D74C43B4CA14DB64488CB73633D6D3.TypeSystemHolder at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:767) ... 3 mor ### On Thu, 2006-04-27 at 15:56 +0530, Ajith Ranabahu wrote: Hi, Try the XMLBeans databinding with the -d xmlbeans On 4/27/06, Koelle, Christian [EMAIL PROTECTED] wrote: Hi, would someone please mind taking a glimpse on the following wsdl-file regarding axis1 and axis2 compatibility? Thanks in advance. All new for me, and I don't know where to look first. Seems that the first wsdl-file I got is not a good start. Background: I can run axis 1.2.1 WSDL2Java on the wsdl without problem, i.e. generate stubs, but get an runtime error, if I execute a method on my stubs. The response returned is exactly how it should be, but there seems to be a problem in the object mapping. I get a similar error for stubs generated with axis 1.3 WSDL2Java. I cannot run axis 2 WSDL2Java on the the file via ant or provided script as I am getting a Unsupported content Simple Content Extension ! All at all, I assume that the WSDL-File is not optimized for Axis. I appreciate all of your comments, as I do not know exactly where to start to look first. It is fairly new for me. I will get into all this but it is far to much to assess the situation now. Thanks in advance Regards Chris Below: WSDL2-Java error Axis2 0.95 Runtime-error Axis 1.2.1 Soap Request Soap Response WSDL-file provided ### Error while running Axis 2 0.95-WSDL2Java Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: org.apache.axis2.schema.SchemaCompilationException : Unsupported content Simple Content Extension ! at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:146) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: org.apache.axis2.schema.SchemaCompilation Exception: Unsupported content Simple Content Extension ! at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp leDBExtension.java:162) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:101) ... 2 more Caused by: org.apache.axis2.schema.SchemaCompilationException: Unsupported content Simple Content Extension ! at org.apache.axis2.schema.SchemaCompiler.processSimpleContent(SchemaCompiler.java:803) at org.apache.axis2.schema.SchemaCompiler.processContentModel(SchemaCompiler.java:672) at org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:654) at
Re: WSDL-File incompatible with Axis1 Axis2
Hi, Why I suggested XMLbeans is that ADB does not handle simple content extensions fully. Unfortunatley that hurls you into the world of xmlbeans which may be a bit unfamiliar. Here is a quick guide of what to do 1. XMLbeans generates a number of binary files of its own format that needs to find it's way to the classpath. these files are found in the resources directory of the output directory for the codegen. 2. the creation of XMLbeans objects need to happen through the fatory inner class generated into each relevant object. The easiest thing for you to do is to use the generated build file. just run ant jar.client to get a jar of the client with all code compiled (AXIS2_HOME need to be set ofcourse) Ajith On 4/27/06, Koelle, Christian [EMAIL PROTECTED] wrote: Thanks for your quick response. Good: The axis2 WSDL2Java runs without error and generates the required java files if -d xmlbeans is used. Notes: Then I sticked to the Axis2 manual: The input parameter are to be created by factories on the Interfaces of input parameter types. Bad: I cannot use any factory on any type, as I am always getting an error like the following. Please note that the generated ,xsb-Files are on the classpath. Question: What would you suggest do next? Is it more expected to be a misusage issue of xmlbeans or more like to get fixed by getting deeper into wsdl-definitions? thx Christian ### Exception in thread main java.lang.ExceptionInInitializerError at _1.schema.xml.authentication.epcis.interchange.specification.epc.UserTokenType$Factory.newInstance(UserTokenType.java:69) at de.fhg.fokus.sensors.epcglob.WebServiceUtilsAxis2.main(WebServiceUtilsAxis2.java:47) Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable to load class with name schemaorg_apache_xmlbeans.system.sE8D74C43B4CA14DB64488CB73633D6D3.TypeSystemHolder. Make sure the generated binary files are on the classpath. at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:781) at _1.schema.xml.authentication.epcis.interchange.specification.epc.UserTokenType.clinit(UserTokenType.java:19) ... 2 more Caused by: java.lang.ClassNotFoundException: schemaorg_apache_xmlbeans.system.sE8D74C43B4CA14DB64488CB73633D6D3.TypeSystemHolder at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:767) ... 3 mor ### On Thu, 2006-04-27 at 15:56 +0530, Ajith Ranabahu wrote: Hi, Try the XMLBeans databinding with the -d xmlbeans On 4/27/06, Koelle, Christian [EMAIL PROTECTED] wrote: Hi, would someone please mind taking a glimpse on the following wsdl-file regarding axis1 and axis2 compatibility? Thanks in advance. All new for me, and I don't know where to look first. Seems that the first wsdl-file I got is not a good start. Background: I can run axis 1.2.1 WSDL2Java on the wsdl without problem, i.e. generate stubs, but get an runtime error, if I execute a method on my stubs. The response returned is exactly how it should be, but there seems to be a problem in the object mapping. I get a similar error for stubs generated with axis 1.3 WSDL2Java. I cannot run axis 2 WSDL2Java on the the file via ant or provided script as I am getting a Unsupported content Simple Content Extension ! All at all, I assume that the WSDL-File is not optimized for Axis. I appreciate all of your comments, as I do not know exactly where to start to look first. It is fairly new for me. I will get into all this but it is far to much to assess the situation now. Thanks in advance Regards Chris Below: WSDL2-Java error Axis2 0.95 Runtime-error Axis 1.2.1 Soap Request Soap Response WSDL-file provided ### Error while running Axis 2 0.95-WSDL2Java Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: org.apache.axis2.schema.SchemaCompilationException : Unsupported content Simple Content Extension ! at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:146) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by:
Re: [Axis2] Good way of notifying the clients to say results are ready in asynchronous messaging
Hi Anne, Thanks for the reply. I already use WS-Addressing. Just wanted to make sure the correctness of my asynchronous communication design and, if any, to ask for a better solution. For example; I'm not sure if its suitable GetOpenAccountResultMsg to have a RelatesTo value that references to its first call. Also, I think that there must be a better way to say a client which service it must call to. Thanks again, Ali Sadik Kumlali --- Anne Thomas Manes [EMAIL PROTECTED] wrote: WS-Addressing. On 4/27/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote: Hi all, I want to send a notification message to my clients when their requests are processed and the results are ready. Then I expect them to call a service to acquire the results. Here is the sample scenario: server.wsdl - OpenAccount - input: OpenAccountMsg - GetOpenAccountResult - input: GetOpenAccountResultMsg - output: GetOpenAccountResultResponseMsg client.wsdl - ResultIsReady (input only) - input: ResultIsReadyMsg OpenAccountMsg (MessageId: A) Client - Server ResultIsReadyMsg (MessageId: B, RelatesTo: A) Client - Server GetOpenAccountResultMsg (MessageId: C, RelatesTo: A) Client - Server - GetOpenAccountResultResponseMsg (MessageId: D, RelatesTo: A) Here are the questions: 1) Do you see any flaw in this scenario? Or is there a common and standards based way to accomplish this kind of asynchronous communication? 2) I haven't found a good way to say my clients which service do they need to call for getting the results. I'm planning to put the name of result service name (GetOpenAccountResultMsg) in notification message (ResultIsReadyMsg). Could you please enlighten me? Any help would be great! Ali Sadik Kumlali __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[axis2] Stuck with JMS
Hi,I am trying to integrate JMS with Axis2 and can get around the following error:The MEP you are using http://www.w3.org/2004/08/wsdl/in-out has not implemented createClient().
My client looks as follows: Options options = new Options(); options.setTo(EPR); options.setAction(SERVICE_NAME.getLocalPart()); options.setTransportInProtocol
(Constants.TRANSPORT_JMS); ServiceClient loggingClient = new ServiceClient(getConfigContext(), clientService); loggingClient.engageModule(new QName(sample-logging-handler));
loggingClient.setOptions(options); loggingClient.sendReceiveNonBlocking(OPERATION_NAME, getPayload(), callback);I keep stumbling in this method:
AxisOperation: public OperationClient createClient(ServiceContext sc, Options options) { throw new UnsupportedOperationException(Messages.getMessage(mepnotyetimplemented, mepURI)); }
I am using Axis2 RC3.Any help would be greatly appreciated.Thomas
Re: Problem deploying axis
You can work around this problem by setting the following property for AdminService in server-config.wsdd to enable remote deployment. parameter name=enableRemoteAdmin value=true/ - Junaid Santunu Podder [EMAIL PROTECTED] com To axis-user@ws.apache.org 04/27/2006 05:49 cc AM Subject Problem deploying axis Please respond to [EMAIL PROTECTED] he.org Hi there, I am facing a problem deploying Axis on a linux server having a dual IP address. This is due to Axis's restriction of only allowing deployment from localhost. The server, I am trying to deploy on has 2 IP addresses and this is confusing AXIS into thinking that its a remote deployment. Has anyone faced this issue and if could let me know a probably solution. Thanks in advance, Santunu This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.
Re: Problem deploying axis
Thanks Junaid. I could get it working. [EMAIL PROTECTED] 27/04/2006 15:06 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Problem deploying axis You can work around this problem by setting the following property for AdminService in server-config.wsdd to enable remote deployment. parameter name=enableRemoteAdmin value=true/ - Junaid Santunu Podder [EMAIL PROTECTED] com To axis-user@ws.apache.org 04/27/2006 05:49 cc AM Subject Problem deploying axis Please respond to [EMAIL PROTECTED] he.org Hi there, I am facing a problem deploying Axis on a linux server having a dual IP address. This is due to Axis's restriction of only allowing deployment from localhost. The server, I am trying to deploy on has 2 IP addresses and this is confusing AXIS into thinking that its a remote deployment. Has anyone faced this issue and if could let me know a probably solution. Thanks in advance, Santunu This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. This email has been scanned for all viruses by the MessageLabs SkyScan service. This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.
Re: [axis2] Stuck with JMS
I actually did for hours ;-)The particularity of my case is that I am using a single axis2.xml for both client and server. On 4/27/06, Davanum Srinivas
[EMAIL PROTECTED] wrote:Please see the test cases :
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/
Thanks,dimsOn 4/27/06, Thomas Van de Velde [EMAIL PROTECTED] wrote: Hi, I am trying to integrate JMS with Axis2 and can get around the following
error: The MEP you are using http://www.w3.org/2004/08/wsdl/in-out has not implemented createClient(). My client looks as follows:
Options options = new Options(); options.setTo(EPR); options.setAction(SERVICE_NAME.getLocalPart()); options.setTransportInProtocol (
Constants.TRANSPORT_JMS); ServiceClient loggingClient = new ServiceClient(getConfigContext(), clientService); loggingClient.engageModule(new
QName(sample-logging-handler)); loggingClient.setOptions(options); loggingClient.sendReceiveNonBlocking(OPERATION_NAME, getPayload(), callback);
I keep stumbling in this method:AxisOperation: public OperationClient createClient(ServiceContext sc, Options options) { throw new UnsupportedOperationException(
Messages.getMessage(mepnotyetimplemented, mepURI)); } I am using Axis2 RC3. Any help would be greatly appreciated. Thomas
--Davanum Srinivas : http://wso2.com/blogs/
Making Axis work with HTTP/Basic authentication and a VB.Net client
I'm trying to do authentication for my Axis web service using HTTP/Basic over SSL, as this seemed to be the easiest option. The client is written in Visual Basic .Net 2005. I've added the HTTPAuthHandler to my WSDD file: ... service name=NtiAuth provider=java:RPC requestFlow handler type=java:org.apache.axis.handlers.http.HTTPAuthHandler/ handler type=soapmonitor/ /requestFlow responseFlow handler type=java:org.apache.axis.handlers.http.HTTPAuthHandler/ handler type=soapmonitor/ /responseFlow ... However no authentication is happening. The VB.Net client seems to be waiting for a 401 WWW-Authenticate Basic error from the server, to indicate that the server wants authentication. Axis isn't sending a 401 but is instead just happily giving me a null username and password. Does anyone know how I can persuade Axis to send back a 401 error? Kevin
Re: Making Axis work with HTTP/Basic authentication and a VB.Net client
The auth handler I have is defined outside the service as: handler name=Authenticate type=java:my.custom.AuthenticationHandler/The transport request flow is defined as: requestFlow handler type=URLMapper/ handler type=java:org.apache.axis.handlers.http.HTTPAuthHandler/ /requestFlow And each service has a request flow of: requestFlow handler type=Authenticate/ /requestFlowOn 4/27/06, Kevin O'Rourke [EMAIL PROTECTED] wrote: I'm trying to do authentication for my Axis web service using HTTP/Basicover SSL, as this seemed to be the easiest option.The client iswritten in Visual Basic .Net 2005.I've added the HTTPAuthHandler to my WSDD file: ... service name=NtiAuth provider=java:RPCrequestFlowhandler type=java:org.apache.axis.handlers.http.HTTPAuthHandler/handler type=soapmonitor/ /requestFlowresponseFlowhandler type=java:org.apache.axis.handlers.http.HTTPAuthHandler/handler type=soapmonitor//responseFlow ...However no authentication is happening.The VB.Net client seems to bewaiting for a 401 WWW-Authenticate Basic error from the server, toindicate that the server wants authentication.Axis isn't sending a 401 but is instead just happily giving me a null username and password.Does anyone know how I can persuade Axis to send back a 401 error?Kevin
Java console application using Axis2 to host WS-I BasicProfile services - is it possible?
Title: Java console application using Axis2 to host WS-I BasicProfile services - is it possible? I know from a previous post that Axis2 supports hosting services in non-webserver applications over other transports like TCP, JMS, etc. Is it also possible to host WS-I BasicProfile services (i.e. HTTP transport, text messages) outside the webserver? I ask because this is something that can be done in .Net using WinFX or using ASMX2 + WSE3 + XP SP2 (i.e. I can host the HTTP runtime in a host other than a formal webserver). I'm just curious if this is an option because I am designing a system where I need a stateful java application - non webserver-based, and want it to host services. The problem is I cannot require Axis on some of the known consumers, so I can't require all the clients to use TCP. Ideally, I would like to define multiple endpoints for the same service logic - one via tcp, the other via http. Is this possible in a console host using Axis2? Many thanks, Bob DeRemer Sr. Software Architect SAP Labs, LLC 350 Eagleview Blvd Exton, PA 19341 USA T1 +1.610.903.8000 x 136 T2 +1.717.505.7923 M +1.717.424.9595 E [EMAIL PROTECTED]
Re: [axis2] Stuck with JMS
Can you please check what we do in Utils.createSimpleServiceforClient?
the return from there is used as a parameter to the ServiceClient
thanks,
dims
On 4/27/06, Thomas Van de Velde [EMAIL PROTECTED] wrote:
I actually did for hours ;-)
The particularity of my case is that I am using a single axis2.xml for both
client and server.
On 4/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Please see the test cases :
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/
Thanks,
dims
On 4/27/06, Thomas Van de Velde [EMAIL PROTECTED] wrote:
Hi,
I am trying to integrate JMS with Axis2 and can get around the following
error:
The MEP you are using
http://www.w3.org/2004/08/wsdl/in-out has not
implemented
createClient().
My client looks as follows:
Options options = new Options();
options.setTo(EPR);
options.setAction(SERVICE_NAME.getLocalPart());
options.setTransportInProtocol ( Constants.TRANSPORT_JMS);
ServiceClient loggingClient = new
ServiceClient(getConfigContext(),
clientService);
loggingClient.engageModule(new
QName(sample-logging-handler));
loggingClient.setOptions(options);
loggingClient.sendReceiveNonBlocking(OPERATION_NAME,
getPayload(),
callback);
I keep stumbling in this method:
AxisOperation:
public OperationClient createClient(ServiceContext sc, Options
options)
{
throw new
UnsupportedOperationException(
Messages.getMessage(mepnotyetimplemented,
mepURI));
}
I am using Axis2 RC3.
Any help would be greatly appreciated.
Thomas
--
Davanum Srinivas : http://wso2.com/blogs/
--
Davanum Srinivas : http://wso2.com/blogs/
Ignore unknown elements
Hello, we are using Axis for accessing a web service that changes from time to time. Quite often, new elements are added to the WSDL that are not relevant to our client and could safely be ignored. However, Axis always throws an exception when encountering unknown elements. Is there a setting so that Axis simply ignores any unknown elements? Thanks for your help Wolfhart Bauer
Re: [axis2] Stuck with JMS
I did the following:AxisService clientService = getConfigContext().getAxisConfiguration().getService(GreetingService);ServiceClient loggingClient = new ServiceClient(getConfigContext(), clientService);
Thanks for your help!On 4/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Can you please check what we do in Utils.createSimpleServiceforClient?the return from there is used as a parameter to the ServiceClientthanks,dimsOn 4/27/06, Thomas Van de Velde
[EMAIL PROTECTED] wrote: I actually did for hours ;-) The particularity of my case is that I am using a single axis2.xml for both client and server.
On 4/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Please see the test cases :
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/ Thanks, dims On 4/27/06, Thomas Van de Velde
[EMAIL PROTECTED] wrote: Hi, I am trying to integrate JMS with Axis2 and can get around the following error:
The MEP you are using http://www.w3.org/2004/08/wsdl/in-out has not implemented createClient().
My client looks as follows: Options options = new Options(); options.setTo(EPR);
options.setAction(SERVICE_NAME.getLocalPart()); options.setTransportInProtocol ( Constants.TRANSPORT_JMS); ServiceClient loggingClient = new
ServiceClient(getConfigContext(), clientService); loggingClient.engageModule(new QName(sample-logging-handler));
loggingClient.setOptions(options); loggingClient.sendReceiveNonBlocking(OPERATION_NAME, getPayload(),
callback); I keep stumbling in this method:AxisOperation: public OperationClient createClient(ServiceContext sc, Options
options) { throw new UnsupportedOperationException( Messages.getMessage(mepnotyetimplemented, mepURI)); }
I am using Axis2 RC3. Any help would be greatly appreciated. Thomas
-- Davanum Srinivas : http://wso2.com/blogs/ --Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] OMElement question
And so, at now, it's not possible, is it? If it is, can anybody show me
a very simple example of how to use custom objects as arguments (or
return value) of ws methods?
Thanks,
Michele
Dennis Sosnoski wrote:
You basically need an interface layer between the JAXB objects and the
Axis2 code. This interface code can potentially be generated for you
using the WSDL2Java tool provided by Axis2, but doing this requires a
JAXB extension for WSDL2Java. This doesn't currently exist, so you'd
need to do the conversions yourself, and Ajith is suggesting that you
look at how the code generated for other data binding frameworks is
structured so you can understand what needs to be done.
I'm planning to add JAXB 2.0 support within the next month or so. It
should be reasonably easy at this point, since the JAXB issues are very
similar to those I've dealt with for JiBX data binding. I believe there
are license issues which will prevent this actually becoming part of the
Axis2 project, but I'm sure we'll link it from the Axis2 site once the
JAXB add-on is available.
- Dennis
Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
Michele Mazzucco wrote:
Hi Ajith,
I'm sorry, but can you be more clear, please? Could you show me a
practical example?
Thanks,
Michele
Ajith Ranabahu wrote:
Hi,
yes this is possible :) Axis2 explicitly allows any databinding to be
plugged in and infact if you codegen for different frameworks like
xmlbeans/adb/jaxme you'll see how the codegenerator generates the
skeletons referring to the generated databinding classes.
if you are doing it by hand then you'll have to write your custom
message receiver and write the fromOM and toOM conversion methods as
well (the implementation of these methods are dependent on the
databinding framework)
My guess is the best choice for you would be to run the codegen with
XMLbeans and look at the generated code. You can then replace the
necessary classes and rewrite the conversion methods.
On 4/25/06, Michele Mazzucco [EMAIL PROTECTED] wrote:
Hi all,
starting from an xml schema, I generate Java classes with JAXB. Now the
question is, can I use those objects as return type or method
argument(s) of my web service methods or I must use exclusively
OMElement objects?
i.e.
say, for an in-out operation, I generate two classes from the xml
schema, RequestObject and ReplyObject. Which of the two options is the
correct one?,
// web service method
ReplyObject fooMethod(RequestObject arg) {
...
}
or
OMElement fooMethod(OMElement arg) {
...
}
Thanks,
Michele
--
Ajith Ranabahu
Re: [axis2] Stuck with JMS
I have changed the client so to be more clisely to the unit test you pointed me to.Now I have:AxisService clientService = Utils.createSimpleServiceforClient(SERVICE_NAME, GreetingService.class.getName
(), OPERATION_NAME);ServiceClient loggingClient = new ServiceClient(getConfigContext(), clientService);an I get a nullpointer :-(java.lang.NullPointerException
at org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:59)On 4/27/06, Thomas Van de Velde
[EMAIL PROTECTED] wrote:I did the following:
AxisService clientService = getConfigContext().getAxisConfiguration().getService(GreetingService);ServiceClient loggingClient = new ServiceClient(getConfigContext(), clientService);
Thanks for your help!On 4/27/06,
Davanum Srinivas [EMAIL PROTECTED] wrote:
Can you please check what we do in Utils.createSimpleServiceforClient?the return from there is used as a parameter to the ServiceClientthanks,dimsOn 4/27/06, Thomas Van de Velde
[EMAIL PROTECTED] wrote: I actually did for hours ;-) The particularity of my case is that I am using a single axis2.xml for both client and server.
On 4/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Please see the test cases :
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/ Thanks, dims On 4/27/06, Thomas Van de Velde
[EMAIL PROTECTED] wrote: Hi, I am trying to integrate JMS with Axis2 and can get around the following
error:
The MEP you are using http://www.w3.org/2004/08/wsdl/in-out
has not implemented createClient().
My client looks as follows: Options options = new Options(); options.setTo(EPR);
options.setAction(SERVICE_NAME.getLocalPart()); options.setTransportInProtocol ( Constants.TRANSPORT_JMS); ServiceClient loggingClient = new
ServiceClient(getConfigContext(), clientService); loggingClient.engageModule(new QName(sample-logging-handler));
loggingClient.setOptions(options); loggingClient.sendReceiveNonBlocking(OPERATION_NAME, getPayload(),
callback); I keep stumbling in this method:AxisOperation: public OperationClient createClient(ServiceContext sc, Options
options) { throw new UnsupportedOperationException( Messages.getMessage(mepnotyetimplemented, mepURI)); }
I am using Axis2 RC3. Any help would be greatly appreciated. Thomas
-- Davanum Srinivas : http://wso2.com/blogs/ --
Davanum Srinivas : http://wso2.com/blogs/
Re: [axis2] Stuck with JMS
Please try using 2 separate axis2.xml's just like in the test case,
once u get that working then try other things :)
thanks,
dims
On 4/27/06, Thomas Van de Velde [EMAIL PROTECTED] wrote:
I have changed the client so to be more clisely to the unit test you pointed
me to.
Now I have:
AxisService clientService =
Utils.createSimpleServiceforClient(SERVICE_NAME,
GreetingService.class.getName (),
OPERATION_NAME);
ServiceClient loggingClient = new
ServiceClient(getConfigContext(),
clientService);
an I get a nullpointer :-(
java.lang.NullPointerException
at
org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:59)
On 4/27/06, Thomas Van de Velde [EMAIL PROTECTED] wrote:
I did the following:
AxisService clientService =
getConfigContext().getAxisConfiguration().getService(GreetingService);
ServiceClient loggingClient = new
ServiceClient(getConfigContext(), clientService);
Thanks for your help!
On 4/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Can you please check what we do in
Utils.createSimpleServiceforClient?
the return from there is used as a parameter to the ServiceClient
thanks,
dims
On 4/27/06, Thomas Van de Velde [EMAIL PROTECTED] wrote:
I actually did for hours ;-)
The particularity of my case is that I am using a single axis2.xml for
both
client and server.
On 4/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Please see the test cases :
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/
Thanks,
dims
On 4/27/06, Thomas Van de Velde [EMAIL PROTECTED] wrote:
Hi,
I am trying to integrate JMS with Axis2 and can get around the
following
error:
The MEP you are using
http://www.w3.org/2004/08/wsdl/in-out has not
implemented
createClient().
My client looks as follows:
Options options = new Options();
options.setTo(EPR);
options.setAction(SERVICE_NAME.getLocalPart());
options.setTransportInProtocol (
Constants.TRANSPORT_JMS);
ServiceClient loggingClient = new
ServiceClient(getConfigContext(),
clientService);
loggingClient.engageModule(new
QName(sample-logging-handler));
loggingClient.setOptions(options);
loggingClient.sendReceiveNonBlocking(OPERATION_NAME,
getPayload(),
callback);
I keep stumbling in this method:
AxisOperation:
public OperationClient createClient(ServiceContext sc, Options
options)
{
throw new
UnsupportedOperationException(
Messages.getMessage(mepnotyetimplemented,
mepURI));
}
I am using Axis2 RC3.
Any help would be greatly appreciated.
Thomas
--
Davanum Srinivas : http://wso2.com/blogs/
--
Davanum Srinivas : http://wso2.com/blogs/
--
Davanum Srinivas : http://wso2.com/blogs/
Re: axis-schema.jar
It's used for the xmlbeans serializer/de-serializer. don't need it otherwise -- dims On 4/27/06, Mukundan Desikan [EMAIL PROTECTED] wrote: Guys, Does any one know why theaxis-schema.jar is included in the axis lib folder.Is it required for Axis runtime? If yes whats its needed for. Thanks Mukund -- Davanum Srinivas : http://wso2.com/blogs/
Re: WS-Security implicit header
Hi Stanley, On 4/27/06, Stanley Stanev [EMAIL PROTECTED] wrote: yes, that's what I was referring I aksed Axis already, but do you know by chance if I am able to generate a WSDL that contains my own implicit headers using Axis 1.x? I don't think you can generate such a WSDL with Axis 1.x where is defines headers to be included maybe an Axis 1.x expert can please correct me on this of I'm wrong? (CCed to Axis-user list) Thanks, Ruchith
Re: [Axis2] Good way of notifying the clients to say results are ready in asynchronous messaging
Hello Ali, I'm sure Anne is correct! I can't comment because I haven't used WS-Addressing yet. :-) I'll just share what I did. Hope I understood your design problem. I defined a register port name. Clients must call this and give me an application name, a session identifier and a URL. These are all specific to our apps. I register the URL. When I want to notify that client, I call him back on the URL he registered. I defined the web service. Clients must implement it. So I know what port name to call, what arguments to pass. The only thing is that arbitrary clients can set the URL to be the service end point on which they publish the service that I'll call in the call back. I'm sure WS-Addressing is a better way to do it. :-) Something I need to learn! Vartan --- Anne Thomas Manes [EMAIL PROTECTED] wrote: WS-Addressing. On 4/27/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote: Hi all, I want to send a notification message to my clients when their requests are processed and the results are ready. Then I expect them to call a service to acquire the results. Here is the sample scenario: server.wsdl - OpenAccount - input: OpenAccountMsg - GetOpenAccountResult - input: GetOpenAccountResultMsg - output: GetOpenAccountResultResponseMsg client.wsdl - ResultIsReady (input only) - input: ResultIsReadyMsg OpenAccountMsg (MessageId: A) Client - Server ResultIsReadyMsg (MessageId: B, RelatesTo: A) Client - Server GetOpenAccountResultMsg (MessageId: C, RelatesTo: A) Client - Server - GetOpenAccountResultResponseMsg (MessageId: D, RelatesTo: A) Here are the questions: 1) Do you see any flaw in this scenario? Or is there a common and standards based way to accomplish this kind of asynchronous communication? 2) I haven't found a good way to say my clients which service do they need to call for getting the results. I'm planning to put the name of result service name (GetOpenAccountResultMsg) in notification message (ResultIsReadyMsg). Could you please enlighten me? Any help would be great! Ali Sadik Kumlali __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[Axis2] Spring + Axis2 0.95 help
Hello there! I've seen some implementations of how to plug Spring + Axis2 here. I have a few questions.1st. Isn't it possible to use something like we had on Axis 1.x? I mean just a class that could have access to ServletContext? All I need is the Servlet context :( 2nd. I've seen a post taliking about using an ObjectFactory in my WebServices, but if I have a factory been instantiated by Spring Listener why bother having another one?If someone here is using Axis2+Spring would you mind sharing your solution? Best RegardsPS:Shouldn't it be a topic on the wiki?
[Axis2] Embebedding Axis2 on current WebApp
Hello, is it possible to use Axis2 administration web module on my current web application? I mean I'd like to have http://host/myapp/admin.jsp and not http://host/axis2/admin.jspIs it possible?Regards
[Axis2] wsdl2java problem?
hi,
i'm using the axis2 wsdl2java tool (axis2 version 1.0-RC2) with xmlbeans
databinding to generate my skeletons from the attached wsdl file.
i don't know why, but i guess the wrong skeleton is generated, since the
methods of the skeletons only contain OMElement as input parameter and
return values. nevertheless, the xmlbeans are created correctly but they
aren't used in the skeleton as paramters.
The wsdl file and the generted skeleton are attached and i'm using the
following ant snippet to invoke wsdl2java:
target name=wsdl2java depends=clean,prepare
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath/
arg value=-uri/
arg file=wsdl/QoSBroker.wsdl/
arg value=-ss/
arg value=-sd/
arg value=-o/
arg file=${basedir}/
arg value=-d /
arg value=xmlbeans /
arg value=-p/
arg value=at.ac.tuwien.vitalab.vieqos/
/java
!-- Move the schema folder to classpath--
move todir=${build.classes}
fileset dir=${build.dir}
include name=**/*schema*/**/*.class/
include name=**/*schema*/**/*.xsb/
/fileset
/move
/target
any help is appreciated. hopefully i'm only missing some small stuff ;-)
best regards,
florian
--
Florian Rosenberg
University Assistant - Vienna University of Technology
Distributed Systems Group (DSG), Information Systems Institute
A-1040 Wien, Argentinierstrasse 8/184-1
Tel: +43-1-58801-18418
Fax: +43-1-58801-18491
mail: [EMAIL PROTECTED]
www: http://www.infosys.tuwien.ac.at/Staff/rosenberg/
/**
* VieQoSBrokerSkeleton.java
*
* This file was auto-generated from WSDL
* by the Apache Axis2 version: 1.0-RC2 Apr 23, 2006 (05:20:08 IST)
*/
package at.ac.tuwien.vitalab.vieqos;
/**
* VieQoSBrokerSkeleton java skeleton for the axisService
*/
public class VieQoSBrokerSkeleton {
/**
* Auto generated method signature
* @param param0
*/
public org.apache.axiom.om.OMElement AddServiceQoS
(org.apache.axiom.om.OMElement param0 )
{
//Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
/**
* Auto generated method signature
* @param param2
*/
public org.apache.axiom.om.OMElement RemoveServiceQoS
(org.apache.axiom.om.OMElement param2 )
{
//Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
/**
* Auto generated method signature
* @param param4
*/
public org.apache.axiom.om.OMElement QueryQoS
(org.apache.axiom.om.OMElement param4 )
{
//Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
}
?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:tns=http://www.vitalab.tuwien.ac.at/VieQoS;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:wsa=http://www.w3.org/2005/08/addressing;
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
name=VieQoSBroker
targetNamespace=http://www.vitalab.tuwien.ac.at/VieQoS;
wsdl:types
xsd:schema
targetNamespace=http://www.vitalab.tuwien.ac.at/VieQoS;
xsd:import namespace=http://www.w3.org/2005/08/addressing;
schemaLocation=schemas/ws-addr.xsd /
xsd:import
namespace=http://schemas.xmlsoap.org/ws/2004/09/policy;
schemaLocation=schemas/policy-2006-03-01-RC1.xsd /
xsd:complexType name=QoSQueryType
xsd:sequence
xsd:element name=serviceAddress
type=wsa:EndpointReferenceType /
xsd:element ref=wsp:Policy /
/xsd:sequence
/xsd:complexType
/xsd:schema
/wsdl:types
wsdl:message name=QoSQueryResponse
wsdl:part type=tns:QoSQueryType name=response /
/wsdl:message
wsdl:message name=QoSQueryRequest
wsdl:part type=tns:QoSQueryType name=request /
/wsdl:message
wsdl:message name=AddServiceQoSResponse
wsdl:part name=response type=tns:QoSQueryType/wsdl:part
/wsdl:message
wsdl:message name=AddServiceQoSRequest
wsdl:part name=request type=tns:QoSQueryType/wsdl:part
/wsdl:message
wsdl:message name=RemoveServiceQoSResponse
wsdl:part name=response type=tns:QoSQueryType/wsdl:part
/wsdl:message
wsdl:message name=RemoveServiceQoSRequest
wsdl:part name=request type=tns:QoSQueryType/wsdl:part
Re: Java console application using Axis2 to host WS-I BasicProfile services - is it possible?
Please see modules\core\src\org\apache\axis2\transport\tcp\TCPServer.java modules\core\src\org\apache\axis2\transport\mail\SimpleMailListener.java modules\core\src\org\apache\axis2\transport\jms\SimpleJMSListener.java modules\core\src\org\apache\axis2\transport\http\SimpleHTTPServer.java thanks, dims On 4/27/06, DeRemer, Bob [EMAIL PROTECTED] wrote: I know from a previous post that Axis2 supports hosting services in non-webserver applications over other transports like TCP, JMS, etc. Is it also possible to host WS-I BasicProfile services (i.e. HTTP transport, text messages) outside the webserver? I ask because this is something that can be done in .Net using WinFX or using ASMX2 + WSE3 + XP SP2 (i.e. I can host the HTTP runtime in a host other than a formal webserver). I'm just curious if this is an option because I am designing a system where I need a stateful java application - non webserver-based, and want it to host services. The problem is I cannot require Axis on some of the known consumers, so I can't require all the clients to use TCP. Ideally, I would like to define multiple endpoints for the same service logic - one via tcp, the other via http. Is this possible in a console host using Axis2? Many thanks, Bob DeRemer Sr. Software Architect SAP Labs, LLC 350 Eagleview Blvd Exton, PA 19341 USA T1 +1.610.903.8000 x 136 T2 +1.717.505.7923 M +1.717.424.9595 E[EMAIL PROTECTED] -- Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] Embebedding Axis2 on current WebApp
Hello, is it possible to use Axis2 administration web module on my current web application? I mean I'd like to have http://host/myapp/admin.jsp and not http://host/axis2/admin.jsp While the detailed HOWTO is still on my list here is what you should do: - Get the latest snapshot axis2.war. - Unzip it - Remove META-INF from extracted contents - Add all content to your web app excluding WEB-INF/web.xml - Add axis2 relevant sections to your own web.xml from axis2.war web.xml While this works axis2 should support adding webservices without unzipping axis2.war. Please note that axis admin got moved to a sub directory for better embeddability.
Re: [Axis2] wsdl2java problem?
I tried running your wsdl, but I'm having some problems on your
external schema reference to policy-2006-03-01-RC1.xsd . I found a
version in googIe, but then got stuck on ws-addr.xsd . Could you
upload all your external xsd files please ?
Robert
http://www.braziloutsource.com/On 4/27/06, Florian Rosenberg
[EMAIL PROTECTED] wrote:hi,i'm using the axis2 wsdl2java tool (axis2 version
1.0-RC2) with xmlbeansdatabinding to generate my skeletons from the attached wsdl file.i don't know why, but i guess the wrong skeleton is generated, since themethods of the skeletons only contain OMElement as input parameter and
return values. nevertheless, the xmlbeans are created correctly but theyaren't used in the skeleton as paramters.The wsdl file and the generted skeleton are attached and i'm using thefollowing ant snippet to invoke wsdl2java:
target name=wsdl2java depends=clean,preparejava classname=org.apache.axis2.wsdl.WSDL2Java fork=trueclasspath refid=
axis.classpath/arg value=-uri/arg file=wsdl/QoSBroker.wsdl/arg value=-ss/arg value=-sd/
arg value=-o/arg file=${basedir}/arg value=-d /arg value=xmlbeans /arg value=-p/
arg value=at.ac.tuwien.vitalab.vieqos//java!-- Move the schema folder to classpath--move todir=${build.classes}
fileset dir=${build.dir}include
name=**/*schema*/**/*.class/include
name=**/*schema*/**/*.xsb//fileset/move /targetany help is appreciated. hopefully i'm only missing some small stuff ;-)best regards,
florian--Florian RosenbergUniversity Assistant - Vienna University of TechnologyDistributed Systems Group (DSG), Information Systems InstituteA-1040 Wien, Argentinierstrasse 8/184-1
Tel:+43-1-58801-18418Fax: +43-1-58801-18491mail: [EMAIL PROTECTED]www: http://www.infosys.tuwien.ac.at/Staff/rosenberg/
/** * VieQoSBrokerSkeleton.java * * This file was auto-generated from WSDL * by the Apache Axis2 version: 1.0-RC2 Apr 23, 2006 (05:20:08 IST) */package
at.ac.tuwien.vitalab.vieqos;/** *VieQoSBrokerSkeleton java skeleton for the axisService */public class VieQoSBrokerSkeleton {/** * Auto generated method signature
* @param param0 */publicorg.apache.axiom.om.OMElement AddServiceQoS(org.apache.axiom.om.OMElement
param0 ) {//Todo
fill this with the necessary business logicthrow
newjava.lang.UnsupportedOperationException();}/** * Auto generated method signature* @param param2 */publicorg.apache.axiom.om.OMElement
RemoveServiceQoS(org.apache.axiom.om.OMElement
param2 ) {//Todo
fill this with the necessary business logicthrow
newjava.lang.UnsupportedOperationException();}/** * Auto generated method signature* @param param4 */publicorg.apache.axiom.om.OMElement
QueryQoS(org.apache.axiom.om.OMElement
param4 ) {//Todo
fill this with the necessary business logicthrow
newjava.lang.UnsupportedOperationException();}}
Re: [Axis2] wsdl2java problem?
hi,
sorry, i forgot. attached are the schemas.
thanks,
florian
robert lazarski wrote:
I tried running your wsdl, but I'm having some problems on your external
schema reference to policy-2006-03-01-RC1.xsd . I found a version in
googIe, but then got stuck on ws-addr.xsd . Could you upload all your
external xsd files please ?
Robert
http://www.braziloutsource.com/
On 4/27/06, *Florian Rosenberg* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
hi,
i'm using the axis2 wsdl2java tool (axis2 version 1.0-RC2) with xmlbeans
databinding to generate my skeletons from the attached wsdl file.
i don't know why, but i guess the wrong skeleton is generated, since the
methods of the skeletons only contain OMElement as input parameter and
return values. nevertheless, the xmlbeans are created correctly but they
aren't used in the skeleton as paramters.
The wsdl file and the generted skeleton are attached and i'm using the
following ant snippet to invoke wsdl2java:
target name=wsdl2java depends=clean,prepare
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid= axis.classpath/
arg value=-uri/
arg file=wsdl/QoSBroker.wsdl/
arg value=-ss/
arg value=-sd/
arg value=-o/
arg file=${basedir}/
arg value=-d /
arg value=xmlbeans /
arg value=-p/
arg value=at.ac.tuwien.vitalab.vieqos/
/java
!-- Move the schema folder to classpath--
move todir=${build.classes}
fileset dir=${build.dir}
include name=**/*schema*/**/*.class/
include name=**/*schema*/**/*.xsb/
/fileset
/move
/target
any help is appreciated. hopefully i'm only missing some small stuff ;-)
best regards,
florian
--
Florian Rosenberg
University Assistant - Vienna University of Technology
Distributed Systems Group (DSG), Information Systems Institute
A-1040 Wien, Argentinierstrasse 8/184-1
Tel: +43-1-58801-18418
Fax: +43-1-58801-18491
mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
www: http://www.infosys.tuwien.ac.at/Staff/rosenberg/
http://www.infosys.tuwien.ac.at/Staff/rosenberg/
/**
* VieQoSBrokerSkeleton.java
*
* This file was auto-generated from WSDL
* by the Apache Axis2 version: 1.0-RC2 Apr 23, 2006 (05:20:08 IST)
*/
package at.ac.tuwien.vitalab.vieqos;
/**
* VieQoSBrokerSkeleton java skeleton for the axisService
*/
public class VieQoSBrokerSkeleton {
/**
* Auto generated method signature
* @param param0
*/
public org.apache.axiom.om.OMElement AddServiceQoS
(org.apache.axiom.om.OMElement param0 )
{
//Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
/**
* Auto generated method signature
* @param param2
*/
public org.apache.axiom.om.OMElement RemoveServiceQoS
(org.apache.axiom.om.OMElement param2 )
{
//Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
/**
* Auto generated method signature
* @param param4
*/
public org.apache.axiom.om.OMElement QueryQoS
(org.apache.axiom.om.OMElement param4 )
{
//Todo fill this with the necessary business logic
throw new java.lang.UnsupportedOperationException();
}
}
?xml version=1.0 encoding=UTF-8?
!--
OASIS takes no position regarding the validity or scope of any intellectual
property or other rights that might be claimed to pertain to the implementation
or use of the technology described in this document or the extent to which any
license under such rights might or might not be available; neither does it
represent that it has made any effort to identify any such rights. Information
on OASIS's procedures with respect to rights in OASIS specifications can be
found at the OASIS website. Copies of claims of rights made available for
publication and any assurances of licenses to be made available, or the result
of an attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this specification, can be
obtained from the OASIS Executive Director.
OASIS invites any interested party to bring to its attention any copyrights,
patents or
Re: WS-Security implicit header
Stanley,The WSDL should define the bits that the application code needs to know about. It should *not* define the bits that the infrastructure (e.g., handlers and intermediaries) is responsible for implementing (i.e ., headers). The infrastructure requirements should be defined using WS-Policy. Now, admittedly, WS-Policy is not yet a standard, and it has limited support by application platforms, but that doesn't change the fact that you really shouldn't define your headers in the WSDL. By the way -- yesterday W3C acknowlegded the submission of the WS-Policy specifications (WS-Policy and WS-PolicyAttachments).See http://www.w3.org/Submission/2006/06/ . On 4/27/06, Ruchith Fernando [EMAIL PROTECTED] wrote:Hi Stanley,On 4/27/06, Stanley Stanev [EMAIL PROTECTED] wrote: yes, that's what I was referring I aksed Axis already, but do you know by chance if I am able to generate a WSDL that contains my own implicit headers using Axis 1.x?I don't think you can generate such a WSDL with Axis 1.x where isdefines headers to be included maybe an Axis 1.x expert canplease correct me on this of I'm wrong? (CCed to Axis-user list) Thanks,Ruchith-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Good way of notifying the clients to say results are ready in asynchronous messaging
Hi Rodrigo, Thank you very much for taking your time and sharing your thoughts with me. I forgot to mention that I already used WS-Addressing. Sorry for that. Actually, after Anne's reply, I looked at the spec and noticed that I needed to spend more time on WS-Addressing :-) If you don't mind I need to ask some questions regarding your reply. 2) The solution you are considering is basically correct, but putting and EndPointReference to the service will be better than a simple service name. Shortly, it will safe you some programming at the client side if you get a ready-to-use EPR ;-) Do you mean that I should use something like this: wsa:EndpointReference wsa:Addressxs:anyURI/wsa:Address wsa:ReferenceProperties... /wsa:ReferenceProperties wsa:ReferenceParameters... /wsa:ReferenceParameters wsa:PortTypexs:QName/wsa:PortType wsa:ServiceName PortName=xs:NCNamexs:QName/wsa:ServiceName wsp:Policy ... /wsp:Policy /wsa:EndpointReference If yes, where should I put this in WSDL? And how do I add it to my ResultIsReadyMsg? Some thoughts about your description: - You should include an EPR in OpenAccountMsg, pointing to the service Do you mean the client need to add wsa:ReplyTo in OpenAccountMsg? If yes, how can I enforce it in WSDL? - Why do not you include the results in the event notification itself? I want the client.wsdl to be as simple as possible. Since I provide GetXResult services for all the asynchronous services (X), clients already know how to handle the responses. I thought that it would be extra work for them implementing AcceptXResult services, too. You might say me to only use AcceptXResult in client.wsdl and remove GetXResult from the server.wsdl. But, I have to provide GetXResult services to handle notification error situations. Thus, the clients will be able to query if they somehow haven't got the notification message yet. Again, thank you very much for your valuable comments. Best regards, Ali Sadik Kumlali --- Rodrigo Ruiz [EMAIL PROTECTED] wrote: Ali, 1) The scenario you describe seems correct to me. Event Notification is a rather common pattern, and some specifications that can be of help are WS-Eventing and WS-BaseNotification. Anyway, your scenario is simple enough for, as Anne stated, WS-Addressing being enough to implement it. 2) The solution you are considering is basically correct, but putting and EndPointReference to the service will be better than a simple service name. Shortly, it will safe you some programming at the client side if you get a ready-to-use EPR ;-) Some thoughts about your description: - You should include an EPR in OpenAccountMsg, pointing to the service that will receive the notification in the client side. - Why do not you include the results in the event notification itself? Regards, Rodrigo Ruiz Anne Thomas Manes wrote: WS-Addressing. On 4/27/06, *Ali Sadik Kumlali* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, I want to send a notification message to my clients when their requests are processed and the results are ready. Then I expect them to call a service to acquire the results. Here is the sample scenario: server.wsdl - OpenAccount - input: OpenAccountMsg - GetOpenAccountResult - input: GetOpenAccountResultMsg - output: GetOpenAccountResultResponseMsg client.wsdl - ResultIsReady (input only) - input: ResultIsReadyMsg OpenAccountMsg (MessageId: A) Client - Server ResultIsReadyMsg (MessageId: B, RelatesTo: A) Client - Server GetOpenAccountResultMsg (MessageId: C, RelatesTo: A) Client - Server - GetOpenAccountResultResponseMsg (MessageId: D, RelatesTo: A) Here are the questions: 1) Do you see any flaw in this scenario? Or is there a common and standards based way to accomplish this kind of asynchronous communication? 2) I haven't found a good way to say my clients which service do they need to call for getting the results. I'm planning to put the name of result service name (GetOpenAccountResultMsg) in notification message (ResultIsReadyMsg). Could you please enlighten me? Any help would be great! Ali Sadik Kumlali __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com No virus
Axis2: JavaMail / ClassLoader issue
Axis team, I just wanted to summarize the problem we faced recently and check with you the possible alternatives. We have just finished packaging a web-service that simply sends email. The main problem is that we had to use the Sun distribution of javamail and jaf. Thus our service hierarchy looks like: Service.aar |_lib |_mail.jar |_jaf.jar |_... However since Axis2 shipped by default with geronimo-javamail and geronimo-activation which are not yet complete, there is class issue at runtime. In order to workaround this problem, we created our own class loader to redirect javax.mail and javax.activation to the correct classes. We unfortunately had no luck with this approach as we can only set the Service class loader and we don't have access to the classloader that loads initially the javax.mail libraries from the geronimo jars: - AxisService service = msgContext.getOperationContext().getServiceContext().getAxisService(); service.setClassLoader(myOwnStuff); - The only workaround so far is to replace in the Axis2 distribution the geronimo jars with the sun jars. I hope I succeeded in describing the problem as it is not a common one nor an easy one. I have two questions: 1- is it possible to have access to the ClassLoader that loads initially the Axis2 libraries ? 2- if not, is it possible to ship Axis2 with the Sun libraries. I haven't seen something that would prevent to distribute it in the license. Many thanks, Arnaud
WSDL2Java: Type EndpointReferenceType is referenced but not defined
Hi Everyone,
I'm new to axis (and web services) and I'm in the
process of trying to implement a web service. I have
a wsdl file (wsdir.wsdl attached) describing the
service and I'm currently trying to create a skeleton
Java code using WSDL2Java. However when I run
WSDL2Java I get the following error message.
# java org.apache.axis.wsdl.WSDL2Java --server-side
--skeletonDeploy true wsdir.wsdl
{http://www.w3.org/2005/03/addressing}EndpointReference
already exists
{http://www.w3.org/2005/03/addressing}EndpointReferenceType
already exists
{http://www.w3.org/2005/03/addressing}ReferenceParametersType
already exists
{http://www.w3.org/2005/03/addressing}Metadata already
exists
{http://www.w3.org/2005/03/addressing}MetadataType
already exists
{http://www.w3.org/2005/03/addressing}MessageID
already exists
{http://www.w3.org/2005/03/addressing}RelatesTo
already exists
{http://www.w3.org/2005/03/addressing}RelatesToType
already exists
{http://www.w3.org/2005/03/addressing}RelationshipTypeOpenEnum
already exists
{http://www.w3.org/2005/03/addressing}RelationshipType
already exists
{http://www.w3.org/2005/03/addressing}ReplyTo already
exists
{http://www.w3.org/2005/03/addressing}From already
exists
{http://www.w3.org/2005/03/addressing}FaultTo already
exists
{http://www.w3.org/2005/03/addressing}To already
exists
{http://www.w3.org/2005/03/addressing}Action already
exists
{http://www.w3.org/2005/03/addressing}AttributedURIType
already exists
{http://www.w3.org/2005/03/addressing}isReferenceParameter
already exists
{http://www.w3.org/2005/03/addressing}FaultCodesOpenEnumType
already exists
{http://www.w3.org/2005/03/addressing}FaultCodesType
already exists
{http://www.w3.org/2005/03/addressing}RetryAfter
already exists
{http://www.w3.org/2005/03/addressing}AttributedNonNegativeIntegerType
already exists
java.io.IOException: Type EndpointReferenceType is
referenced but not defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Thread.java:595)
I searched the archives and found people with similar
error messages to me but I'm still having trouble
figuring out how to fix it. Can somebody tell me what
I'm doing wrong? Thanks in advance.
-Jason
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: WSDL2Java: Type EndpointReferenceType is referenced but not defined
Hi Everyone,
I forgot to attach the wsdl and xsd documents to my
original post. Sorry.
-Ben
--- Jason Sweek [EMAIL PROTECTED] wrote:
Hi Everyone,
I'm new to axis (and web services) and I'm in the
process of trying to implement a web service. I
have
a wsdl file (wsdir.wsdl attached) describing the
service and I'm currently trying to create a
skeleton
Java code using WSDL2Java. However when I run
WSDL2Java I get the following error message.
# java org.apache.axis.wsdl.WSDL2Java --server-side
--skeletonDeploy true wsdir.wsdl
{http://www.w3.org/2005/03/addressing}EndpointReference
already exists
{http://www.w3.org/2005/03/addressing}EndpointReferenceType
already exists
{http://www.w3.org/2005/03/addressing}ReferenceParametersType
already exists
{http://www.w3.org/2005/03/addressing}Metadata
already
exists
{http://www.w3.org/2005/03/addressing}MetadataType
already exists
{http://www.w3.org/2005/03/addressing}MessageID
already exists
{http://www.w3.org/2005/03/addressing}RelatesTo
already exists
{http://www.w3.org/2005/03/addressing}RelatesToType
already exists
{http://www.w3.org/2005/03/addressing}RelationshipTypeOpenEnum
already exists
{http://www.w3.org/2005/03/addressing}RelationshipType
already exists
{http://www.w3.org/2005/03/addressing}ReplyTo
already
exists
{http://www.w3.org/2005/03/addressing}From already
exists
{http://www.w3.org/2005/03/addressing}FaultTo
already
exists
{http://www.w3.org/2005/03/addressing}To already
exists
{http://www.w3.org/2005/03/addressing}Action already
exists
{http://www.w3.org/2005/03/addressing}AttributedURIType
already exists
{http://www.w3.org/2005/03/addressing}isReferenceParameter
already exists
{http://www.w3.org/2005/03/addressing}FaultCodesOpenEnumType
already exists
{http://www.w3.org/2005/03/addressing}FaultCodesType
already exists
{http://www.w3.org/2005/03/addressing}RetryAfter
already exists
{http://www.w3.org/2005/03/addressing}AttributedNonNegativeIntegerType
already exists
java.io.IOException: Type EndpointReferenceType is
referenced but not defined.
at
org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:665)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
at
org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at
org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Thread.java:595)
I searched the archives and found people with
similar
error messages to me but I'm still having trouble
figuring out how to fix it. Can somebody tell me
what
I'm doing wrong? Thanks in advance.
-Jason
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
wsdir.wsdl
Description: 50286871-wsdir.wsdl
wsdir.xsd
Description: 2112488950-wsdir.xsd
[axis2] Array serialization with xmlbeans databinding - inconsistent?
Hi everyone, Im working on porting an axis1.1 service over to axis2 and Im running into a problem with arrays. On the provider side, I need access to the raw soap xml in some cases so that I can pass it off for some custom handling. The problem is that when the object represents an array, the xml looks significantly different when the array has only one item than when the array has more than one item. Here's a sample section from the wsdl: ... s:schema elementFormDefault=qualified targetNamespace=someservice.com s:complexType name=Person s:sequence s:element name=Name type=s:string/ s:element name=Age type=s:int/ /s:sequence /s:complexType s:complexType name=PersonArray s:sequence s:element name=Person type=s0:Person minOccurs=0 maxOccurs=unbounded/ s:element name=Description type=s:string minOccurs=0 maxOccurs=1/ /s:sequence /s:complexType s:element name=AddPeople s:complexType s:sequence s:element name=Category type=s:string/ s:element name=People type=s0:PersonArray/ /s:sequence /s:complexType /s:element s:element name=AddPeopleResponse s:complexType s:sequence s:element name=Result type=s:int/ /s:sequence /s:complexType /s:element ... On the consumer side, I execute some code like: Person p = Person.Factory.newInstance(); p.setName(Fred); p.setAge(32); Person p2 = Person.Factory.newInstance(); p2.setName(Barney); p2.setAge(34); PersonArray pa = PersonArray.Factory.newInstance(); Person[] pArray = new Person[2]; pArray[0] = p; pArray[1] = p2; pa.setPersonArray(pArray); In this case, pa.xmlText() evaluates to: xml-fragment xmlns:ns=someservice.com ns:Person ns:NameFred/ns:Name ns:Age32/ns:Age /ns:Person ns:Person ns:NameBarney/ns:Name ns:Age34/ns:Age /ns:Person /xml-fragment Which is as I would expect. But if I execute: Person p = Person.Factory.newInstance(); p.setName(Fred); p.setAge(32); PersonArray pa = PersonArray.Factory.newInstance(); Person[] pArray = new Person[1]; pArray[0] = p; pa.setPersonArray(pArray); Then, pa.xmlText() evalutes to: Person xmlns=someservice.com NameFred/Name Age32/Age /Person Which isn't really what I would expect. Instead, I expect something like: xml-fragment xmlns:ns=someservice.com ns:Person ns:NameFred/ns:Name ns:Age32/ns:Age /ns:Person /xml-fragment That is, I would expect the tag representing the collection/array to be present in its serialization. In axis1.1, the xml seemed fairly consistent when dealing with arrays. Has this changed? Is the above by design or following standards, or is there a bug here? Thanks in advance for any suggestions, Dave
Re: Axis2: JavaMail / ClassLoader issue
Please replace the geronimo jars with the ones from SUN in your environment. There are certain clauses in the Sun Binary License that is unacceptable to ASF. thanks, dims On 4/27/06, Arnaud Blandin [EMAIL PROTECTED] wrote: Axis team, I just wanted to summarize the problem we faced recently and check with you the possible alternatives. We have just finished packaging a web-service that simply sends email. The main problem is that we had to use the Sun distribution of javamail and jaf. Thus our service hierarchy looks like: Service.aar |_lib |_mail.jar |_jaf.jar |_... However since Axis2 shipped by default with geronimo-javamail and geronimo-activation which are not yet complete, there is class issue at runtime. In order to workaround this problem, we created our own class loader to redirect javax.mail and javax.activation to the correct classes. We unfortunately had no luck with this approach as we can only set the Service class loader and we don't have access to the classloader that loads initially the javax.mail libraries from the geronimo jars: - AxisService service = msgContext.getOperationContext().getServiceContext().getAxisService(); service.setClassLoader(myOwnStuff); - The only workaround so far is to replace in the Axis2 distribution the geronimo jars with the sun jars. I hope I succeeded in describing the problem as it is not a common one nor an easy one. I have two questions: 1- is it possible to have access to the ClassLoader that loads initially the Axis2 libraries ? 2- if not, is it possible to ship Axis2 with the Sun libraries. I haven't seen something that would prevent to distribute it in the license. Many thanks, Arnaud -- Davanum Srinivas : http://wso2.com/blogs/
Re: [axis2] Stuck with JMS
How did u create client service , the service you passed to create
serviceClient has to have operation with inverse of original MEP. For
example if the server side has in-out operation then corresponding
client side service will have an operation with out-in operation.
So change your client side service class and see.
Thomas Van de Velde wrote:
Hi,
I am trying to integrate JMS with Axis2 and can get around the
following error:
The MEP you are using http://www.w3.org/2004/08/wsdl/in-out has not
implemented createClient().
My client looks as follows:
Options options = new Options();
options.setTo(EPR);
options.setAction(SERVICE_NAME.getLocalPart());
options.setTransportInProtocol (Constants.TRANSPORT_JMS);
ServiceClient loggingClient = new
ServiceClient(getConfigContext(),
clientService);
loggingClient.engageModule(new
QName(sample-logging-handler));
loggingClient.setOptions(options);
loggingClient.sendReceiveNonBlocking(OPERATION_NAME,
getPayload(),
callback);
I keep stumbling in this method:
AxisOperation:
public OperationClient createClient(ServiceContext sc, Options
options) {
throw new
UnsupportedOperationException(Messages.getMessage(mepnotyetimplemented,
mepURI));
}
I am using Axis2 RC3.
Any help would be greatly appreciated.
Thomas
--
Thanks,
Deepal
~Future is Open~
