Re: issue 731 - please have a look
Samisa Abeysinghe wrote: Mark Nüßler wrote: hello users, on 26.09.2007 Royston Day found an issue, i just correct my svn-code localy. Can someone have a look - 4 me Royston is right. https://issues.apache.org/jira/browse/AXIS2C-731 I think Rampart folks uses base64 encoding. Can someone using rampart please verify that the proposed code it correct. I tried with the new code and it worked fine for all the scenarios in Rampart/C. But I'm concerned about the interoperability. So it's too early to say that new implementation is correct unless it is inter-operable with other implementations. I'll update on that later. -Kau Thanks, Samisa... mfg derMark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://kaushalye.blogspot.com/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: issue 731 - please have a look
Kaushalye Kapuruge wrote: Samisa Abeysinghe wrote: Mark Nüßler wrote: hello users, on 26.09.2007 Royston Day found an issue, i just correct my svn-code localy. Can someone have a look - 4 me Royston is right. https://issues.apache.org/jira/browse/AXIS2C-731 I think Rampart folks uses base64 encoding. Can someone using rampart please verify that the proposed code it correct. I tried with the new code and it worked fine for all the scenarios in Rampart/C. But I'm concerned about the interoperability. So it's too early to say that new implementation is correct unless it is inter-operable with other implementations. I'll update on that later. axutil_base64_decode_len() is the same implementation as that of the apr_base64_decode_len() found in libapr. AFAIK, this does not returns the exact decoded length of the encoded string, but returns at least as many number of bytes that is necessary. Exact length is anyway returned by the [axutil/apr]_base64_decode(). Thus, if the length returned from the proposed code is correct, there should be no problems with interoperability. -Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
AXIS2C: Does WSDL2C support xml:lang?
Is the xml:lang attribute supported by the WSDL2C tool? My schema definition contains a reference to this, but the generated struct is empty. Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710
Axis2/C where is axis2_char_t* defined
This seems like a silly question, but where is axis2_chart_t defined? I can't find it. Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710
JBoss and Apache Axis compatibility
I'm in the midst of integrating two components, one runs in JBoss and other components exposes some web services deployed in Axis. When i integrate them, there will be a communication between component deployed in JBOSS and Web services exposed via Axis. If i understand correctly, AXIS by default uses RPC service style and JBOSS uses document/literal encoding format. So there is a notion of soap-wsdl encoding format change required here. All i wanted to know is that, 1.Is there any compatibility issues (if any) between JBOSS and Axis ? 2.JBOSS-Axis interaction with respect to the soap encoding format ? 3.Some explanation on SOAP encodingStyle ? Expecting ur favorable reply Regards Arun Email :[EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JBoss-and-Apache-Axis-compatibility-tf4675459.html#a13358175 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2/Java - Trouble building Axis2/Java from source
Keith, because the mar plugin pom get included in the 'overall pom' for the build, I suspect that when it can't be found, for some reason the custom repository on ws.zones isn't included.That or there was an intermittent problem with ws.zones! David On 23/10/2007, keith chapman [EMAIL PROTECTED] wrote: The error you got when installing WSDL4J can be mitigated by going into modules/tools/axis2-mar-maven-plugin and doing mvn install I wonder why maven could not download wsdl4j in the first place though. Thanks, Keith. On 10/22/07, Michael Mole [EMAIL PROTECTED] wrote: I'm having trouble building Axis2/Java from source. Can anyone tell me if I'm doing something wrong? When I try to build Axis2 from source, it tells me this: ( I use this command: %mvn install ) 2) wsdl4j:wsdl4j:jar:1.6.2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=wsdl4j -DartifactId=wsdl4j \ -Dversion=1.6.2 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -Dg roupId=wsdl4j -DartifactId=wsdl4j \ -Dversion=1.6.2 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.axis2:axis2-kernel:jar:1.3 2) wsdl4j:wsdl4j:jar:1.6.2 However, I get another error when I try to manually install wsdl4j, using this command: C:\axis2java-1.3-srcmvn install:install-file -Dfile=C:\WSDL4J\wsdl4j-1_6_2\lib\wsdl4j.jar -DgroupId=wsdl4j -DartifactId=wsdl4j -Dversion=1.6.2 -Dpackaging=jar [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Axis 2.0 - Parent [INFO] Apache Axis 2.0 - Data Binding [INFO] Apache Axis 2.0 - Kernel [INFO] Apache Axis 2.0 - Code Generation [INFO] Apache Axis 2.0 - ADB Codegen [INFO] Apache Axis 2.0 - tool - MAR Maven Plugin [INFO] Apache Axis 2.0 - Addressing [INFO] Apache Axis 2.0 - Java2WSDL [INFO] Apache Axis 2.0 - Fast Infoset [INFO] Apache Axis 2.0 - MTOM Policy [INFO] Apache Axis 2.0 - SAAJ API [INFO] Apache Axis 2.0 - SAAJ [INFO] Apache Axis 2.0 - JAXWS API [INFO] Apache Axis 2.0 - JWS API [INFO] Apache Axis 2.0 - Metadata [INFO] Apache Axis 2.0 - JSON [INFO] Apache Axis 2.0 - Clustering [INFO] Apache Axis 2.0 - JAXWS [INFO] Apache Axis 2.0 - Scripting [INFO] Apache Axis 2.0 - JAXB-RI Data Binding [INFO] Apache Axis 2.0 - JiBX Data Binding [INFO] Apache Axis 2.0 - spring [INFO] Apache Axis 2.0 - XMLBeans Data Binding [INFO] Apache Axis 2.0 - Integration [INFO] Apache Axis 2.0 - MEX [INFO] Apache Axis 2.0 - MEX-Module [INFO] Apache Axis 2.0 - Ping [INFO] Apache Axis 2.0 - tool - AAR Maven Plugin [INFO] Apache Axis 2.0 - Version Service [INFO] Apache Axis 2.0 - SOAP Monitor [INFO] Apache Axis 2.0 - tool - Ant Plugin [INFO] Apache Axis 2.0 - Root [INFO] Apache Axis 2.0 - tool - Eclipse Codegen Plugin [INFO] Apache Axis 2.0 - tool - Eclipse service Plugin [INFO] Apache Axis 2.0 - tool - Intellij IDEA Plugin [INFO] Apache Axis 2.0 - tool - Java2WSDL Maven Plugin [INFO] Apache Axis 2.0 - tool - WSDL2Code Maven Plugin [INFO] Apache Axis 2.0 - Web Application module [INFO] Apache Axis 2.0 - Samples [INFO] Searching repository for plugin with prefix: 'install'. Downloading: http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.6.2/axis2-mar-ma ven-plugin-1.6.2.pom Downloading: http://repo1.maven.org/maven2/org/apache/axis2/axis2-mar-maven-plugin/1.6.2/axis2-mar-maven-plugi n-1.6.2.pom Downloading: http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.6.2/axis2-mar-ma ven-plugin-1.6.2.pom Downloading: http://tomcat.apache.org/dev/dist/m2-repository/org/apache/axis2/axis2-mar-maven-plugin/1.6.2/axi s2-mar-maven-plugin-1.6.2.pom Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/axis2/axis2-mar-maven-plugin/1. 6.2/axis2-mar-maven-plugin-1.6.2.pom Downloading: http://repo1.maven.org/eclipse/org/apache/axis2/axis2-mar-maven-plugin/1.6.2/axis2-mar-maven-plug in-1.6.2.pom Downloading: http://jibx.sourceforge.net/maven/org.apache.axis2/poms/axis2-mar-maven-plugin-1.6.2.pom Downloading: http://download.java.net/maven/1//org.apache.axis2/poms/axis2-mar-maven-plugin-1.6.2.pom Downloading: http://repo1.maven.org/maven2/org/apache/axis2/axis2-mar-maven-plugin/1.6.2/axis2-mar-maven-plugi n-1.6.2.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.axis2:axis2-mar-maven-plugin
invoking .Net web service From Axis 1.2 RC web service, How to save SOAP message
Hi, i want to save a SOAP message in DataBase. I am invoking .Net web service to send the Response xml from my Axis 1.2RC web service. When i am invoking .Net web service then i am passing a bean object to .Net web service Stub. So, after invoking or before invoking the . net web services, can we save the SOAP message. bcz after invoking the web service SOAP message is sent to other end. is it possible ??? Give some idea. Santosh Kumar Sharma -- View this message in context: http://www.nabble.com/invoking-.Net-web-service-From-Axis-1.2-RC-web-service%2C-How-to-save-SOAP-message-tf4675517.html#a13358339 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to use WSDL to validate soap message?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please read a doc on data binding and please 1. do not cross post 2. do not use dev-list to ask non-architectural questions. Chinthaka Wenshuang Sun wrote: Hi, How to use WSDL to validate the soap message in axis2, is the API about the function provided? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHHZ85jON2uBzUhh8RAtRGAJ9cQZIkS6+HQVieeCgzRFoPU4tuzACgldY2 Q9NuWsytX9oEaM19DTE5u/w= =y11O -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Which style am I using?
Hi everyone, I'm kind of new in web services so I need your help once again. Say I have the following wsdl: wsdl:definitions targetNamespace=http://www.example.org; wsdl:documentation Blah blah /wsdl:documentation wsdl:types xs:schema targetNamespace=http://www.example.org; attributeFormDefault=qualified elementFormDefault=qualified xs:element name=viewLesson xs:complexType xs:sequence xs:element name=lesson_id type=xs:long/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=viewLessonMessage wsdl:part name=part1 element=ns0:viewObservation/ /wsdl:message wsdl:message name=viewLessonResponse wsdl:part name=part1 element=ns0:viewLessonResponse/ /wsdl:message so I send and receive messages like (minus the soap envelope): ns0:viewLesson ...namespace stuff ns0:lesson_id1/ns0:lesson_id /ns0:viewLesson Which style am I using? I think I'm using document/wrapped but am I right? I've read the developer works article on this but I'm not certain yet. Thanks in advance. -- Dimitris Mouchritsas Computer Services
minOccurs=0 attribute and .NET
Hello to all! I recently experienced a problem trying to do the following: - expose a POJO as a webservice, generating the WSDL with Axis2 Java2WSDL - create a client with .NET WebService Studio 2.0 Suppose my Java methods signatures are these: public Integer a(String, Integer) public String b(Integer, String) (please note: the actual methods declare to launch some exceptions, too) Axis2 Java2WSDL adds the minOccurs=0 for each element of each complex type, both for the input parameters and for the output parameters. When generating clients using .NET WebService Studio 2.0, the result is the following: - all the generated C# methods input parameters are doubled, except for the string ones: the doubled parameters are booleans whose meaning is: is the previous parameter specified or not? - all the generated C# methods return parameters are void, except for the string ones The actual result are clients with methods like these: void a(string, Integer32, Boolean) string b(Integer32, Boolean, string) We could discuss if this is a correct behaviour by .NET WebService 2.0 or not, however, my question is this: why does Axis2 Java2WSDL specify minOccurs=0 for each parameter? What I would expect is that every method parameter (either input ones or return ones) IS mandatory. Does Axis2 specify minOccurs=0 with the meaning of: it may be null? Or are there other specific reasons? Is there a way to customize this aspect of the WSDL generation? Thanks in advance for any reply. -- Mauro Molinari Software Developer [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[AXIS2] Using a custom truststore
Hi there, is it possible to specify a truststore for a client at run time other than using: System.setProperty(javax.net.ssl.trustStore, ...); you can't use the above in a multi client environment as they all overwrite each others' truststore details. is there any way to tell stub._getServiceClient() to use a specific truststore without using System properties? thanks, Alistair -- mov eax,1 mov ebx,0 int 80h
Re: How to use WSDL to validate soap message?
Eran Chinthaka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please read a doc on data binding and please
1. do not cross post
2. do not use dev-list to ask non-architectural questions.
Chinthaka
Wenshuang Sun wrote:
Hi,
How to use WSDL to validate the soap message in axis2, is the API
about the function provided?
Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHHZ85jON2uBzUhh8RAtRGAJ9cQZIkS6+HQVieeCgzRFoPU4tuzACgldY2
Q9NuWsytX9oEaM19DTE5u/w=
=y11O
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I've actually used the lib from Xerces. You need xml-apis.jar from
there. Then I placed my .xsd files in the root of the archive file (aar)
and my validation method is like this:
public String validate(String schemaFile, OMElement xml) {
String returnMessage = null;
try {
SchemaFactory schemaFactory =
SchemaFactory.newInstance(http://www.w3.org/2001/XMLSchema;);
Schema schemaXSD =
schemaFactory.newSchema(this.getClass().getResource(/ + schemaFile));
Validator validator= schemaXSD.newValidator();
DocumentBuilder parser =
DocumentBuilderFactory.newInstance().newDocumentBuilder();
InputSource docSource = new InputSource(new
StringReader(xml.toString()));
Document document = parser.parse(docSource);
validator.validate(new DOMSource(document));
} catch (Exception e) {
e.printStackTrace();
returnMessage = e.toString();
// Clear the org.xml.sax.SAXParseException from the string
returnMessage = returnMessage.replaceAll(
org\\.xml\\.sax\\.SAXParseException: , );
}
return returnMessage;
}
For small messages I have not noticed a delay in the validation. But I
still need to check with attachments. Also notice the / in the
getResource. This
is crucial for finding the schema file in the archive.
RE: Getting teh following error trying to set the transport properties dynamically
Sending again as earlier one didn't go through
Thanks Regards,
Ajeet Phansalkar
_
From: Ajeet Phansalkar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 10:35 AM
To: 'axis-user@ws.apache.org'
Subject: Getting teh following error trying to set the transport properties
dynamically
Hi,
I have created a Stubs using ADB binding from .NET webservice wsdl.When
running the client to access the webservice
I got the error on Unknown host exception.It looked like the client was
unable to go through the proxy to the webservice.The web service is outside
my client's network,hence using the proxy.
To resolve this problem I assumed that the stubs would be using the
axis2.xml file ,so I set the configurations in transport sender there. But
still the problem persisted as my java client is a standalone and not in a
J2EE app server. So I am trying to set the transport sender properties
dynamically in code. But now I get the following error:
og4j:WARN No appenders could be found for logger
(org.apache.axis2.description.AxisService).
log4j:WARN Please initialize the log4j system properly.
org.apache.axis2.AxisFault: Transport out has not been set
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
n.java:374)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisO
peration.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
com.choicepoint.bixg.axis2.webservice.SearchAPI1Stub.CustomSearch(SearchAPI1
Stub.java:764)
at com.choicepoint.bixg.axis2.client.Client.doInOnly(Client.java:64)
at com.choicepoint.bixg.axis2.client.Client.main(Client.java:20)
Following is the piece of code in stub which I am trying to set the
properties
public SearchAPI1Stub(org.apache.axis2.context.ConfigurationContext
configurationContext,
java.lang.String targetEndpoint, boolean useSeparateListener)
throws org.apache.axis2.AxisFault {
//To populate AxisService
populateAxisService();
populateFaults();
_serviceClient = new
org.apache.axis2.client.ServiceClient(configurationContext,_service);
configurationContext =
_serviceClient.getServiceContext().getConfigurationContext();
_serviceClient.getOptions().setTo(new
org.apache.axis2.addressing.EndpointReference(
targetEndpoint));
_serviceClient.getOptions().setUseSeparateListener(useSeparateListener);
//Set the soap version
_serviceClient.getOptions().setSoapVersionURI(org.apache.axiom.soap.SOAP12Co
nstants.SOAP_ENVELOPE_NAMESPACE_URI);
//_serviceClient.getOptions().setSenderTransport(new
TransportOutDescription(new QName(Constants.TRANSPORT_HTTP)));
_serviceClient.getOptions().setProperty(HTTPConstants.HTTP_PROTOCOL_VERSION,
HTTPConstants.HEADER_PROTOCOL_11);
HttpTransportProperties.ProxyProperties proxyProperties = new
HttpTransportProperties.ProxyProperties();
proxyProperties.setProxyName(proxyname);
proxyProperties.setProxyPort(proxyport);
proxyProperties.setDomain(domain name);
HttpTransportProperties.Authenticator
auth = new HttpTransportProperties.Authenticator();
auth.setUsername(username);
auth.setPassword(password);
// set if realm or domain is known
_serviceClient.getOptions().setProperty(org.apache.axis2.transport.http.HTTP
Constants.AUTHENTICATE, auth);
_serviceClient.getOptions().setProperty(HTTPConstants.PROXY,proxyProperties)
;
}
Request help in figuring out this issue.
Thanks Regards,
Ajeet Phansalkar
http://www.patni.com
World-Wide Partnerships. World-Class Solutions.
_
This e-mail message may contain proprietary, confidential or legally
privileged information for the sole use of the person or entity to
whom this message was originally addressed. Any review, e-transmission
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you have received this e-mail in error
kindly delete this e-mail from your records. If it appears that this
mail has been forwarded to you without proper authority, please notify
us immediately at [EMAIL PROTECTED] and delete this mail.
_
[axis2 1.3] Metadata echange documentation
Hi all, I need any documentation on the Metadata exchange module of axis2 1.3 (mex). thanks in advance Regards, Nencho
Re: [axis2] Define policy in services.xml on operation level
Hi Nencho, It seems that you've set the useOriginalWSDL parameter to 'true' which outputs the WSDL document in the service aar for any ?wsdl requests. Obviously that doesn't include the policies that you've defined within the operation definition in the services.xml. Best, Sanka Nencho Lupanov wrote: Hi all, do you know wheather it is valid to attach a policy in services.xml descriptor on operation level , i tryed this just by embedding the policy tag as a child of the operation tag, just like i would done it on a service level but it is not reflected in the wsdl - is that a problem in the wsdl generation or i am doing something wrong? You may found my services.xml attached thanks, Nencho - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sanka Samaranayake WSO2 Inc. http://www.bloglines.com/blog/sanka http://www.wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Amazon Web Service Java Library with Apache Axis2
Hi, Did you try including that library in lib folder in your service aar file? --Sanka Gia Hieu Dinh wrote: Hi all, I'm looking for invoking the Amazon Web Service inside my Axis2 web service. Amazon provides a java library to connect to the web services. http://developer.amazonwebservices.com/connect/entry.jspa?entryID=880ref=featured I have developed a standalone application with this library and it works fine. However, when I invoke it inside the Axis2 Web Service, I cannot reach the Amazon Web Service. I have copy these library to axis2/web-inf/lib and %TOMCAT_HOME%/share/lib, but nothing happens. Could you please help me figure out how to use this library? Thanks. Harry -- Sanka Samaranayake WSO2 Inc. http://www.bloglines.com/blog/sanka http://www.wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2 1.3] Metadata echange documentation
Hi sanka, Do we have any document on this ? Thanks Deepal Hi all, I need any documentation on the Metadata exchange module of axis2 1.3 (mex). thanks in advance Regards, Nencho - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best way to realize stateful servicesarchitecturewithmassivedata?
Steps similar to MTOM sample with file caching enabled. Received dataStream is loaded in XML object for further transformation. regards Yogesh robert lazarski [EMAIL PROTECTED] 10/22/2007 05:17 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Best way to realize stateful servicesarchitecturewithmassivedata? That's pretty kool. Did you use any streaming to avoid putting the data in memory and building the tree? Or did you just more or less follow the same steps in the mtom tutorial? Robert On 10/22/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi We were in similar situation we were planning to transfer 1GB file as SOAP as attachment. 1) Axis2 give pretty good support using MTOM and SWA for transferring any size file. 1GB file transferred in 67sec on local network. File caching feature is great. 2) But it is not good idea to transfer SOAP with such large attachment. We also hit some our app server service bus handling limitation. So we decided to process data in chunk. We get file data in chunk and till we get all data correctly we dont send confirm to end point (which really delete file on source system . End of our getFile operation / confirming file received at server ). Same way on reverse we put data in chunk to some temp file on destination endpoint. after placing all data at end we rename it to required file. Let me know your thoughts Regards Yogesh Dhake Walker, Jeff [EMAIL PROTECTED] 10/22/2007 11:46 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject RE: Best way to realize stateful servicesarchitecturewithmassivedata? Michele, I'm not sure JMS is a viable alternative if large amounts of data are transferred. That statement would imply there is some sort of size cutoff. There isn't. Just remember, that with JMS you can have persisted queues and then all of that data would have to be stored temporarily. Personally, I think some of the lessons from JMS (message queuing in general) can be applied to web services; keep the msgs as small as possible. Large data transfer (across the network) is a serious problem. There is no easy solution that I've seen. Having said that, there are quite a few posters who have used attachments with their web services. I have used the older DIME format, but other posters have used the newer MTOM. I would be interested to see what their performance was like, with large files (ie. around a Gigabyte, say). Since MTOM chunks up the files, transferring any sized file should theoretically be possible. Does anyone have any opinions on using MTOM for transferring Gb and and multi-Gb files?? -jeff -Original Message- From: Michele Mazzucco [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 11:21 AM To: axis-user@ws.apache.org Subject: RE: Best way to realize stateful servicesarchitecturewithmassivedata? Jeff, I mentioned JMS as possible choice if one has to transfer large amount of data since it is asynchronous. Michele On Mon, 2007-10-22 at 11:10 -0400, Walker, Jeff wrote: You mentioned WS over JMS. Again, added delay, since another protocol layer is employed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] == This transmittal and any attachments may contain confidential, privileged or sensitive information and is solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that you have received this transmittal and any attachments in error and any review, dissemination, distribution or copying thereof is strictly prohibited. If you have received this transmittal and any attachments in error please notify the sender and immediately destroy the message and all its attachments. Any opinions herein expressed may be those of the author and not necessarily of Mizuho Corporate Bank, Ltd., Mizuho Corporate Bank (USA), Mizuho Securities USA Inc. or any other affiliates of Mizuho Financial Group (Mizuho). Mizuho accepts no responsibility for the accuracy or completeness of any information herein contained. E-Mail received by or sent from officer of Mizuho Securities USA Inc. (which is a registered U.S. broker-dealer and the entity through which Mizuho generally conducts its investment banking, capital markets, and securities business in the United States) is electronically archived and recorded and is subject to review and monitoring by and/or disclosure to persons other than the recipient, including (but not limited to) Mizuho Securities USA Inc. supervisory personnel. Such
RE: AXIS Fault Required Attribute localType is null
Raghu, I do not see the type variable in the WSDL. I have attached the WSDL file. Thanks for the help ! regards -Saket Raizada 309-763-5492 Automation (Maintenance) From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 7:16 PM To: axis-user@ws.apache.org Subject: RE: AXIS Fault Required Attribute localType is null Hi Saket, Can you post your WSDL? From the Axis Fault it looks like you have a variable named type in the Incident object which is defined as not nullable in WSDL and you are not setting that in your request. Thanks Raghu From: Saket Raizada [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 3:48 PM To: axis-user@ws.apache.org Subject: AXIS Fault Required Attribute localType is null Hi Folks, I am using AXIS 2, 1.3 and created a client for an existing WebService I am trying to use the WebService to create an incident using the example code below StringType contact = new StringType(); contact.setString(user1); incident.setContact(contact); stub.createIncident(incident) I get an AXIS Fault Required Attribute localType is null , there is no SOAP body message generated..., however if i comment out the line //incident.setContact(contact) , the incident gets generated and i can see the SOAP messages etc. I am using ADB binding and am out of ideas what localType is (it's not part of incident or web service that i am trying to access) also no SOAP BODY XML is generated. Any pointers will be very helpful -machoq ?xml version=1.0 encoding=UTF-8 standalone=yes ?definitions targetNamespace=http://openview.hp.com/xmlns/SM/1; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:cmn=http://openview.hp.com/xmlns/SM/1/Common; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:ns=http://openview.hp.com/xmlns/SM/1; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://schemas.xmlsoap.org/wsdl/ http://schemas.xmlsoap.org/wsdl/;typesxs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; attributeFormDefault=unqualified elementFormDefault=qualified targetNamespace=http://openview.hp.com/xmlns/SM/1; version=2007-04-14 Rev 1 xmlns=http://openview.hp.com/xmlns/SM/1; xmlns:cmn=http://openview.hp.com/xmlns/SM/1/Common; xmlns:xmime=http://www.w3.org/2005/05/xmlmime;xs:import namespace=http://www.w3.org/2005/05/xmlmime; schemaLocation=http://www.w3.org/2005/05/xmlmime/xs:import namespace=http://openview.hp.com/xmlns/SM/1/Common; schemaLocation=http://xyz.com:111/SM/1/Common.xsd/xs:complexType name=Incidentxs:sequencexs:element minOccurs=0 name=IncidentID nillable=true type=cmn:StringType/xs:element minOccurs=0 name=Category nillable=true type=cmn:StringType/xs:element minOccurs=0 name=OpenTime nillable=true type=cmn:DateTimeType/xs:element minOccurs=0 name=OpenedBy nillable=true type=cmn:StringType/xs:element minOccurs=0 name=severity nillable=true type=cmn:StringType/xs:element minOccurs=0 name=UpdatedTime nillable=true type=cmn:DateTimeType/xs:element minOccurs=0 name=PrimaryAssignmentGroup nillable=true type=cmn:StringType/xs:element minOccurs=0 name=ClosedTime nillable=true type=cmn:DateTimeType/xs:element minOccurs=0 name=ClosedBy nillable=true type=cmn:StringType/xs:element minOccurs=0 name=ClosureCode nillable=true type=cmn:StringType/xs:element minOccurs=0 name=ConfigurationItem nillable=true type=cmn:StringType/xs:element minOccurs=0 name=Location nillable=true type=cmn:StringType/xs:element minOccurs=0 name=IncidentDescriptionxs:complexTypexs:complexContentxs:extension base=cmn:ArrayTypexs:sequencexs:element maxOccurs=unbounded minOccurs=0 name=IncidentDescription type=cmn:StringType//xs:sequence/xs:extension/xs:complexContent/xs:complexType/xs:elementxs:element minOccurs=0 name=Resolutionxs:complexTypexs:complexContentxs:extension base=cmn:ArrayTypexs:sequencexs:element maxOccurs=unbounded minOccurs=0 name=Resolution type=cmn:StringType//xs:sequence/xs:extension/xs:complexContent/xs:complexType/xs:elementxs:element minOccurs=0 name=AssigneeName nillable=true type=cmn:StringType/xs:element minOccurs=0 name=Contact nillable=true type=cmn:StringType/xs:element minOccurs=0 name=JournalUpdatesxs:complexTypexs:complexContentxs:extension base=cmn:ArrayTypexs:sequencexs:element maxOccurs=unbounded minOccurs=0 name=JournalUpdates type=cmn:StringType//xs:sequence/xs:extension/xs:complexContent/xs:complexType/xs:elementxs:element minOccurs=0 name=AlertStatus nillable=true type=cmn:StringType/xs:element minOccurs=0 name=ContactLastName nillable=true type=cmn:StringType/xs:element minOccurs=0 name=ContactFirstName nillable=true type=cmn:StringType/xs:element minOccurs=0 name=Company nillable=true type=cmn:StringType/xs:element minOccurs=0 name=BriefDescription nillable=true
My fresh token is already invalid!!! (Rampart throws NPE)
Hi All,
I have the SAML2 token issuer. I request it using STSClient:
Token responseToken = stsClient.requestSecurityToken(servicePolicy,
sts, stsPolicy, service);
Then I add it to the TokenStorage:
TokenStorage store = TrustUtil.getTokenStore(ctx);
store.add(responseToken); // now store contains my SAML2 token
The problem is when I try to get the list of valid tokens:
Token[] tokens = store.getValidTokens();
for (int i=0; itokens.length; i++)
{
l.info(Token in TokenStore + tokens[i].getId());
}
I don't enter in the for loop. When I try to send the message to the
endpoint, I got this:
16:21:15,931 INFO [XUAAssertions]
Payloadaxis2ns1:RegistryStoredQuery
xmlns:axis2ns1=http://tiani/xds;WSO2 WSAS
Rocks!!!/axis2ns1:RegistryStoredQuery
16:21:15,954 ERROR [STDERR] java.lang.NullPointerException
16:21:15,956 ERROR [STDERR] at
org.apache.rampart.builder.SymmetricBindingBuilder.initializeTokens(SymmetricBindingBuilder.java:681)
16:21:15,957 ERROR [STDERR] at
org.apache.rampart.builder.SymmetricBindingBuilder.build(SymmetricBindingBuilder.java:73)
In SymmetricBindingBuilder at the line 681 I have:
SecureConversationToken secConvTok =
(SecureConversationToken) sigTok;
try { -- this is the 681
String id = RampartUtil.getSecConvToken(rmd, secConvTok);
rmd.setSecConvTokenId(id);
I'm using rampart 1.3, and the code is from three days ago. It shouldn't be
here. Is not WS-SecConv.
My policy is:
wsp:Policy wsu:Id=ServicePolicy
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
wsp:ExactlyOne
wsp:All
sp:SymmetricBinding
xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
wsp:Policy
sp:ProtectionToken
wsp:Policy
sp:ProtectionToken
wsp:Policy
sp:IssuedToken
sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient;
Issuer
xmlns=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
Address
xmlns=http://www.w3.org/2005/08/addressing;
http://foo.bar/we/don/t/process/this/yet
/Address
/Issuer
sp:RequestSecurityTokenTemplate
t:TokenType
xmlns:t=http://schemas.xmlsoap.org/ws/2005/02/trust;
urn:oasis:names:tc:SAML:2.0:assertion
/t:TokenType
/sp:RequestSecurityTokenTemplate
/sp:IssuedToken
/wsp:Policy
wsp:Policy
sp:IncludeTimestamp /
/wsp:Policy
/sp:ProtectionToken
/wsp:Policy
/sp:ProtectionToken
/wsp:Policy
/sp:SymmetricBinding
/wsp:All
/wsp:ExactlyOne
/wsp:Policy
This message was sent using IMP, the Internet Messaging Program.
-
To unsubscribe, e-mail: [EMAIL
AXIS1 Problem with generated sources: Params were mixed up within super constructor.
Hello, I have a troble while building the sources generated by Axis1 1.4. There's a problem with super constructor, it looks like params were mixed up within. For example, there are two classes: one is MarkupContext which extends MimeResponse. Constructor of MimeResponse is generated in such a way that described attribute is at the end. But, constructor of MarkupContext invokes super with the attribute placed as a first param. == complexType name=MimeResponse sequence element name=useCachedItem type=xsd:boolean default=false minOccurs=0/ element name=mimeType type=xsd:string minOccurs=0/ element name=itemString type=xsd:string minOccurs=0/ element name=itemBinary type=xsd:base64Binary minOccurs=0/ element name=locale type=xsd:string minOccurs=0/ element name=requiresRewriting type=xsd:boolean default=false minOccurs=0/ element name=cacheControl type=types:CacheControl minOccurs=0/ element name=clientAttributes type=types:NamedString minOccurs=0/ element name=extensions type=types:Extension minOccurs=0 maxOccurs=unbounded/ /sequence attribute name=ccppProfileWarning type=xsd:string use=optional/ /complexType element name=MimeResponse type=types:MimeResponse/ complexType name=MarkupContext complexContent extension base=types:MimeResponse sequence element name=preferredTitle type=xsd:string minOccurs=0/ element name=validNewModes type=xsd:string minOccurs=0 maxOccurs=unbounded/ /sequence /extension /complexContent /complexType element name=MarkupContext type=types:MarkupContext/ == Regards, Alexey. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JBoss and Apache Axis compatibility
I am using JBOSS and Axis 1.4 and they work fine. Its just plain java objects communication between jboss and axis so I am not sure why you are concerned with rpc encoding style.. Arun Sivaraman [EMAIL PROTECTED] wrote: I'm in the midst of integrating two components, one runs in JBoss and other components exposes some web services deployed in Axis. When i integrate them, there will be a communication between component deployed in JBOSS and Web services exposed via Axis. If i understand correctly, AXIS by default uses RPC service style and JBOSS uses document/literal encoding format. So there is a notion of soap-wsdl encoding format change required here. All i wanted to know is that, 1.Is there any compatibility issues (if any) between JBOSS and Axis ? 2.JBOSS-Axis interaction with respect to the soap encoding format ? 3.Some explanation on SOAP encodingStyle ? Expecting ur favorable reply Regards Arun Email :[EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JBoss-and-Apache-Axis-compatibility-tf4675459.html#a13358175 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: org.apache.axis2.databinding.ADBException: Property cannot be null!
Excellent! Thanks very much. Somehow -Eosv does not solve the problem.
So I put the nillable=true in the element there, and it works.
Amila Suriarachchi wrote:
this means your object structure do not have loaded the required fault
elements.
see you schema there should be an element named fault without
minOccurs=0 or nillable=ture.
So ADB gives an exception because of this.
if you want to remove this use -Eosv when genrating the code.
Amia.
On 10/23/07, *Huitang Li* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi,
I created a web service code based on a wsdl, and it is run in resin
3.1.3, and I have the soapmonitor activated. When a web service
client
sent a soap message to it, it threw the following exception:
java.lang.RuntimeException: Can not serialize OM Element Envelope
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:916)
at
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(SOAPMonitorHandler.java:101)
at org.apache.axis2.engine.Phase.invoke (Phase.java:292)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
at
org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:442)
at
org.apache.axis2.transport.http.AxisServlet.handleFault
(AxisServlet.java:403)
at
org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:366)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:154)
at javax.servlet.http.HttpServlet.service (HttpServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:91)
at
com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java:103)
at
com.caucho.server.security.SecurityFilterChain.doFilter
(SecurityFilterChain.java:134)
at
com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:178)
at
com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:241)
at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:268)
at
com.caucho.server.port.TcpConnection.run(TcpConnection.java:586)
at com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java :690)
at com.caucho.util.ThreadPool$Item.run(ThreadPool.java:612)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.axis2.databinding.ADBException: Property
cannot be
null!
at test.Fault.serialize (Fault.java:95)
at test.Fault$1.serialize(Fault.java:80)
at
org.apache.axis2.databinding.ADBDataSource.serialize(ADBDataSource.java:82)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume
(OMSourcedElementImpl.java:599)
at
org.apache.axiom.soap.impl.llom.SOAPFaultDetailImpl.internalSerialize(SOAPFaultDetailImpl.java:86)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java
:756)
at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.internalSerialize(SOAPFaultImpl.java:192)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
(OMElementImpl.java:772)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java
:210)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString
(OMElementImpl.java:913)
... 18 more
This exception will not be shown when all elements in the requesting
soap message are filled with non-empty (no-blankspace) values.
I notice that the exception is thrown from the following
axis2-generated
code:
public void serialize(final javax.xml.namespace.QName parentQName,
final org.apache.axiom.om.OMFactory factory,
org.apache.axis2.databinding.utils.writer.MTOMAwareXMLStreamWriter
xmlWriter)
throws javax.xml.stream.XMLStreamException,
org.apache.axis2.databinding.ADBException {
//We can safely assume an element has only one type associated
with it
if (localFault == null) {
throw new org.apache.axis2.databinding.ADBException(
Property cannot be null!);
the line where the exception is thrown.
}
localFault.serialize(MY_QNAME, factory, xmlWriter);
}
My question is: In the line where the exception is thrown, why is the
parameter localFault null? How to
[Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference
Maybe someone can give a little insight into the issue(s) that I am having. We are trying to embed Axis2 (1.3) into a internal application via Tomcat (5.5) Tomcat seems to be working fine (it's used for other war deployments) and the axis2.war deploys fine (see below) Deployment code Context context = embedded.createContext(/axis2, axis2.war); context.setReloadable(false); host.addChild(context); War being deployed [java] Oct-23-07 11:36:11.081 : INFO : main : org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache Tomcat/5.5.17 [java] Oct-23-07 11:36:11.091 : INFO : main : org.apache.catalina.core.StandardHost : XML validation disabled [java] Oct-23-07 11:36:11.293 : INFO : main : rg.apache.catalina.startup.ContextConfig : No default web.xml [java] Oct-23-07 11:36:11.915 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3 [java] Oct-23-07 11:36:11.925 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3 [java] Oct-23-07 11:36:11.949 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: addressing-1.3 [java] Oct-23-07 11:36:11.960 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: soapmonitor-1.3 [java] Oct-23-07 11:36:11.971 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: metadataExchange-1.3 [java] Oct-23-07 11:36:12.010 : INFO : main : org.apache.axis2.scripting.ScriptModule : script module activated [java] Oct-23-07 11:36:12.189 : INFO : main : .apache.axis2.deployment.ServiceDeployer : Deploying Web service: version.aar The issue that I am having is that once axis is deployed, about the only things I can get to come back are the following From the request (http://BLAHBLASH/axis2/services) soapenv:Reason xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Text xml:lang=en-USThe service cannot be found for the endpoint reference (EPR) /axis2/services/soapenv:Text /soapenv:Reason It looks like things are close to working and that I am just missing something. Can anyone help shed any light on this? Also, not sure if this helps, but I also get the following when I try to just access the context url From the request (http://BLAHBLASH/axis2/) HTTP Status 404 - /axis2/ type Status report message /axis2/ description The requested resource (/axis2/) is not available. Apache Tomcat/5.5.17 And a NPE from the console of the server of [java] java.lang.NullPointerException [java] at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363 ) [java] at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284 ) [java] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136 ) [java] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105 ) [java] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :107) [java] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) [java] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) [java] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(Http11BaseProtocol.java:664) [java] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav a:527) [java] at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo rkerThread.java:80) [java] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:684) [java] at java.lang.Thread.run(Thread.java:595) James Maes Software Architect Materialogic PH: 800-333-7144 PH: 314-997-4342 Ext. 3422 FX: 314-997-7814 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error creating message from generated client
No, the client throws the exception when trying to create the request message. It doesn't actually reach the server. Kimberly Nicholls keith chapman wrote: I presume this error occurs when you receive the response. Can you check the messages using TCP Monitor please and post it here. Thanks, Keith. On 10/22/07, * Kimberly Nicholls* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I am having trouble creating a SOAP message from a generated client when the message includes attachments -- the client throws org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html. I am using axis2 1.3, and I can make requests to other methods (without attachments) in the same service with no problems. Here's what I did: - set enableMTOM to true in axis2.xml - created method in my POJO service: public long createAttachment(long messageID, DataHandler attData) - generated client stub via wsdl2java - added these lines to client stub: _serviceClient.getOptions().setProperty( Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE); _serviceClient.getOptions().setTimeOutInMilliSeconds(1); - created client that runs the method like this: DataHandler attData = new DataHandler(new FileDataSource(filename)); long attachmentID = stub.createAttachment(messageID, attData); When I run the client, I get [INFO] OMException in getSOAPBuilder org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:219) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:177) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:163) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:161) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:110) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:609) at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:178) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:326) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) ... Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:219) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:177) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:163) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:161) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:110) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:609) at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:178) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:87) ... 6 more Running other methods in the same client with the same service work fine, if they don't have attachments. The file I'm trying to send is a 2.5k jpg. What am I doing wrong? Kimberly -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference
Check accessing these links in your server. http://blahblash/axis2/axis2-web/ For console home page http://blahblash/axis2/services/listServices For deployed services Upul On 10/23/07, James Maes [EMAIL PROTECTED] wrote: Maybe someone can give a little insight into the issue(s) that I am having. We are trying to embed Axis2 (1.3) into a internal application via Tomcat (5.5) Tomcat seems to be working fine (it's used for other war deployments) and the axis2.war deploys fine (see below) Deployment code Context context = embedded.createContext(/axis2, axis2.war); context.setReloadable(false); host.addChild(context); War being deployed [java] Oct-23-07 11:36:11.081 : INFO : main : org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache Tomcat/5.5.17 [java] Oct-23-07 11:36:11.091 : INFO : main : org.apache.catalina.core.StandardHost : XML validation disabled [java] Oct-23-07 11:36:11.293 : INFO : main : rg.apache.catalina.startup.ContextConfig : No default web.xml [java] Oct-23-07 11:36:11.915 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3 [java] Oct-23-07 11:36:11.925 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3 [java] Oct-23-07 11:36:11.949 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: addressing-1.3 [java] Oct-23-07 11:36:11.960 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: soapmonitor-1.3 [java] Oct-23-07 11:36:11.971 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: metadataExchange-1.3 [java] Oct-23-07 11:36:12.010 : INFO : main : org.apache.axis2.scripting.ScriptModule : script module activated [java] Oct-23-07 11:36:12.189 : INFO : main : .apache.axis2.deployment.ServiceDeployer : Deploying Web service: version.aar The issue that I am having is that once axis is deployed, about the only things I can get to come back are the following From the request (http://BLAHBLASH/axis2/services) soapenv:Reason xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Text xml:lang=en-USThe service cannot be found for the endpoint reference (EPR) /axis2/services/soapenv:Text /soapenv:Reason It looks like things are close to working and that I am just missing something. Can anyone help shed any light on this? Also, not sure if this helps, but I also get the following when I try to just access the context url From the request (http://BLAHBLASH/axis2/) HTTP Status 404 - /axis2/ type Status report message /axis2/ description The requested resource (/axis2/) is not available. Apache Tomcat/5.5.17 And a NPE from the console of the server of [java] java.lang.NullPointerException [java] at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java :363 ) [java] at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java :284 ) [java] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :136 ) [java] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105 ) [java] at org.apache.catalina.core.StandardEngineValve.invoke( StandardEngineValve.java :107) [java] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java :148) [java] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) [java] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(Http11BaseProtocol.java:664) [java] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket( PoolTcpEndpoint.jav a:527) [java] at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWo rkerThread.java:80) [java] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( ThreadPool.jav a:684) [java] at java.lang.Thread.run(Thread.java:595) James Maes Software Architect Materialogic PH: 800-333-7144 PH: 314-997-4342 Ext. 3422 FX: 314-997-7814 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
New stup for each call
Hello, Do I have to create new stub before each call ? In my case i have EJB that calls webservice. If i save aquired port in attribute and use it in multiple calls i get some strange exception. MainQueryEngineBean.doQuery().engine:[EMAIL PROTECTED] PWC1635: Illegal access: this web application instance has been stopped already (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) urlSet = [URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/AllegroWebApi.jar, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/BidBull-ejb.jar, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/AllegroEngine-ejb.jar, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/MainQueryEngine-ejb_jar/, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/AllegroEngine-ejb_jar/, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/BidBull-ejb_jar/, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/MainQueryEngine-ejb.jar, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/applications/j2ee-apps/BidBull/BidBull-war_war/WEB-INF/classes/, URLEntry : file:/opt/glassfish-v2-b58/domains/domain1/generated/ejb/j2ee-apps/BidBull/] doneCalled = false Parent - EJBClassLoader : urlSet = [] doneCalled = false Parent - [EMAIL PROTECTED] AT Tue Oct 23 19:40:29 CEST 2007 BY :com.sun.enterprise.loader.EJBClassLoader.printStackTraceToString(EJBClassLoader.java:812) com.sun.enterprise.loader.EJBClassLoader.done(EJBClassLoader.java:172) com.sun.enterprise.server.AbstractLoader.done(AbstractLoader.java:359) com.sun.enterprise.server.ApplicationLoader.unload(ApplicationLoader.java:264) com.sun.enterprise.server.TomcatApplicationLoader.unload(TomcatApplicationLoader.java:213) com.sun.enterprise.server.ApplicationManager.applicationUndeployed(ApplicationManager.java:525) com.sun.enterprise.server.ApplicationManager.applicationUndeployed(ApplicationManager.java:699) com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:930) com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912) com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461) com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176) com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308) com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226) com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStopEvent(ServerDeploymentTarget.java:332) com.sun.enterprise.deployment.phasing.ApplicationStopPhase.runPhase(ApplicationStopPhase.java:136) com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919) com.sun.enterprise.deployment.phasing.PEDeploymentService.stop(PEDeploymentService.java:652) com.sun.enterprise.deployment.phasing.PEDeploymentService.stop(PEDeploymentService.java:699) com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.stop(ApplicationsConfigMBean.java:767) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375) com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358) com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464) com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90) $Proxy1.invoke(Unknown Source) com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304) com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174) com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69) com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference
When requesting the URL (http://BLAHBLAH/axis2/axis2-web/) I get this response HTTP Status 404 - /axis2/axis2-web/ type Status report message /axis2/axis2-web/ description The requested resource (/axis2/axis2-web/) is not available. Apache Tomcat/5.5.17 And this on the server console [java] Oct-23-07 12:45:04.917 : ERROR : http-8081-Processor3 : g.apache.catalina.core.StandardHostValve : Exception Processing ErrorPage[errorCode=404, location=/axis2-web/Error/error404.jsp] [java] java.lang.NullPointerException [java] at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363 ) [java] at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284 ) [java] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136 ) [java] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105 ) [java] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :107) [java] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) [java] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) [java] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(Http11BaseProtocol.java:664) [java] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav a:527) [java] at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo rkerThread.java:80) [java] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:684) [java] at java.lang.Thread.run(Thread.java:595) James Maes Software Architect Materialogic PH: 800-333-7144 PH: 314-997-4342 Ext. 3422 FX: 314-997-7814 From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 12:37 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference Check accessing these links in your server. http://blahblash/axis2/axis2-web/ For console home page http://blahblash/axis2/services/listServices For deployed services Upul On 10/23/07, James Maes [EMAIL PROTECTED] wrote: Maybe someone can give a little insight into the issue(s) that I am having. We are trying to embed Axis2 (1.3) into a internal application via Tomcat (5.5) Tomcat seems to be working fine (it's used for other war deployments) and the axis2.war deploys fine (see below) Deployment code Context context = embedded.createContext(/axis2, axis2.war); context.setReloadable(false); host.addChild (context); War being deployed [java] Oct-23-07 11:36:11.081 : INFO : main : org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache Tomcat/5.5.17 [java] Oct-23-07 11:36: 11.091 : INFO : main : org.apache.catalina.core.StandardHost : XML validation disabled [java] Oct-23-07 11:36:11.293 : INFO : main : rg.apache.catalina.startup.ContextConfig : No default web.xml [java] Oct-23-07 11:36:11.915 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3 [java] Oct-23-07 11:36:11.925 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3 [java] Oct-23-07 11:36:11.949 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: addressing-1.3 [java] Oct-23-07 11:36:11.960 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: soapmonitor-1.3 [java] Oct-23-07 11:36:11.971 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: metadataExchange-1.3 [java] Oct-23-07 11:36:12.010 : INFO : main : org.apache.axis2.scripting.ScriptModule : script module activated [java] Oct-23-07 11:36:12.189 : INFO : main : .apache.axis2.deployment.ServiceDeployer : Deploying Web service: version.aar The issue that I am having is that once axis is deployed, about the only things I can get to come back are the following From the request (http://BLAHBLASH/axis2/services) soapenv:Reason xmlns:soapenv= http://www.w3.org/2003/05/soap-envelope; soapenv:Text xml:lang=en-USThe service cannot be found for the endpoint reference (EPR) /axis2/services/soapenv:Text /soapenv:Reason It looks like things are close to working and that I am just missing something. Can anyone help shed any light on this? Also, not sure if this helps, but I also get the following when I try to just access the
Re: [Axis2] - Incorrect operation name in SOAP response under Load
We're encountering a strange issue during the Load Test of our Webservice
(using Axis2) on IBM Websphere 6.1. Under high loads, the function name in the
response is being returned incorrectly. For example, if the SOAP request is
for getABC(), the correct code is being executed by the webservice and the
correct data is being returned but the name of the function in the SOAP
response is getXYZ instead. Note, getXYZ is also a valid operation in the
Webservice but the call was not made to it. No errors in app server logs and
under low volumes everything works great.
RESPONSE:
?xml version='1.0' encoding='utf-8'?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
ns:getXYZ xmlns:ns=http://webservice.edars.eo/xsd; -
INSTEAD OF getABC -
ns:return
CORRECT DATA BEING RETURNED HERE
/ns:return
/ns:getXYZ - INSTEAD OF getABC -
/soapenv:Body
/soapenv:Envelope
Anyone seen this before or have any ideas as to how to tackle it? I've never
encountered this in Axis 1.x and am wondering if there's some caching
etc going on that may be causing it by multi-thread access. Saw below in JIRA
and was wondering if there was any relation?? Appreciate your input.
AXIS2-2794
- Axis2 contexts use
unsyncronized HashMap instead of Hashtables
Created: 11/Jun/07 12:33 PM
Updated: 11/Jun/07 02:44 PM
Component/s:
kernel
Affects Version/s:
1.3
Fix Version/s:
None
Description
« Hide
Axis2 context hierachy uses HashMaps to store the properties and since
HashMaps are not syncronized, the results of multitreaded access is not
undefinded. It is advisable to switch to Hashtables. However we have
not seen this error happens so far in our bug reports, which is indeed
stange enough.
Description
Axis2 context hierachy uses HashMaps to store the properties and since
HashMaps are not syncronized, the results of multitreaded access is not
undefinded. It is advisable to switch to Hashtables. However we have
not seen this error happens so far in our bug reports, which is indeed
stange enough.
Show »
!--
restoreDivFromCookie('description-open', 'jira.viewissue.cong.cookie', '1');
restoreDivFromCookie('description-closed', 'jira.viewissue.cong.cookie',
'0');
//--
-Ab
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
RE: AXIS Fault Required Attribute localType is null
Hi Saket, Can you also post your Common.xsd file which has the definition of all the Types. Thanks Raghu From: Saket Raizada [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 6:38 AM To: axis-user@ws.apache.org Subject: RE: AXIS Fault Required Attribute localType is null Raghu, I do not see the type variable in the WSDL. I have attached the WSDL file. Thanks for the help ! regards -Saket Raizada 309-763-5492 Automation (Maintenance) From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 7:16 PM To: axis-user@ws.apache.org Subject: RE: AXIS Fault Required Attribute localType is null Hi Saket, Can you post your WSDL? From the Axis Fault it looks like you have a variable named type in the Incident object which is defined as not nullable in WSDL and you are not setting that in your request. Thanks Raghu From: Saket Raizada [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 3:48 PM To: axis-user@ws.apache.org Subject: AXIS Fault Required Attribute localType is null Hi Folks, I am using AXIS 2, 1.3 and created a client for an existing WebService I am trying to use the WebService to create an incident using the example code below StringType contact = new StringType(); contact.setString(user1); incident.setContact(contact); stub.createIncident(incident) I get an AXIS Fault Required Attribute localType is null , there is no SOAP body message generated..., however if i comment out the line //incident.setContact(contact) , the incident gets generated and i can see the SOAP messages etc. I am using ADB binding and am out of ideas what localType is (it's not part of incident or web service that i am trying to access) also no SOAP BODY XML is generated. Any pointers will be very helpful -machoq
Re: Which style am I using?
Dimitris, The snippet of your WSDL isn't valid. This: wsdl:part name=part1 element=ns0:viewObservation/ should be this: wsdl:part name=part1 element=ns0:viewLesson/ We actually don't have enough information to determine if the style is wrapped doc/literal. What is the name of the operation? If it is viewLesson, then most toolkits will interpret the style as wrapped doc/literal. If you want all toolkits to recognize it as wrapped doc/literal, then the part names should be parameters rather than part1, e.g.: wsdl:part name=parameters element=ns0:viewLesson/ For more information on the wrapped style, see these links: http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html http://pzf.fremantle.org/2007/05/handlign.html Anne On 10/23/07, Dimitris Mouchritsas [EMAIL PROTECTED] wrote: Hi everyone, I'm kind of new in web services so I need your help once again. Say I have the following wsdl: wsdl:definitions targetNamespace=http://www.example.org wsdl:documentation Blah blah /wsdl:documentation wsdl:types xs:schema targetNamespace=http://www.example.org attributeFormDefault=qualified elementFormDefault=qualified xs:element name=viewLesson xs:complexType xs:sequence xs:element name=lesson_id type=xs:long/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=viewLessonMessage wsdl:part name=part1 element=ns0:viewObservation/ /wsdl:message wsdl:message name=viewLessonResponse wsdl:part name=part1 element=ns0:viewLessonResponse/ /wsdl:message so I send and receive messages like (minus the soap envelope): ns0:viewLesson ...namespace stuff ns0:lesson_id1/ns0:lesson_id /ns0:viewLesson Which style am I using? I think I'm using document/wrapped but am I right? I've read the developer works article on this but I'm not certain yet. Thanks in advance. -- Dimitris Mouchritsas Computer Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AXIS Fault Required Attribute localType is null
Hi Raghu, The common.xsd contained this information for the value i was setting and i see that the type value must be set. In the generated StringType.java i see a function to set the type and i also see that it sends an error Required Attribute localType is null if the type is not set. Thanks a lot for your help ! Below is the snippet from the Commons.xsd - http://ov95dev2.opr.test.statefarm.org:13080/SM/1/Common.xsd# xs:complexType name=StringType - http://ov95dev2.opr.test.statefarm.org:13080/SM/1/Common.xsd# xs:simpleContent - http://ov95dev2.opr.test.statefarm.org:13080/SM/1/Common.xsd# xs:extension base=xs:string xs:attribute fixed=String name=type type=xs:string use=required / xs:attribute name=mandatory type=xs:boolean use=optional / xs:attribute name=readonly type=xs:boolean use=optional / /xs:extension /xs:simpleContent /xs:complexType regards -Saket Raizada From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 1:08 PM To: axis-user@ws.apache.org Subject: RE: AXIS Fault Required Attribute localType is null Hi Saket, Can you also post your Common.xsd file which has the definition of all the Types. Thanks Raghu From: Saket Raizada [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 6:38 AM To: axis-user@ws.apache.org Subject: RE: AXIS Fault Required Attribute localType is null Raghu, I do not see the type variable in the WSDL. I have attached the WSDL file. Thanks for the help ! regards -Saket Raizada 309-763-5492 Automation (Maintenance) From: Raghu Upadhyayula [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 7:16 PM To: axis-user@ws.apache.org Subject: RE: AXIS Fault Required Attribute localType is null Hi Saket, Can you post your WSDL? From the Axis Fault it looks like you have a variable named type in the Incident object which is defined as not nullable in WSDL and you are not setting that in your request. Thanks Raghu From: Saket Raizada [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 3:48 PM To: axis-user@ws.apache.org Subject: AXIS Fault Required Attribute localType is null Hi Folks, I am using AXIS 2, 1.3 and created a client for an existing WebService I am trying to use the WebService to create an incident using the example code below StringType contact = new StringType(); contact.setString(user1); incident.setContact(contact); stub.createIncident(incident) I get an AXIS Fault Required Attribute localType is null , there is no SOAP body message generated..., however if i comment out the line //incident.setContact(contact) , the incident gets generated and i can see the SOAP messages etc. I am using ADB binding and am out of ideas what localType is (it's not part of incident or web service that i am trying to access) also no SOAP BODY XML is generated. Any pointers will be very helpful -machoq
RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference
After digging into the Axis code, it looks like the problem is caused by the following The RequestDispatch returned from httpServletRequest.getRequestDispatcher(Constants.AXIS_WEB_CONTENT_ROOT + jspName).include(httpServletRequest, httpServletResponse); in AbstractAgent.java (renderView method) is null. The following are the inputs that were passed into that call. Constants.AXIS_WEB_CONTENT_ROOT [/axis2-web/] jspName [listServices.jsp] I assume that this all points to something miss configured on my end on my part, but I am out of ideas. Does this help shed any light on the issue for anyone? James Maes Software Architect Materialogic PH: 800-333-7144 PH: 314-997-4342 Ext. 3422 FX: 314-997-7814 -Original Message- From: James Maes [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 12:46 PM To: axis-user@ws.apache.org Subject: RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference When requesting the URL (http://BLAHBLAH/axis2/axis2-web/) I get this response HTTP Status 404 - /axis2/axis2-web/ type Status report message /axis2/axis2-web/ description The requested resource (/axis2/axis2-web/) is not available. Apache Tomcat/5.5.17 And this on the server console [java] Oct-23-07 12:45:04.917 : ERROR : http-8081-Processor3 : g.apache.catalina.core.StandardHostValve : Exception Processing ErrorPage[errorCode=404, location=/axis2-web/Error/error404.jsp] [java] java.lang.NullPointerException [java] at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:363 ) [java] at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:284 ) [java] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136 ) [java] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105 ) [java] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :107) [java] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) [java] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) [java] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(Http11BaseProtocol.java:664) [java] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav a:527) [java] at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo rkerThread.java:80) [java] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:684) [java] at java.lang.Thread.run(Thread.java:595) James Maes Software Architect Materialogic PH: 800-333-7144 PH: 314-997-4342 Ext. 3422 FX: 314-997-7814 From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 12:37 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference Check accessing these links in your server. http://blahblash/axis2/axis2-web/ For console home page http://blahblash/axis2/services/listServices For deployed services Upul On 10/23/07, James Maes [EMAIL PROTECTED] wrote: Maybe someone can give a little insight into the issue(s) that I am having. We are trying to embed Axis2 (1.3) into a internal application via Tomcat (5.5) Tomcat seems to be working fine (it's used for other war deployments) and the axis2.war deploys fine (see below) Deployment code Context context = embedded.createContext(/axis2, axis2.war); context.setReloadable(false); host.addChild (context); War being deployed [java] Oct-23-07 11:36:11.081 : INFO : main : org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache Tomcat/5.5.17 [java] Oct-23-07 11:36: 11.091 : INFO : main : org.apache.catalina.core.StandardHost : XML validation disabled [java] Oct-23-07 11:36:11.293 : INFO : main : rg.apache.catalina.startup.ContextConfig : No default web.xml [java] Oct-23-07 11:36:11.915 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: ping-1.3 [java] Oct-23-07 11:36:11.925 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: script-1.3 [java] Oct-23-07 11:36:11.949 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: addressing-1.3 [java] Oct-23-07 11:36:11.960 : INFO : main : g.apache.axis2.deployment.ModuleDeployer : Deploying module: soapmonitor-1.3
nested complex types
Hi all :).
I'm having some trouble getting nested complex types to work correctly.
I'm noticing that for members of the generated class, instead of using
the generated Wrapper class ( which it does generate ) , it uses
OMElement.
When I run wsdl2java I get several warnings about missing types, for
example :
[WARN] Type {urn:beagle}CompanyBasicInfo missing!
I noticed that the items that don't give me warnings are declared like
this:
complexType name=UsUkSICMapRecord
sequence
element name=us-sic-code type=xsd:string minOccurs=1
maxOccurs=1/
element name=uk-sic-code type=xsd:string minOccurs=1
maxOccurs=1/
/sequence
/complexType
and all the ones that it complains are missing are declared like:
element name=CompanyBasicInfo
complexType
sequence
element name=gid type=xsd:string minOccurs=1 maxOccurs=1/
element name=duns type=xsd:string minOccurs=1
element name=misc type=ns:CompanyRecord minOccurs=1
maxOccurs=1/
...
/sequence
/complexType
/element
The wsdl file I'm using was created by gSOAP, and I'm using Axis2-1.3,
and java1.6 on ubuntu amd64.
Thanks!
Charlie
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How Axis Callback works?
I have queried service using WSDL generated and can see XML Response out
put..
Using
1. stub.query_my_record(my_Record_Query__Message5);
2. stub.startquery_my_record(my_Record_Query__Message5,
O_tempCallbackN1000C);
Here O_tempCallbackN1000C is callback object.
But I am not sure How Axis Callback works? Can Callback and its method
getClientData() can b used for getting java response object?
public my_Record_Query_ProviderCallbackHandler(Object clientData) {
this.clientData = clientData;
}
/**
* Please use this constructor if you don't want to set any
clientData
*/
public my_Record_Query_ProviderCallbackHandler() {
this.clientData = null;
}
/**
* Get the client data
*/
public Object getClientData() {
return clientData;
}
What I am trying to do is get the Java response object back from
stub/callback. Your help is greatly appreciated.
Regards
AJ
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).
Hi, I have a problem with the soap:address location generated when I browse the WSDL in the browser. I'm using Axis2 1.3. I'm looking at the WSDL in the browser using http://ws.qa.company.com/webservices/services/MyWSService?wsdl I get the WSDL and the soap:address location in the WSDL looks like soap:address location=http://10.5.2.182:80/webservices/services/MyWSService http://10.5.2.182/webservices/services/MyWSService / But then problem is with the IP Address coming in the soap:address location 10.5.2.182 is not a public IP that is accessible from Internet. What changes should I do to change the soap:address location to look like soap:address location=http://ws.qa.company.com/webservices/MyWSService / Another thing, I found is that this is working fine if I use ?wsdl2 in the URL above. Note: In my services.xml I have useOriginalWSDL property set to true and modifyUserWSDLPortAddress was also set to true. I've tried changing modifyUserWSDLPortAddress to false, but what happened in that case was the soap:address location was not modified at all. The soap:address location case as http://localhost:80/webservices/services/MyWSService http://localhost/webservices/services/MyWSService because the original WSDL had this address in the soap:address location, since the localhost was coming as it it, I've change the modifyUserWSDLPortAddress property back to true. Thanks in Advance. Raghu
[Axis2] Problem with soap:address location in the WSDL (IP Address is not a public IP that is accessible from Internet).
Hi, I have a problem with the soap:address location generated when I browse the WSDL in the browser. I'm using Axis2 1.3. I'm looking at the WSDL in the browser using http://ws.qa.company.com/webservices/services/MyWSService?wsdl I get the WSDL and the soap:address location in the WSDL looks like soap:address location=http://10.5.2.182:80/webservices/services/MyWSService http://10.5.2.182/webservices/services/MyWSService / But then problem is with the IP Address coming in the soap:address location 10.5.2.182 is not a public IP that is accessible from Internet. What changes should I do to change the soap:address location to look like soap:address location=http://ws.qa.company.com/webservices/services/MyWSService http://ws.qa.company.com/webservices/MyWSService / Another thing, I found is that this is working fine if I use ?wsdl2 in the URL above. Note: In my services.xml I have useOriginalWSDL property set to true and modifyUserWSDLPortAddress was also set to true. I've tried changing modifyUserWSDLPortAddress to false, but what happened in that case was the soap:address location was not modified at all. The soap:address location case as http://localhost:80/webservices/services/MyWSService http://localhost/webservices/services/MyWSService because the original WSDL had this address in the soap:address location, since the localhost was coming as it, I've change the modifyUserWSDLPortAddress property back to true. Thanks in Advance. Raghu
Axis2 1.3 wsdl2java generates code with missing methods
I am using wsdl2java to generate java code from a wsdl using wsdl2java options -o -ss -sd -ssi -f -uw -uri -ns2p. The result includes a MessageReceiverInOut class that is missing a method resulting in a compiletime error method wrapIsUploadAllowed(OperationStatusType) is undefined for the type ...MessageReceiverInOut. I observed that this seems to happen when wsdl parts in different messages refer to the same complex type. In such cases, the wrap methods in the MessageReceiver class for the first operation is created while that for the other one is not created. E.g. in this case the method wrapUpload(OperationStatusType) gets created while wrapIsUploadAllowed(OperationStatusType) is missing. Wsdl snippet is included below. Is this a bug? s:complexType name=OperationStatusType s:sequence s:element name=successFlag type=s:boolean/ s:element name=messageLevel type=s:string/ s:element name=messageCode type=s:string/ s:element name=message type=s:string/ /s:sequence /s:complexType s:element name=OperationStatusElement type=tns:OperationStatusType/ s:element name=UploadRequestElement s:complexType s:sequence s:element name=sessiontoken type=s:string/ s:element name=trackingnumber type=s:string/ s:element name=version type=s:int/ /s:sequence /s:complexType /s:element s:element name=IsUploadAllowedRequestElement s:complexType s:sequence s:element name=SessionToken type=s:string/s:element s:element name=TrackingNumber type=s:string/s:element s:element name=Version type=s:int/s:element /s:sequence /s:complexType /s:element ... wsdl:message name=UploadRequest wsdl:part name=uploadrequest element=tns:UploadRequestElement/wsdl:part /wsdl:message wsdl:message name=UploadResponse wsdl:part name=uploadoperationstatus element=tns:OperationStatusElement/wsdl:part /wsdl:message wsdl:message name=IsUploadAllowedRequest wsdl:part name=uploadcheckrequest element=tns:IsUploadAllowedRequestElement/wsdl:part /wsdl:message wsdl:message name=IsUploadAllowedResponse wsdl:part name=uploadcheckoperationstatus element=tns:OperationStatusElement/wsdl:part /wsdl:message ... wsdl:operation name=Upload wsdl:input message=tns:UploadRequest/wsdl:input wsdl:output message=tns:UploadResponse/wsdl:output /wsdl:operation wsdl:operation name=IsUploadAllowed wsdl:input message=tns:IsUploadAllowedRequest/wsdl:input wsdl:output message=tns:IsUploadAllowedResponse/wsdl:output /wsdl:operation ... soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=Upload soap:operation soapAction= style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation wsdl:operation name=IsUploadAllowed
Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference
Actually the Axis2 web service engine is working fine. You can depoly aar in the services directory and access them. (e.g. /axis2/services/Version?wsdl) From the request (http://BLAHBLASH/axis2/serviceshttp://blahblash/axis2/services ) soapenv:Reason xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Text xml:lang=en-USThe service cannot be found for the endpoint reference (EPR) /axis2/services/soapenv:Text /soapenv:Reason Instead of deploying the axis2.war file directly, unzip the war file and deploy as an exploded archive Context context = embedded.createContext(/axis2, /path/to/axis2); Also check whether there is an axis2-web directory in you exploded war directory, which is only an admin console. Upul On 10/24/07, James Maes [EMAIL PROTECTED] wrote: After digging into the Axis code, it looks like the problem is caused by the following The RequestDispatch returned from httpServletRequest.getRequestDispatcher(Constants.AXIS_WEB_CONTENT_ROOT + jspName).include(httpServletRequest, httpServletResponse); in AbstractAgent.java (renderView method) is null. The following are the inputs that were passed into that call. Constants.AXIS_WEB_CONTENT_ROOT [/axis2-web/] jspName [listServices.jsp] I assume that this all points to something miss configured on my end on my part, but I am out of ideas. Does this help shed any light on the issue for anyone? James Maes Software Architect Materialogic PH: 800-333-7144 PH: 314-997-4342 Ext. 3422 FX: 314-997-7814 -Original Message- From: James Maes [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 12:46 PM To: axis-user@ws.apache.org Subject: RE: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference When requesting the URL (http://BLAHBLAH/axis2/axis2-web/) I get this response HTTP Status 404 - /axis2/axis2-web/ type Status report message /axis2/axis2-web/ description The requested resource (/axis2/axis2-web/) is not available. Apache Tomcat/5.5.17 And this on the server console [java] Oct-23-07 12:45:04.917 : ERROR : http-8081-Processor3 : g.apache.catalina.core.StandardHostValve : Exception Processing ErrorPage[errorCode=404, location=/axis2-web/Error/error404.jsp] [java] java.lang.NullPointerException [java] at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java :363 ) [java] at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java :284 ) [java] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :136 ) [java] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105 ) [java] at org.apache.catalina.core.StandardEngineValve.invoke( StandardEngineValve.java :107) [java] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java :148) [java] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) [java] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC onnection(Http11BaseProtocol.java:664) [java] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket( PoolTcpEndpoint.jav a:527) [java] at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWo rkerThread.java:80) [java] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( ThreadPool.jav a:684) [java] at java.lang.Thread.run(Thread.java:595) James Maes Software Architect Materialogic PH: 800-333-7144 PH: 314-997-4342 Ext. 3422 FX: 314-997-7814 From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 12:37 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Deploying axis2.war within an Embedded Tomcat 5.5 server - axis2/services returning The service cannot be found for the endpoint reference Check accessing these links in your server. http://blahblash/axis2/axis2-web/ For console home page http://blahblash/axis2/services/listServices For deployed services Upul On 10/23/07, James Maes [EMAIL PROTECTED] wrote: Maybe someone can give a little insight into the issue(s) that I am having. We are trying to embed Axis2 (1.3) into a internal application via Tomcat (5.5) Tomcat seems to be working fine (it's used for other war deployments) and the axis2.war deploys fine (see below) Deployment code Context context = embedded.createContext(/axis2, axis2.war); context.setReloadable(false); host.addChild (context); War being deployed [java] Oct-23-07 11:36:11.081 : INFO: main : org.apache.catalina.core.StandardEngine : Starting
Re: org.apache.axis2.databinding.ADBException: Property cannot be null!
On 10/23/07, Huitang Li [EMAIL PROTECTED] wrote:
Excellent! Thanks very much. Somehow -Eosv does not solve the problem.
what is the Axis2 version you use? this is available in Axis2 1.3.
So I put the nillable=true in the element there, and it works.
Amila Suriarachchi wrote:
this means your object structure do not have loaded the required fault
elements.
see you schema there should be an element named fault without
minOccurs=0 or nillable=ture.
So ADB gives an exception because of this.
if you want to remove this use -Eosv when genrating the code.
Amia.
On 10/23/07, *Huitang Li* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi,
I created a web service code based on a wsdl, and it is run in resin
3.1.3, and I have the soapmonitor activated. When a web service
client
sent a soap message to it, it threw the following exception:
java.lang.RuntimeException: Can not serialize OM Element Envelope
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(
OMElementImpl.java:916)
at
org.apache.axis2.handlers.soapmonitor.SOAPMonitorHandler.invoke(
SOAPMonitorHandler.java:101)
at org.apache.axis2.engine.Phase.invoke (Phase.java:292)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java
:212)
at
org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:442)
at
org.apache.axis2.transport.http.AxisServlet.handleFault
(AxisServlet.java:403)
at
org.apache.axis2.transport.http.AxisServlet.processAxisFault(
AxisServlet.java:366)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java
:154)
at javax.servlet.http.HttpServlet.service (HttpServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:91)
at
com.caucho.server.dispatch.ServletFilterChain.doFilter(
ServletFilterChain.java:103)
at
com.caucho.server.security.SecurityFilterChain.doFilter
(SecurityFilterChain.java:134)
at
com.caucho.server.webapp.WebAppFilterChain.doFilter(
WebAppFilterChain.java:178)
at
com.caucho.server.dispatch.ServletInvocation.service(
ServletInvocation.java:241)
at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java
:268)
at
com.caucho.server.port.TcpConnection.run(TcpConnection.java:586)
at com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:690)
at com.caucho.util.ThreadPool$Item.run(ThreadPool.java:612)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.axis2.databinding.ADBException: Property
cannot be
null!
at test.Fault.serialize (Fault.java:95)
at test.Fault$1.serialize(Fault.java:80)
at
org.apache.axis2.databinding.ADBDataSource.serialize(
ADBDataSource.java:82)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume
(OMSourcedElementImpl.java:599)
at
org.apache.axiom.soap.impl.llom.SOAPFaultDetailImpl.internalSerialize(
SOAPFaultDetailImpl.java:86)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java
:756)
at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.internalSerialize(
SOAPFaultImpl.java:192)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
(OMElementImpl.java:772)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:756)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
SOAPEnvelopeImpl.java
:210)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:756)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java
:345)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString
(OMElementImpl.java:913)
... 18 more
This exception will not be shown when all elements in the requesting
soap message are filled with non-empty (no-blankspace) values.
I notice that the exception is thrown from the following
axis2-generated
code:
public void serialize(final javax.xml.namespace.QNameparentQName,
final org.apache.axiom.om.OMFactory factory,
org.apache.axis2.databinding.utils.writer.MTOMAwareXMLStreamWriter
xmlWriter)
throws javax.xml.stream.XMLStreamException,
org.apache.axis2.databinding.ADBException {
//We can safely assume an element has only one type
associated
with it
if (localFault == null) {
throw new
Re: error creating message from generated client
it seems this error happens when processing the request. reason seems to be that reqeust send to and invalide soap end point and it sends back an html page instead of valide soap message. On 10/22/07, Kimberly Nicholls [EMAIL PROTECTED] wrote: I am having trouble creating a SOAP message from a generated client when the message includes attachments -- the client throws org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html. this means you have got an html page. have you set the end point correctly in the stub? I am using axis2 1.3, and I can make requests to other methods (without attachments) in the same service with no problems. Here's what I did: - set enableMTOM to true in axis2.xml - created method in my POJO service: public long createAttachment(long messageID, DataHandler attData) - generated client stub via wsdl2java - added these lines to client stub: _serviceClient.getOptions().setProperty( Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE ); _serviceClient.getOptions().setTimeOutInMilliSeconds(1); - created client that runs the method like this: DataHandler attData = new DataHandler(new FileDataSource(filename)); long attachmentID = stub.createAttachment(messageID, attData); When I run the client, I get [INFO] OMException in getSOAPBuilder org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode( StAXSOAPModelBuilder.java:219) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement( StAXSOAPModelBuilder.java:177) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next( StAXOMBuilder.java:163) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope( StAXSOAPModelBuilder.java:161) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init( StAXSOAPModelBuilder.java:110) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder( BuilderUtil.java:609) at org.apache.axis2.transport.TransportUtils.createDocumentElement (TransportUtils.java:178) at org.apache.axis2.transport.TransportUtils.createSOAPMessage( TransportUtils.java:111) at org.apache.axis2.transport.TransportUtils.createSOAPMessage( TransportUtils.java:87) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse( OutInAxisOperation.java:326) here the exception Occurs in handling the response not when sending . at org.apache.axis2.description.OutInAxisOperationClient.send( OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl( OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute( OperationClient.java:163) ... Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element must contain the local name, Envelope , but found html at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode( StAXSOAPModelBuilder.java:219) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement( StAXSOAPModelBuilder.java:177) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next( StAXOMBuilder.java:163) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope( StAXSOAPModelBuilder.java:161) at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init( StAXSOAPModelBuilder.java:110) at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder( BuilderUtil.java:609) at org.apache.axis2.transport.TransportUtils.createDocumentElement (TransportUtils.java:178) at org.apache.axis2.transport.TransportUtils.createSOAPMessage( TransportUtils.java:111) at org.apache.axis2.transport.TransportUtils.createSOAPMessage( TransportUtils.java:87) ... 6 more Running other methods in the same client with the same service work fine, if they don't have attachments. The file I'm trying to send is a 2.5kjpg. What am I doing wrong? Kimberly -- Amila Suriarachchi, WSO2 Inc.
