[Axis2][1.0] Congrats!
Hi all, 1.0 release is finally announced at the side. Congratulations to Axis2 Team for their efforts. Ali Sadik Kumlali __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[ANN] [Axis2] Axis2 1.0 Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After nearly two years of development, we are very proud to announce the release of Apache Axis2 1.0! Check out our official site: http://ws.apache.org/axis2 Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis SOAP stack to build on the lessons learnt from Apache Axis. Apache Axis2 is more efficient, more modular and more XML-oriented than the older version. It is carefully designed to support the easy addition of plug-in modules that extend its functionality for features such as security and reliability. A module supporting WS-Security (Apache Rampart) is available immediately and a module supporting WS-Reliable Messaging (Apache Sandesha) will be available within days. Apache Axis2 not only supports SOAP 1.1 and SOAP 1.2, but it also has integrated support for the widely popular REST style of Web services: the same business logic implementation can offer both a WS-* style interface as well as a REST style interface simultaneously. Apache Axis2 is built on Apache Axiom, a new high performant, pull-based XML object model that was released two days ago. - - Features - Programming Model - Improved, XML-centric client API including full WSDL and policy support - Support for any message exchange pattern - Synchronous and asynchronous calls - Archived service deployment model supporting full service encapsulation with versioning support - Archived module deployment model supporting controlled extensibility with versioning support - Hot deployment - WS-Policy driven code generation extensions - Flexible service lifecyle model - Support for querying service's WSDL (using ?wsdl), schema (using ?xsd) and policies (using ?policy) Supported Specifications - SOAP 1.1 and 1.2 - Message Transmission Optimization Mechanism (MTOM), XML Optimized Packaging (XOP) and SOAP with Attachments - WSDL 1.1, including both SOAP and HTTP bindings - WS-Addressing (submission and final) - WS-Policy - SAAJ 1.1 Transports - HTTP - SMTP - JMS - TCP Supported Data Bindings - Axis Data Binding (ADB) - XMLBeans - JibX - JaxMe Tools - WSDL2Java: Generate Java stubs and skeletons from a WSDL document. - Java2WSDL: Generate a WSDL document from a Java class. - Eclipse Plugins - Intellij Idea Plugins - Web application for administering Apache Axis2 Extension Modules - Apache Rampart: Supporting WS-Security (and soon WS-Policy) - Apache Sandesha2: Supporting WS-Reliable Messaging (Apache Axis2 comes built in with a module that supports WS-Addressing.) Known Issues and Limitations - Recursive schemas (A includes B which includes A) may cause problems - JaxMe data binding support is experimental - Axis2-595: Hot redeployment in Apache Tomcat has problems - Axis2-666: AddressingSubmissionInHandler does not deserialize EPR extensibility attributes and elements - AXIS2-667: Operation dispatch based on message body has a known issue - Axis Data Binding (ADB) does not cover all of XML Schema; its an 80-20 design point. Unsupported XML Schema features include: - Simple content extension and restriction - Complex content restriction - ADB does not support xsi:type based deserialization at runtime - No support yet for unwrapping of doc/lit WSDL files (in stub generation) - No support yet for rpc/encoded style WSDL documents (in stub generation) Thank you for your interest in Axis2. - -The Axis2 Development Team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEWuzUjOGcXNDx0CARAiJ/AKCQSeWfOF9wSA0bkXAUZvV4v+5tnwCgpPT8 ZN+nk4SdvRDOqDWhNAIqT6o= =Gvdc -END PGP SIGNATURE-
[Axis2] installation guide - broken link (v. 1.0)
Hi all, the installation guide page doesn't work (http://ws.apache.org/axis2/download/1_0/installationguide.html) Michele
Re: [Axis2] installation guide - broken link (v. 1.0)
I's been fixed at SVN head. I'm not sure whether it's reflected to the site. Ali Sadik Kumlali --- Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, the installation guide page doesn't work (http://ws.apache.org/axis2/download/1_0/installationguide.html) Michele __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[Axis2] hot service undeployment
Hi all, I know it's possible to deploy services while the server is running (Tomcat + Axis2), but is it possible to undeploy services while the server is on? Thanks, Michele
[Axis2 1.0] Service deployment problems
Hi all, it seems there are some problems to deploy services on Axis2 1.0 (or at least into the web browser console): all services but the version.aar one show a message like this error descriptionUnable to generate WSDL for this service/description reason Either user has not dropped the wsdl into META-INF or operations use message receivers other than RPC. /reason /error instead of the WSDL file (please try with groovyService, available into the userguide dir, for example). Michele
Re: [Axis2] hot service undeployment
You have that capability , but you have to edit axis2.xml file in order to have this feature. You have to change to parameter name=hotupdate locked=falsefalse/parameter following parameter name=hotupdate locked=falsefalse/parameter Michele Mazzucco wrote: Hi all, I know it's possible to deploy services while the server is running (Tomcat + Axis2), but is it possible to undeploy services while the server is on? Thanks, Michele -- Thanks, Deepal ~Future is Open~
Re: [Axis2] installation guide - broken link (v. 1.0)
it is fixed in the site now. Ali Sadik Kumlali wrote: I's been fixed at SVN head. I'm not sure whether it's reflected to the site. Ali Sadik Kumlali --- Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, the installation guide page doesn't work (http://ws.apache.org/axis2/download/1_0/installationguide.html) Michele __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Thanks, Deepal ~Future is Open~
Re: [Axis2 1.0] Service deployment problems
Hi, The WSDL generation functionality has changed for 1.0 since the WSDL generation had a flaw. Unless you have the WSDL inside the META-INF of the aar file, the WSDL is not auto generated except for the special situation where the message receiver is the RPCInOutMessageReceiver. The reason for this is that the java2wsdl code generator assumes the service to be rpc when generating the WSDL and if the user has any custom message receiver installed everything gets screwed up! Ajith On 5/5/06, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, it seems there are some problems to deploy services on Axis2 1.0 (or at least into the web browser console): all services but the version.aar one show a message like this error descriptionUnable to generate WSDL for this service/description reason Either user has not dropped the wsdl into META-INF or operations use message receivers other than RPC. /reason /error instead of the WSDL file (please try with groovyService, available into the userguide dir, for example). Michele -- Ajith Ranabahu
Using AXIS to pass through a SOAP document
I have a project that requires an Axis implementation to pass through an entire SOAP document, untouched, to a 3rd party Java class as a string. This Java class will then respond with an ACK or an ERR. The thing is, I do not want Axis to attempt to look inside the document, I just want it to say ok, here you go 3rd party Java class, you tell me what to respond with. I also require this 3rd party Java class to be able to send out Web Service documents to remote servers and get the responses back, but that is another story. So, bottom line. Can an existing Axis implementation continue to serve its Web Services happily but ALSO be able to pass through other SOAP documents (maybe any it doesn't understand?) to a 3rd party Java class for validation and respond to the client as instructed by that Java class. Many thanks in advance, Mark This message was checked by MailScan for WorkgroupMail. www.workgroupmail.com
[Axis 1.3] Problems using XmlBeans
Hi,
I developed a web service using Axis 1.3 final. Since I already had a
WSDL for the service interface, I decided to create the types using
XmlBeans 2.1.0. So I have a simple interface for the service:
public SearchResultDocument search( QueryDocument query );
I created a server-config.wsdd containing a definition for the service
and a typeMapping tag for each xmlbean I have (although I think I need
only a mapping for SearchResultDocument and QueryDocument, do I?). When
I deploy the service and try accessing the wsdl
(http://localhost/axis/services/myService?wsdl) I receive a
NullPointerException thrown by XmlBeanSerializer:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.NullPointerException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
at
org.apache.axis.encoding.ser.xbeans.XmlBeanSerializer.getTypeNode(XmlBeanSerializer.java:276)
at
org.apache.axis.encoding.ser.xbeans.XmlBeanSerializer.writeSchemaForDocType(XmlBeanSerializer.java:134)
at
org.apache.axis.encoding.ser.xbeans.XmlBeanSerializer.writeSchema(XmlBeanSerializer.java:120)
at
org.apache.axis.wsdl.fromJava.Types.makeTypeElement(Types.java:1849)
at
org.apache.axis.wsdl.fromJava.Types.writeTypeForPart(Types.java:421)
at
org.apache.axis.wsdl.fromJava.Types.writeWrappedParameter(Types.java:612)
at
org.apache.axis.wsdl.fromJava.Emitter.writeWrapperPart(Emitter.java:1680)
at
org.apache.axis.wsdl.fromJava.Emitter.writeRequestMessage(Emitter.java:1467)
at
org.apache.axis.wsdl.fromJava.Emitter.writeMessages(Emitter.java:1106)
at
org.apache.axis.wsdl.fromJava.Emitter.writePortType(Emitter.java:1075)
at
org.apache.axis.wsdl.fromJava.Emitter.getWSDL(Emitter.java:484)
at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:331)
at
org.apache.axis.providers.BasicProvider.generateWSDL(BasicProvider.java:242)
at
org.apache.axis.strategies.WSDLGenStrategy.visit(WSDLGenStrategy.java:33)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at
org.apache.axis.SimpleChain.generateWSDL(SimpleChain.java:104)
at
org.apache.axis.handlers.soap.SOAPService.generateWSDL(SOAPService.java:319)
at
org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:482)
at
org.apache.axis.transport.http.QSWSDLHandler.invoke(QSWSDLHandler.java:68)
...
Since I created the beans from WSDL, I expect Axis to generate an
equivalent WSDL using the XmlBeans themselves.
If I try to set a mapping using the concrete XmlBeans implementations
(SearchResultDocumentImpl), Axis doesn't seem to ever invoke
writeSchema() on the serializer, that is what I expect. I'm in doubt if
I really need a typemapping *also* for the concrete implementations
because I suspect that when from the service I return a SearchResultImpl
Axis can't find a serializer for that...
I tried to use the ser/deser provided at
http://issues.apache.org/jira/browse/AXIS-1764 with no luck. I found
problems integrating it with my actual installation, seems it cannot
find org.w3.x2001.xmlSchema.SchemaDocument$Schema... Since it looks like
importing a XmlBeans of the XSchema schema, I tried to create it but
then I had a ClassCastException
org.apache.xmlbeans.impl.xb.xsdschema.impl.Sc
hemaDocumentImpl$SchemaImpl at XmlBeanSerializer.java:151.
I'm a bit frustrated, so I didn't investigated the problem anymore...
Someone could help?
Bye,
Davide Romanini
Re: [Axis2 1.0] soap action
Thanks, it works. but why I need to explicitly set the SoapAction with Dynamic invocation ? I think Axis2 should automatically set the soapAction In Axis Feature list it is written : /Dynamic ServiceClient http://wiki.apache.org/ws/ServiceClient generation for a given WSDL and invoking the corresponding service using generated client/ Arnaud Deepal Jayasinghe a écrit : ServiceClient sc= new ServiceClient(); Option opt = new Option(); opt.setAction(Your soapaction); Arnaud MERGEY wrote: With dynamic invocation my web service call failed because soapaction is not valid, in wsdl : soap:operation soapAction=http://eyesoft.de/ws/geoip/2002/12/GetCountryFromIP; style=document/ Axis2 dynamic invocation httpclient.wire.header - DEBUG - POST /ws/v1/geoip/geoipconversion.asmx HTTP/1.1[\r][\n] httpclient.wire.header - DEBUG - User-Agent: Axis/2.0[\r][\n] httpclient.wire.header - DEBUG - SOAPAction: [\r][\n] Axis dynamic invocation org.apache.axis.transport.http.HTTPSender - DEBUG - POST /ws/v1/geoip/geoipconversion.asmx HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.3 Host: www.xmlwebservices.cc Cache-Control: no-cache Pragma: no-cache SOAPAction: http://eyesoft.de/ws/geoip/2002/12/GetCountryFromIP; How can I tell to Axis2 to put correct soapaction ? thanks Arnaud
RE: axis 1.2.1 and xsd:dateTime Help!
That was it thanks! _ From: [EMAIL PROTECTED] on behalf of Simon Fell Sent: Thu 5/4/2006 8:58 PM To: axis-user@ws.apache.org Subject: RE: axis 1.2.1 and xsd:dateTime Help! In Java month starts at 0, in XSD month starts at 1, I think this accounts for the difference you're seeing. Cheers Simon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Thursday, May 04, 2006 5:42 PM To: axisUser Subject: axis 1.2.1 and xsd:dateTime Help! I appear to be having an issue with the deserialization of dateTime elements. My schema defines an element like so... xsd:element name=beginDateTime typexsd:dateTime/ I turned on axis level debugging to see the following... ns1:temporalExtent seasonal=false ns1:dateTimeRange ns1:beginDateTime1997-05-01T00:00:00/ns1:beginDateTime ns1:endDateTime1997-06-01T00:00:00/ns1:endDateTime ns1:incrementPT6H/ns1:increment /ns1:dateTimeRange /ns1:temporalExtent This is the correct input but the beginDateTime and endDateTime change after they go over the wire. The month gets decremented by one. Later in the log I see this 2805626 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::startElement() 2805626 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Enter: DeserializationContext::startElement(urn:esg, dateTimeRange) 2805626 [TP-Processor1] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(pushHandler00) 2805626 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Pushing handler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 2805626 [TP-Processor1] DEBUG org.apache.axis.utils.NSStack - NSPush (32) 2805627 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::startElement() 2805627 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Enter: DeserializationContext::startElement(urn:esg, beginDateTime) 2805627 [TP-Processor1] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(pushHandler00) 2805627 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Pushing handler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 2805627 [TP-Processor1] DEBUG org.apache.axis.utils.NSStack - NSPush (32) 2805627 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Exit: DeserializationContext::startElement() 2805627 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Enter: DeserializationContext::endElement(urn:esg, beginDateTime) 2805627 [TP-Processor1] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(popHandler00) 2805627 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializationContext - Popping handler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 2805628 [TP-Processor1] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(setValueInTarget00) 2805628 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializerImpl - Set value java.util.GregorianCalendar[time=86244480,areFieldsSet=true,areAllFi elds Set=true,lenient=true,zone=s un.util.calendar.ZoneInfo[id=GMT,offset=0,dstSavings=0,useDaylight=fal se,t ransitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ER A=1, YEAR=1997,MONTH=4,WEEK_OF_YEAR=18,WEE K_OF_MONTH=1,DAY_OF_MONTH=1,DAY_OF_YEAR=121,DAY_OF_WEEK=5,DAY_OF_WEEK_IN _MON TH=1,AM_PM=0,HOUR=0,HOUR_OF_DAY=0,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_O FFSE T=0,DST_OFFSET=0] in target org.apach [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 2805628 [TP-Processor1] DEBUG org.apache.axis.i18n.ProjectResourceBundle - org.apache.axis.i18n.resource::handleGetObject(setValueInTarget00) 2805628 [TP-Processor1] DEBUG org.apache.axis.encoding.DeserializerImpl - Set value java.util.GregorianCalendar[time=86244480,areFieldsSet=true,areAllFi elds Set=true,lenient=true,zone=s un.util.calendar.ZoneInfo[id=GMT,offset=0,dstSavings=0,useDaylight=fal se,t ransitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ER A=1, YEAR=1997,MONTH=4,WEEK_OF_YEAR=18,WEE K_OF_MONTH=1,DAY_OF_MONTH=1,DAY_OF_YEAR=121,DAY_OF_WEEK=5,DAY_OF_WEEK_IN _MON TH=1,AM_PM=0,HOUR=0,HOUR_OF_DAY=0,MINUTE=0,SECOND=0,MILLISECOND=0,ZONE_O FFSE T=0,DST_OFFSET=0] in target org.apach [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 2805628 [TP-Processor1] DEBUG org.apache.axis.utils.NSStack - NSPop (32) Notice that the MONTH is being set to 4. So when I get to the server the value I see for beginDateTime is 1997-04-01 which is obviously not what I'd expect. Any idea what is happening here? thanks, Gregg
Sample UDDI data
Hi, I am working on webservice and need a UDDI registry with sample data. Now, IBM, Microsoft and others have shutdown their registries. There is a UDDI server with weblogic, but it is empty. Is there any place I can download sample data? Any information would be appreciated. Thanks in advance. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [Axis2 1.0] Service deployment problems
Ajith, this is non my case since I deployed my services as well services from the sample folder (that work on Axis2 RC4), all working with the Axis2 primary APIs. Michele Ajith Ranabahu wrote: Hi, The WSDL generation functionality has changed for 1.0 since the WSDL generation had a flaw. Unless you have the WSDL inside the META-INF of the aar file, the WSDL is not auto generated except for the special situation where the message receiver is the RPCInOutMessageReceiver. The reason for this is that the java2wsdl code generator assumes the service to be rpc when generating the WSDL and if the user has any custom message receiver installed everything gets screwed up! Ajith On 5/5/06, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, it seems there are some problems to deploy services on Axis2 1.0 (or at least into the web browser console): all services but the version.aar one show a message like this error descriptionUnable to generate WSDL for this service/description reason Either user has not dropped the wsdl into META-INF or operationsuse message receivers other than RPC. /reason /error instead of the WSDL file (please try with groovyService, available into the userguide dir, for example). Michele -- Ajith Ranabahu
Re: [Axis2] hot service undeployment
Hi Deepal, my axis2.xml has the following line parameter name=hotupdate locked=falsetrue/parameter but I can't delete any service while the server is running. Michele Deepal Jayasinghe wrote: You have that capability , but you have to edit axis2.xml file in order to have this feature. You have to change to parameter name=hotupdate locked=falsefalse/parameter following parameter name=hotupdate locked=falsefalse/parameter Michele Mazzucco wrote: Hi all, I know it's possible to deploy services while the server is running (Tomcat + Axis2), but is it possible to undeploy services while the server is on? Thanks, Michele
Re: Axis 1.3 axis-wsdl2java StackOverflowError?
I saw some bug reports on this situation for Axis 2 (I am currently using 1.3). Could this be a similar problem? Joshua [EMAIL PROTECTED] 05/04/2006 02:46 PM Please respond to axis-user To:axis-user@ws.apache.org cc: Subject:Axis 1.3 axis-wsdl2java StackOverflowError? All, I am not sure how to debug this one. I am receiving a StackOverflowError when running the axis-wsdl2java ant task (See below) to generate the client code. The interesting thing is, Axis generated this service and it is able to get consumed by a weblogic test client which generates its own code. Where should I begin looking? Regards, Joshua generate: [axis-wsdl2java] WSDL2Java http://localhost:7001/app/services/MyService?wsdl [axis-wsdl2java] Parsing XML file: http://localhost:7001/app/services/MyService?wsdl [axis-wsdl2java] Exception in thread Thread-0 java.lang.StackOverflowError [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getComplexElementExtensionBase(SchemaUtils.java:1067) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getBaseType(SchemaUtils.java:2051) [axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:529) [axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:533) [axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:533) [axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:533) [axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:533) . * This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. *
Help Please: Problem while serializing to .Net Client
Hi All, I am having problem in serializing the data back to a .Net client. The client gets back the object but all attributes in the object seems to be null. I have implemented my webservice using java and I am using Axis 1.3. The client is developed using .Net 1.1 (C#). Can anybody please let me know where all should I check for debugging this problem. I have been struggling since yesterday but no success. FYI, it works fine when the client is in java Thanks, 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.
Axis 1.0 throws an exception while providing WSDL
I coded an axis2 service that I put in the Axis2 webapp. The WSDL (UTF-8 encoded) in the aar contains accents (e.g. "prnom") in the XSD element annotations. When I try to get WSDL from deployed service (MyService?wsdl) an Exception is thrown : javax.servlet.ServletException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:111) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) cause mre org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.description.AxisService.getWSDL(AxisService.java:558) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:533) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:144) org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:89) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:109) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) It's seems to me that's a bug cause my WSDL is a valid XML file.
axis 1.3 throws NullPointerException when deployed to tomcat
i deploy axis along with my web service application inside a war-file to tomcat 5.1.15 through tomcat manager using ant. all libs that axis and my application are depending on are already installed in tomcat/common/lib in order to minimize upload time when deploying. each time i deploy the war file axis throws a NullPointerException and tomcat has to be restarted in order to make axis function properly. i have been struggling with this for months and i am pretty fed up with restarting tomcat for every little change i make. :-) i get one error before the NullPointerException, which tells me that it 'has no functional impact'. thus i might be looking for answers in the wrong place when reading :[ http://ws.apache.org/axis/java/integration-guide.html#Configuration ] please advise. /johan see stack trace below: 08:45:54,127 INFO AprLifecycleListener:86 - The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/local/jdk1.5.0_05/jre/lib/i386/client:/usr/local/jdk1.5.0_05/jre/lib/i386:/usr/local/jdk1.5.0_05/jre/../lib/i386 08:45:54,727 INFO Http11BaseProtocol:147 - Initializing Coyote HTTP/1.1 on http-8080 08:45:54,737 INFO Catalina:511 - Initialization processed in 4227 ms 08:45:55,636 INFO StandardService:442 - Starting service Catalina 08:45:55,678 INFO StandardEngine:431 - Starting Servlet Engine: Apache Tomcat/5.5.15 08:45:55,752 INFO StandardHost:716 - XML validation disabled 08:46:03,811 INFO Http11BaseProtocol:159 - Starting Coyote HTTP/1.1 on http-8080 08:46:04,612 INFO ChannelSocket:374 - JK: ajp13 listening on /0.0.0.0:8009 08:46:04,714 INFO JkMain:343 - Jk running ID=0 time=0/260 config=null 08:46:04,934 INFO StoreLoader:229 - Find registry server-registry.xml at classpath resource 08:46:05,331 INFO Catalina:559 - Server startup in 10592 ms 09:32:03,339 INFO [/manager]:638 - Manager: init: Associated with Deployer 'Catalina:type=Deployer,host=localhost' 09:32:03,370 INFO [/manager]:638 - Manager: init: Global resources are available 09:32:03,448 INFO [/manager]:638 - Manager: undeploy: Undeploying web application at '/axis' 09:32:03,656 INFO HostConfig:1017 - Undeploying context [/axis] 09:32:03,754 INFO [/manager]:638 - Manager: deploy: Deploying web application at '/axis' 09:32:03,759 INFO [/manager]:638 - Manager: Uploading WAR file to /home/ergo/kat/webapps/axis.war 09:32:03,896 INFO HostConfig:783 - Deploying web application archive axis.war 09:32:04,521 INFO WebappClassLoader:1823 - Illegal access: this web application instance has been stopped already. Could not load META-INF/services/org.apache.axis.EngineConfigurationFactory. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. 09:32:04,541 ERROR [/axis]:667 - StandardWrapper.Throwable java.lang.NullPointerException at org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:962) at java.lang.ClassLoader.getResources(ClassLoader.java:1015) at org.apache.commons.discovery.jdk.JDK12Hooks.getResources(JDK12Hooks.java:150) at org.apache.commons.discovery.resource.DiscoverResources$1.getNextResources(DiscoverResources.java:153) at org.apache.commons.discovery.resource.DiscoverResources$1.getNextResource(DiscoverResources.java:129) at org.apache.commons.discovery.resource.DiscoverResources$1.hasNext(DiscoverResources.java:116) at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassNames(DiscoverNamesInFile.java:186) at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassName(DiscoverNamesInFile.java:170) at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.hasNext(DiscoverNamesInFile.java:157) at org.apache.commons.discovery.resource.names.NameDiscoverers$1.getNextIterator(NameDiscoverers.java:143) at org.apache.commons.discovery.resource.names.NameDiscoverers$1.hasNext(NameDiscoverers.java:126) at org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.getNextResource(ResourceClassDiscoverImpl.java:159) at org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.hasNext(ResourceClassDiscoverImpl.java:147) at org.apache.axis.configuration.EngineConfigurationFactoryFinder$1.run(EngineConfigurationFactoryFinder.java:120) at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(EngineConfigurationFactoryFinder.java:113) at org.apache.axis.transport.http.AxisServletBase.getEngineEnvironment(AxisServletBase.java:273) at org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:172) at org.apache.axis.transport.http.AxisServletBase.getOption(AxisServletBase.java:396)
Re: Axis 1.0 throws an exception while providing WSDL
Do you have an XML encoding declaration at the top of your WSDL? eg. ?xml version=1.0 encoding=utf-8? Chances are that you are missing an encoding declaration (so the parser defaults to UTF-8 encoding), and are using a non-UTF-8 encoding (eg. ISO-8859-*). UTF-8 uses between 1 and 4 bytes to encode a character, and uses the high order bit of the first byte to indicate multibyte characters. So if your actual encoding is a single byte per character, and uses characters beyond 127, then you will run into this problem. What editor and environment did you use to produce the WSDL? steve I coded an axis2 service that I put in the Axis2 webapp. The WSDL (UTF-8 encoded) in the aar contains accents (e.g. preacute;nom) in the XSD element annotations. When I try to get WSDL from deployed service (MyService?wsdl) an Exception is thrown : javax.servlet.ServletException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:111) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) cause megrave;re org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is:org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.description.AxisService.getWSDL(AxisService.java:558) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:533) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:144) org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:89) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:109) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) It's seems to me that's a bug cause my WSDL is a valid XML file. -- Steve Barham tel: +44 (0)7973 199 471 Systems Engineer Formicary - delivering quality financial technology solutions http://www.formicary.net/
Re: Axis 1.0 throws an exception while providing WSDL
Steve Barham a crit: I create my WSDL with JAXP/DOM : Here is the java code to write DOM document to file Transformer xformer = TransformerFactory.newInstance().newTransformer(); xformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8"); //$NON-NLS-1$ OutputStream os = new FileOutputStream(getWSDLFile()); Writer writer = new OutputStreamWriter(os, "UTF8"); //$NON-NLS-1$ xformer.transform(new DOMSource(mDocument), new StreamResult(writer)); os.close(); Furthermore I check the generated XML file with XML Schema Validator (http://www.w3.org/2001/03/webdata/xsv) that doesn't find any errors. I can send you the WSDL if it can help. Seb Do you have an XML encoding declaration at the top of your WSDL? eg. ?xml version="1.0" encoding="utf-8"? Chances are that you are missing an encoding declaration (so the parser defaults to UTF-8 encoding), and are using a non-UTF-8 encoding (eg. ISO-8859-*). UTF-8 uses between 1 and 4 bytes to encode a character, and uses the high order bit of the first byte to indicate multibyte characters. So if your actual encoding is a single byte per character, and uses characters beyond 127, then you will run into this problem. What editor and environment did you use to produce the WSDL? steve I coded an axis2 service that I put in the Axis2 webapp. The WSDL (UTF-8 encoded) in the aar contains accents (e.g. "preacute;nom") in the XSD element annotations. When I try to get WSDL from deployed service (MyService?wsdl) an Exception is thrown : javax.servlet.ServletException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:111) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) cause megrave;re org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.description.AxisService.getWSDL(AxisService.java:558) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:533) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:144) org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:89) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:109) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) It's seems to me that's a bug cause my WSDL is a valid XML file.
WSDL soap-adress not correctly set by Axis2 1.0 webapp
When I deploy a service to Axis2 webapp The soapaddress is set by Axis2 to soap:address location=http://localhost:8080/axis2/services/MyService/ that's fine. However if I changed Axis2 webapp name to a other name the soapaddress is still set to http://localhost:8080/axis2/services/MyService so obviously the client can't find the Service (404 Error). Is there a way to configure that or is it a bug ? Thanks Sebastien
Re: [Axis2] hot service undeployment
Hi Michele, If this is under windows I had the same problem with Axis 1.x war files. To solve it, I edited the %CATALINA_HOME%/conf/context.xml file and added the following attributes to the root Context element. Context antiJARLocking=true antiResourceLocking=true I don't use Axis2, so I can't confirm it'll work, but may be worth a try. Richard. Michele Mazzucco wrote: Hi Deepal, my axis2.xml has the following line parameter name=hotupdate locked=falsetrue/parameter but I can't delete any service while the server is running. Michele Deepal Jayasinghe wrote: You have that capability , but you have to edit axis2.xml file in order to have this feature. You have to change to parameter name=hotupdate locked=falsefalse/parameter following parameter name=hotupdate locked=falsefalse/parameter Michele Mazzucco wrote: Hi all, I know it's possible to deploy services while the server is running (Tomcat + Axis2), but is it possible to undeploy services while the server is on? Thanks, Michele
[Axis 1.3] Null pointer when launching SoapMonitor
Hi All, I am trying to launch the soap monitor applet but it throws a null pointer exception and applet does not load up. I have tried looking for the class SOAPMonitorApplet in the distribution of Axis 1.3 but it appears to be missing. Could anybody please tell me how to fix this. Regards, 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: [Axis 1.3] Null pointer when launching SoapMonitor
Thanks Steve. That has solved that problem but when I start the monitor I am not able to see any activity. Below is my deploy-monitor.wsdd file : deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; handler name=soapmonitor type=java:org.apache.axis.handlers.SOAPMonitorHandler parameter name=wsdlURL value=/axis/SOAPMonitorService-impl.wsdl/ parameter name=namespace value=http://tempuri.org/wsdl/2001/12/SOAPMonitorService-impl.wsdl/ parameter name=serviceName value=SOAPMonitorService/ parameter name=portName value=Demo/ /handler service name=SOAPMonitorService provider=java:RPC parameter name=allowedMethods value=publishMessage/ parameter name=className value=org.apache.axis.monitor.SOAPMonitorService/ parameter name=scope value=Application/ /service service name=http://localhost:8080/axis/services/IPromptServices/createLoan; provider=java:RPC requestFlow handler type=soapmonitor/ /requestFlow responseFlow handler type=soapmonitor/ /responseFlow /service /deployment Please let me know if I am missing anything. Steve Barham [EMAIL PROTECTED] 05/05/2006 13:24 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: [Axis 1.3] Null pointer when launching SoapMonitor Hi, If the NPE is down to not being able to load the classes, then copy all the SOAPMonitorApplet* class files from: axis-1_3\webapps\axis\WEB-INF\classes to the root directory of your webapp - ie. on the top level, so that they are accessible as /SOAPMonitorApplet*.class You can find the source to the SOAPMonitorApplet at: axis-1_3\webapps\axis\SOAPMonitorApplet.java Cheers, Steve Hi All, I am trying to launch the soap monitor applet but it throws a null pointer exception and applet does not load up. I have tried looking for the class SOAPMonitorApplet in the distribution of Axis 1.3 but it appears to be missing. Could anybody please tell me how to fix this. Regards, 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. -- Steve Barham tel: +44 (0)7973 199 471 Systems Engineer Formicary - delivering quality financial technology solutions http://www.formicary.net/ 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.
Abstract types
Hi, I'm using axis 1.3 and jdk 1.5, and I'm trying to send a tree constructed using the composite design pattern. So I have an abstract class and a set of instantiating classes. I've then constructed the WSDL to describe these classes and using WSDL2Java constructed the bean serialisers etc. I've added the beanMappings to the wsdd file and it is being added to the server-config.wsdd file correctly. The abstract class contains no data. If I send an object is instantiated from a concrete class with no data it all works fine. However if send an object that contains data it fails with the error; org.xml.sax.SAXException: Invalid element in net.climateprediction.handleService.statements.expandedStatements.ExpandedStatement - (name of data reference) I think this is because although the extended concrete class has the set option the abstract class doesn't, and axis is trying to call set on the abstract class instead of the concrete class. Also I get the error org.xml.sax.SAXException: No object was found for class type class [Lnet.climateprediction.handleService.statements.expandedStatements.ExpandedStatement; if the class contains a reference to the abstract class to enable it to reference another node in the tree (ie. the concrete class is a branch node). It seems axis is trying to instantiate an object from the abstract class instead of the concrete class derived from it. Both of these errors would appear to be caused by axis trying to use references to the wrong class. Does anyone have any ideas on how to correct this, do I need to add additional information to the beanMapping when classes are extended, or to the wsdd file or is this a bug. Any help would be greatfully appreciated Daniel
[ANN] Apache Rampart 1.0 Released
We are happy to announce the 1.0 release of Apache Rampart. Apache Rampart is the Apache Axis2 module that implements the WS-Security specification based on Apache WSS4J 1.5.0 and the Apache AXIOM-DOOM implementation. In addition to the WS-Security features listed in the WSS4J web site (http://ws.apache.org/wss4j) rampart provides: * Ability to MTOM optimize parts of the message * Convenient and intuitive configurations * Mechanism to dynamically configure the module * Experimental WS-SecurityPolicy support This module was successfully tested for interoparability with other WS-Security implementations. You can download the rampart-1.0.mar from: http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/rampart/1_0/ For documentation on configuration please refer http://ws.apache.org/axis2/modules/rampart/1_0/security-module.html Let rampart secure your messages !!! Apache Rampart Team signature.asc Description: OpenPGP digital signature
Re: [Axis 1.3] Null pointer when launching SoapMonitor
The soap monitor servlet needs to be configured in web.xml , as default port of 5001. If the port isn't open, the applet does nothing but show itself. HTH, Robert http://www.braziloutsource.com/On 5/5/06, Santunu Podder [EMAIL PROTECTED] wrote:Thanks Steve.That has solved that problem but when I start the monitor I am not able to see any activity. Below is my deploy-monitor.wsdd file :deployment xmlns=http://xml.apache.org/axis/wsdd/xmlns:java= http://xml.apache.org/axis/wsdd/providers/javahandler name=soapmonitortype=java:org.apache.axis.handlers.SOAPMonitorHandlerparameter name=wsdlURL value=/axis/SOAPMonitorService-impl.wsdl/parameter name=namespace value=http://tempuri.org/wsdl/2001/12/SOAPMonitorService-impl.wsdl /parameter name=serviceName value=SOAPMonitorService/parameter name=portName value=Demo//handlerservice name=SOAPMonitorService provider=java:RPC parameter name=allowedMethods value=publishMessage/parameter name=classNamevalue=org.apache.axis.monitor.SOAPMonitorService/parameter name=scope value=Application/ /serviceservicename=http://localhost:8080/axis/services/IPromptServices/createLoanprovider=java:RPC requestFlowhandler type=soapmonitor//requestFlowresponseFlowhandler type=soapmonitor//responseFlow /service/deploymentPlease let me know if I am missing anything.Steve Barham [EMAIL PROTECTED] 05/05/2006 13:24Please respond toaxis-user@ws.apache.orgToaxis-user@ws.apache.orgccSubject Re: [Axis 1.3] Null pointer when launching SoapMonitorHi,If the NPE is down to not being able to load the classes, then copy allthe SOAPMonitorApplet* class files from:axis-1_3\webapps\axis\WEB-INF\classes to the root directory of your webapp - ie. on the top level, so that theyare accessible as /SOAPMonitorApplet*.classYou can find the source to the SOAPMonitorApplet at:axis-1_3\webapps\axis\SOAPMonitorApplet.java Cheers,Steve Hi All, I am trying to launch the soap monitor applet but it throws a nullpointer exception and applet does not load up. I have tried looking for the class SOAPMonitorAppletin the distribution of Axis 1.3 but it appears to be missing. Could anybody please tell me how to fix this. Regards, Santunu This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the senderby 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.--Steve Barham tel: +44 (0)7973 199 471Systems EngineerFormicary - delivering quality financial technology solutionshttp://www.formicary.net/ This email has been scanned for all viruses by the MessageLabs SkyScanservice.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 with .Net 1.1 client
1.4 is stable. See http://www.apache.org/dist/ws/axis/. On 5/4/06, Rodrigo Ruiz [EMAIL PROTECTED] wrote:Anne, by 1.4 do you mean the latest midnight build? Is it stable enough to rely on it? Or you mean to use it (by now) just for code generation?Thanks,RodrigoAnne Thomas Manes wrote: Use 1.4. On 5/3/06, *Rich Rodriguez* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: With the Axis 1.3 BeanSerializer the array items seem to be named the same as the array property itself. This is fixed in the next version? On 5/3/06, * Anne Thomas Manes* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Edit the WSDL and change the elements named item in your two arrays to unique names. You need to be using Axis 1.4 to get it to generate the appropriate SOAP messages, though. On 5/3/06, *Santunu Podder* [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] wrote: Hi All, I am having a problem invoking a java web service from a .Net 1.1 client. The apache axis generated wsdl specifies a class member of type array which incidently results in exception while invocation. The error I am getting is as below : Unhandled Exception: System.InvalidOperationException: Method TestServices.createAccount can not be reflected. --- System.InvalidOperationException: There was an error reflecting 'createAccountResult'. --- System.InvalidOperationException: There was an error reflecting type 'test.services.AccountTransactionResponse'. --- System.InvalidOperationException : There was an error reflecting field 'amounts'. --- System.InvalidOperationException: The XML element named 'item' from namespace ' http://localhost:8080/axis/services/Account http://localhost:8080/axis/services/Account' references distinct types test.services.AccountDetails and System.Double. Use XML attributes to specify another XML name or namespace for the element or types. The member amounts is of type array and looks like the error is because of that. But .Net 2.0 client does not have this problem. A java client does not have any problem either. Could anybody please let me know how to overcome this. 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. No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.2/329 - Release Date: 02/05/2006-GRIDSYSTEMSRodrigo Ruiz Aguayo Parc Bit - Son Espanyol07120 Palma de Mallorcamailto:[EMAIL PROTECTED]Baleares - EspañaTel:+34-971435085 Fax:+34-971435082 http://www.gridsystems.com-No virus found in this outgoing message.Checked by AVG Free Edition.Version: 7.1.385 / Virus Database: 268.5.2/329 - Release Date: 02/05/2006
Re: Axis2 1.0 - BUG getting namespaces
Bugs can be logged here:
http://issues.apache.org/jira/
http://issues.apache.org/jira/browse/AXIS2
thanks,
dims
On 5/5/06, Steve Barham [EMAIL PROTECTED] wrote:
Hi all,
Using Axis2 1.0, have run into a bug getting the namespace for a service
from its class name. The method is declared as:
public static StringBuffer namespaceFromClassName(String className ,
ClassLoader classLoader) throws Exception
{
return namespaceFromPackageName(Class.forName(className, true,
classLoader).getPackage().getName());
}
Unfortunately, this will throw a NPE if Class.getPackage() returns null.
This will happen in a number of situations, most obviously where the class
has no package, but also where it has a package which was not created by
the Axis deployment classloader.
I'm looking into the problem at the moment, and might be brave enough to
suggest a fix if one is readily apparent. How does one go about submitting
patches to Apache projects?
Cheers,
steve
--
Steve Barham tel: +44 (0)7973 199 471
Systems Engineer
Formicary - delivering quality financial technology solutions
http://www.formicary.net/
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis 1.3] Null pointer when launching SoapMonitor
Thanks Steve. I did everything what you suggested. But this time, when I invoke my web service it throws the following exception System.Web.Services.Protocols.SoapException: org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at com.closepf.services.IPromptServices.adjustLoan(MTATransactionRequest request) at example.client.Client.adjustLoan(IPromptServices ipromptServices) I can see the request flowing in the SoapMonitor but then it throws the above exception. Steve Barham [EMAIL PROTECTED] 05/05/2006 13:51 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: [Axis 1.3] Null pointer when launching SoapMonitor Have you enabled the SOAPMonitor servlet in your web.xml? servlet servlet-nameSOAPMonitorService/servlet-name display-nameSOAPMonitorService/display-name servlet-class org.apache.axis.monitor.SOAPMonitorService /servlet-class init-param param-nameSOAPMonitorPort/param-name param-value5001/param-value /init-param load-on-startup100/load-on-startup /servlet servlet-mapping servlet-nameSOAPMonitorService/servlet-name url-pattern/SOAPMonitor/url-pattern /servlet-mapping By way of comparison, my deployment descriptor for testing a single service is: deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; service name=MessageService provider=java:RPC requestFlow handler name=soapmonitor type=java:org.apache.axis.handlers.SOAPMonitorHandler/ /requestFlow parameter name=className value=com.foo.bar.webservice.MessageService/ parameter name=allowedMethods value=*/ responseFlow handler name=soapmonitor type=java:org.apache.axis.handlers.SOAPMonitorHandler/ /responseFlow /service /deployment Cheers, steve Thanks Steve. That has solved that problem but when I start the monitor I am not able to see any activity. Below is my deploy-monitor.wsdd file : deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; handler name=soapmonitor type=java:org.apache.axis.handlers.SOAPMonitorHandler parameter name=wsdlURL value=/axis/SOAPMonitorService-impl.wsdl/ parameter name=namespace value=http://tempuri.org/wsdl/2001/12/SOAPMonitorService-impl.wsdl/ parameter name=serviceName value=SOAPMonitorService/ parameter name=portName value=Demo/ /handler service name=SOAPMonitorService provider=java:RPC parameter name=allowedMethods value=publishMessage/ parameter name=className value=org.apache.axis.monitor.SOAPMonitorService/ parameter name=scope value=Application/ /service service name=http://localhost:8080/axis/services/IPromptServices/createLoan; provider=java:RPC requestFlow handler type=soapmonitor/ /requestFlow responseFlow handler type=soapmonitor/ /responseFlow /service /deployment Please let me know if I am missing anything. Steve Barham [EMAIL PROTECTED] 05/05/2006 13:24 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: [Axis 1.3] Null pointer when launching SoapMonitor Hi, If the NPE is down to not being able to load the classes, then copy all the SOAPMonitorApplet* class files from: axis-1_3\webapps\axis\WEB-INF\classes to the root directory of your webapp - ie. on the top level, so that they are accessible as /SOAPMonitorApplet*.class You can find the source to the SOAPMonitorApplet at: axis-1_3\webapps\axis\SOAPMonitorApplet.java Cheers, Steve Hi All, I am trying to launch the soap monitor applet but it throws a null pointer exception and applet does not load up. I have tried looking for the class SOAPMonitorApplet in the distribution of Axis 1.3 but it appears to be missing. Could anybody please tell me how to fix this. Regards, 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
Re: Problem with .Net 1.1 client
Is 1.4 for java? Anne Thomas Manes [EMAIL PROTECTED] 05/05/2006 14:16 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Problem with .Net 1.1 client 1.4 is stable. See http://www.apache.org/dist/ws/axis/. On 5/4/06, Rodrigo Ruiz [EMAIL PROTECTED] wrote: Anne, by 1.4 do you mean the latest midnight build? Is it stable enough to rely on it? Or you mean to use it (by now) just for code generation? Thanks, Rodrigo Anne Thomas Manes wrote: Use 1.4. On 5/3/06, *Rich Rodriguez* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: With the Axis 1.3 BeanSerializer the array items seem to be named the same as the array property itself. This is fixed in the next version? On 5/3/06, * Anne Thomas Manes* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Edit the WSDL and change the elements named item in your two arrays to unique names. You need to be using Axis 1.4 to get it to generate the appropriate SOAP messages, though. On 5/3/06, *Santunu Podder* [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] wrote: Hi All, I am having a problem invoking a java web service from a .Net 1.1 client. The apache axis generated wsdl specifies a class member of type array which incidently results in exception while invocation. The error I am getting is as below : Unhandled Exception: System.InvalidOperationException: Method TestServices.createAccount can not be reflected. --- System.InvalidOperationException: There was an error reflecting 'createAccountResult'. --- System.InvalidOperationException: There was an error reflecting type 'test.services.AccountTransactionResponse'. --- System.InvalidOperationException : There was an error reflecting field 'amounts'. --- System.InvalidOperationException: The XML element named 'item' from namespace ' http://localhost:8080/axis/services/Account http://localhost:8080/axis/services/Account' references distinct types test.services.AccountDetails and System.Double. Use XML attributes to specify another XML name or namespace for the element or types. The member amounts is of type array and looks like the error is because of that. But .Net 2.0 client does not have this problem. A java client does not have any problem either. Could anybody please let me know how to overcome this. 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. No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.2/329 - Release Date: 02/05/2006 -- --- GRIDSYSTEMSRodrigo Ruiz Aguayo Parc Bit - Son Espanyol 07120 Palma de Mallorcamailto:[EMAIL PROTECTED] Baleares - España Tel:+34-971435085 Fax:+34-971435082 http://www.gridsystems.com --- -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.2/329 - Release Date: 02/05/2006 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
Re: Problem with .Net 1.1 client
Anne, thanks for the info. I have downloaded it, and in its release notes it states that Axis 1.4 is a final release. Is that correct? I do not see any mention to Axis 1.4 in the web page (http://ws.apache.org/axis/java/releases.html) Rodrigo Anne Thomas Manes wrote: 1.4 is stable. See http://www.apache.org/dist/ws/axis/. On 5/4/06, *Rodrigo Ruiz* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Anne, by 1.4 do you mean the latest midnight build? Is it stable enough to rely on it? Or you mean to use it (by now) just for code generation? Thanks, Rodrigo Anne Thomas Manes wrote: Use 1.4. On 5/3/06, *Rich Rodriguez* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: With the Axis 1.3 BeanSerializer the array items seem to be named the same as the array property itself. This is fixed in the next version? On 5/3/06, * Anne Thomas Manes* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Edit the WSDL and change the elements named item in your two arrays to unique names. You need to be using Axis 1.4 to get it to generate the appropriate SOAP messages, though. On 5/3/06, *Santunu Podder* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi All, I am having a problem invoking a java web service from a .Net 1.1 client. The apache axis generated wsdl specifies a class member of type array which incidently results in exception while invocation. The error I am getting is as below : Unhandled Exception: System.InvalidOperationException: Method TestServices.createAccount can not be reflected. --- System.InvalidOperationException: There was an error reflecting 'createAccountResult'. --- System.InvalidOperationException: There was an error reflecting type 'test.services.AccountTransactionResponse'. --- System.InvalidOperationException : There was an error reflecting field 'amounts'. --- System.InvalidOperationException: The XML element named 'item' from namespace ' http://localhost:8080/axis/services/Account http://localhost:8080/axis/services/Account' references distinct types test.services.AccountDetails and System.Double. Use XML attributes to specify another XML name or namespace for the element or types. The member amounts is of type array and looks like the error is because of that. But .Net 2.0 client does not have this problem. A java client does not have any problem either. Could anybody please let me know how to overcome this. 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. No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.5.2/329 - Release Date: 02/05/2006 --
AXIS 1.3: Unable to generate client code using wsdl2java ant task
All,
When i run the wsdl2java ant task, it blows up with a StackOverflowError. The tool works when my web service only contains simple datatypes, but blows up when I have a complex return type. When putting together the wsdd file, I had to add several beanMapping elements (See below). Is there a similar construct needed for the wsdl2java tool? Has anyone run into this problem?
SAMPLE FROM WSDD FILE
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Address/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObjectWithHistory/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Case/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Consumer/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationPreference/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactMethod/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.DomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.EligibilityProfile/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Email/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ExternalSystemKey/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Occupation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Gender/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Party/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Phone/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.PhoneType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ReferenceObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.SourceSystem/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.State/
SAMPLE FROM ANT FILE
target name=generate depends=init description=executes axis wsdl2java
axis-wsdl2java
output=${generated.dir}
testcase=false
verbose=true
typemappingversion=1.2
url="">
debug=true
/axis-wsdl2java
/target
SAMPLE ERROR MESSAGE
[axis-wsdl2java] Exception in thread Thread-0 java.lang.StackOverflowError
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getComplexElementExtensionBase(SchemaUtils.java:1067)
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getBaseType(SchemaUtils.java:2051)
[axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:529)
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
RE: Interoperability with .NET
Ensure you ran the WSDL2Java process http://www.codeproject.com/dotnet/NET_WS_with_AXIS.asp?df=100forumid=37 978exp=0select=1284668 -Original Message- From: GOBE HOBONA [mailto:[EMAIL PROTECTED] Sent: Thursday, May 04, 2006 12:57 PM To: axis-user@ws.apache.org Subject: Interoperability with .NET Hello, I am attempting to run the MyService example from a Microsoft.NET client. I get the following SoapException from .NET when running the echo operation. Envelope namespace http://org.apache.axis2/xsd was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/; Basically, has anybody successfully read-in SOAP objects from an Axis2 web service to a .NET client? Any examples of compatibility tests or programs will be much appreciated. [This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy.]
CodeGenerationException
Hi,
i just installed Axis2 1.0 and get an CodeGenerationException for the
attached WSDL file.
build.xml:241: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
org.apache.axis2.schema.SchemaCompilationException:
java.lang.NullPointerException
My Ant-Task:
codegen wsdlfilename=D:/workspace_3.1/XFireTest/IIsEqualService.wsdl
output=${generated.dir}
serverside=true
generateServiceXml=true
language=java
/
Ingo
--
CRM Products Development - New Technologies
Tel: +49 721 / 9638-255
CAS Software AG
Well informed. Always and everywhere.
www.cas.de
IIsEqualService.wsdl
Description: application/xml
Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
More coffee... This error is caused by Axis 1.3.
-Joshua
[EMAIL PROTECTED]
05/05/2006 10:24 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:AXIS 1.3: Unable to generate client code using wsdl2java ant task
All,
When i run the wsdl2java ant task, it blows up with a StackOverflowError. The tool works when my web service only contains simple datatypes, but blows up when I have a complex return type. When putting together the wsdd file, I had to add several beanMapping elements (See below). Is there a similar construct needed for the wsdl2java tool? Has anyone run into this problem?
SAMPLE FROM WSDD FILE
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Address/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObjectWithHistory/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Case/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Consumer/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationPreference/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactMethod/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.DomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.EligibilityProfile/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Email/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ExternalSystemKey/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Occupation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Gender/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Party/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Phone/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.PhoneType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ReferenceObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.SourceSystem/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.State/
SAMPLE FROM ANT FILE
target name=generate depends=init description=executes axis wsdl2java
axis-wsdl2java
output=${generated.dir}
testcase=false
verbose=true
typemappingversion=1.2
url="">
debug=true
/axis-wsdl2java
/target
SAMPLE ERROR MESSAGE
[axis-wsdl2java] Exception in thread Thread-0 java.lang.StackOverflowError
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getComplexElementExtensionBase(SchemaUtils.java:1067)
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getBaseType(SchemaUtils.java:2051)
[axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:529)
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
jaxb Axis 1.3
Hello, I've seen a lot of questions ( with almost 0% of answering rate) on how to utilize Axis 1.3 with any of sophisticated XML binding API. Would be it possible to add such an example into the Axis documentation. The most general approach here (because apparently nobody cares about adding serializes for every existing XML binding framework) I see is to convert Axis object into the DOM object and then to corresponding object of the XML API ( and the same in the reverse direction). It would be extremely nice to have such an example for JAXB ( please don’t give an advice to use Axis2). Thanks, Maxim Grigoriev.
Re: EJB mapping declarations
That looks fine providing the AS supports axis 1.3 on the server side. I know for example jboss won't. Your example, however, may help on the client side registering a serializer via ServiceFactory, if you need one. HTH, Robert http://www.braziloutsource.com/ On 5/5/06, G.Vasiakos [EMAIL PROTECTED] wrote: Hello all,I am using AXIS 1.3 and i want to deploy an EJB (provider:EJB) service. In the wsdd file i would like to include the type mappings description for complex type objects. Is the declaration same as in an rpc service or i have to make changes? I want to use the EJB provider in order to update my class files without restarting the axis servlet(hot deploy).This is the RPC type mapping that works :typeMapping xmlns:ns= http://com.test/gamedetails qname=ns:GameDetailsObj type=java:com.test.gamedetails.GameDetailsObj serializer=org.apache.axis.encoding.ser.BeanSerializerFactory deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory encodingStyle=http://schemas.xmlsoap.org/soap/encoding/ /If something has to be changed please tell me. Thank you Χρησιμοποιείτε Yahoo! Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων http://login.yahoo.com/config/mail?.intl=gr
Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Can you provide the wsdl/schema that's causing the error please?On 5/5/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
More coffee... This error is caused by Axis 1.3.
-Joshua
[EMAIL PROTECTED]
05/05/2006 10:24 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:AXIS 1.3: Unable to generate client code using wsdl2java ant task
All,
When i run the wsdl2java ant task, it blows up with a StackOverflowError. The tool works when my web service only contains simple datatypes, but blows up when I have a complex return type. When putting together the wsdd file, I had to add several beanMapping elements (See below). Is there a similar construct needed for the wsdl2java tool? Has anyone run into this problem?
SAMPLE FROM WSDD FILE
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Address/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObjectWithHistory/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Case/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Consumer/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationPreference/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactMethod/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.DomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.EligibilityProfile/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Email/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ExternalSystemKey/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Occupation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Gender/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Party/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Phone/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.PhoneType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ReferenceObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.SourceSystem/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.State/
SAMPLE FROM ANT FILE
target name=generate depends=init description=executes axis wsdl2java
axis-wsdl2java
output=${generated.dir}
testcase=false
verbose=true
typemappingversion=1.2
url="">
debug=true
/axis-wsdl2java
/target
SAMPLE ERROR MESSAGE
[axis-wsdl2java] Exception in thread Thread-0 java.lang.StackOverflowError
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getComplexElementExtensionBase(SchemaUtils.java:1067)
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getBaseType(SchemaUtils.java:2051)
[axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:529)
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
Re: CodeGenerationException
Ingo,When using document/literal, your input message may have at most one body part. You have two. I suggest the following:Define an element called isEqualOperation, defined as a complex type comprising a sequence of the in0 and in1 elements:
xsd:element name=isEqualOperation xsd:complexType xsd:sequence xsd:element name=in0 type=xsd:string/
xsd:element name=in1 type=xsd:string/ /xsd:sequence /xsd:complexType/xsd:elementModify your input message to reference this new element:
wsdl:message name=isEqualOperationRequest wsdl:part element=tns:isEqualOperation name=isEqualOperation//wsdl:message
AnneOn 5/5/06, Ingo Siebert [EMAIL PROTECTED] wrote:
Hi,i just installed Axis2 1.0 and get an CodeGenerationException for theattached WSDL file.build.xml:241: org.apache.axis2.wsdl.codegen.CodeGenerationException:java.lang.RuntimeException
:org.apache.axis2.schema.SchemaCompilationException:java.lang.NullPointerExceptionMy Ant-Task:codegen wsdlfilename=D:/workspace_3.1/XFireTest/IIsEqualService.wsdloutput=${
generated.dir}serverside=truegenerateServiceXml=truelanguage=java/Ingo--CRM Products Development - New Technologies
Tel: +49 721 / 9638-255CAS Software AGWell informed. Always and everywhere.www.cas.de
Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Anne,
Here you go!
Thanks,
Joshua
Anne Thomas Manes [EMAIL PROTECTED]
05/05/2006 10:57 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Can you provide the wsdl/schema that's causing the error please?
On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
More coffee... This error is caused by Axis 1.3.
-Joshua
[EMAIL PROTECTED]
05/05/2006 10:24 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:AXIS 1.3: Unable to generate client code using wsdl2java ant task
All,
When i run the wsdl2java ant task, it blows up with a StackOverflowError. The tool works when my web service only contains simple datatypes, but blows up when I have a complex return type. When putting together the wsdd file, I had to add several beanMapping elements (See below). Is there a similar construct needed for the wsdl2java tool? Has anyone run into this problem?
SAMPLE FROM WSDD FILE
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Address/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObjectWithHistory/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Case/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Consumer/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationPreference/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactMethod/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.DomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.EligibilityProfile/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Email/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ExternalSystemKey/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Occupation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Gender/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Party/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Phone/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.PhoneType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ReferenceObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.SourceSystem/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.State/
SAMPLE FROM ANT FILE
target name=generate depends=init description=executes axis wsdl2java
axis-wsdl2java
output=${generated.dir}
testcase=false
verbose=true
typemappingversion=1.2
url="">
debug=true
/axis-wsdl2java
/target
SAMPLE ERROR MESSAGE
[axis-wsdl2java] Exception in thread Thread-0 java.lang.StackOverflowError
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getComplexElementExtensionBase(SchemaUtils.java:1067)
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getBaseType(SchemaUtils.java:2051)
[axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:529)
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or
Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Anne,
Thanks for your help. Is there anything else I can provide to assist?
Joshua
Anne Thomas Manes [EMAIL PROTECTED]
05/05/2006 10:57 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Can you provide the wsdl/schema that's causing the error please?
On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
More coffee... This error is caused by Axis 1.3.
-Joshua
[EMAIL PROTECTED]
05/05/2006 10:24 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:AXIS 1.3: Unable to generate client code using wsdl2java ant task
All,
When i run the wsdl2java ant task, it blows up with a StackOverflowError. The tool works when my web service only contains simple datatypes, but blows up when I have a complex return type. When putting together the wsdd file, I had to add several beanMapping elements (See below). Is there a similar construct needed for the wsdl2java tool? Has anyone run into this problem?
SAMPLE FROM WSDD FILE
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Address/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObjectWithHistory/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Case/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Consumer/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationPreference/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactMethod/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.DomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.EligibilityProfile/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Email/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ExternalSystemKey/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Occupation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Gender/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Party/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Phone/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.PhoneType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ReferenceObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.SourceSystem/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.State/
SAMPLE FROM ANT FILE
target name=generate depends=init description=executes axis wsdl2java
axis-wsdl2java
output=${generated.dir}
testcase=false
verbose=true
typemappingversion=1.2
url="">
debug=true
/axis-wsdl2java
/target
SAMPLE ERROR MESSAGE
[axis-wsdl2java] Exception in thread Thread-0 java.lang.StackOverflowError
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getComplexElementExtensionBase(SchemaUtils.java:1067)
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getBaseType(SchemaUtils.java:2051)
[axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:529)
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use,
Re: [Axis2 1.0]Bug? when generating java from WSDL
Jose,The schema has two identical definitions of the FTAction type. Which is obviously an error. The WSDL also imports another schema with a namespace of http://ft.tomas.org/xsd , which also defines the FTAction type, and your elements reference this imported type rather than one from the http://tomas.org/faultTolerance/Service/Types namespace. Did you create a new interface and class to generate your WSDL or did you use the class previously generated by Axis1? I suggest you start completely from scratch. Or better yet -- start from the WSDL from your working web service. AnneOn 5/5/06, José Antonio Sánchez [EMAIL PROTECTED] wrote: I have a working web service deployed in Axis 1.3 so I tested if I canport it to Axis2.I downloaded the Axis2 binary distribution and ecipse plugin. First Icreated the FaultToleranceService interface and the FTAction class that were the starting point of my old service. They are attached.Using the Eclipse generation wizard, I successfully created theattached wsdl file but when I try to generate the java server and stubcode from it I get the following error: Exception in thread mainorg.apache.axis2.wsdl.codegen.CodeGenerationException:java.lang.RuntimeException: java.lang.RuntimeException: Schema fornamespace ' http://tomas.org/faultTolerance/Service/Types' alreadycontains type 'FTActionI tried with the Eclipse code generation wizard and manually with thewsdl2java class and the result is the same.I understand that, as the wsdl code is generated from an Axis2 tool, it must be understood by another Axis2 tool without this kind ofproblems.--Regards.José Antonio Sánchez
Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Joshua, This is not a valid schema construct: complexType name=local complexContent extension base=tns2:local
Just how did you generate this WSDL?AnneOn 5/5/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Anne,
Here you go!
Thanks,
Joshua
Anne Thomas Manes [EMAIL PROTECTED]
05/05/2006 10:57 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Can you provide the wsdl/schema that's causing the error please?
On 5/5/06,
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
More coffee... This error is caused by Axis 1.3.
-Joshua
[EMAIL PROTECTED]
05/05/2006 10:24 AM
Please respond to axis-user
To:axis-user@ws.apache.org
cc:
Subject:AXIS 1.3: Unable to generate client code using wsdl2java ant task
All,
When i run the wsdl2java ant task, it blows up with a StackOverflowError. The tool works when my web service only contains simple datatypes, but blows up when I have a complex return type. When putting together the wsdd file, I had to add several beanMapping elements (See below). Is there a similar construct needed for the wsdl2java tool? Has anyone run into this problem?
SAMPLE FROM WSDD FILE
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Address/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.BaseDomainObjectWithHistory/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Case/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Consumer/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationPreference/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactLocationType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ContactMethod/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.DomainObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.EligibilityProfile/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Email/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ExternalSystemKey/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Occupation/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Gender/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Party/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.Phone/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.PhoneType/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.ReferenceObject/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.SourceSystem/
beanMapping qname=ns:local xmlns:ns=java:mycompany.webservice.dto languageSpecificType=java:mycompany.webservice.dto.State/
SAMPLE FROM ANT FILE
target name=generate depends=init description=executes axis wsdl2java
axis-wsdl2java
output=${generated.dir}
testcase=false
verbose=true
typemappingversion=1.2
url="">
debug=true
/axis-wsdl2java
/target
SAMPLE ERROR MESSAGE
[axis-wsdl2java] Exception in thread Thread-0 java.lang.StackOverflowError
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getComplexElementExtensionBase(SchemaUtils.java:1067)
[axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SchemaUtils.getBaseType(SchemaUtils.java:2051)
[axis-wsdl2java]at org.apache.axis.wsdl.toJava.JavaGeneratorFactory.javifyTypeEntryName(JavaGeneratorFactory.java:529)
*
This
Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Anne, I simply configured my service in the WSDD file using the following: deployment xmlns=http://xml.apache.org/axis/wsdd/ xmlns:java=http://xml.apache.org/axis/wsdd/providers/java globalConfiguration parameter name=dotNetSoapEncFix value=true/ parameter name=sendMultiRefs value=false/ /globalConfiguration handler name=URLMapper type=java:org.apache.axis.handlers.http.URLMapper/ service name=ConsumerService provider=java:RPC style=document use=literal parameter name=className value=com.hartfordlife.consumer.webservice.impl.JaxRpcConsumerService/ parameter name=allowedMethods value=echoText, getConsumerByPartyId/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.Address/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.BaseDomainObject/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.BaseDomainObjectWithHistory/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.Case/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.Consumer/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.ContactLocation/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.ContactLocationPreference/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.ContactLocationType/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.ContactMethod/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.DomainObject/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.EligibilityProfile/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.Email/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.ExternalSystemKey/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.GbdOccupation/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.Gender/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.Party/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.Phone/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.PhoneType/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.ReferenceObject/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.SourceSystem/ beanMapping qname=ns:local xmlns:ns=java:com.hartfordlife.consumer.webservice.dto languageSpecificType=java:com.hartfordlife.consumer.webservice.dto.State/ /service transport name=http requestFlow handler type=URLMapper/ /requestFlow /transport /deployment Anne Thomas Manes [EMAIL PROTECTED] 05/05/2006 11:32 AM Please respond to axis-user To:axis-user@ws.apache.org cc: Subject:Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task Joshua, This is not a valid schema construct: complexType name=local complexContent extension base=tns2:local Just how did you generate this WSDL? Anne On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Anne, Here you go! Thanks, Joshua Anne Thomas Manes [EMAIL PROTECTED] 05/05/2006 10:57 AM Please respond to axis-user To:axis-user@ws.apache.org cc: Subject:Re: AXIS 1.3: Unable to
Re: [Axis2 1.0]Bug? when generating java from WSDL
If I start with the wsdl from the working service, I get the same error. The two classes (FTAction and FaultToleranceService interface) are written by me, although they were writter for the Axis1 service, they are not generated at all and so, they should generate a good WSDL file with Axis2. On 5/5/06, Anne Thomas Manes [EMAIL PROTECTED] wrote: Jose, The schema has two identical definitions of the FTAction type. Which is obviously an error. The WSDL also imports another schema with a namespace of http://ft.tomas.org/xsd , which also defines the FTAction type, and your elements reference this imported type rather than one from the http://tomas.org/faultTolerance/Service/Types namespace. Did you create a new interface and class to generate your WSDL or did you use the class previously generated by Axis1? I suggest you start completely from scratch. Or better yet -- start from the WSDL from your working web service. Anne On 5/5/06, José Antonio Sánchez [EMAIL PROTECTED] wrote: I have a working web service deployed in Axis 1.3 so I tested if I can port it to Axis2. I downloaded the Axis2 binary distribution and ecipse plugin. First I created the FaultToleranceService interface and the FTAction class that were the starting point of my old service. They are attached. Using the Eclipse generation wizard, I successfully created the attached wsdl file but when I try to generate the java server and stub code from it I get the following error: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.RuntimeException: Schema for namespace ' http://tomas.org/faultTolerance/Service/Types' already contains type 'FTAction I tried with the Eclipse code generation wizard and manually with the wsdl2java class and the result is the same. I understand that, as the wsdl code is generated from an Axis2 tool, it must be understood by another Axis2 tool without this kind of problems. -- Regards. José Antonio Sánchez -- Saludos. José Antonio Sánchez
Re: [Axis2 1.0]Bug? when generating java from WSDL
On 5/5/06, José Antonio Sánchez [EMAIL PROTECTED] wrote: If I start with the wsdl from the working service, I get the same error. The two classes (FTAction and FaultToleranceService interface) are written by me, although they were writter for the Axis1 service, they are not generated at all and so, they should generate a good WSDL file with Axis2. On 5/5/06, Anne Thomas Manes [EMAIL PROTECTED] wrote: Jose, The schema has two identical definitions of the FTAction type. Which is obviously an error. The WSDL also imports another schema with a namespace of http://ft.tomas.org/xsd , which also defines the FTAction type, and your elements reference this imported type rather than one from the http://tomas.org/faultTolerance/Service/Types namespace. Did you create a new interface and class to generate your WSDL or did you use the class previously generated by Axis1? I suggest you start completely from scratch. Or better yet -- start from the WSDL from your working web service. Anne On 5/5/06, José Antonio Sánchez [EMAIL PROTECTED] wrote: I have a working web service deployed in Axis 1.3 so I tested if I can port it to Axis2. I downloaded the Axis2 binary distribution and ecipse plugin. First I created the FaultToleranceService interface and the FTAction class that were the starting point of my old service. They are attached. Using the Eclipse generation wizard, I successfully created the attached wsdl file but when I try to generate the java server and stub code from it I get the following error: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.RuntimeException: Schema for namespace ' http://tomas.org/faultTolerance/Service/Types' already contains type 'FTAction I tried with the Eclipse code generation wizard and manually with the wsdl2java class and the result is the same. I understand that, as the wsdl code is generated from an Axis2 tool, it must be understood by another Axis2 tool without this kind of problems. -- Regards. José Antonio Sánchez -- Saludos. José Antonio Sánchez -- Saludos. José Antonio Sánchez
Re: [Axis2 1.0]Bug? when generating java from WSDL
I checked it with the wsdl generated by Axis 1.3. It's attached and it seems to work. So the problem is not with the wsdl2java but with the java2wsdl process. On 5/5/06, José Antonio Sánchez [EMAIL PROTECTED] wrote: If I start with the wsdl from the working service, I get the same error. The two classes (FTAction and FaultToleranceService interface) are written by me, although they were writter for the Axis1 service, they are not generated at all and so, they should generate a good WSDL file with Axis2. On 5/5/06, Anne Thomas Manes [EMAIL PROTECTED] wrote: Jose, The schema has two identical definitions of the FTAction type. Which is obviously an error. The WSDL also imports another schema with a namespace of http://ft.tomas.org/xsd , which also defines the FTAction type, and your elements reference this imported type rather than one from the http://tomas.org/faultTolerance/Service/Types namespace. Did you create a new interface and class to generate your WSDL or did you use the class previously generated by Axis1? I suggest you start completely from scratch. Or better yet -- start from the WSDL from your working web service. Anne On 5/5/06, José Antonio Sánchez [EMAIL PROTECTED] wrote: I have a working web service deployed in Axis 1.3 so I tested if I can port it to Axis2. I downloaded the Axis2 binary distribution and ecipse plugin. First I created the FaultToleranceService interface and the FTAction class that were the starting point of my old service. They are attached. Using the Eclipse generation wizard, I successfully created the attached wsdl file but when I try to generate the java server and stub code from it I get the following error: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.RuntimeException: Schema for namespace ' http://tomas.org/faultTolerance/Service/Types' already contains type 'FTAction I tried with the Eclipse code generation wizard and manually with the wsdl2java class and the result is the same. I understand that, as the wsdl code is generated from an Axis2 tool, it must be understood by another Axis2 tool without this kind of problems. -- Regards. José Antonio Sánchez -- Saludos. José Antonio Sánchez -- Saludos. José Antonio Sánchez ?xml version=1.0 encoding=UTF-8? wsdl:definitions targetNamespace=http://tomas.org/faultTolerance/Service; xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:impl=http://tomas.org/faultTolerance/Service; xmlns:intf=http://tomas.org/faultTolerance/Service; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; 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.3 Built on Oct 05, 2005 (05:23:37 EDT)-- wsdl:types schema targetNamespace=http://tomas.org/faultTolerance/Service; xmlns=http://www.w3.org/2001/XMLSchema; import namespace=http://schemas.xmlsoap.org/soap/encoding// complexType name=FTAction sequence element name=action nillable=true type=soapenc:string/ element name=value type=xsd:int/ /sequence /complexType complexType name=ArrayOfFTAction complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=impl:FTAction[]/ /restriction /complexContent /complexType /schema /wsdl:types wsdl:message name=doFTActionResponse wsdl:part name=doFTActionReturn type=impl:ArrayOfFTAction/ /wsdl:message wsdl:message name=doFTActionRequest wsdl:part name=in0 type=impl:ArrayOfFTAction/ /wsdl:message wsdl:portType name=FaultToleranceService wsdl:operation name=doFTAction parameterOrder=in0 wsdl:input message=impl:doFTActionRequest name=doFTActionRequest/ wsdl:output message=impl:doFTActionResponse name=doFTActionResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=FTServiceSoapBinding type=impl:FaultToleranceService wsdlsoap:binding style=rpc transport=http://schemas.xmlsoap.org/soap/http/ wsdl:operation name=doFTAction wsdlsoap:operation soapAction=/ wsdl:input name=doFTActionRequest wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://tomas.org/faultTolerance/Service; use=encoded/ /wsdl:input wsdl:output name=doFTActionResponse wsdlsoap:body encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://tomas.org/faultTolerance/Service; use=encoded/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=FaultToleranceServiceService wsdl:port binding=impl:FTServiceSoapBinding name=FTService wsdlsoap:address location=http://localhost:8080/axis/services/FTService/ /wsdl:port
Axis appends 'Services' to the service name.
Hi All, When I generate my wsdl using axis, it appends an extra word 'Service' to the service name. Pasted below is a section of my wsdl... wsdl:service name=TestServicesService wsdl:port binding=impl:TestServicesSoapBinding name=TestServices wsdlsoap:address location=http://localhost:8080/axis/services/TestServices/ /wsdl:port /wsdl:service Is there any way to get rid of this extra 'Service' word from the name (TestServices) Regards, 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: Axis appends 'Services' to the service name.
Try the wsdlServiceElement parameter in the deployment descriptor:parameter name=wsdlServiceElement value=ClaimCodeService/On 5/5/06, Santunu Podder [EMAIL PROTECTED] wrote: Hi All,When I generate my wsdl using axis, it appends an extra word 'Service' tothe service name.Pasted below is a section of my wsdl...wsdl:service name=TestServicesService wsdl:port binding=impl:TestServicesSoapBindingname=TestServices wsdlsoap:addresslocation= http://localhost:8080/axis/services/TestServices//wsdl:port /wsdl:serviceIs there any way to get rid of this extra 'Service' word from the name(TestServices) Regards,SantunuThis 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.
[Axis2] HTTP Transport Receiver
I noticed that the SimpleHTTPServer packaged with Axis2 and configured as the default Transport Receiver for http requests is not production-worthy. Do you have a standard alternative http server recommended for production use? If so, how should it be configured in the axis2.xml file?
Calendar classCastException
Hello,
Im a newbie to AXIS
and am having troubles with Calendars.
I assume its
something simple, but cant seem to figure it out.
Any help is MUCH
appreciated.
Here is the
error
AxisFaultfaultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionfaultSubcode:
faultString: java.lang.ClassCastException:
java.util.GregorianCalendarfaultActor: faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:C1002441java.lang.ClassCastException:
java.util.GregorianCalendarat
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
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)at
javax.xml.parsers.SAXParser.parse(SAXParser.java:375)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:2443)at
org.apache.axis.client.Call.invoke(Call.java:2366)at
org.apache.axis.client.Call.invoke(Call.java:1812)at
com.crlcorp.webservice.AuthorizeLabSoapBindingStub.processAuthorization(AuthorizeLabSoapBindingStub.java:205)at
test.TestClient.main(TestClient.java:36)
Here is the
generated WSDL:
?xml
version="1.0" encoding="UTF-8"?wsdl:definitions
targetNamespace="urn:AuthorizeLabTest" xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="urn:AuthorizeLabTest" xmlns:intf="urn:AuthorizeLabTest"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns1="http://model.webservice.crlcorp.com"
xmlns:tns2="http://datautil.crlcorp.com"
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 targetNamespace="http://model.webservice.crlcorp.com"
xmlns="http://www.w3.org/2001/XMLSchema"
import namespace="urn:AuthorizeLabTest"/ import
namespace="http://datautil.crlcorp.com"/
import namespace="http://schemas.xmlsoap.org/soap/encoding/"/
complexType name="AuthorizationRequest"
sequence element name="bloodState"
nillable="true" type="soapenc:string"/
element name="cocID" nillable="true"
type="soapenc:string"/ element
name="urinState" nillable="true"
type="soapenc:string"/ element name="userId"
nillable="true" type="soapenc:string"/
element name="userPwd" nillable="true"
type="soapenc:string"/
/sequence /complexType
complexType name="AuthorizationResult"
sequence element name="bloodMessage"
nillable="true" type="soapenc:string"/
element name="cocId" nillable="true"
type="soapenc:string"/ element
name="message" nillable="true"
type="soapenc:string"/ element
name="urinMessage" nillable="true"
type="soapenc:string"/
/sequence /complexType
complexType name="LabTestAuthorization"
sequence element name="id"
nillable="true" type="soapenc:long"/ element
name="cocID" nillable="true"
type="soapenc:string"/ element
name="bloodTestState" nillable="true"
type="soapenc:string"/ element
name="urinTestState" nillable="true"
type="soapenc:string"/ element
name="lastDateModified" nillable="true"
type="xsd:dateTime"/ /sequence
/complexType /schema schema
targetNamespace="http://datautil.crlcorp.com" xmlns="http://www.w3.org/2001/XMLSchema"
import namespace="urn:AuthorizeLabTest"/ import
namespace="http://model.webservice.crlcorp.com"/
import namespace="http://schemas.xmlsoap.org/soap/encoding/"/
complexType name="DatabaseException"
sequence/ /complexType
/schema schema targetNamespace="urn:AuthorizeLabTest"
xmlns="http://www.w3.org/2001/XMLSchema"
import
Re: Axis 1.0 throws an exception while providing WSDL
Please log a bug report (http://issues.apache.org/jira/) and upload your wsdl. thanks, dims On 5/5/06, Sébastien Arod [EMAIL PROTECTED] wrote: Steve Barham a écrit : I create my WSDL with JAXP/DOM : Here is the java code to write DOM document to file Transformer xformer = TransformerFactory.newInstance().newTransformer(); xformer.setOutputProperty(OutputKeys.ENCODING, UTF-8); //$NON-NLS-1$ OutputStream os = new FileOutputStream(getWSDLFile()); Writer writer = new OutputStreamWriter(os, UTF8); //$NON-NLS-1$ xformer.transform(new DOMSource(mDocument), new StreamResult(writer)); os.close(); Furthermore I check the generated XML file with XML Schema Validator (http://www.w3.org/2001/03/webdata/xsv) that doesn't find any errors. I can send you the WSDL if it can help. Seb Do you have an XML encoding declaration at the top of your WSDL? eg. ?xml version=1.0 encoding=utf-8? Chances are that you are missing an encoding declaration (so the parser defaults to UTF-8 encoding), and are using a non-UTF-8 encoding (eg. ISO-8859-*). UTF-8 uses between 1 and 4 bytes to encode a character, and uses the high order bit of the first byte to indicate multibyte characters. So if your actual encoding is a single byte per character, and uses characters beyond 127, then you will run into this problem. What editor and environment did you use to produce the WSDL? steve I coded an axis2 service that I put in the Axis2 webapp. The WSDL (UTF-8 encoded) in the aar contains accents (e.g. preacute;nom) in the XSD element annotations. When I try to get WSDL from deployed service (MyService?wsdl) an Exception is thrown : javax.servlet.ServletException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:111) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) cause megrave;re org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1); nested exception is: org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6e (at char #1999, byte #-1) org.apache.axis2.description.AxisService.getWSDL(AxisService.java:558) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:533) org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:144) org.apache.axis2.transport.http.ListingAgent.handle(ListingAgent.java:89) org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:109) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) It's seems to me that's a bug cause my WSDL is a valid XML file. -- Davanum Srinivas : http://wso2.com/blogs/
[Axis2] Runtime?
What are the runtime requirements for Zxis 2 as far as the JDK Version? Will this still work on JDK 1.3? I could not find this information on the site after much searching. Still I could have just overlooked it. Michael
Experiences testing Axis2 1.0 with Oracle OC4J (9.0.4)
Hello,
I copied the content of axis2.war into a web application and run it from
the OC4J container (9.0.4) from JDeveloper 9.0.5.2.
I noticed the following problems:
1. Because we have an 'error.jsp' file and an 'Error' subdirectory in
the axis2-web directory, the jsp compiler reports an error:
Error: package and class have same name: _axis2_2d_web._error
Resolution: rename the directory 'Error' to 'Errors' and change the
error-page urls in the web.xml accordingly.
2. When I click on the 'Services' link on the Welcome page, the
contenttype of the result page is text/plain instead of text/html, so I
get the page source in Firefox. The same behavior in all pages that are
generated using the request.getRequestDispatcher(jspname).include().
Putting the following line before the dispatching in the renderView
method of the AbstractAgent class resolves the problem:
httpServletResponse.setContentType(text/html;charset=UTF-8);
3. Getting the wsdl of the 'version' service on the service list page
(url: context-root/services/version?wsdl) displays an error:
Requested resource not found!
This is because the line 87 in ListingAgent does not detect the wsdl
request parameter:
httpServletRequest.getParameter(wsdl) returns null in OC4J
(request.getParameterNames() returns an empty enumeration).
Calling with context-root/services/version?wsdl=x will return the wsdl.
I have never used jsp with OC4J before (we use Velocity), so I think the
OC4J gurus can comment these issues and hopefully can find better solutions.
One more strange code fragment in RPCMessageReceiver.java (around line 114):
// Handling the response
AxisMessage outaxisMessage =
op.getMessage(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
if (inaxisMessage != null) {
messageNameSpace =
outaxisMessage.getElementQName().getNamespaceURI();
}
instead of checking inaxisMessage != null probably we should check
outaxisMessage != null. I think the problem is the result of copy/pasting.
Regards,
Laszlo
RE: Help Please: Problem while serializing to .Net Client
I've seen reports that axis 1.3 generates soap messages that don't match the generated WSDL when the types for the service are in multiple difference packages (the wsdl creates a schema per package, but the runtime messages from axis don't reflect that). This would cause problems for .NET and any other WSDL based tool. If you get a capture of the response message from axis, you can either by hand, or using a tool validate it against the generated WSDL. Cheers Simon -Original Message- From: Santunu Podder [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 4:08 AM To: axis-user@ws.apache.org Subject: Help Please: Problem while serializing to .Net Client Hi All, I am having problem in serializing the data back to a .Net client. The client gets back the object but all attributes in the object seems to be null. I have implemented my webservice using java and I am using Axis 1.3. The client is developed using .Net 1.1 (C#). Can anybody please let me know where all should I check for debugging this problem. I have been struggling since yesterday but no success. FYI, it works fine when the client is in java Thanks, 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: AXIS 1.3: Unable to generate client code using wsdl2java ant task
Anne, I was able to get the generator to generate a client by playing around with the bean mappings. If it is not obvious to you already, I am new at this. What should my bean mappings look like? This is what I have now: beanMapping qname=java:Address xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Address/ beanMapping qname=java:BaseDomainObject xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.BaseDomainObject/ beanMapping qname=java:BaseDomainObjectWithHistory xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.BaseDomainObjectWithHistory/ beanMapping qname=java:Case xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Case/ beanMapping qname=java:Consumer xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Consumer/ beanMapping qname=java:ContactLocation xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactLocation/ beanMapping qname=java:ContactLocationPreference xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactLocationPreference/ beanMapping qname=java:ContactLocationType xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactLocationType/ beanMapping qname=java:ContactMethod xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ContactMethod/ beanMapping qname=java:DomainObject xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.DomainObject/ beanMapping qname=java:EligibilityProfile xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.EligibilityProfile/ beanMapping qname=java:Email xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Email/ beanMapping qname=java:ExternalSystemKey xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ExternalSystemKey/ beanMapping qname=java:GbdOccupation xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.GbdOccupation/ beanMapping qname=java:Gender xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Gender/ beanMapping qname=java:Party xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Party/ beanMapping qname=java:Phone xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.Phone/ beanMapping qname=java:PhoneType xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.PhoneType/ beanMapping qname=java:ReferenceObject xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.ReferenceObject/ beanMapping qname=java:SourceSystem xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.SourceSystem/ beanMapping qname=java:State xmlns:ns=java:mycompany.consumer.webservice.dto languageSpecificType=java:mycompany.consumer.webservice.dto.State/ Anne Thomas Manes [EMAIL PROTECTED] 05/05/2006 11:32 AM Please respond to axis-user To:axis-user@ws.apache.org cc: Subject:Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task Joshua, This is not a valid schema construct: complexType name=local complexContent extension base=tns2:local Just how did you generate this WSDL? Anne On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Anne, Here you go! Thanks, Joshua Anne Thomas Manes [EMAIL PROTECTED] 05/05/2006 10:57 AM Please respond to axis-user To:axis-user@ws.apache.org cc: Subject:Re: AXIS 1.3: Unable to generate client code using wsdl2java ant task Can you provide the wsdl/schema that's causing the error please? On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: More coffee... This error is caused by Axis 1.3. -Joshua [EMAIL PROTECTED] 05/05/2006 10:24 AM Please respond to axis-user To:axis-user@ws.apache.org cc: Subject:AXIS 1.3: Unable to generate client code using wsdl2java ant task All, When i run the wsdl2java ant task, it blows up with a StackOverflowError. The tool works when my web service only contains simple datatypes, but blows up when I have a complex return type. When putting together the wsdd
RE: Abstract types
This seems very similar to an issue that I had. I believe it is a bug. I ended up going back to 1.2.1. Gregg _ From: [EMAIL PROTECTED] on behalf of Daniel Goodman Sent: Fri 5/5/2006 9:01 AM To: axis-user@ws.apache.org Subject: Abstract types Hi, I'm using axis 1.3 and jdk 1.5, and I'm trying to send a tree constructed using the composite design pattern. So I have an abstract class and a set of instantiating classes. I've then constructed the WSDL to describe these classes and using WSDL2Java constructed the bean serialisers etc. I've added the beanMappings to the wsdd file and it is being added to the server-config.wsdd file correctly. The abstract class contains no data. If I send an object is instantiated from a concrete class with no data it all works fine. However if send an object that contains data it fails with the error; org.xml.sax.SAXException: Invalid element in net.climateprediction.handleService.statements.expandedStatements.ExpandedSt atement - (name of data reference) I think this is because although the extended concrete class has the set option the abstract class doesn't, and axis is trying to call set on the abstract class instead of the concrete class. Also I get the error org.xml.sax.SAXException: No object was found for class type class [Lnet.climateprediction.handleService.statements.expandedStatements.Expanded Statement; if the class contains a reference to the abstract class to enable it to reference another node in the tree (ie. the concrete class is a branch node). It seems axis is trying to instantiate an object from the abstract class instead of the concrete class derived from it. Both of these errors would appear to be caused by axis trying to use references to the wrong class. Does anyone have any ideas on how to correct this, do I need to add additional information to the beanMapping when classes are extended, or to the wsdd file or is this a bug. Any help would be greatfully appreciated Daniel
Regarding overloaded methods in a WSDL
Hi All, I have a third party WSDL which has overloaded methods. I am using apache-axis 1.2 and when trying to run WSDL2Java it complains saying, the method is overloaded. But when I use xml-axis-10 I dont get this problem and I could generate the client side stubs. May I know why is this happening? And how to generate client side code using apache-axis 1.2 Any help highly appreciated. Thanks regards, Helen.
RE: Abstract types
i use axis 1.3 and abstract types quite extensively... I 'originally' had a problem with axis, but i have had none for around 6-12 months... i find though that you really need to follow the process to the letter to make it work... here's my process, if it helps... 1.) construct a valid wsdl 2.) run ant target on wsdl to create .java classes making sure to pass the -s option to get the deploy.wsdd file 3.) cut the typemapping from the deploy.wsdd and paste into the server-config.wsdd 4.) check the parameter and operation tags and copy them if need be 5.) restart i find that if you edit the server-config.wsdd by hand, you could run into real trouble, so if you've done that (and it sounds like you did as you refer to 'beanmapping') i'd suggest you try this... i used to try to edit the files myself manaully too but i had such a hard time with axis that i now edit ONLY the wsdl file, and use the axis tools 100% from that point... hth, cwd -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 4:15 PM To: axis-user@ws.apache.org Subject: RE: Abstract types This seems very similar to an issue that I had. I believe it is a bug. I ended up going back to 1.2.1. Gregg _ From: [EMAIL PROTECTED] on behalf of Daniel Goodman Sent: Fri 5/5/2006 9:01 AM To: axis-user@ws.apache.org Subject: Abstract types Hi, I'm using axis 1.3 and jdk 1.5, and I'm trying to send a tree constructed using the composite design pattern. So I have an abstract class and a set of instantiating classes. I've then constructed the WSDL to describe these classes and using WSDL2Java constructed the bean serialisers etc. I've added the beanMappings to the wsdd file and it is being added to the server-config.wsdd file correctly. The abstract class contains no data. If I send an object is instantiated from a concrete class with no data it all works fine. However if send an object that contains data it fails with the error; org.xml.sax.SAXException: Invalid element in net.climateprediction.handleService.statements.expandedStatements.Expand edSt atement - (name of data reference) I think this is because although the extended concrete class has the set option the abstract class doesn't, and axis is trying to call set on the abstract class instead of the concrete class. Also I get the error org.xml.sax.SAXException: No object was found for class type class [Lnet.climateprediction.handleService.statements.expandedStatements.Expa nded Statement; if the class contains a reference to the abstract class to enable it to reference another node in the tree (ie. the concrete class is a branch node). It seems axis is trying to instantiate an object from the abstract class instead of the concrete class derived from it. Both of these errors would appear to be caused by axis trying to use references to the wrong class. Does anyone have any ideas on how to correct this, do I need to add additional information to the beanMapping when classes are extended, or to the wsdd file or is this a bug. Any help would be greatfully appreciated Daniel
Re: How do you set the name?
I believe the namespace in the bean mapping should be some URN rather than a java:package declaration. For example:beanMapping qname=java:Address xmlns:ns=
http://foo.com/address languageSpecificType=java:my.package.Address/
On 5/5/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
When running wsdl2java in debug mode, I see the following:
[axis-wsdl2java] org.apache.axis.wsdl.symbolTable.DefinedType
[axis-wsdl2java] QName: {http://hartfordlife.com}ArrayOf_tns1_Address
[axis-wsdl2java] name: org.apache.xml.axis.wsdd.providers.java.Address[]
[axis-wsdl2java] isReferenced? true
[axis-wsdl2java] Class: org.apache.axis.wsdl.symbolTable.DefinedType
[axis-wsdl2java] Base?: false
[axis-wsdl2java] Undefined?: false
[axis-wsdl2java] isSimpleType? false
[axis-wsdl2java] Node: [complexType: null]
[axis-wsdl2java] Dims: []
[axis-wsdl2java] isOnlyLiteralReferenced: false
[axis-wsdl2java] RefType:
[axis-wsdl2java] QName: {http://xml.apache.org/axis/wsdd/providers/java}Address
[axis-wsdl2java] name: org.apache.xml.axis.wsdd.providers.java.Address
[axis-wsdl2java] isReferenced? true
[axis-wsdl2java] Class: org.apache.axis.wsdl.symbolTable.DefinedType
[axis-wsdl2java] Base?: false
[axis-wsdl2java] Undefined?: false
[axis-wsdl2java] isSimpleType? false
[axis-wsdl2java] Node: [complexType: null]
[axis-wsdl2java] Dims:
[axis-wsdl2java] isOnlyLiteralReferenced: false
[axis-wsdl2java] RefType:null
[axis-wsdl2java]
I am using the following beanMapping:
beanMapping qname=java:Address xmlns:ns=java:my.package languageSpecificType=java:my.package.Address/
How do I set the name to my.package.Address instead of org.apache.xml.axis.wsdd.providers.java.Address?
Thanks!
Joshua
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
[axis2-1.0] Exception-Serialisation Bug with xmlbeans databinding?
Is anyone else having problems with the serialisation of
exceptions when using xmlbeans databinding (worked fine with 0.94
and adb)?
The exception looks like this:
--
public class ServiceException extends AxisFault {
public ServiceException(ServiceFault f) {
super(Integer.toString(f.getCode()), new QName(...), null);
}
}
--
Throwing an instance gives me the following error:
org.apache.axiom.om.OMException
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
at
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
- Andreas
Re: How do you set the name?
If I understand correctly, you want your complex type Address with a
package name of your choosing, correct? This worked for me back in my
axis 1.x days:
target name=my-wsdl2java description=Generate compiled complex
interfaces and classes from wsdl
depends=clean,prepare
echo message=Creating the custom complex objects using axis tools /
delete dir=resources/axis/com /
axis-wsdl2java
output=resources/axis
verbose=true
url=""
mapping
namespace=http://com/hostedtelecom/callcentreweb
package=com.hostedtelecom.callcentreweb.endpoint /
/axis-wsdl2java
echo message=Creating the IDE custom complex objects JAR /
javac srcdir=resources/axis destdir=${build} debug=true
include name=**/*.java /
classpath refid=classpath-jboss/
/javac
copy todir=${build}
fileset dir=resources/axis
include name=**/*.class/
/fileset
/copy
jar jarfile=lib/myWsdl.jar
fileset dir=${build} /
/jar
delete dir=${build} /
/target
That'll create your packages as com.hostedtelecom.callcentreweb.endpoint .
HTH,
Robert
http://www.braziloutsource.com/On 5/5/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
When running wsdl2java in debug mode, I see the following:
[axis-wsdl2java] org.apache.axis.wsdl.symbolTable.DefinedType
[axis-wsdl2java] QName: {http://hartfordlife.com}ArrayOf_tns1_Address
[axis-wsdl2java] name: org.apache.xml.axis.wsdd.providers.java.Address[]
[axis-wsdl2java] isReferenced? true
[axis-wsdl2java] Class: org.apache.axis.wsdl.symbolTable.DefinedType
[axis-wsdl2java] Base?: false
[axis-wsdl2java] Undefined?: false
[axis-wsdl2java] isSimpleType? false
[axis-wsdl2java] Node: [complexType: null]
[axis-wsdl2java] Dims: []
[axis-wsdl2java] isOnlyLiteralReferenced: false
[axis-wsdl2java] RefType:
[axis-wsdl2java] QName: {http://xml.apache.org/axis/wsdd/providers/java}Address
[axis-wsdl2java] name: org.apache.xml.axis.wsdd.providers.java.Address
[axis-wsdl2java] isReferenced? true
[axis-wsdl2java] Class: org.apache.axis.wsdl.symbolTable.DefinedType
[axis-wsdl2java] Base?: false
[axis-wsdl2java] Undefined?: false
[axis-wsdl2java] isSimpleType? false
[axis-wsdl2java] Node: [complexType: null]
[axis-wsdl2java] Dims:
[axis-wsdl2java] isOnlyLiteralReferenced: false
[axis-wsdl2java] RefType:null
[axis-wsdl2java]
I am using the following beanMapping:
beanMapping qname=java:Address xmlns:ns=java:my.package
languageSpecificType=java:my.package.Address/
How do I set the name to my.package.Address instead of org.apache.xml.axis.wsdd.providers.java.Address?
Thanks!
Joshua
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
Re: Calendar classCastException
Hi Tom,
I am not an expert myself but will try to help until one of the
other folks replies.
Your error could be unrelated to AXIS itself. It could be that you
just have a bug in your Java code.
Are you trying to cast a Calendar to a GregorianCalendar anywhere?
Or, are you trying to return a GregorianCalendar object as the
return type of a web service end point? If so, you might need
a bean mapping construct in your WSDD deployment file for your
service.
Something like this:
beanMapping
qname=ns:GregorianCalendar
xmlns:ns=http://model.webservice.crlcorp.com;
languageSpecificType=java:com.crlcorp.webservice.model/
If you're writing a JAX-RPC DII client, you will need a
serializer and de-serializer to help AXIS marshall and unmarshall
the GregorianCalendar object. Add something like this to your
call.
Service service = serviceFactory.createService(...);
Call call = (Call) service.createCall(...);
BeanSerializerFactory bsf =
new BeanSerializerFactory(cl, classQName);
BeanDeserializerFactory bdf =
new BeanDeserializerFactory(cl, classQName);
call.registerTypeMapping(cl, classQName, bsf, bdf);
Again, I'm relatively new to AXIS myself, so my apologies if I'm
sending you on the wrong track.
Vartan
--- Tom Bollwitt [EMAIL PROTECTED] wrote:
Hello,
Im a newbie to AXIS and am having troubles with Calendars.
I assume its something simple, but cant seem to figure it out.
Any help is MUCH appreciated.
Here is the error
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.ClassCastException: java.util.GregorianCalendar
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:C1002441
java.lang.ClassCastException: java.util.GregorianCalendar
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.ja
va:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.jav
a:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onContext.java:1087)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(
AbstractSAXParser.java:633)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEnd
Element(XMLNSDocumentScannerImpl.java:719)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$F
ragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:16
85)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.s
canDocument(XMLDocumentFragmentScannerImpl.java:368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.java:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.java:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.jav
a:148)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Abstr
actSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationCon
text.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(MustUnderstan
dChecker.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:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.crlcorp.webservice.AuthorizeLabSoapBindingStub.processAuthorization(
AuthorizeLabSoapBindingStub.java:205)
at test.TestClient.main(TestClient.java:36)
Here is the generated WSDL:
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=urn:AuthorizeLabTest
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=urn:AuthorizeLabTest xmlns:intf=urn:AuthorizeLabTest
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:tns1=http://model.webservice.crlcorp.com;
xmlns:tns2=http://datautil.crlcorp.com;
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.3
Built on Oct 05, 2005 (05:23:37 EDT)--
wsdl:types
schema targetNamespace=http://model.webservice.crlcorp.com;
xmlns=http://www.w3.org/2001/XMLSchema;
import namespace=urn:AuthorizeLabTest/
import namespace=http://datautil.crlcorp.com/
import namespace=http://schemas.xmlsoap.org/soap/encoding//
complexType name=AuthorizationRequest
sequence
element name=bloodState nillable=true type=soapenc:string/
Re: [Axis2] Problems getting wsdl from deployed services in Axis2 v1.0
Thanks, The problem is that I've tried putting a wsdl file in the META-INF dir on the SercurityService (samples) and axis2 doesn't recognize it and sends always the same error (wsdl not found in META-INF.) Sérgio Sousa -Original Message-From: "robert lazarski" [EMAIL PROTECTED] To: axis-user@ws.apache.orgDate: Fri, 5 May 2006 20:42:31 -0300 Subject: Re: [Axis2] Problems getting wsdl from deployed services in Axis2 v1.0Just put the WSDL inside the META-INF of the aar file. See this article for an explanation of this and a few other common issues: http://www.developer.com/open/article.php/3589126HTH, Robert http://www.braziloutsource.com/ On 5/5/06, Sérgio Sousa [EMAIL PROTECTED] wrote: Hi, Can anyone tell me please how do I include a wsdl file in the aar archive?What name should this wsdl file have?Thanks. Sérgio Sousa
Re: [Axis2] Problems getting wsdl from deployed services in Axis2 v1.0
Which security sample? The security sample I'm aware of that has SecureService -modules/samples/src/sample/security/ - doesn't use databinding. So AFAIK you can't link a wsdl under META-INF to a services.xml that was _not_ created by wsdl2java. If you can that's news to me. What I think you are trying to do is use databinding on your wsdl, and then place InflowSecurity and OutflowSecurity via the module security-axis2.mar into your wsdl2java generated services.xml . If that's the case, just follow the sample after the messageReceiver part. Then you'll need to engage the module as explained in the security how-to. If that's not the case perhaps Ruchith can comment. HTH, Robert http://www.braziloutsource.com/On 5/5/06, Sérgio Sousa [EMAIL PROTECTED] wrote: Thanks, The problem is that I've tried putting a wsdl file in the META-INF dir on the SercurityService (samples) and axis2 doesn't recognize it and sends always the same error (wsdl not found in META-INF.) Sérgio Sousa -Original Message-From: robert lazarski [EMAIL PROTECTED] To: axis-user@ws.apache.orgDate: Fri, 5 May 2006 20:42:31 -0300 Subject: Re: [Axis2] Problems getting wsdl from deployed services in Axis2 v1.0Just put the WSDL inside the META-INF of the aar file. See this article for an explanation of this and a few other common issues: http://www.developer.com/open/article.php/3589126HTH, Robert http://www.braziloutsource.com/ On 5/5/06, Sérgio Sousa [EMAIL PROTECTED] wrote: Hi, Can anyone tell me please how do I include a wsdl file in the aar archive?What name should this wsdl file have?Thanks. Sérgio Sousa
Re: Calendar classCastException
I'm not sure if you can use GregorianCalendar directly with xsd:dateTime in all databinding frameworks. I know this works:
Calendar cal = new GregorianCalendar();
And this also works:
Calendar now = Calendar.getInstance();
What may not as I've never tried it is this:
GregorianCalendar gregCal = new GregorianCalendar(2021,02,01);
And then gregCal as your param to your complex object. So I'd try a
vanilla Calendar to see if the problem is xsd:dateTime in axis 1.x
doesn't accept a sub-type of calendar.
HTH,
Robert
http://www.braziloutsource.com/On 5/5/06, Tom Bollwitt
[EMAIL PROTECTED]
wrote:
Hello,
Im a newbie to AXIS
and am having troubles with Calendars.
I assume its
something simple, but cant seem to figure it out.
Any help is MUCH
appreciated.
Here is the
error
AxisFaultfaultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionfaultSubcode:
faultString: java.lang.ClassCastException:
java.util.GregorianCalendarfaultActor: faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:C1002441java.lang.ClassCastException:
java.util.GregorianCalendarat
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
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)at
javax.xml.parsers.SAXParser.parse(SAXParser.java:375)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:2443)at
org.apache.axis.client.Call.invoke(Call.java:2366)at
org.apache.axis.client.Call.invoke(Call.java:1812)at
com.crlcorp.webservice.AuthorizeLabSoapBindingStub.processAuthorization(AuthorizeLabSoapBindingStub.java:205)at
test.TestClient.main(TestClient.java:36)
Here is the
generated WSDL:
?xml
version=1.0 encoding=UTF-8?wsdl:definitions
targetNamespace=urn:AuthorizeLabTest xmlns:apachesoap=http://xml.apache.org/xml-soap
xmlns:impl=urn:AuthorizeLabTest xmlns:intf=urn:AuthorizeLabTest
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/
xmlns:tns1=http://model.webservice.crlcorp.com
xmlns:tns2=http://datautil.crlcorp.com
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 targetNamespace=http://model.webservice.crlcorp.com
xmlns=http://www.w3.org/2001/XMLSchema
import namespace=urn:AuthorizeLabTest/ import
namespace=http://datautil.crlcorp.com/
import namespace=http://schemas.xmlsoap.org/soap/encoding//
complexType name=AuthorizationRequest
sequence element name=bloodState
nillable=true type=soapenc:string/
element name=cocID nillable=true
type=soapenc:string/ element
name=urinState nillable=true
type=soapenc:string/ element name=userId
nillable=true type=soapenc:string/
element name=userPwd nillable=true
type=soapenc:string/
/sequence /complexType
complexType name=AuthorizationResult
sequence element name=bloodMessage
nillable=true type=soapenc:string/
element name=cocId nillable=true
type=soapenc:string/ element
name=message nillable=true
type=soapenc:string/ element
name=urinMessage nillable=true
type=soapenc:string/
/sequence /complexType
complexType name=LabTestAuthorization
sequence element name=id
nillable=true type=soapenc:long/ element
name=cocID nillable=true
type=soapenc:string/ element
name=bloodTestState nillable=true
type=soapenc:string/ element
name=urinTestState nillable=true
type=soapenc:string/ element
name=lastDateModified nillable=true
Think I found a bug in wsdl2java handling reserved word Case - Where to go from here?
Given the following simplified class:
public class EligibilityProfile {
private mypackager.Case _case;
}
The WSDL file get created fine:
s0:complexType name=EligibilityProfile
s0:complexContent
s0:extension base=java:BaseDomainObject xmlns:java=java:mycompany.webservice.dto
s0:sequence
s0:element minOccurs=1 name=EligibilityProfileId nillable=true type=xs:long /
s0:element minOccurs=1 name=Case nillable=true type=java:Case /
/s0:sequence
/s0:extension
/s0:complexContent
/s0:complexType
When wsdl2java get run however, I get the following EligibilityProfile class created (Note the case of the _case class name):
public class EligibilityProfile {
private mypackager._case _case;
}
This class won't even compile. If I refactor mypackager._class in the generated code to mypackager.Class it compiles, but I get a problem parsing a message:
org.xml.sax.SAXException: Invalid element in mycompany.webservice.dto.EligibilityProfile - case
at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
How should I proceed?
Regards,
Joshua
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
ArrayOf Causing some problems
I am having an issue with running a Function that returns an Array. I have a function called returnContacts that returns an array of Contact. The return type from Axis built objects is ArrayOfContacts. If I try to use the ArrayOfContact type, I get an error when I run the function saying NoSuchMethodError. If i try to set the return type to Contact[] then I get a compile error. ContactsLocator locScen = new ContactsLocator(); ContactsSoap servScen = locScen.getContactsSoap(new URL(m_strContactURL)); ArrayOfContact arrContact = servScen.returnContacts(m_ticketId.getTicketID(), Test); What am I doing wrong? Thanks -- Scott Carr OpenOffice.org Documentation Co-Lead This message was sent using IMP, the Internet Messaging Program.
Re: [axis2-1.0] Exception-Serialisation Bug with xmlbeans databinding?
Andreas,
Please open a jira bug and then upload your wsdl to the bug.
thanks,
dims
On 5/5/06, Andreas Hörnicke [EMAIL PROTECTED] wrote:
Is anyone else having problems with the serialisation of
exceptions when using xmlbeans databinding (worked fine with 0.94
and adb)?
The exception looks like this:
--
public class ServiceException extends AxisFault {
public ServiceException(ServiceFault f) {
super(Integer.toString(f.getCode()), new QName(...), null);
}
}
--
Throwing an instance gives me the following error:
org.apache.axiom.om.OMException
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:265)
at
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChildrenQNameIterator.java:75)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElementImpl.java:222)
- Andreas
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Experiences testing Axis2 1.0 with Oracle OC4J (9.0.4)
Laszlo,
I've create a JIRA issue:
http://issues.apache.org/jira/browse/AXIS2-682
thanks,
dims
On 5/5/06, Czeglédi László [EMAIL PROTECTED] wrote:
Hello,
I copied the content of axis2.war into a web application and run it from
the OC4J container (9.0.4) from JDeveloper 9.0.5.2.
I noticed the following problems:
1. Because we have an 'error.jsp' file and an 'Error' subdirectory in
the axis2-web directory, the jsp compiler reports an error:
Error: package and class have same name: _axis2_2d_web._error
Resolution: rename the directory 'Error' to 'Errors' and change the
error-page urls in the web.xml accordingly.
2. When I click on the 'Services' link on the Welcome page, the
contenttype of the result page is text/plain instead of text/html, so I
get the page source in Firefox. The same behavior in all pages that are
generated using the request.getRequestDispatcher(jspname).include().
Putting the following line before the dispatching in the renderView
method of the AbstractAgent class resolves the problem:
httpServletResponse.setContentType(text/html;charset=UTF-8);
3. Getting the wsdl of the 'version' service on the service list page
(url: context-root/services/version?wsdl) displays an error:
Requested resource not found!
This is because the line 87 in ListingAgent does not detect the wsdl
request parameter:
httpServletRequest.getParameter(wsdl) returns null in OC4J
(request.getParameterNames() returns an empty enumeration).
Calling with context-root/services/version?wsdl=x will return the wsdl.
I have never used jsp with OC4J before (we use Velocity), so I think the
OC4J gurus can comment these issues and hopefully can find better solutions.
One more strange code fragment in RPCMessageReceiver.java (around line 114):
// Handling the response
AxisMessage outaxisMessage =
op.getMessage(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
if (inaxisMessage != null) {
messageNameSpace =
outaxisMessage.getElementQName().getNamespaceURI();
}
instead of checking inaxisMessage != null probably we should check
outaxisMessage != null. I think the problem is the result of copy/pasting.
Regards,
Laszlo
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] Runtime?
Michael Rasmussen wrote: What are the runtime requirements for Zxis 2 as far as the JDK Version? Will this still work on JDK 1.3? I could not find this information on the site after much searching. Still I could have just overlooked it. During the first face-2-face itself we decided to have jdk 1.4 as the minimum jdk. So we can not assure abt the support for jdk 1.3. And at the same time, I've been developing on jdk 1.5 and IIRC, Dims once tested on jdk 1.6 as well. -- Chinthaka Michael signature.asc Description: OpenPGP digital signature
Re: Problem with .Net 1.1 client
Rodrigo, Fixed the web site. thanks. -- dims On 5/5/06, Rodrigo Ruiz [EMAIL PROTECTED] wrote: Anne, thanks for the info. I have downloaded it, and in its release notes it states that Axis 1.4 is a final release. Is that correct? I do not see any mention to Axis 1.4 in the web page (http://ws.apache.org/axis/java/releases.html) Rodrigo Anne Thomas Manes wrote: 1.4 is stable. See http://www.apache.org/dist/ws/axis/. On 5/4/06, *Rodrigo Ruiz* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Anne, by 1.4 do you mean the latest midnight build? Is it stable enough to rely on it? Or you mean to use it (by now) just for code generation? Thanks, Rodrigo Anne Thomas Manes wrote: Use 1.4. On 5/3/06, *Rich Rodriguez* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: With the Axis 1.3 BeanSerializer the array items seem to be named the same as the array property itself. This is fixed in the next version? On 5/3/06, * Anne Thomas Manes* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Edit the WSDL and change the elements named item in your two arrays to unique names. You need to be using Axis 1.4 to get it to generate the appropriate SOAP messages, though. On 5/3/06, *Santunu Podder* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi All, I am having a problem invoking a java web service from a .Net 1.1 client. The apache axis generated wsdl specifies a class member of type array which incidently results in exception while invocation. The error I am getting is as below : Unhandled Exception: System.InvalidOperationException: Method TestServices.createAccount can not be reflected. --- System.InvalidOperationException: There was an error reflecting 'createAccountResult'. --- System.InvalidOperationException: There was an error reflecting type 'test.services.AccountTransactionResponse'. --- System.InvalidOperationException : There was an error reflecting field 'amounts'. --- System.InvalidOperationException: The XML element named 'item' from namespace ' http://localhost:8080/axis/services/Account http://localhost:8080/axis/services/Account' references distinct types test.services.AccountDetails and System.Double. Use XML attributes to specify another XML name or namespace for the element or types. The member amounts is of type array and looks like the error is because of that. But .Net 2.0 client does not have this problem. A java client does not have any problem either. Could anybody please let me know how to overcome this. 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. No virus found
