Problem when invoking a service from a Flex web service client: The reply is not returned to the client
Dear all, I’m using axis2c (1.5) as a web service container for my application. When using C clients and stubs automatically generated by wsdl2c utility everything is Ok and I can reach, invoke and get results from my services. Now I’am trying to reach my services from another client using Flex. I have used the Flex tool to generated action script files from WSDL. Everything went OK and I can see that data types are correctly generated. However when I invoke the service : 1) the service is correctly reached and invoked (see logs) 2) But, the result is not returned to the client and i have a log saying « [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler AddressingOutHandler within the phase MessageOut [Mon Sep 28 09:53:22 2009] [info] Starting addressing out handler [Mon Sep 28 09:53:22 2009] [debug] addr_out_handler.c(133) No action present. Stop processing addressing » I have checked if SOAP message generated from Flex does contain the SOAPAction and the answer is yes. The SOAPAction is correctly set in the message. Could anyone help please ? I cannot understand why the reply is not returned to the client. Kind regards, Here is the server’s log : [Mon Sep 28 09:53:22 2009] [debug] http_worker.c(195) Client HTTP version HTTP/1.1 [Mon Sep 28 09:53:22 2009] [debug] soap_builder.c(895) Identified soap version is soap11 [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler request_uri_based_dispatcher within the phase Transport [Mon Sep 28 09:53:22 2009] [debug] req_uri_disp.c(100) Checking for service using target endpoint address : http://127.0.0.1:9090/axis2/services/mmas_management_service [Mon Sep 28 09:53:22 2009] [debug] req_uri_disp.c(121) Service found using target endpoint address [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler AddressingInHandler within the phase Transport [Mon Sep 28 09:53:22 2009] [info] Starting addressing in handler [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler addressing_based_dispatcher within the phase Transport [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler rest_dispatcher within the phase Dispatch [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler soap_message_body_based_dispatcher within the phase Dispatch [Mon Sep 28 09:53:22 2009] [debug] soap_body_disp.c(231) Checking for operation using SOAP messagebody's first child's local name : join [Mon Sep 28 09:53:22 2009] [debug] soap_body_disp.c(240) Operation found using SOAP message body's first child's local name [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler soap_action_based_dispatcher within the phase Dispatch [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler dispatch_post_conditions_evaluator within the phase PostDispatch [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler context_handler within the phase PostDispatch ** (process:10055): DEBUG: axis2_skel_mmas_management_service_join (this is my service implementation) ** (process:10055): DEBUG: sms_sitesmanagementdatamodel_endPointAlreadyExists (this is my service implementation) [Mon Sep 28 09:53:22 2009] [debug] phase.c(210) Invoke the handler AddressingOutHandler within the phase MessageOut [Mon Sep 28 09:53:22 2009] [info] Starting addressing out handler [Mon Sep 28 09:53:22 2009] [debug] addr_out_handler.c(133) No action present. Stop processing addressing [Mon Sep 28 09:53:22 2009] [info] Request served in 0.007 seconds °°+ Dr. Abdelkader GOUAICH Associate Professor/Maître de Conférences Universite Montpellier II Tel: +33 (0)467418675 Fax: +33 (0)467418585
Message coming back short
Silverlight 2.0 is calling an Axis2/C 1.6 server requesting a method that takes a string as an in, though it isn't used and returns a complex result. Here is the most relevant part of the WSDL: xsd:element name=getDefaultSettings xsd:complexType xsd:sequence xsd:element name=in type=xsd:string/xsd:element /xsd:sequence /xsd:complexType /xsd:element xsd:element name=getDefaultSettingsResponse xsd:complexType xsd:sequence xsd:element name=defaultSettings type=tns:DefaultSettings/xsd:element /xsd:sequence /xsd:complexType /xsd:element xsd:complexType name=DefaultSettings xsd:sequence xsd:element name=CompanyName type=xsd:string/xsd:element xsd:element name=EnableFavorites type=xsd:boolean/xsd:element xsd:element name=EnableSlideShow type=xsd:boolean/xsd:element xsd:element name=EventName type=xsd:string nillable=true/xsd:element xsd:element name=PhoneNumberFormat type=xsd:string/xsd:element xsd:element name=Theme type=xsd:string/xsd:element xsd:element name=ThumbnailSize type=xsd:int/xsd:element xsd:element name=TimeoutAfter type=xsd:int/xsd:element xsd:element name=TimeoutStarts type=xsd:int/xsd:element xsd:element name=UserLang type=xsd:string/xsd:element /xsd:sequence /xsd:complexType Thanks to TCPMon, the request Envelope is this: s:Envelope xmlns:s=http://schemas.xmlsoap.org/soap/envelope/; s:Body xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd= http://www.w3.org/2001/XMLSchema; getDefaultSettings xmlns=urn:mmpp:parataMgr in xmlns=not used/in /getDefaultSettings /s:Body/s:Envelope The response is: soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; soapenv:Body n:getDefaultSettingsResponse xmlns:n=urn:mmpp:parataMgr defaultSettings CompanyNameMiltonstreet Photography/CompanyName EnableFavoritestrue/EnableFavorites EnableSlideShowtrue/EnableSlideShow EventNameBigEvent/EventName PhoneNumberFormatTrue/PhoneNumberFormat ThemeBlue/Theme /defaultSettings /n:getDefaultSettingsResponse /soapenv:Body /soapenv:Envelope A number of the elements in the defaultSettings are simply missing. All the elements where not in order originally, so I sorted the WSDL, regenerated the source and recompiled and the same elements are always missing. Any thoughts on what is going on? Sam
Re: Message coming back short
I sorted the WSDL, regenerated the source and recompiled and the same elements are always missing. I was mistaken, it is always the last elements that are lost, which ever elements come last.
Re: aar and hibernate
On Sat, Sep 26, 2009 at 2:11 AM, ANTHONY ENNIS tony.en...@insightbb.comwrote:
I have a web service that performs a simple database lookup. Unfortunately,
Persistence.createEntityManagerFactory('xyzzy') fails in all cases.
My aar looks like:
/com
(class files in package format eg com/this/that/x.class)
/META-INF
services.xml
/lib
numerous jars
I don't know where to put the persistence.xml file. I have tried putting
it everywhere. I keep getting the following error:
try this as well.
create a jar file containing your clases and the persistence.xml file
eg a jar containing.
persistence.xml
com/this/that
and put under lib folder
eg
/lib
other.jars
your.jar
thanks,
Amila.
javax.persistence.PersistenceException: No Persistence provider for
EntityManager named xyzzy
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:56)
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34)
at
com.papajohns.snapshot.webservice.SurveySubmissionWebService.getSurvey(SurveySubmissionWebService.java:63)
(etc)
Or does that error mean something else?
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
unsubscribe
Re: unsubscribe
Please send a mail to axis-user-unsubscr...@ws.apache.org On Mon, Sep 28, 2009 at 08:45, Chamara Silva chamarasi...@gmail.com wrote:
Re: Axis client not listning to correct port when sertting the replayTo header
2009/9/25 Håkon Sagehaug hakon.sageh...@bccs.uib.no Hi all, I've been playing aroung with the replyTo header that I send to my web service so it can respond to the port I want it to, this works fine when I don't set the replyto option in the service client, but when I set it lets say something like this options.setReplyTo(new EndpointReference( http://localhost:1/;)); I still get this info message in my client INFO: Listening on port 6060 So my question is, how can I make axis open the port on my client that I want cheers, håkon you need to create a configuration context by pointing to an axis2.xml. then configure the http listner of the axis2.xml. use the configuration context object to when creating the service client or stub. eg. ConfigurationContext configurationContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem( AXIS2_REPOSITORY_LOCATION, AXIS2_CLIENT_CONFIG_FILE); ServiceClient serviceClient = new ServiceClient(configurationContext, null); thanks, Amila. -- Håkon Sagehaug, Scientific Programmer Parallab, Bergen Center for Computational Science (BCCS) UNIFOB AS (University of Bergen Research Company) -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
Compilation Failure in Axis2 trunk
Hi, I got compilation failure during the building of Axis2 trunk. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[32,30] cannot find symbol symbol : class ParserInputStreamDataSource location: package org.apache.axiom.om.ds /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[109,12] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[109,49] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[159,12] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder /mnt/var/builder/bamboo_home_2.0_beta5/xml-data/build-dir/AXIS2-NIGHTLY/modules/jaxws/src/org/apache/axis2/jaxws/context/listener/ParserInputStreamCustomBuilder.java:[159,49] cannot find symbol symbol : class ParserInputStreamDataSource location: class org.apache.axis2.jaxws.context.listener.ParserInputStreamCustomBuilder Thank you, Regards, Chamara
IndexOutOfBoundsException: Index: 0, Size: 0
I am facing a very strange problem while dealing with apache axis dl
webservices. Every thing goes fine but after browsing (through browser)
webservice's WSDL. Webservice client is unable to query to webservice, its
very strange for me and I am unable to find the actually issue i get the
below exception after the above described scenario. Kindly suggest me what
to do its urgent. Thanks in advance. Note every thing work fine before
visiting WSDL through browser issue comes only when we visit WSDL through
browser.
--Abid
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:mabid.i2c.com
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:1792)
--
View this message in context:
http://www.nabble.com/IndexOutOfBoundsException%3A-Index%3A-0%2C-Size%3A-0-tp25641895p25641895.html
Sent from the Axis - User mailing list archive at Nabble.com.
WS-Trust with Rampart
It is possible to exploit WS-Trust operations with the new Rampart release?! If so, could you point me to some references or best practices?! Thanks -- Francesco Stampacchia
Re: WS-Trust with Rampart
Yes, it is possible to use Rampart for trust operation and by default Rampart comes with a token issuer, renewer, validator and canceller for SAML tokens. What exactly is your scenario ? thanks, Nandana -- Forwarded message -- From: Francesco Stampacchia stampacchiafrance...@gmail.com Date: Mon, Sep 28, 2009 at 1:00 PM Subject: WS-Trust with Rampart To: axis-user@ws.apache.org It is possible to exploit WS-Trust operations with the new Rampart release?! If so, could you point me to some references or best practices?! Thanks -- Francesco Stampacchia
Re: WS-Trust with Rampart
I've got a WSC on domain A that has to access a WS on domain B. WSC would present its credentials to its local STS and so obtains a SAML2 Assertion. Then the newly generated assertion is sent to the WS. The WS will present the received assertion to its STS in order to validate it. Validation will be succsessful only if both STS are federated. Thanks 2009/9/28 Nandana Mihindukulasooriya nandana@gmail.com Yes, it is possible to use Rampart for trust operation and by default Rampart comes with a token issuer, renewer, validator and canceller for SAML tokens. What exactly is your scenario ? thanks, Nandana -- Forwarded message -- From: Francesco Stampacchia stampacchiafrance...@gmail.com Date: Mon, Sep 28, 2009 at 1:00 PM Subject: WS-Trust with Rampart To: axis-user@ws.apache.org It is possible to exploit WS-Trust operations with the new Rampart release?! If so, could you point me to some references or best practices?! Thanks -- Francesco Stampacchia -- Francesco Stampacchia
hibernate and axis2
Thanks for the replies. I'm at work now and don't have access to the postings sent earlier. I created a new jar that included my classes and the persistence.xml file. I placed it in my lib directory. No difference. I'm working in part off code/requirements I didn't write. One wrinkle is that my boss told me to use JPA persistence. He's on vacation now. This is the code to get a session: emf = Persistence.createEntityManagerFactory(Constants.PERSISTENCE); em = emf.createEntityManager(); Given that it is the epicenter of my problem, perhaps I should mention it! I removed the persistence.xml file completely and verified the error (javax.persistence.PersistenceException: No Persistence provider for EntityManager named xyzzy) is generated by a missing persistence.xml file.
automatic generation of a module .mar
Hello Using Axis2.1.4.1, I wanna know how can I generate automatically a module .mar file. This generation must be done within an other java class in which we have to write the core of handlers and module classes and also to generate the MANIFEST.MF file and module.xml file under the META-INF repository. I will be waiting for your helps thank you -- Asma MÂALEJ BESBES Laboratoire LAAS - CNRS Toulouse - France Tèl: +33 (0)5 61 33 62 63 Mobile: +33 (0)6 72 18 36 56 E-mail: amaa...@laas.fr
Re: automatic generation of a module .mar
Did you try for Aixs2 Maven MAR Plug-in ..? please take a look [1] [1] - http://ssagara.blogspot.com/2009/03/axis2-maven-module-mar-plug-in.html On Mon, Sep 28, 2009 at 10:17 PM, Asma Maalej amaa...@laas.fr wrote: Hello Using Axis2.1.4.1, I wanna know how can I generate automatically a module .mar file. This generation must be done within an other java class in which we have to write the core of handlers and module classes and also to generate the MANIFEST.MF file and module.xml file under the META-INF repository. I will be waiting for your helps thank you -- Asma MĀALEJ BESBES Laboratoire LAAS - CNRS Toulouse - France Tčl: +33 (0)5 61 33 62 63 Mobile: +33 (0)6 72 18 36 56 E-mail: amaa...@laas.fr -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
Re: unsubscribe
Please send a mail to axis-user-unsubscr...@ws.apache.org On Mon, Sep 28, 2009 at 19:50, Sie, Yang yang@fmr.com wrote: unsubscribe
Re: IndexOutOfBoundsException: Index: 0, Size: 0
One more thing when we reload application through TomCat Manager or we
restart the Tomcat we are in happy scenario but whenever some one click to
see the WSDL then there is no way to send the client's requests. Kindly
suggest some direction for debugging the issue. Thanks in advance
mabid wrote:
I am facing a very strange problem while dealing with apache axis dl
webservices. Every thing goes fine but after browsing (through browser)
webservice's WSDL. Webservice client is unable to query to webservice, its
very strange for me and I am unable to find the actually issue i get the
below exception after the above described scenario. Kindly suggest me what
to do its urgent. Thanks in advance. Note every thing work fine before
visiting WSDL through browser issue comes only when we visit WSDL through
browser.
--Abid
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:mabid.i2c.com
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:1792)
--
View this message in context:
http://www.nabble.com/IndexOutOfBoundsException%3A-Index%3A-0%2C-Size%3A-0-tp25641895p25657182.html
Sent from the Axis - User mailing list archive at Nabble.com.
