RE: POJO Classpath Question
How about WEB-INF/classes? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, December 03, 2007 11:49 AM To: axis-user@ws.apache.org Subject: POJO Classpath Question I am trying to implement a simple encryption service using POJOs in Tomcat. I use an encryption package that is supplied to me as a jar. This encryption package requires that a keystore file of a specified name be found on the classpath. I've tried putting this file in all sorts of likely places (Tomcat\lib, axis2\web-inf\lib, axis2\web-info\services, jarred up in the .aar) but to no avail. Can anyone tell me where I can put a resource to be found via a classpath search from within the POJO? Actually from within a dependent jar? Is there a way to add to the classpath for a POJO?
RE: BEA 8.1 sp5 and Axis2 (QName no such method)
The NoSuchMethodError is because you have an older version of QName that lacks this constructor on your classpath. Write a debugging method that prints out QName.class.getProtectionDomain().getCodeSource().getLocation() from the point of your code where this error occurs. If QName is coming from a jar in Weblogic itself, you may have to investigate a custom classloading strategy to run Axis 2 on the app server (or hack the jar and update QName...). Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: k2g [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 21, 2007 10:56 AM To: axis-user@ws.apache.org Subject: BEA 8.1 sp5 and Axis2 (QName no such method) Here is the QName incompatibility ... is this something to do with a bad jar ... how do i figure out which QName is getting loaded please comment on it. 21 Nov 2007 13:13:39,399 DEBUG AxisService [ExecuteThread: '12' for queue: ' weblogic.kernel.Default'][]: mapActionToOperation: Mapping Action to Operation: action: urn:PMWSRadiusSearch; operation: [EMAIL PROTECTED] 21 Nov 2007 13:13:39,399 DEBUG Loader [ExecuteThread: '12' for queue: ' weblogic.kernel.Default'][]: Trying to find [org/apache/axis2/deployment/axis2_default.xml] using [EMAIL PROTECTED]( finder: [EMAIL PROTECTED] , annotation: [EMAIL PROTECTED], parent: [EMAIL PROTECTED]( finder: [EMAIL PROTECTED], annotation: geocode@, parent: [EMAIL PROTECTED] ( finder: [EMAIL PROTECTED], annotation: ApplicationClassLoader@, parent: [EMAIL PROTECTED]( finder: [EMAIL PROTECTED] , annotation: null, parent: [EMAIL PROTECTED] class loader. 21 Nov 2007 13:13:39,399 DEBUG StAXUtils [ExecuteThread: '12' for queue: 'weblogic.kernel.Default'][]: XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader 21 Nov 2007 13:13:39,430 ERROR Framework [ExecuteThread: '12' for queue: 'weblogic.kernel.Default'][]: Processing Framework Error javax.ejb.EJBException : EJB Exception: : java.lang.NoSuchMethodError: javax.xml.namespace.QName.init(Ljava/lang/String;Ljava/lang/String;Ljava/la ng/String;)V at com.ctc.wstx.sr.NsInputElementStack.getCurrentElementName(NsInputElementStack .java :651) at com.ctc.wstx.sr.BasicStreamReader.getName(BasicStreamReader.java:723) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:160) at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement (OMDocumentImpl.java:130) at org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuild er.java:359) at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:568) at org.apache.axis2.deployment.DescriptionBuilder.buildOM (DescriptionBuilder.java:96) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilde r.java:79) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(Deploy mentEngine.java :615) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileS ystemConfigurator.java:115) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationConte xt(ConfigurationContextFactory.java :64) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationConte xtFromFileSystem(ConfigurationContextFactory.java:180) at org.apache.axis2.client.ServiceClient.configureServiceClient (ServiceClient.java:146) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:139) at com.sample.extservice.library.adb.ServiceStub.init(ServiceStub.java:187) at com.sample.eflatbed.extservice.library.adb.ServiceStub.init(ServiceStub.jav a:173) ... -- -- Krishna
RE: Possible classloader issue - help needed
Joao,
(I don't see where the Xerces jar is--it's not in your AAR. Can't be the Sun
JDK 1.5 version, because all of those are prefaced with com.sun.)
You might try:
1) Run the JRE with -verbose:class option. See if your class is actually
getting loaded.
2) Get a reference to a classloader the is in your code and compare this with
the classloader for org.apache.commons.digester.Digester. See if they are the
same (using identity ==).
This might help:
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html. Note that
the web application classloaders are child-first classloaders, so classes
loaded by these won't be visible to parent classloaders in the tree. Not sure
if the Axis 2.0 classloaders are the same way.
Hope this helps,
Brennan Spies
Sr. Programmer Analyst
Shared Application Services
(209) 341-6457
-Original Message-
From: João Luís Pinto [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 1:41 AM
To: axis-user@ws.apache.org
Subject: Possible classloader issue - help needed
Hello,
I'm trying to load a commons-chain catalog (from a file inside the
service folder) and invoke a chain inside the invokeBusinessLogic
method of the MessageReceiver (AbstractInOutMessageReceiver subclass).
I'm using the latest release of Axis2 and of Commons-Chain. The
service is deployed in Tomcat 6.0.14 in exploded form, and includes
the jar dependencies in the service's /lib folder. No jars were added
to the axis WEB-INF/lib folder nor to the Tomcat setup.
Here is the relevant code snippet:
code
ConfigParser configParser = new ConfigParser();
Parameter parameter =
msgContext.getParameter(Constants.CATALOG_FILE_URL_PARAM);
if (parameter == null)
{
log.error(Parameter + Constants.CATALOG_FILE_URL_PARAM //$NON-NLS-1$
+ not found!); //$NON-NLS-1$
}
else
{
URL url = msgContext.getAxisService()
.getClassLoader()
.getResource(parameter.getValue().toString().trim());
log1.debug(Loading + url); //$NON-NLS-1$
configParser.parse(url);
}
catalog = CatalogFactory.getInstance().getCatalog();
/code
The following exception is thrown in the last line of the else block:
java.lang.ClassNotFoundException: org.apache.commons.chain.impl.CatalogBase
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:3181)
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:3207)
at
org.apache.commons.digester.Digester.startElement(Digester.java:1456)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknow
n
Source)
at
org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootEleme
ntHook(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatch
er.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1745)
at
org.apache.commons.chain.config.ConfigParser.parse(ConfigParser.java:198)
The CatalogBase class is of course part of the commons-chain jar
included like previously mentioned in the service /lib folder.
Does anyone have any idea on what could be going wrong?
I can provide any additional information required to make a better
judgement if needed.
Thank you,
João
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Error :javax.xml.namespace.QName
Sounds like you have an older version of QName (which lacks that constructor) on your path (looks similar to a WebSphere 5.x problem where one of the parent classloaders loads an older version of QName). Try something like QName.class.getProtectionDomain().getCodeSource().getLocation() at the point of the exception to see which one is being used. Brennan -Original Message- From: renjith kalappurackal [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 11:16 AM To: axis-user@ws.apache.org Subject: Error :javax.xml.namespace.QName Hi All, I am stuck with this particular problem when I tried to deploy my Web Service Solution in JBoss (jboss-3.0.8_tomcat-4.1.24). The solution works fine in my local machine. And When I tried to deploy my service on another machine I am getting an error java.lang.NoSuchMethodError: javax.xml.namespace.QName.init(Ljava/lang/String;Ljava/lang/String;Ljava/la ng/String;)V Please see the attached file more details. Could anyone tell me the reason why I am getting this error. The Jboss server environment is having other services that are developed in Axis 1.0 The way I deployed axis2.war is by creating a directory webapps in JBoss\server\default\deploy and putting axis2.war which contains AAR file into the newly created directory(JBoss\server\default\deploy\webapps). Thanks in Advance. Renjith Kalappurackal _ Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://us.rd.yahoo.com/evt=48224/*http:/sims.yahoo.com/
RE: Axis/Wss4j Websphere NoClassDefFoundError
I haven't played around with v6.1 yet, but in 5.x Axis is included as part of the base WAS libraries in WAS_HOME/lib. Since these libs are loaded first, it can interfere with any Axis installation on your own app path. You may want to try PARENT_LAST classloading. -Original Message- From: Michelle Vogt [mailto:[EMAIL PROTECTED] Sent: Thursday, May 03, 2007 4:11 PM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: Axis/Wss4j Websphere NoClassDefFoundError We already have the relevant axis and wss4j jar files in our app lib directory. And, this was working previously on the previous. On 5/4/07, Martin Gainty [EMAIL PROTECTED] wrote: download axis-src-1_4.zip from http://apache.osuosl.org/ws/axis/1_4/ (and compile the package) M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Michelle Vogt [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Thursday, May 03, 2007 6:37 PM Subject: Axis/Wss4j Websphere NoClassDefFoundError We are trying to use Websphere 6.1 with axis and wss4j security. When the security is enabled, the following exception is thrown when the web service is called: NoClassDefFoundError: org.apache.axis.Handler This is part of the wsdd config file specifying the handler: handler type=java:org.apache.ws.axis.security.WSDoAllReceiver If security is disabled then the web service works fine. And, also if the handler type is replaced with a type in our own app, then it works fine also. Has anybody been able to get anything similar working, or had similar problems with this on websphere? We're using axis 1.4, and wss4j 1.5 thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problems using Axis on i5/iSeries/AS400/whatever they call it these days
Jon, NoClassDefFoundError is a linkage error. Probably because the ClassLoader that loaded org.apache.catalina.startup.HostConfig is unable to see the ClassLoader that loaded HttpSessionListener (i.e. it was loaded by a child or sibling ClassLoader). AFAIK, Tomcat does not expose its classloading tree via JMX, so you may have to do some investigative work using logging calls like (retrieving different ClassLoaders)... ClassLoader cl = Class.forName(some.test.class).getClassLoader(); Class.forName(javax.servlet.http.HttpSessionListener, false, cl).getProtectionDomain().getCodeSource() .getLocation(); My guess (?) is that HttpSessionListener is in one of the jars on your Shared or WebApp classpath, and is not being loaded by the Common classloader. Bootstrap | System | Common (Servlet api classes should be here...) / \ Catalina Shared / \ Webapp1 Webapp2 ... -Original Message- From: Jon Brisbin [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 25, 2007 8:17 AM To: axis-user@ws.apache.org Subject: Problems using Axis on i5/iSeries/AS400/whatever they call it these days I downloaded the latest Axis 1 so I could provide the C++ guys a way to contact the 400 from their native code. I put the latest Axis 1.4 and Tomcat 5.5 on the 400 (v5r4 and Java 1.5). I can get Tomcat to fire up, but I can't run Axis in it because of a ClassNotFoundError: 2007-04-25 09:10:24,262 ERROR [org.apache.catalina.startup.HostConfig] (Thread java.lang.NoClassDefFoundError: javax/servlet/http/HttpSessionListener Tomcat itself runs fine, and I can deploy the same files on my Linux box and they work fine. It looks like when it gets to the 400, there are some classloader issues and it's not seeing the jar files in the server. Does anyone have suggestions on what I can do to get this issue resolved. I really need to get this fixed today if I can manage it. -- Thanks! Jon Brisbin NPC International, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Migrating .net web service to axis HELP
You can use Axis 2.0 with WAS 5.1...but because the root WAS classloader has jars on its classpath that are incompatible, you'll need to... 1. Use non-delegating classloading option (PARENT_LAST) on the server. 2. Fix bugs that result from this...(Commons Logging--need to define a system property for the logging factory, etc.) -Original Message- From: Moorthy GT [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 03, 2007 8:17 AM To: axis-user@ws.apache.org Subject: Re: Migrating .net web service to axis HELP Angel: Thanks for your reply. Is axis 2 compatible with Websphere 5.1? Can you give me the command to generate WSDD from WSDl using WSDL2JAVA tool? Thanks, Moorthy Hi, Do you really have a requirement to use Axis1 ? You'd better use Axis2 IMO. Otherwise it's perfectly fine to generate service descriptors from a WSDL file, using the wsdl2java tool. Regards, Angel -- View this message in context: http://www.nabble.com/Migrating-.net-web-service-to-axis-HELP-tf3514920.html# a9814694 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to make SOAP messages smaller?
This should be pretty easy to do...have the servlet filter check the Accept-Encoding before applying GZIP compression. Then, when debugging, have the client turn off this header. -Original Message- From: Christian Poecher [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 28, 2007 10:12 AM To: axis-user@ws.apache.org Subject: Re: How to make SOAP messages smaller? Ryan Nelsestuen schrieb: It sort of depends on your architecture and who the callers are, but you can put a GZipFilter in front of your AxisServlet and compress it that way... of course, that means the client has to be capable of uncompressing gzip as well as indicating that they support gzip in an HTTP header... Thx for your input! I thought about HTTP compression before, but what I don't like, is that the SOAP message looks like garbage then to the human eye. Maybe I can find a solution to make it optional for the client. That would at least help the client developer to debug. -Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: stand-alone SOAP server with Axis
Hakan, (Assuming you are talking about Axis2...) Embedding an HTTP Server like Jetty (http://www.ebmwebsourcing.net/blog/page/christophehamerling/20070307?catname =%2FPEtALS) might be a better solution in terms of scalability. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, March 25, 2007 10:24 PM To: axis-user@ws.apache.org Subject: Re: stand-alone SOAP server with Axis Hi Martin, Thank you for the information. I guess I forgot to metioned that I might have to use Java. Is there still chance to use simple_axis_server ? Regards Hakan Martin Gainty [EMAIL PROTECTED] 26/03/2007 10:46 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: stand-alone SOAP server with Axis http://ws.apache.org/axis/cpp/index.html http://ws.apache.org/axis/cpp/index.html Bon Chance! Martin-- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Sunday, March 25, 2007 8:38 PM Subject: stand-alone SOAP server with Axis Hi, Are there any documentation on how to build a standan-alone SOAP server without using Tomcat or JBOSS. Thanks Hakan This email may contain privileged/confidential information. You may not copy or disclose this email to anyone without the written permission of the sender. If you have received this email in error please kindly delete this message and notify the sender. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission. This email may contain privileged/confidential information. You may not copy or disclose this email to anyone without the written permission of the sender. If you have received this email in error please kindly delete this message and notify the sender. Opinions expressed in this email are those of the sender and not necessarily the opinions of the employer. This email and any attached files should be scanned to detect viruses. No liability will be accepted by the employer for loss or damage (whether caused by negligence or not) as a result of email transmission.
RE: Benefits of using Message style WS
If you have overloaded operations in WSDL, you cannot use doc/literal wrapped style. In the wrapped pattern, you require an element to have the same name as the operation, and you cannot have two elements with the same name in XML. Other than that, doc/lit wrapped has the nice advantage that it is the best of both worlds, having the operation name in the SOAP message but also the greater expressiveness of the document style. Good article here: http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ If you are using Axis 2.0 with databinding, you may want to choose a databinding framework (such as JiBX) that supports the wrapped style. Brennan -Original Message- From: Joshua White [mailto:[EMAIL PROTECTED] Sent: Thursday, March 01, 2007 7:27 AM To: axis-user@ws.apache.org Subject: Benefits of using Message style WS Hello, I am having a hard time understanding the benefits of using a message style web service as opposed to a regular doc/lit wrapped service. Could someone please clarify this for me? Regards, Joshua
RE: Benefits of using Message style WS
The Message style, as defined in Axis 1.x, is really just raw XML (no databinding). You would, of course, use this if you did not want Java - XML databinding. E.g., you want to do a transformation with XSL or XQuery, or do your own XML parsing, etc., etc. -Original Message- From: Joshua White [mailto:[EMAIL PROTECTED] Sent: Thursday, March 01, 2007 12:19 PM To: axis-user@ws.apache.org Subject: Re: Benefits of using Message style WS Brennan, Thanks for the reply. I understand the value of the doc/literal wrapped style. I was hoping to go one step further though. Axis 1.X supports RPC, Document, Wrapped, and Message style services. I was hoping to determine the benefits of using Messsage style services over doc/literal wrapped. To be perfectly honest, I don't know enough about Axis2 to know if Message style services are still supported. Have you used them? Do you know what the advantages are? Joshua On 3/1/07, Spies, Brennan [EMAIL PROTECTED] wrote: If you have overloaded operations in WSDL, you cannot use doc/literal wrapped style. In the wrapped pattern, you require an element to have the same name as the operation, and you cannot have two elements with the same name in XML. Other than that, doc/lit wrapped has the nice advantage that it is the best of both worlds, having the operation name in the SOAP message but also the greater expressiveness of the document style. Good article here: http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ If you are using Axis 2.0 with databinding, you may want to choose a databinding framework (such as JiBX) that supports the wrapped style. Brennan -Original Message- From: Joshua White [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Thursday, March 01, 2007 7:27 AM To: axis-user@ws.apache.org Subject: Benefits of using Message style WS Hello, I am having a hard time understanding the benefits of using a message style web service as opposed to a regular doc/lit wrapped service. Could someone please clarify this for me? Regards, Joshua
RE: Benefits of using Message style WS
Yes. This is independent of your databinding choice. -Original Message- From: Joshua White [mailto:[EMAIL PROTECTED] Sent: Thursday, March 01, 2007 12:46 PM To: axis-user@ws.apache.org Subject: Re: Benefits of using Message style WS Exactly. I am trying to determine if there is any benefit of creating a service this way. Are you still able to specify a schema for both your input/output arguments in the wsdl file if you send messages this way? -Josh On 3/1/07, Spies, Brennan [EMAIL PROTECTED] wrote: The Message style, as defined in Axis 1.x, is really just raw XML (no databinding). You would, of course, use this if you did not want Java - XML databinding. E.g., you want to do a transformation with XSL or XQuery, or do your own XML parsing, etc., etc. -Original Message- From: Joshua White [mailto: [EMAIL PROTECTED] Sent: Thursday, March 01, 2007 12:19 PM To: axis-user@ws.apache.org Subject: Re: Benefits of using Message style WS Brennan, Thanks for the reply. I understand the value of the doc/literal wrapped style. I was hoping to go one step further though. Axis 1.X supports RPC, Document, Wrapped, and Message style services. I was hoping to determine the benefits of using Messsage style services over doc/literal wrapped. To be perfectly honest, I don't know enough about Axis2 to know if Message style services are still supported. Have you used them? Do you know what the advantages are? Joshua On 3/1/07, Spies, Brennan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: If you have overloaded operations in WSDL, you cannot use doc/literal wrapped style. In the wrapped pattern, you require an element to have the same name as the operation, and you cannot have two elements with the same name in XML. Other than that, doc/lit wrapped has the nice advantage that it is the best of both worlds, having the operation name in the SOAP message but also the greater expressiveness of the document style. Good article here: http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ If you are using Axis 2.0 with databinding, you may want to choose a databinding framework (such as JiBX) that supports the wrapped style. Brennan -Original Message- From: Joshua White [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Thursday, March 01, 2007 7:27 AM To: axis-user@ws.apache.org Subject: Benefits of using Message style WS Hello, I am having a hard time understanding the benefits of using a message style web service as opposed to a regular doc/lit wrapped service. Could someone please clarify this for me? Regards, Joshua
RE: Benefits of using Message style WS
The Axis 1.x user's guide is using style in this context to refer to both the WSDL style and the databinding choice. The only difference then b/n Document and Message is that Message has no databinding. -Original Message- From: Spies, Brennan Sent: Thursday, March 01, 2007 12:49 PM To: axis-user@ws.apache.org Subject: RE: Benefits of using Message style WS Yes. This is independent of your databinding choice. -Original Message- From: Joshua White [mailto:[EMAIL PROTECTED] Sent: Thursday, March 01, 2007 12:46 PM To: axis-user@ws.apache.org Subject: Re: Benefits of using Message style WS Exactly. I am trying to determine if there is any benefit of creating a service this way. Are you still able to specify a schema for both your input/output arguments in the wsdl file if you send messages this way? -Josh On 3/1/07, Spies, Brennan [EMAIL PROTECTED] wrote: The Message style, as defined in Axis 1.x, is really just raw XML (no databinding). You would, of course, use this if you did not want Java - XML databinding. E.g., you want to do a transformation with XSL or XQuery, or do your own XML parsing, etc., etc. -Original Message- From: Joshua White [mailto: [EMAIL PROTECTED] Sent: Thursday, March 01, 2007 12:19 PM To: axis-user@ws.apache.org Subject: Re: Benefits of using Message style WS Brennan, Thanks for the reply. I understand the value of the doc/literal wrapped style. I was hoping to go one step further though. Axis 1.X supports RPC, Document, Wrapped, and Message style services. I was hoping to determine the benefits of using Messsage style services over doc/literal wrapped. To be perfectly honest, I don't know enough about Axis2 to know if Message style services are still supported. Have you used them? Do you know what the advantages are? Joshua On 3/1/07, Spies, Brennan [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: If you have overloaded operations in WSDL, you cannot use doc/literal wrapped style. In the wrapped pattern, you require an element to have the same name as the operation, and you cannot have two elements with the same name in XML. Other than that, doc/lit wrapped has the nice advantage that it is the best of both worlds, having the operation name in the SOAP message but also the greater expressiveness of the document style. Good article here: http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ If you are using Axis 2.0 with databinding, you may want to choose a databinding framework (such as JiBX) that supports the wrapped style. Brennan -Original Message- From: Joshua White [mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Thursday, March 01, 2007 7:27 AM To: axis-user@ws.apache.org Subject: Benefits of using Message style WS Hello, I am having a hard time understanding the benefits of using a message style web service as opposed to a regular doc/lit wrapped service. Could someone please clarify this for me? Regards, Joshua
RE: axis2 on Websphere
Larry, You *probably* have a classloader issue. If you look at the MBean (here for the embedded version of WAS 5 in RAD, you'll have to find the correct MBean for WAS 6...) WebSphere:name=UTC.war,process=server1,Application=IBMUTC,platform=common, node=localhost,J2EEName=IBMUTC#UTC.war,Server=server1,version=5.0,type=WebMod ule, mbeanIdentifier=cells/localhost/applications/IBMUTC.ear/deployments/IBMUTC/de ployment.xml#WebModuleDeployment_1, cell=localhost getClassLoaderInfo(java.lang.String) level: (int) atDepthOnly: (boolean) showClasses: true showCodeSource: true showDelegation: true showHierarchy: true showModules: (boolean) showDepth: true This operation will return an XML with your classloader tree, showing which classes were loaded and from what source. Brennan -Original Message- From: Xu, Larry [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 28, 2007 2:57 PM To: axis-user@ws.apache.org Subject: axis2 on Websphere Hi guys, I have a Axis2 webservice deployed on a Websphere App Server 6, and my client web app is deployed on Websphere App Server 5, whenever I try to invoke in the webservice in my web app client, it gives me ClassDefNotFound exception for various class which ARE included in the axis jars that I put in my web app's web-inf/lib directory. When I do a Class.forName() for that class I can find it, yet during runtime it still gives me the ClassDefNotFound exception. Is there some incompatibility issues with WAS 5 and axis2 jars? Thanks, Larry Xu
RE: [Axis2] Trouble deploying axis2.war
Mike, You have an older version of the QName class that is getting loaded before the one in your Axis library...if you are using Weblogic 9.2, you might want to take a look at using a Filtering Classloader to load the class from your Axis lib instead: http://e-docs.bea.com/wls/docs92/programming/classloading.html#filteringClass Loader Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Mike Ferraro [mailto:[EMAIL PROTECTED] Sent: Monday, January 29, 2007 11:16 AM To: axis-user@ws.apache.org Subject: [Axis2] Trouble deploying axis2.war Hello, I'm new to Axis2 and am trying to go through the instructions from the beginning. My goal is to develop a set of web services using existing Java objects. I tried downloading the latest war file and dropping into my app server. I use Weblogic. I dropped the war file into the appropriate directory and deployed the application through the WL admin console. In the startup log I got the message below. Does anyone know the cause of this? Thank you, Mike Ferraro Jan 29, 2007 1:33:16 PM EST Error HTTP BEA-101125 [ServletContext(id=4653899,name=axis2,context-path=/axis2)] Error occu rred while instantiating servlet: AxisServlet. java.lang.NoSuchMethodError: javax.xml.namespace.QName.init(Ljava/lang/String;Ljava/lang/String;Lja va/lang/String;)V at org.apache.axis2.engine.InstanceDispatcher.clinit(InstanceDispatcher.j ava:41) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA ccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons tructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at java.lang.Class.newInstance0(Class.java:308) at java.lang.Class.newInstance(Class.java:261) at org.apache.axis2.deployment.util.Utils.loadHandler(Utils.java:88) at org.apache.axis2.deployment.AxisConfigBuilder.processPhaseList(AxisConfi gBuilder.java:264) at org.apache.axis2.deployment.AxisConfigBuilder.processPhaseOrders(AxisCon figBuilder.java:292) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigB uilder.java:107) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(D eploymentEngine.java:690) at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxis Configurator.java:129) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle t.java:392) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:331) at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletS tubImpl.java:993) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu bject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118 ) at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl. java:869) at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImp l.java:848) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl .java:787) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServ letContext.java:3252) at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppSer vletContext.java:3197) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe rvletContext.java:3174) at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletC ontext.java:5647) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:869) at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.ja va:2022) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer .java:2063) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.act ivateContainer(SlaveDeployer.java:2592) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(Sla veDeployer.java:2515) at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer .java:2317) at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(Slav eDeployer.java:2399) at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeploye r.java:2311) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(Slav eDeployer.java:2479) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveD eployer.java:798) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeploye r.java:507) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeploy er.java:465) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandle r.java:25)
RE: Clustering
You may want to think about clustering at the JVM level (e.g. Terracota, http://www.terracotta.org/), which uses heap-level replication. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Rajith Attapattu [mailto:[EMAIL PROTECTED] Sent: Monday, January 22, 2007 10:05 AM To: axis-user@ws.apache.org Subject: Re: Clustering Stefan, If your web services are truly stateless or if your state is backed by a data base after every request then u can deploy axis2 in a cluster. However if your services have some state carried in the service ctx or service group contexts (SOAPSession or Application scope) then u have to wait till we add the replication support for this. Unfortuantely I have been sitting on this for a while. Hopefully will try to add this soon into a branch and where people can play around with it. This is based on a proposal by Chamikara/Chathura. Regards, Rajith On 1/20/07, Stefan Kok [EMAIL PROTECTED] wrote: Hi All I am curious do Axis support any form of clustering ? I have seen some proposals on the net but that about it. Regards Stefan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WSDL Design
The classic approach here is to use abstract and concrete WSDLs for each service, where the abstract WSDL defines the types, messages, and portTypes; and the concrete WSDL defines the binding and service elements. Each concrete WSDL will import the appropriate abstract WSDL. (Blog on this: http://blogs.sun.com/gopalan/entry/wsdl_the_wsdl_model). This would allow you to change the abstract model without having to edit multiple WSDL files each time, as well as having multiple bindings for a given interface (HTTP, JMS, etc.). Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Ramesh Gurunathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 09, 2007 8:32 PM To: axis-user@ws.apache.org Subject: WSDL Design Hi Everyone, I'm looking for a WSDL design article. We are providing web service interface for existing APIs, which consist of nearly 50 business logic interface classes, in total it's going to have about 300 business methods. Obviously, writing a single WSDL which (flat) include all the methods of 50 business classes is not a good. Maintenance of such a mega WSDL will be disastrous. If the API, for which web services layer is provided, gets changed, then it will be impossible to ensure that the WSDL is up-to-date with the API changes. What is the right approach and design in this case? My goal is to come up with WSDL that 1) Separates business logic (types, messages, port types) from implementation details (SOAP binding and service end point definitions). 2) Easier maintenance. i.e. When there is a change detected in a business logic class, lets say BusinessLogic1.java, I want to directly edit the WSDL fragment file and not disturb the other WSDL fragments. 3) Of the total 50 business classes, some of the classes can be grouped as module. i.e. A BusinessLogicModule1 contains BusinessLogic1.java, BusinessLogic2.java, etc., I'm thinking of designing WSDL like this: Master.wsdl | |-- Module1.wsdl |--- BusinessLogic1.wsdl |- BusinessLogic1.xsd |--- BusinessLogic2.wsdl | BusinessLogic2.xsd |- Module2.wsdl |- Module3.wsdl Basically, the master.wsdl imports all the module level wsdl fragments. Each module.wsdl imports BusinessLogicN.wsdl. Each business logic wsdl declares messages and a port type. The Module.wsdl not only imports all the business logic wsdls but it creates bindings for each of the port types. The Master.wsdl not only imports all the module wsdls but declares service end points for each of the port types. I may be wrong in my understanding. Please point me to a WSDL design article, if you know any. What do you think on the design above? Appreciate if you could share your thoughts and experience. Thanks in advance Ramesh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Questions about Axis2
I'd agree with Dennis that, if you know you are using Java on both sides of the wire, RMI is a more efficient and easier to setup than an XML/SOAP-based service. But there is another reason (a better one in my mind) than platform/language neutrality to go with the XML/SOAP option: declarative vs. imperative programming. RMI introduces a level of coupling to the Java interfaces that is unavoidable, whereas a good XML interface should be like an SQL statement: tell me what you want, and I (the service) will decide how to do it. -Original Message- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Saturday, December 16, 2006 10:33 PM To: axis-user@ws.apache.org Subject: Re: Questions about Axis2 For sending objects between Java applications RMI is generally your best bet. The only reason to use SOAP/XML is if you want to allow non-Java clients or servers to be used. If you *do* want to allow for non-Java support, JiBX data binding lets you work with java.util.Collection classes without much effort. The upcoming Axis2 1.1.1 release will have improved support for what's called unwrapped interfaces using JiBX, and I'll be releasing a new version of the JiBX tools that provide code-binding and code+binding-schema support in conjunction with the Axis2 1.1.1 release. These new tools include support for Java 5 generic collections, so that handling the type of data structures you described becomes very easy using JiBX. The main downside of JiBX is the limited schema support. It's about on a par with ADB, and much more limited than XMLBeans. But JiBX is primarily focused on working with existing Java code, so for your case it's probably the easiest way to implement web services. - Dennis Dennis M. Sosnoski SOA and Web Services in Java Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117 Vanfleet, David wrote: Thanks for your comments Anne, what you're saying makes since to me. Some of the data I'll be transferring is raw XML so SOAP sounds like a reasonable protocol for that. However, other data is in the form of Java objects and it would be nice if it could be transferred and received as a Java object. How do I specify data binding for those objects (such as the one below)? is this done through the services.xml file? I do think that SOAP is the best protocol for what I need. However, if I was to look into using anther protocols do you know of any that you can recommend? I could always open an HTTP connection to a Java servlet and pass the data as a serialized Java object, I'm not sure what the advantages or disadvantages are for doing this? Thanks again, David -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Saturday, December 16, 2006 12:01 PM To: axis-user@ws.apache.org Subject: Re: Questions about Axis2 David, The first thing you need to understand is that SOAP is not an especially good protocol for transferring language-specific collections. If your goal is to implement a Java-to-Java client/server application, perhaps you should consider using a different protocol -- one that supports the Java type system. SOAP used the XML Schema type system. For best results using SOAP, your service interface should use types that map reasonably well to the XML Schema type system. (i.e., don't try to use Vector or List to generate your interface -- use simple arrays instead) The next thing you need to understand is that there is a layer of indirection between the data/object model used by the server and data/object model used by the client. Just because you use language-specific collections on the server to generate your WSDL interface, those collections are not apparent to the client. The client only sees the schema representation of the objects. If you want your client to convert that schema into the same Java object types that you use on the server, then you need to specify the data binding mapping rather than using a tool like wsdl2java to generate it. Anne On 12/16/06, Vanfleet, David [EMAIL PROTECTED] wrote: Hi, I'm new to both Axis2 and web services and I'm having a hard time grasping all the various types of databinding that can be created (POJO, AXIOM, ADB, XMLBeans and JiBX). I have a couple of general questions about Axis2 and web services. I need to create a service that can pass complex objects between the client and the server. Something like my modified weather example below. My questions about this are as follows: 1) In the testing I've done I noticed that it fails when there are any java.util.Vector or java.util.List objects within the object being transferred. I have seen several other posts about this but with no responses. Does anyone know why this is the case? How can I get around this? I read that using an ArrayList
RE: Apache Rampart 1.1 Released
Cool. Someone should update this page: http://ws.apache.org/axis2/modules/index.html with Rampart and Sandesha links. -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Sunday, December 10, 2006 9:54 PM To: axis-user@ws.apache.org Subject: Apache Rampart 1.1 Released Apache Rampart team is happy to announce the 1.1 release of Apache Rampart You can download the releases from: http://www.apache.org/dyn/closer.cgi/ws/rampart/1_1 Apache Rampart 1.1 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis 1.1, based on Apache WSS4J 1.5.1 and the Apache AXIOM-DOOM 1.2.1 implementation. What is in this release There are two main Apache Axis2 modules provided with this release. * rampart-1.1.mar * This provides support for WS-Security and WS-SecureConversation features. rahas-1.1.mar This module provides the necessary components to enable SecurityTokenService functionality on a service. Apache Rampart 1.1 introduces a new configuration model based on WS-Policy and WS-Security Policy and it is important to note that Apache Rampart 1.0 style configuration is now deprecated and will not be available in next major version. Apache Rampart 1.1 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.1 to configure WS-SecureConversation + WS-ReliableMessaging scenarios. The rampart module was successfully tested for interoperability with other WS-Security implementations. WS - Sec* specifications supported by Apache Rampart are as follows: * WS - Security 1.0 * WS - Secure Conversation - February 2005 * WS - Security Policy - 1.1 - July 2005 * WS - Trust - February 2005 * WS - Trust - WS-SX spec - EXPERIMENTAL Thank you for using Apache Rampart. The Apache Rampart team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Kandula2
Does anyone know the status of the Kandula2 project at Apache (planned release date, etc.)? We have a definite need for distributed transactions in our current web service... Brennan Spies Sr. Programmer Analyst Shared Application Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] How to build web service that is invoked via HTTP Post ?
Have you looked at the REST examples? http://ws.apache.org/axis2/1_1/rest-ws.html Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: S. Sharif [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 11:09 AM To: axis-user@ws.apache.org Subject: [Axis2] How to build web service that is invoked via HTTP Post ? Hi, I am new to building web services in Java, even though I have been using Java for several years mostly in building web applications. I have been assigned the task to replace several web services that were previsouly built using some proprietary software, and re-build them in Java. I have started looking into Axis2 several days ago. But the examples I have tried so far do not seem to work the same way as the web services that I am replacing. I have recenly found out that there is no existing WSDL file for the web services that I am converting to Java, and that these web services are invoked via HTTP Post. The client invokes the web service by passing an xml request to them via HTTP Post and then receives back an xml via HTTP Reponse. So it seems that the SOAP examples on the Axis2 website do not apply to me. Should I still use Axis2 in my situation, or how should I go about building these web services in Java? Any suggestions are welcome. Thanks. -Saladin ** * Saladin Sharif * e-mail: [EMAIL PROTECTED] * Visit homepage @ http://gaia.ecs.csus.edu/~sharifs ** _ ___ Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] JMS client How
You can use the generated client that the Axis 2.0 code generator supplies. The default endpoint in the generated stub/unit test and the generated WSDL won’t be correct, but you can modify them to fit pretty easily. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: falom [mailto:[EMAIL PROTECTED] Sent: Sunday, November 19, 2006 11:10 PM To: axis-user@ws.apache.org Subject: [Axis2] JMS client How Hi, How to write client call to a JMS service in Axis2. Does ServiceClient support this in some way or do i need to implement the axis2 JMSSender or other ways to accomplish that? falom _ 抢注雅虎免费邮箱-3.5G容量，20M附件！ http://cn.mail.yahoo.com
RE: Re[2]: [AXIS2] Integration with standalone java program
Yes, you can use Axis 2.0 in a standalone context. The java app will need some type of available transport to communicate remotely--Axis provides some simple ones (SimpleHTTPServer, TCPServer, etc.). If you are still in the design phase of the app, you might consider doing it as a Spring 2.0 app, which gives you a wealth of options (including doing it with JMX and Spring's own MBeanServer-- http://static.springframework.org/spring/docs/2.0.x/reference/jmx.html ). Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Igor Borovkov [mailto:[EMAIL PROTECTED] Sent: Friday, November 17, 2006 12:03 PM To: Sanjiva Weerawarana Cc: axis-user@ws.apache.org Subject: Re[2]: [AXIS2] Integration with standalone java program Sanjiva Weerawarana, great thanks for your answer. But I am afraid I didn't fully correctly formulate the question. Let me explain the problem more clearly. Assume we have the java program P1 that streams video to a network. We want to develop AXIS2 based webservice to control streaming process (for instance, start and stop of streaming). In such case, could we really embed axis2 to that java program and not to use any appserver? If yes, could you suggest me some tut or javadoc's url where I can get a direction for following searches. Hello. I need to invoke methods of a standalone java program from a webservice. Is it possible to embed to in Axis2? Yes, absolutely. Is it better way than using RMI to communicate with the standalone java program? Depends on your requirements- if the only consumers of of your service are other Java programs within your local network then RMI may suffice. If you need clients in C and .Net and PHP and Java all to access it then you Web services is a better approach. Sanjiva. -- Cheers, Igor Borovkov E-mail: [EMAIL PROTECTED] Mob. phone: +38-067-252-66-99 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Is Axis2 1.1 working for you?
It's been working a while for me (since before 1.1), but my case is pretty straightforward. I can't really vouch for anyone who is using Rampart, MTOM, etc. I would like to see more out-of-the-box robust support for JMS (i.e., from the codegen module)...yes, it's not WS-I, but in the enterprise it's of major importance (esp. in my area, EAI) where in many cases HTTP just won't cut it. This is, hopefully, a 1.2 goal. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 11:13 AM To: axis-user@ws.apache.org Cc: Axis developer list Subject: [Axis2] Is Axis2 1.1 working for you? Folks, Please chime in with your observations: - Is Axis2 1.1 working for you? - Did you find a problem? - Is it in JIRA? (What's the JIRA issue #) based on this feedback, depending on the issues/problems, the dev team can decide on whether to cut a quick 1.1.1 off the 1.1 branch and what that 1.1.1 should contain as fixes. Otherwise, onwards towards 1.2... Thanks, dims -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Compiling the source code of Axis2
For Windows, Maven puts your downloaded jars into
${HOME}/.maven/repository directory.
-Original Message-
From: Kedar, Shahar
[mailto:[EMAIL PROTECTED]
Sent: Wednesday,
November 15, 2006 2:46
AM
To: axis-user@ws.apache.org
Subject: [Axis2] Compiling the
source code of Axis2
Hi,
Where can I get all the JARs required for compiling all
Axis2 modules? I was hoping the after running Maven, I will have all the jars
downloaded to some directory, but if they did, I can't find them now.
Thanks,
Shahar Kedar
externalMapping - what is it?
Does anyone know the specifics of what is/how to use the externalMapping Ant task attribute (or em command line option) listed in the Axis 2.0 1.1 documentation? BTW, the Option Reference table on this page (http://ws.apache.org/axis2/tools/1_1/CodegenToolReference.html) is missing entries for a few of the command line options that are cross-referenced by the Ant Task Reference table. Brennan Spies Sr. Programmer Analyst Shared Application Services
RE: Axiom, ADB, XMLBeans, JiBX: how to choose?
Other than some of the funny programming conventions used in the lib (lots of inner classes), I like XmlBeans too, mostly because it is closer to the bare metal of XML structure. Other XML-Java binding frameworks, which tend to focus on doing mapping (explicit or implicit) between JavaBeans and XML are a little more elegant but lose something in the translation, esp. with complex schemas. I also like the built-in support for XPath and XQuery: http://xmlbeans.apache.org/docs/2.0.0/guide/conSelectingXMLwithXQueryPathXPat h.html -Original Message- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 15, 2006 12:49 PM To: axis-user@ws.apache.org Subject: Re: Axiom, ADB, XMLBeans, JiBX: how to choose? As Jhan suggested, XMLBeans has the best schema support of any of the frameworks (all is a very big claim to make regarding schema, since there are still disputes over what the specification means in some areas, but certainly XMLBeans comes about as close as anything does). ADB and JiBX each have some areas where they don't support schema correctly. In the JiBX case, the most important one is probably the lack of support for xsi:type (used for one form of polymorphism in schema documents). JiBX is the only data binding framework which currently offers full support for unwrapping operations in Axis2. The Quick Start Guide (http://ws.apache.org/axis2/1_1/quickstartguide.html) gives a very simple example of using this - if you compare the JiBX client and server code with the other examples you'll see how unwrapping simplifies usage. This simple example doesn't use a binding definition, since it's dealing only with a couple of primitive types that have default handling, but in general you'll need a binding definition to tell JiBX how to convert your Java objects to and from XML. JiBX does provide primitive tools for generating code and bindings from schema, and binding and schema from code, but generally you're going to need to work with the binding definition as the basis of anything you do using JiBX. You can see http://www.jibx.org for details on JiBX, and http://ws.apache.org/axis2/1_1/jibx/jibx-codegen-integration.html (also included in the Axis2 documentation download) for details on how to use JiBX with Axis2. - Dennis Dennis M. Sosnoski SOA, Web Services, and XML Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117 Jhan Yuler wrote: ADB, XMLBeans, JiBX are framework for binding xml data to java beans and viceversa. Each one of these have own home page and explains the architecture and use way. ADB Axis Data Bindind was created for the project Apache Axis2 for optimize the marshaling and unmarshaling process using Axis... XMLBeans is my favorite, http://xmlbeans.apache.org/ it is easy to use, and very flexible and support all Schema standard I dont know the JiBX framework, but it seems to be really good (especialy for de performance), i am learning about this. ADB and XMLBeans generates java code from a schema definition (xsd file). And the generated code, extends from classes of the each framework. In the case of JiBX you must to have the java beans created, and define a databinding file that indicates to the framework how to bind the xml data to java beans fields. This is very usefull in the case that you have previously created the beans and need to use in the message of a web service. I recommend to you visit the web sites of each one of this frameworks for best information. Solo conoce el vino bueno, aquel que probó el vino amargo From: BoD [EMAIL PROTECTED] Reply-To: axis-user@ws.apache.org To: axis-user@ws.apache.org Subject: Axiom, ADB, XMLBeans, JiBX: how to choose? Date: Wed, 15 Nov 2006 11:00:01 +0100 MIME-Version: 1.0 Received: from mail.apache.org ([140.211.11.2]) by bay0-mc7-f1.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Wed, 15 Nov 2006 03:13:04 -0800 Received: (qmail 65118 invoked by uid 500); 15 Nov 2006 11:13:13 - Received: (qmail 65080 invoked by uid 99); 15 Nov 2006 11:13:12 - Received: pass (hermes.apache.org: domain of [EMAIL PROTECTED] designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Nov 2006 03:13:08 -0800 Received: from list by ciao.gmane.org with local (Exim 4.43)id 1GkHYy-0004mk-Brfor axis-user@ws.apache.org; Wed, 15 Nov 2006 11:00:12 +0100 Received: from jraf.org ([82.66.230.87])by main.gmane.org with esmtp (Gmexim 0.1 (Debian))id 1AlnuQ-0007hv-00 for axis-user@ws.apache.org; Wed, 15 Nov 2006 11:00:12 +0100 Received: from BoD by jraf.org with local (Gmexim 0.1 (Debian))id 1AlnuQ-0007hv-00for axis-user@ws.apache.org; Wed, 15 Nov 2006 11:00:12 +0100 X-Message-Info:
RE: client-side Axis2SampleDocLit
Adrian,
Your classpath is not set correctly:
http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/classpath.html
That is, the classpath needs to reference the root folder of your classes
directory or the .jar/.zip file explicitly.
-Original Message-
From: adrian rutle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 9:27 AM
To: axis-user@ws.apache.org
Subject: client-side Axis2SampleDocLit
Hi
D:\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDocLitClient\build\classesjav
a
-
cp
.:D:\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDocLitClient\build\lib:D:\Ph
D\MOD250-JWS\axis2-bin\lib:D:\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDoc
Lit
Client\build\classes\org\apache\axis2\userguide
org.apache.axis2.userguide.TestClient
Gives:
Exception in thread main java.lang.NoClassDefFoundError:
org/apache/axis2/user
guide/TestClient
I am sure that the class file TestClient exists in that folder.
package org.apache.axis2.userguide;
import org.apache.axis2.userguide.*;
import org.apache.axis2.userguide.axis2sampledoclit.*;
import org.apache.axis2.userguide.axis2sampledoclit.impl.*;
public class TestClient
{
public static void main(String []args){
System.out.println(\t=== we try to run our TestClient);
try
{
org.apache.axis2.userguide.Axis2SampleDocLitServiceStub stub
= new
org.apache.axis2.userguide.Axis2SampleDocLitServiceStub(null,
http://localhost:8080/axis2/services/Axis2SampleDocLitService;);
//Create the request document to be sent.
org.apache.axis2.userguide.axis2sampledoclit.EchoStringDocument reqDoc =
org.apache.axis2.userguide.axis2sampledoclit.EchoStringDocument.Factory.newIn
stance();
org.apache.axis2.userguide.axis2sampledoclit.EchoStringDocument.EchoString
es = reqDoc.getEchoString();
es.setEchoStringParam(Axis2 Echo);
//invokes the Web service.
org.apache.axis2.userguide.axis2sampledoclit.EchoStringResponseDocument
resDoc =
stub.echoString(reqDoc);
System.out.println(resDoc.getEchoStringResponse().getEchoStringReturn());
}
catch (java.rmi.RemoteException e)
{
e.printStackTrace();
}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: client-side Axis2SampleDocLit
\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDoc
Lit
Client\build\classes\org\apache\axis2\userguide
should be:
\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDoc
Lit
Client\build\classes\
You are incorrectly referencing the actual folder where the class file is, so
it is searching for the subdirectories given by your package structure, and
not finding it.
Brennan Spies
Sr. Programmer Analyst
Shared Application Services
-Original Message-
From: adrian rutle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 9:58 AM
To: axis-user@ws.apache.org
Subject: Re: client-side Axis2SampleDocLit
Spies, Brennan skrev:
Adrian,
Your classpath is not set correctly:
http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/classpath.html
That is, the classpath needs to reference the root folder of your classes
directory or the .jar/.zip file explicitly.
Thanks, but I have put all the jar files from axis2/lib in the jdk/lib
directory, and the CLASSPATH var from control panel points to these
locations
AXIS2_HOME=D:\PhD\MOD250-JWS\axis2-bin
CLASSPATH=D:\PhD\MOD250-JWS\axis2-bin\lib;.;C:\Programfiler\Java\jdk1.5.0_07\
lib
-Original Message-
From: adrian rutle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 9:27 AM
To: axis-user@ws.apache.org
Subject: client-side Axis2SampleDocLit
Hi
D:\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDocLitClient\build\classesjav
a
-
cp
.:D:\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDocLitClient\build\lib:D:\Ph
D\MOD250-JWS\axis2-bin\lib:D:\PhD\MOD250-JWS\axis2-bin\samples\Axis2SampleDoc
Lit
Client\build\classes\org\apache\axis2\userguide
org.apache.axis2.userguide.TestClient
Gives:
Exception in thread main java.lang.NoClassDefFoundError:
org/apache/axis2/user
guide/TestClient
I am sure that the class file TestClient exists in that folder.
package org.apache.axis2.userguide;
import org.apache.axis2.userguide.*;
import org.apache.axis2.userguide.axis2sampledoclit.*;
import org.apache.axis2.userguide.axis2sampledoclit.impl.*;
public class TestClient
{
public static void main(String []args){
System.out.println(\t=== we try to run our TestClient);
try
{
org.apache.axis2.userguide.Axis2SampleDocLitServiceStub stub
= new
org.apache.axis2.userguide.Axis2SampleDocLitServiceStub(null,
http://localhost:8080/axis2/services/Axis2SampleDocLitService;);
//Create the request document to be sent.
org.apache.axis2.userguide.axis2sampledoclit.EchoStringDocument reqDoc =
org.apache.axis2.userguide.axis2sampledoclit.EchoStringDocument.Factory.newIn
stance();
org.apache.axis2.userguide.axis2sampledoclit.EchoStringDocument.EchoString
es = reqDoc.getEchoString();
es.setEchoStringParam(Axis2 Echo);
//invokes the Web service.
org.apache.axis2.userguide.axis2sampledoclit.EchoStringResponseDocument
resDoc =
stub.echoString(reqDoc);
System.out.println(resDoc.getEchoStringResponse().getEchoStringReturn());
}
catch (java.rmi.RemoteException e)
{
e.printStackTrace();
}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Standalone axis
Title: Standalone axis
Close to what I was doing. All I am doing
in the class is configuring the runtime, then using the JMSListener class as my
server (it uses the thread pool from Doug Leas lib to
handle incoming requests). You do not actually need to create the service
yourself. The Axis runtime will do that for you. It helps to look at the code
for JMSListenerit explains a lot. Regardless of whether you use it
standalone or inside of an HTTP server, it is basically the same thing
happening since the JMSListener and JMSSender classes handle all the transport
in and out in either case.
Remember, you have to have a certain
directory structure for Axis 2 (which I just copy from the axis2.war), like
config
n
axis2.xml
repository
n
modules
-- modules.listing
-- *.mar
files
n
services
-- services.listing
-- *.aar
So I deploy my actual .aar service file under
the /services folder after doing the code generation, modifying the generated
code, then using the generated Ant build.xml file to create the .aar and other artifacts.
You should also place the standard addressing.mar under modules, and any other
modules you are using.
Of course, I am assuming that you have
already made the appropriate modifications to your axis2.xml and services.xml
(in your .aar) to enable JMS transport. I commented out all of the
HTTP-specific configuration in axis2.xml because I did not need it in this
case. See the Axis 1.1 docs for JMS transport for a fuller explanation; also
see my comments below and in the previous post in the link.
This is a very simple implementation (not
sure how it scales on the Axis service side, but a good JMS server setup will
scale well on the messaging end). It works well, though, for what we use it for
public class JMSServer { public static void main(String[] args) { //initialize the Log4J logging-I just put it in my config folder (you can put it elsewhere) PropertyConfigurator.configure(./conf/log4j.properties); try { //The first arg to the method is the root repository location //which contains the /modules and /services subfolders //The second arg is the location of the global config file, axis2.xml ConfigurationContext context = ConfigurationContextFactory .createConfigurationContextFromFileSystem(./repository, ./conf/axis2.xml); //gets the JMS configuration, as I specified in the previous post TransportInDescription trIn = context.getAxisConfiguration() .getTransportIn(new QName(Constants.TRANSPORT_JMS)); final TransportListener listener = trIn.getReceiver(); //Add a shutdown hook, so that when you stop the java process, it //will shutdown your listener gracefully Runtime.getRuntime().addShutdownHook( new Thread(new Runnable() { public void run() { try { listener.stop(); } catch (AxisFault e) { e.printStackTrace(); } } })); //initialize the listener with the context and transport-in description listener.init(context, trIn); //starts the transport listening for incoming JMS messages listener.start(); } catch (Exception e) { e.printStackTrace(); } } //end main()}
Brennan Spies
Sr. Programmer Analyst
Shared Application Services
-Original Message-
From: Kang, Kamaljeet K.
[mailto:[EMAIL PROTECTED]
Sent: Tuesday,
November 14, 2006 11:51 AM
To: Spies, Brennan
Subject: RE: Standalone axis
Thanks again Brennan. I
am sorry but I still do not see the example in JMS. I am trying the following,
let me know if it will work
//
Start the listener and pass the configuration from axis2.xml
JMSListener jmsListener = new JMSListener();
ConfigurationContextFactory builder = new ConfigurationContextFactory();
ConfigurationContext confContext =
builder.createConfigurationContextFromFileSystem(d:\\websvc\\mtosi\\conf,
axis2.xml);
jmsListener.init(confContext, confContext.getAxisConfiguration().getTransportIn(
new QName(Constants.TRANSPORT_JMS)));
jmsListener.start();
//Create a service and add it to the
context.
// ? Not sure how to create a service and pass
the configuration from 'service.xml'
AxisService service = Utils.createSimpleService(serviceName,
TestJMS.class.getName(), operationName);
confContext.getAxisConfiguration().addService(service);
thanks
Kamal
From: Spies, Brennan
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006
1:39 PM
To: Kang, Kamaljeet K.
Subject: RE: Standalone axis
Kamal,
If you look at the
documentation for the newly released 1.1 version of Axis 2.0, they show you how
to set it up in the section on JMS transport. There they assume that you are
embedding it in an HTTP server. In my case I am actually using it as a
standalone Java application.
Brennan Spies
Sr. Programmer
Analyst
Shared
Application Services
-Original Message-
From: Kang, Kamaljeet K.
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006
10:35 AM
To: Spies, Brennan
Subject: RE: Standalone axis
Brennan,
Thanks a
lot for replying.
Actually,
I want to embed AxisEngine (with JMS
RE: Standalone axis
Title: Standalone axis I have an example of a very simple standalone JMSServer class here: http://www.mail-archive.com/axis-user@ws.apache.org/msg20494.html -Original Message- From: Kang, Kamaljeet K. [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 2:28 PM To: axis-user@ws.apache.org Subject: Standalone axis Hi, I just want to setup webservice with JMS as transport and I do not want to install Tomcat or other application server. Can somebody please show me how to do this? Also, can somebody tell me if there is any documentation of 'savan'. kamal The information contained in this message may be privilegedand confidential and protected from disclosure. If the readerof this message is not the intended recipient, or an employeeor agent responsible for delivering this message to theintended recipient, you are hereby notified that any reproduction,dissemination or distribution of this communication is strictlyprohibited. If you have received this communication in error,please notify us immediately by replying to the message anddeleting it from your computer. Thank you. Tellabs
RE: WSDL2Java support JMS binding
Yeah, I was wondering the same thing myself... ;) Short answer probably is...not in 1.1. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 10:19 AM To: axis-user@ws.apache.org Subject: Re: WSDL2Java support JMS binding You can follow the JIRA: https://issues.apache.org/jira/browse/AXIS2-1381 thanks, dims On 11/9/06, Kang, Kamaljeet K. [EMAIL PROTECTED] wrote: Hi, I would like to know, when is axis2 WSDL2Java tool going to support JMS binding from WSIF? thanks Kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: wsdl schema prefix
You mean something like (I assume you are using Eclipse's validator)...
cvc-complex-type.2.1: Element 'soap:address' must have no character or
element information item [children], because the type's content type is
empty.
Just change your tags so they are of the form soap:address/ rather than
soap:address/soap:address, and the validation errors should disappear.
The same goes for soap:body and soap:operation elements.
Brennan Spies
Sr. Programmer Analyst
Shared Application Services
(209) 341-6457
-Original Message-
From: Philipp Perner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 12:55 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl schema prefix
hi
I have included the namespace declaration in my wsdl file as you can see
attached.
But you were right, I had to manually add it -- 17 new errors occured
after validation.
is this a bug?
Spies, Brennan schrieb:
Do you have the namespace declaration
xmlns:xs=http://www.w3.org/2001/XMLSchema;
as an attribute of your root element?
-Original Message-
From: Philipp Perner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 10:06 AM
To: axis-user@ws.apache.org
Subject: wsdl schema prefix
me again!
I didnt use the Axis2 Code Generator, because in my posting above the
wsdl was not valid, whatever the reasons were.
So I manually generated my wsdl file with Java2WSDL
No i have a wsdl file which has after validation one single error:
error in line 229: The prefix xs for element xs:schema is not bound.
can anyone help me?
the command I generated wsdl with is:
java -cp {required librarypaths} org.apache.ws.java2wsdl.Java2WSDL -o
../wsdl -l http://localhost:8081/axis2/services/Pseudonymisierung; -sn
Pseudonymisierung -cn healthgate.axis.service.Pseudonymisierung -of
Pseudonymisierung.wsdl
Is there anything wrong with the command? do I have to add anything that
binds the prefix?
kind regards,
Philipp
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: wsdl schema prefix
Do you have the namespace declaration
xmlns:xs=http://www.w3.org/2001/XMLSchema;
as an attribute of your root element?
-Original Message-
From: Philipp Perner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 10:06 AM
To: axis-user@ws.apache.org
Subject: wsdl schema prefix
me again!
I didnt use the Axis2 Code Generator, because in my posting above the
wsdl was not valid, whatever the reasons were.
So I manually generated my wsdl file with Java2WSDL
No i have a wsdl file which has after validation one single error:
error in line 229: The prefix xs for element xs:schema is not bound.
can anyone help me?
the command I generated wsdl with is:
java -cp {required librarypaths} org.apache.ws.java2wsdl.Java2WSDL -o
../wsdl -l http://localhost:8081/axis2/services/Pseudonymisierung; -sn
Pseudonymisierung -cn healthgate.axis.service.Pseudonymisierung -of
Pseudonymisierung.wsdl
Is there anything wrong with the command? do I have to add anything that
binds the prefix?
kind regards,
Philipp
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Crimson parser
Try removing Crimson from your classpath and using Xerces instead. I believe the last release of Crimson was back in 2001... Brennan Spies -Original Message- From: stevenw [mailto:[EMAIL PROTECTED] Sent: Sunday, November 05, 2006 10:36 AM To: axis-user@ws.apache.org Subject: Crimson parser Hi All, Hopefully, I can get some help here, because I am at the end of my rope. I am trying to get an axis client to work for some wsdl I have. I have created the java clients using Axis WSDL2JAVA. I created a test WAS 6 project using Rational Application Developer and everything worked fine. It was just one simple servlet in a web project calling the web service (included the Axis generated client in the WEB-INF/lib directory. Then, when I tried to move it to the real project, I receive the following error: [11/5/06 8:02:10:948 MST] 0045 InternalExcep F Exception: [11/5/06 8:02:10:948 MST] 0045 InternalExcep F TRAS0014I: The following exception was logged org.apache.axis.ConfigurationException: java.lang.IllegalStateException: can't declare any more prefixes in this context java.lang.IllegalStateException: can't declare any more prefixes in this context at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:524) at org.apache.crimson.parser.Parser2.parse(Parser2.java:305) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442) at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:18 5) at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369) at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:388) at org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java: 179) at org.apache.axis.AxisEngine.init(AxisEngine.java:172) at org.apache.axis.AxisEngine.init(AxisEngine.java:156) at org.apache.axis.client.AxisClient.init(AxisClient.java:52) at org.apache.axis.client.Service.getAxisClient(Service.java:104) at org.apache.axis.client.Service.init(Service.java:113) It seems that the real difference from the real project (that throws the above error) and test project (that does not fail) if the presence of Struts and the crimson.jar. As you can see from the stack trace above, the parser being used is crimson. So, my question ishow do I get the Axis client to use a different parser instead of the crimson parser? I tried taking the crimson parser out of the classpath, but then Struts fails. help Thanks, Steve -- View this message in context: http://www.nabble.com/Crimson-parser-tf2578513.html#a7188039 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Converting from UTF-8 to ISO-8859-I with Axis2 and Java
I haven't studied the specs to be able to decide how it should work... Section 3.1.5 of the Simple SOAP Binding Profile (WS-I) states that Content-Type HTTP header field-value must indicate the correct character encoding, using the charset parameter. In absence of this, it must use the default us-ascii charset. Furthermore, it says that the 'encoding' attribute on the envelope should be ignored... http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0.html#Character_Enco dings -Original Message- From: Manuel Mall [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 8:24 AM To: axis-user@ws.apache.org Subject: Re: Converting from UTF-8 to ISO-8859-I with Axis2 and Java On Thursday 02 November 2006 00:03, Bruno Negrao wrote: Manuel, It seems you are using SoapUI to decode the SOAP response. Does SoapUI uses axis2 do send/receive the messages? The log shows the case were SoapUI is the client and Axis2 is the server. The server does decode the message, that is converts the text...text element into a Java String and then puts that String back into the response. I also tested with an Axis2 client and it works fine as well. In the end I was mainly interested in the 'wire' log. And it shows correct encoding. This meant that the Axis2 service correctly decoded and encoded the XML. You should use Axis2 to decode the response, not SoapUI. Can you make your echo service available on the internet? No guarantee it will be available for long. But for the time being: http://arcus.com.au:6060/axis2/services/EchoService Also I saw your server is setting the Content-Type: text/xml; charset=iso-8859-1[\r][\n] header on its responses. This is different from my case since my server omits this header. My hypotheses is axis2 gets encoding type of the response from the Content-Type header instead from the XML declaration. Yes, that could well be the case. I haven't studied the specs to be able to decide how it should work. I assume its along the following lines: 1) If http is the transport and an http Content-type header exists use that encoding else 2) attempt encoding detection as per XML spec, that is look for an xml prolog and do some UTF byte mark sniffing... Regards, bruno Cheers Manuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Converting from UTF-8 to ISO-8859-I with Axis2 and Java
Well, its not actually part of the SOAP protocol, but WS-I. But since WS-I is a very widely accepted standard for interoperability (Axis 2 in many cases assumes you are WS-I compliant), its best to follow those recommendations. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Bruno Negrao [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 10:28 AM To: axis-user@ws.apache.org Subject: Re: Converting from UTF-8 to ISO-8859-I with Axis2 and Java On 11/1/06, Spies, Brennan [EMAIL PROTECTED] wrote: I haven't studied the specs to be able to decide how it should work... Section 3.1.5 of the Simple SOAP Binding Profile (WS-I) states that Content-Type HTTP header field-value must indicate the correct character encoding, using the charset parameter. In absence of this, it must use the default us-ascii charset. Furthermore, it says that the 'encoding' attribute on the envelope should be ignored... http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0.html#Character_Enco dings Brennan, It seems you solved this thread. If these are the specifications of SOAP protocol, Axis2 does not need any update, my SOAP server does. I'll ask them to change it and if they do it i'll post the result here on this thread. Thank you, bruno
RE: Generate stubs from WSDL for Business Objects XiR2
Eric, Can't really make that call for you, but there have been a significant number of bug fixes between 1.0 and the current RC for 1.1. Release for 1.1 is coming soon, so if you can wait, that should be more easy to recommend. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Eric Hartmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:53 AM To: axis-user@ws.apache.org Subject: Re: Generate stubs from WSDL for Business Objects XiR2 Hi, I'm using Axis2 1.0. Does the nightly build is stable enough to be used in production ? -eric Spies, Brennan wrote: Are you using the most recent nightly build for Axis2 1.1? Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- *From:* Eric Hartmann [mailto:[EMAIL PROTECTED] *Sent:* Monday, October 30, 2006 8:18 AM *To:* axis-user@ws.apache.org *Subject:* Generate stubs from WSDL for Business Objects XiR2 Hi, I'm trying to use Axis2 to connect to Business Objects Web Services. I've generated all my classes with WSDL2Java but when compiling my project, I have the following errors : [INFO]/projects/hrprocess.lvmh/TestCreationUserBo/src/main/java/com/adp/hr/bu sinessobjects/webservices/BICatalogStub.java:[4997,75] cannot find symbol [INFO]symbol : method convertToOMAttribute(java.lang.String) [INFO]location: class org.apache.axis2.databinding.utils.ConverterUtil I've checked thtat ConverterUtil does not contain the convertToOMAttribute method. Is there any workaround ? Thanks in advance, -eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: need JMX support !
-Original Message- From: xu cai [mailto:[EMAIL PROTECTED] Sent: Monday, October 30, 2006 10:04 PM To: axis-user@ws.apache.org Subject: need JMX support ! hi all, I wanna use JMX to manage the web services deployed in Axis, Could somebody help me with these questions ? 1) Does Axis support JMX ? Axis 1 doeshttp://ws.apache.org/axis/java/apiDocs/org/apache/axis/management/jmx/package-summary.html 2) is there any good jmx web console for Tomcat ? MC4J is nice (http://mc4j.org/confluence/display/mc4j/Home), and of course there is always JConsole if you are running on JSE 5.0. thanks xucai
RE: Generate stubs from WSDL for Business Objects XiR2
Are you using the most recent nightly build for Axis2 1.1? Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Eric Hartmann [mailto:[EMAIL PROTECTED] Sent: Monday, October 30, 2006 8:18 AM To: axis-user@ws.apache.org Subject: Generate stubs from WSDL for Business Objects XiR2 Hi, I'm trying to use Axis2 to connect to Business Objects Web Services. I've generated all my classes with WSDL2Java but when compiling my project, I have the following errors : [INFO]/projects/hrprocess.lvmh/TestCreationUserBo/src/main/java/com/adp/hr/businessobjects/webservices/BICatalogStub.java:[4997,75] cannot find symbol [INFO]symbol : method convertToOMAttribute(java.lang.String) [INFO]location: class org.apache.axis2.databinding.utils.ConverterUtil I've checked thtat ConverterUtil does not contain the convertToOMAttribute method. Is there any workaround ? Thanks in advance, -eric
RE: org.apache.axis2.AxisFault: java.security.AccessControlException: access denied
How-to is here: http://tomcat.apache.org/tomcat-5.5-doc/security-manager-howto.html Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2006 6:35 AM To: axis-user@ws.apache.org Subject: Re: org.apache.axis2.AxisFault: java.security.AccessControlException: access denied Looks like you are using Sun's JDK and Tomcat. Are you running tomcat with -security option on? If so, you will need to edit conf\catalina.policy and grant more privileges to Axis2 classes. -- dims On 10/27/06, Rodrigo Tenório [EMAIL PROTECTED] wrote: Hi! As you can see I'm a newbie using Axis2... So, I created a Web Service in my local machine and it worked. When I uploaded it to the server the following exception ocurred: INFO: Received Error Message with id urn:uuid:BA369201AA15F7592411619529529531 org.apache.axis2.AxisFault: java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperat ion.java:302) at br.com.ptn.exemplo.ws.cliente.FatorialWSStub.calcular(FatorialWSStub.java:138 ) at br.com.ptn.exemplo.Main.init(Main.java:36) at br.com.ptn.exemplo.Main.main(Main.java:47) Caused by: java.lang.Exception: org.apache.axis2.AxisFault: java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader); nested exception is: java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:247) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAsPrivileged(Subject.java:517) at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275) at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161 ) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationF ilterChain.java:245) at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterC hain.java:50) at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain. java:156) at java.security.AccessController.doPrivileged(Native Method) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCha in.java:152) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.jav a:204) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.jav a:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java: 107) at br.com.locaweb.tomcat.LocaWebValve.invoke(LocaWebValve.java:101) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java: 876) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java :684) at java.lang.Thread.run(Thread.java:595) Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader) at java.security.AccessControlContext.checkPermission(AccessControlContext.java: 264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.Thread.setContextClassLoader(Thread.java:1306) at org.apache.axis2.receivers.AbstractMessageReceiver.saveTCCL(AbstractMessageRe ceiver.java:45) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractI nOutSyncMessageReceiver.java:38) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTT
RE: [Axis2] Which App server do you use?
We use Websphere (mainly) and also JBoss. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2006 7:01 AM To: axis-user@ws.apache.org Cc: Axis developer list Subject: [Axis2] Which App server do you use? Folks, We got Axis2 war working under Weblogic 9.2 and Websphere 6.1 (non-exploded) yesterday. For weblogic, you need to add a weblogic.xml with the prefer-web-inf stuff. In websphere, you need to set the class loader order to Classes loaded with parent class loader first and the WAR class loader policy to Class loader for each WAR file in application. Getting back the $subject? Which App server do you use? So that we can focus testing... thanks, dims -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Looking for xml schema for services.xml
Title: Looking for xml schema for services.xml I must correct myselfit looks like there is one Under the subversion repository, \xdocs\1_1\resources\schemas\services.xsd. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 10:18 AM To: axis-user@ws.apache.org Subject: RE: Looking for xml schema for services.xml No documentation, no xsd,...well I guess I need to navigate through the axis2 code to see what options are currently availablein the services.xml and what the valid values for these options are... :-) Gul From: Spies, Brennan [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 1:03 PM To: axis-user@ws.apache.org Subject: RE: Looking for xml schema for services.xml Gul, Dont think there is one yetprobably because the cement hasnt really dried, and wiggle room is needed in case other features are added. There probably should be one eventually, if for no other reason than tooling/users being able to validate it. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 6:49 AM To: axis-user@ws.apache.org Subject: Looking for xml schema for services.xml I want to see the xsd for the services xml to have a better understanding of it (information about it is all over the place and hard to get the full picture for usage of advance features). I checked the nightly src distr. and couldn't find a schema for the services.xml ? Can someone help me to find it in the axis2 src repository ? Thank you Gul
RE: [Axis2] RM module vs. ActiveMQ
Good analysis of this topic here: http://www.oreillynet.com/xml/blog/2004/02/mom_wsrel_and_wire_protocol_in.htm l My thoughts: * WS-RM is about interoperability, which has no guarantee in JMS (no standard wire format) * A JMS server is likely to be faster (no XML parsing) * Most JMS implementations, like ActiveMQ, are likely to be more mature * WS-RM is mostly focused on message acknowledgement, ordering, and dealing with duplicates, but doesn't provide other QoS guarantees (e.g. durability) * WS-RM is good for bridging different types of messaging systems (i.e., the two technologies are not necessarily exclusive...) It all depends on your requirements... Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 3:52 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] RM module vs. ActiveMQ WSRM with DB persistence provides comparable capability to ActiveMQ. Anne On 10/26/06, falom [EMAIL PROTECTED] wrote: Hi, If i use reliable messaging module with DB persistence for my axis2 service, do i still have reason to consider using activeMQ? falom 抢注雅虎免费邮箱-3.5G容量，20M附件！ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: WS Addressing :: Axis2 :: JMS Webs ervice lookup issues
Axis 2.0 currently supports the JNDI lookup model, with the client invocation looking something like: jms:/Topic?transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactoryjava.naming.provider.url=""> The full documentation is in Subversion, /xdocs/1_1/jms-transport.html. The docs seems to indicate that it has been tested (only?) with ActiveMQ, but Ive used it with Tibco EMS as well. InitialContext is used to get both the ConnectionFactory and Destination. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Brian De Pradine [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 24, 2006 10:27 AM To: axis-user@ws.apache.org Cc: [EMAIL PROTECTED] Subject: RE: WS Addressing :: Axis2 :: JMS Webs ervice lookup issues Hello Vaibhav, I would have responded earlier, but I was out last week. Anyway, I recall from one of your earlier emails that you were using WebSphere to host your JMS web service. If this is the case, then you may be able to use the new client here [1] to access it. This client runs in a J2SE environment, and supports things like JNDI look up. Do note, however, that I am not sure whether the JMS support in Axis2 will work with this client. I believe that it was only tested with ActiveMQ, but I could be wrong :-) [1] http://www-1.ibm.com/support/docview.wss?uid=swg24012804 Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Vaibhav Pandey [EMAIL PROTECTED] wrote on 16/10/2006 06:05:19: Hi, I am trying to forward reply from the destination WS to another WS(actually a JMS WS) using WS Addressing. For this i need to specify various configurations like: java.naming.provider.url="" etcnow as given in my examples its usually tcp://localhost:port and thn tcp is configured in axis2.xml Now as i can see in the axis2.xml file there are configurations for tcp but not for iiop.does that make any difference ?? Bcoz after configuring all the required parameters, i am getting an error that unable to do the lookup.i have tried practically all possible configurations.kindly let me knw if u r aware of any configuration details regarding this.. Thanks Regards, Vaibhav -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Saturday, October 14, 2006 7:26 PM To: axis-user@ws.apache.org Subject: Re: WS Addressing :: Axis2 :: JMS Webs ervice lookup issues On Fri, 2006-10-13 at 11:43 +0530, Vaibhav Pandey wrote: Hi all, i have a small doubt regarding the protocol to be used during lookup of my JMS WS installed in an application server other than the one in which i have installed axis... as mentioned in all tutorials:- tcp://localhost:6061 there is a mapping of tcp with transport recievers and transport senders in axis2.xml but there is nothing of this sought for iiop .. My JMS WS is in web sphere RAD6 and i want to do a lookup of it:- iiop://localhost:2809 Do i need to add any new entries in this file in order to provide support for iiop or is it that there is no support yet for it ?? There's no support for it. As far as I know there aren't any SOAP stacks that support sending SOAP over IIOP. Its not theoretically impossible but its not a common pattern for an object to receive a SOAP message as a string first argument! Can you explain what you're looking for? Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: axis2 1.1
I havent been able to reach the link for the nightly distribution for almost 2 days now (10060 - Connection timeout). Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: Friday, October 20, 2006 7:25 PM To: axis-dev@ws.apache.org Cc: axis-user@ws.apache.org; George Wilder; Beth Ayres Subject: Re: axis2 1.1 Hi Tony, We have done some major packaging/distribution changes after the 1.1-RC1, of course with the feedback we received. 1.1-RC2 will take some more time to appear, since we need some more testing for those changes. In the mean time I recommend you to try axis2-1.1 branch nightlies available at http://people.apache.org/dist/axis2/nightly/... Thanks, Thilina On 10/21/06, Tony Dean [EMAIL PROTECTED] wrote: Thanks Anne. -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] Sent: Friday, October 20, 2006 4:15 PM To: axis-dev@ws.apache.org Cc: axis-user@ws.apache.org Subject: Re: axis2 1.1 RC1 was released on Oct 9: Download locations : * binary and source distributions - http://people.apache.org/~thilina/axis2/1.1-RC1/ * jars http://people.apache.org/~thilina/maven/org.apache.axis2/jars/ * mars (addressing and SOAP monitor) http://people.apache.org/~thilina/maven/org.apache.axis2/mars/ * Tools http://people.apache.org/~thilina/axis2/1.1-RC1/eclipse_codegen_plugin_1.1-RC1http://people.apache.org/~thilina/axis2/1.1-RC1/idea_codegen_plugin_1.1-RC1/ On 10/20/06, Tony Dean [EMAIL PROTECTED] wrote: Hi, I thought there were plans to do a release candidate for 1.1... RC1, RC2? Is such a candidate available? Thanks. Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED] SAS... The Power to Know http://www.sas.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/
RE: SOAP and Session
Is this what you are looking for? http://www.wso2.net/articles/rampart/java/2006/08/15/usernametoken-auth Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Gul Onural [mailto:[EMAIL PROTECTED] Sent: Monday, October 23, 2006 12:23 PM To: axis-user@ws.apache.org Subject: RE: SOAP and Session I am also interested in the same subject if anyone can comment on... Gul -Original Message- From: Frans Thamura @ FB - Meruvian [mailto:[EMAIL PROTECTED] Sent: Monday, October 23, 2006 6:31 AM To: axis-user@ws.apache.org Subject: SOAP and Session Hi All, I just got input from my friends to implement session in SOAP, because I want to put like a basket in shoping chart like in the server, anyone can help to implement this ? how to make the SOAP Server store the session in the server i think session is needed to implement in user login also right, so we dont have to sent user/password every time request a sOAP can help? Frans - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] RE: SOAP/JMS document
Sharad:
As I said before, the documentation for this is in the link Dims sent below
(in SVN):
http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1
How I did it:
1. I uncommented the transport receiver configuration in my axis2.xml, and
added the right info (in my case for Tibco EMS) like so:
transportReceiver name=jms
class=org.apache.axis2.transport.jms.JMSListener
...
parameter name=TibcoQueueConnectionFactory locked=false
parameter name=java.naming.factory.initial
locked=falsecom.tibco.tibjms.naming.TibjmsInitialContextFactory/parameter
parameter name=java.naming.provider.url
locked=falsetibjmsnaming://localhost:7222/parameter
parameter name=transport.jms.ConnectionFactoryJNDIName
locked=falseQueueConnectionFactory/parameter
/parameter
...
/transportReceiver
2. After WSDL2Java code generation, and doing my skeleton implementation, I
call my Stub with a URL like the following:
String endpointURL = jms:/QUEUENAME?
+ transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory
+ java.naming.factory.initial=
+ com.tibco.tibjms.naming.TibjmsInitialContextFactory
+ java.naming.provider.url=tibjmsnaming://localhost:7222
+ java.naming.security.principal=user
+ java.naming.security.credentials=password;
3. Add the following the services.xml:
service name=QueryMessageService
transports
transportjms/transport
/transports
messageReceivers
...
/messageReceivers
parameter locked=false name=ServiceClass
...
/parameter
parameter name=transport.jms.ConnectionFactory
locked=trueTibcoQueueConnectionFactory
/parameter
parameter name=transport.jms.Destination
locked=trueEJGALLO.WINERY.SAS.WORKFLOW.SERVICE.QUERY
/parameter
operation name=Query mep=http://www.w3.org/2004/08/wsdl/in-out;
...
/operation
/service
4. Since I wanted to deploy the JMS-based service as a standalone web service
with JMS transport only, I wrote a very simple class to configure Axis and
launch the JMSListener:
/**
* @author Brennan Spies
* Simple server with JMS receiver.
*/
public class JMSServer {
/**
* @param args
*/
public static void main(String[] args)
{
PropertyConfigurator.configure(./conf/log4j.properties);
try {
ConfigurationContext context = ConfigurationContextFactory
.createConfigurationContextFromFileSystem(./repository,
./conf/axis2.xml);
TransportInDescription trIn = context.getAxisConfiguration()
.getTransportIn(new
QName(Constants.TRANSPORT_JMS));
final TransportListener listener = trIn.getReceiver();
Runtime.getRuntime().addShutdownHook(new Thread(new
Runnable() {
public void run() {
try {
listener.stop();
} catch (AxisFault e) {
e.printStackTrace();
}
}
}));
listener.init(context, trIn);
listener.start();
} catch (Exception e) {
e.printStackTrace();
}
}
}
That's it. Since JMSListener already has ThreadPoolExecutor as part of its
implementation, there is no need to add any additional server-specific code.
Hope this helps,
Brennan
-Original Message-
From: Sharad Baronia [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 10:37 AM
To: axis-user@ws.apache.org; Spies, Brennan
Subject: X-Spam:::RE: SOAP/JMS document
Hi Brennan,
It does it works, any documentation on this? Architectural or a flow
diagram would help...
Thanks,
/Sharad
-Original Message-
From: Spies, Brennan [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 10:28 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: SOAP/JMS document
Done.
Brennan Spies
Sr. Programmer Analyst
Shared Application Services
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 10:03 AM
To: axis-user@ws.apache.org
Subject: Re: SOAP/JMS document
Is it the same as this? http://issues.apache.org/jira/browse/AXIS2-545
If it is then, please add your feedback there.
-- dims
On 10/13/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Brennan,
Please open an enhancement request in JIRA with your example/sample.
thanks,
dims
On 10/13/06, Spies, Brennan [EMAIL PROTECTED] wrote:
Ali,
I understand your
RE: NoClassDefFoundError: org/apache/axis2/transport/http/SimpleHTTPServer
For *nix, a handy trick to use is to run the following shell script in your lib directory: for i in *.jar; do echo $i; unzip -l $i | grep java.lang.String; done (Will vary by system and shell you are usingI am using Korn Shell here, but others are similar.) This will quickly tell you whether or not you have that class in one of your jars, or whether you are experiencing a different issue. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 19, 2006 6:49 AM To: axis-user@ws.apache.org Subject: Re: NoClassDefFoundError: org/apache/axis2/transport/http/SimpleHTTPServer Hi Thilina, Here is my latest error...same thing with the axis2-std-1.1-SNAPSHOT-bin.zip: [EMAIL PROTECTED] /cygdrive/c/Program Files/Apache Software Foundation/axis 2-std-1.1-SNAPSHOT-bin/bin $ sh ./http-server.sh the classpath :../lib/XmlSchema-SNAPSHOT.jar:../lib/activation-1.1.jar:../lib/an nogen-0.1.0.jar:../lib/axiom-api-SNAPSHOT.jar:../lib/axiom-dom-SNAPSHOT.jar:../l ib/axiom-impl-SNAPSHOT.jar:../lib/axis2-adb-1.1-SNAPSHOT.jar:../lib/axis2-adb-co degen-1.1-SNAPSHOT.jar:../lib/axis2-codegen-1.1-SNAPSHOT.jar:../lib/axis2-java2w sdl-1.1-SNAPSHOT.jar:../lib/axis2-jaxbri-1.1-SNAPSHOT.jar:../lib/axis2-jibx-1.1- SNAPSHOT.jar:../lib/axis2-kernel-1.1-SNAPSHOT.jar:../lib/axis2-saaj-1.1-SNAPSHOT .jar:../lib/axis2-spring-1.1-SNAPSHOT.jar:../lib/axis2-tools-1.1-SNAPSHOT.jar:.. /lib/axis2-xmlbeans-1.1-SNAPSHOT.jar:../lib/backport-util-concurrent-2.2.jar:../ lib/commons-codec-1.3.jar:../lib/commons-fileupload-1.1.1.jar:../lib/commons-htt pclient-3.0.1.jar:../lib/commons-logging-1.1.jar:../lib/geronimo-spec-jms-1.1-rc 4.jar:../lib/jakarta-httpcore-4.0-alpha2.jar:../lib/jaxen-1.1-beta-10.jar:../lib /jaxme2-0.5.1.jar:../lib/jaxmeapi-0.5.1.jar:../lib/jaxmejs-0.5.1.jar:../lib/jaxm exs-0.5.1.jar:../lib/jibx-bind-SNAPSHOT.jar:../lib/jibx-run-SNAPSHOT.jar:../lib/ mail-1.4.jar:../lib/neethi-SNAPSHOT.jar:../lib/servletapi-2.3.jar:../lib/spring- beans-1.2.8.jar:../lib/spring-context-1.2.8.jar:../lib/spring-core-1.2.8.jar:../ lib/spring-web-1.2.8.jar:../lib/stax-api-1.0.1.jar:../lib/stax-utils-20060915.ja r:../lib/woden-1.0.0M6.jar:../lib/wsdl4j-1.6.1.jar:../lib/wstx-asl-3.0.1.jar:../ lib/xbean-2.2.0.jar:../lib/xercesImpl-2.8.1.jar:../lib/xml-apis-1.3.03.jar Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis2/tran sport/http/SimpleHTTPServer Adam Ellwood Sr. LDAP Upgrade Analyst (Cell) +1.443.223.9837 Thilina Gunarathne [EMAIL PROTECTED] 19-Oct-2006 09:32 Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: NoClassDefFoundError: org/apache/axis2/transport/http/SimpleHTTPServer Seems like you have downloaded the 1.0.. Axis2 has moved a long way from there.. Please use the nightly builds available at http://people.apache.org/dist/axis2/nightly/ FYI: Today we modified the http-server to simpleaxis2server... You will get that in nightlies in few hours. ~Thilina On 10/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I downloaded the latest standard binary build and I am running Windows XP and Cygwin. I am getting this error when I try to run the bin/http-server.sh script: $ sh ./http-server.sh the classpath :../lib/XmlSchema-1.0.2.jar:../lib/annogen-0.1.0.jar:../lib/axiom- api-1.0.jar:../lib/axiom-dom-1.0.jar:../lib/axiom-impl-1.0.jar:../lib/axis2-adb- 1.0.jar:../lib/axis2-codegen-1.0.jar:../lib/axis2-jibx-1.0.jar:../lib/axis2-kern el-1.0.jar:../lib/axis2-tools-1.0.jar:../lib/axis2-xmlbeans-1.0.jar:../lib/backp ort-util-concurrent-2.1.jar:../lib/commons-codec-1.3.jar:../lib/commons-fileuplo ad-1.0.jar:../lib/commons-httpclient-3.0.jar:../lib/commons-logging-1.0.4.jar:.. /lib/geronimo-spec-activation-1.0.2-rc4.jar:../lib/geronimo-spec-javamail-1.3.1- rc5.jar:../lib/geronimo-spec-jms-1.1-rc4.jar:../lib/jaxen-1.1-beta-8.jar:../lib/ jaxme2-0.5.1.jar:../lib/jaxmeapi-0.5.1.jar:../lib/jaxmejs-0.5.1.jar:../lib/jaxme xs-0.5.1.jar:../lib/log4j-1.2.13.jar:../lib/neethi-1.0.1.jar:../lib/servletapi-2 .3.jar:../lib/stax-api-1.0.jar:../lib/stax-utils-20060501.jar:../lib/wsdl4j-1.5. 2.jar:../lib/wstx-asl-2.9.3.jar:../lib/xbean-2.1.0.jar Exception in thread main java.lang.NoClassDefFoundError: org/apache/axis2/tran sport/http/SimpleHTTPServer -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/
RE: simpleaxis2server.bat: System can not find the given axis2.xml
The build.xml file that is generated by WSDL2Java expects an environmental variable called exactly that (pointing to the root of your axis installation). Try adding this, and see if it works. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 19, 2006 12:10 PM To: axis-user@ws.apache.org Subject: simpleaxis2server.bat: System can not find the given axis2.xml I have downloaded the latest nightly standard binary dist, I get this error running simpleaxis2server.bat: C:\axis2\axis2-1.1-SNAPSHOT\binsimpleaxis2server.bat Using AXIS2_HOME: C:\axis2\axis2-1.1-SNAPSHOT Using JAVA_HOME: C:\jdk1.6.0 [SimpleAxisServer] Starting [SimpleAxisServer] Using the Axis2 RepositoryC:\axis2\axis2-1.1-SNAPSHOT\bin\$AX IS2_HOME\repository [SimpleAxisServer] Using the Axis2 Configuration FileC:\axis2\axis2-1.1-SNAPSHOT \bin\$AXIS2_HOME\conf\axis2.xml Oct 19, 2006 2:50:51 PM org.apache.axis2.transport.SimpleAxis2Server main SEVERE: Error starting SimpleAxisServer org.apache.axis2.AxisFault: System can not find the given axis2.xml $AXIS2_HOME\ conf\axis2.xml at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfigurati on(FileSystemConfigurator.java:111) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurat ionContext(ConfigurationContextFactory.java:61) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurat ionContextFromFileSystem(ConfigurationContextFactory.java:180) at org.apache.axis2.transport.SimpleAxis2Server.main(SimpleAxis2Server.j ava:78) [SimpleAxisServer] Shutting down The axis2.xml file is where it should be, but the $AXIS2_HOME in the following lines look suspicious to me: [SimpleAxisServer] Using the Axis2 RepositoryC:\axis2\axis2-1.1-SNAPSHOT\bin\$AX IS2_HOME\repository [SimpleAxisServer] Using the Axis2 Configuration FileC:\axis2\axis2-1.1-SNAPSHOT \bin\$AXIS2_HOME\conf\axis2.xml Adam
RE: Compilation error with WSDL2Java and XmlBeans
It's not WSDL 2.0, or there would be no portType, but rather an interface definition. The wsdl:binding section here does deviate from the standard boilerplate for a sync operation SOAP over HTTP (not using soap:operation and specifying soap:header info, having multiple operations per portType/binding), but it is legal WSDL. From the 1.1 spec (section 3.2): definitions binding soap:binding style=rpc|document transport=uri operation soap:operation soapAction=uri? style=rpc|document?? input soap:body parts=nmtokens? use=literal|encoded encodingStyle=uri-list? namespace=uri? soap:header message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?* soap:headerfault message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?/* soap:header /input output soap:body parts=nmtokens? use=literal|encoded encodingStyle=uri-list? namespace=uri? soap:header message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?* soap:headerfault message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?/* soap:header /output fault* soap:fault name=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri? /fault /operation /binding port soap:address location=uri/ /port /definitions It's not shown above, but section 2.4 2.5 puts a * after operation subelements, showing that multiple operations are allowed. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 7:20 AM To: axis-user@ws.apache.org Subject: Re: Compilation error with WSDL2Java and XmlBeans This looks like WSDL 2.0 , though I'm not sure since I've never used it. Looking at the structure it seems to be. I don't see the style definition for example. Furthermore, you are getting warnings using eclipses WTP validation, the second seeming more important: 1 WS-I: (BP2803) The wsdl:import element's namespace attribute value is a relative URI. NotificationService.wsdl 1 WS-I: (BP2105) A wsdl:import element in the WSDL namespace under the wsdl:definitions element, is preceded by child elements other than wsdl:documentation elements.NotificationService.wsdl The error I get running wsdl2java on these is that it can't resolve your binding: [java] 17/10/2006 11:11:01 org.apache.axis2.description.WSDL11ToAxisServiceBuilder findBinding [java] INFO: A service element was not found - picking a random binding! [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngin e.java:112) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl; nested exception is: [java] org.apache.axis2.AxisFault: No bindings found in wsdl [java] at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL1 1ToAxisServiceBuilder.java:246) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngin e.java:103) [java] ... 2 more HTH, Robert On 10/16/06, Jerome Magnet [EMAIL PROTECTED] wrote: That's the nightly package I used to get the output mentioned earlier (see below). Also, I tried to simplify the XSD of the messages by having all definitions in one XSD file. I simplified the message schema with a simple element definition with one level of element's containment for each message. And, I have one namespace for WSDL and XSD definitions. Unfortunately, the result is still the same. I don't get any XmlBeans Java classes for all schema definitions as I would get by compiling with XmlBeans. I attached the BAT file (replaced extension by txt) I use to invoke WSDL2Java. Jerome Output based on simplified XSD Using AXIS2_HOME: D:\Apps\axis2 Using JAVA_HOME:D:\Java\jdk1.5.0_02 AXIS2_CLASS_PATH D:\Apps\axis2;D:\Apps\axis2\lib\activation-1.1.jar;D:\Apps\axis2\lib\ann ogen-0.1.0. jar;D:\Apps\axis2\lib\axiom-api.jar;D:\Apps\axis2\lib\axiom-dom.jar;D:\A pps\axis2\lib\axiom-impl.jar ;D:\Apps\axis2\lib\axis2-adb-1.1-SNAPSHOT.jar;D:\Apps\axis2\lib\axis2-ad b-codegen-1.1.jar;D:\Apps\ax
RE: Compilation error with WSDL2Java and XmlBeans
Jerome, I am using the more boilerplate version of wsdl:binding, like so... wsdl:binding soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=... soap:operation soapAction=.../ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output ... /wsdl:operation /wsdl:binding I've had no problems using the same top-down code generation scenario with XMLBeans. My guess (and it's only a guess) is that the code generator is not handling multiple operations. My advice (which you can take or leave...): 1. File a JIRA. The Axis 2 team has been really good about fixing these. Most of the ones I've filed have been fixed in 24 hrs. or less. 2. If you're pressed for time, change it so that each portType and binding only has one operation. 3. The namespace should be a URI. I personally prefer URNs myself (never liked URLs for this, seems silly to have protocol info like http:// in a namespace). Something like urn:tmf854:v1:ws works... 4. Get rid of the redundant include's on your XSD (e.g. where A is included in B, A is included in C, and B and C are both included in your WSDL). Technically, the code generator should handle it by unique schemaLocation, but it may not be (I suspect this is why you were getting the messages saying it would not overwrite an existing class). Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Jerome Magnet [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 10:19 AM To: axis-user@ws.apache.org Subject: RE: Compilation error with WSDL2Java and XmlBeans Yes. It is definitely WSDL 1.1. Refer to the two nms in all the wsdl;definitions of my wsdl files are based on WSDL 1.1 nms: xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; and xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; We have a lot of tools already making use of these WSDL files. XMLspy is my XML editor (use it with Eclipse plug-ins or native). Also, other tools/middleware such as Artix from IONA can process these WSDL files without any problems. Here are my comments on the two issues found so far: BP2803 I guess this is just a warning. Because it is a valid URI. I also changed that to a true HTTP address in my simplification attempt. BP2105 I moved the wsdl:import above the wsdl:types and the the schema import. It still fails. I don't know how the above issues relate to the issue of not having any XmlBeans Java classes generated for my schema. Should I be expecting that, or should I re-use the Java code I generate for my XSD's using XmlBeans (scomp)? Is there a document that describes the integration process of XmlBeans as databinder with axis2 based on simple example (one operation)? Thanks again, Jerome -Original Message- From: Spies, Brennan [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 12:35 PM To: axis-user@ws.apache.org Subject: RE: Compilation error with WSDL2Java and XmlBeans It's not WSDL 2.0, or there would be no portType, but rather an interface definition. The wsdl:binding section here does deviate from the standard boilerplate for a sync operation SOAP over HTTP (not using soap:operation and specifying soap:header info, having multiple operations per portType/binding), but it is legal WSDL. From the 1.1 spec (section 3.2): definitions binding soap:binding style=rpc|document transport=uri operation soap:operation soapAction=uri? style=rpc|document?? input soap:body parts=nmtokens? use=literal|encoded encodingStyle=uri-list? namespace=uri? soap:header message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?* soap:headerfault message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?/* soap:header /input output soap:body parts=nmtokens? use=literal|encoded encodingStyle=uri-list? namespace=uri? soap:header message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?* soap:headerfault message=qname part=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri?/* soap:header /output fault* soap:fault name=nmtoken use=literal|encoded encodingStyle=uri-list? namespace=uri? /fault /operation /binding port soap:address location=uri/ /port
RE: how to: code generation when there are multiple interfaces for a single service in WSDL
Yadav, I think you are running into a similar issue that Robert and I were discussing with Jerome earlier, where Axis 2 WSDL2Java code generation does not seem to be handling portType/bindings with multiple operations. You should either create a JIRA or attach a comment to an existing one if Jerome has created it already. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Yadav, Yogendra (IT) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 11:50 AM To: axis-user@ws.apache.org Subject: how to: code generation when there are multiple interfaces for a single service in WSDL I am trying to generate code for WSRP WSDL. This WSDL has one service name WSRPServiceand multiple interfaces: WSRPBaseService WSRPServiceDescriptionService WSRPRegistrationService WSRPPortletManagementService Commend used: wsdl2java -d adb -p com.sample -ss -sd -g -uri wsrp_service.wsdl -pn WSRPServiceDescriptionService First run generates code alright, subsequent runs say INFO: File .\src\com\sample\WSRPServiceStub.java will not be overwritten. C:\work\WSRPwsdl2java -d adb -p com.sample -ss -sd -g -uri wsrp_service.wsdl -pn WSRPServiceDescriptionService Using AXIS2_HOME: C:\software\axis2-rc1 Using JAVA_HOME: //ms/dist/msjava/PROJ/sunjdk/1.5.0_04 Retrieving document at 'wsrp_v1_bindings.wsdl', relative to 'file:/C:/work/WSRP/'. Retrieving document at 'wsrp_v1_interfaces.wsdl', relative to 'file:/C:/work/WSRP/wsrp_v1_bindings.wsdl'. Retrieving schema at 'wsrp_v1_types.xsd', relative to 'file:/C:/work/WSRP/wsrp_v1_interfaces.wsdl'. Retrieving schema at 'xml.xsd', relative to 'file:/C:/work/WSRP/wsrp_v1_types.xsd'. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceSkeleton.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceMessageReceiverInOut.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\InvalidRegistrationException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\OperationFailedException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceCallbackHandler.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\InvalidRegistrationException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\OperationFailedException.java will not be overwritten. Oct 17, 2006 2:42:06 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File .\src\com\sample\WSRPServiceStub.java will not be overwritten. Files are attached. NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
RE: Compilation error with WSDL2Java and XmlBeans
Jerome, Can't see your XSD definitions, but are you using elementFormDefault=qualified? (BTW, I have been using Axis 2.0 with the exact same scenario as you have, and works for me). Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Jerome Magnet [mailto:[EMAIL PROTECTED] Sent: Monday, October 16, 2006 1:17 PM To: axis-user@ws.apache.org Subject: RE: Compilation error with WSDL2Java and XmlBeans Robert, I tried the latest nightly load. It does not fail as before. But, I got the following output (see below): I got three java classes and 2 XML resources. I don't see any XMLBeans Java classes based on the XML schema of all messages (request/Response/Exception). Also, reading the generated wsdl it has all the message schema missing. Actually, the namespace is missing. And, the prefix of my parts are null (See extract below)? Does it mean that I can use the Java classes compiled with XmlBeans? Is there a recipe to follow on how to integrate XmlBeans library of java classes with the Java code generated by axis2? Thanks, Jerome generated WSDL wsdl:definitions xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tmf854WS=tmf854.v1.ws xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; targetNamespace=tmf854.v1.ws wsdl:types/ wsdl:message name=subscribe wsdl:part name=part1 element=null:subscribe/ /wsdl:message wsdl:message name=subscribe wsdl:part name=mtosiHeader element=null:header/ /wsdl:message wsdl:message name=subscribeResponse wsdl:part name=part1 element=null:subscribeResponse/ /wsdl:message wsdl:message name=subscribeResponse wsdl:part name=mtosiHeader element=null:header/ /wsdl:message wsdl:message name=ProcessingFailureException wsdl:part name=part1 element=null:ProcessingFailureException/ ... output from WSDL2Java Retrieving document at 'NotificationServiceSOAP.wsdl', relative to 'file:/D:/Jeromem/Code/testAxis2/ ./wsdl/'. Retrieving document at 'NotificationService.wsdl', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl /NotificationServiceSOAP.wsdl'. Retrieving schema at 'xsd/interfaces/NotificationService.xsd', relative to 'file:/D:/Jeromem/Code/te stAxis2/wsdl/NotificationService.wsdl'. Retrieving schema at '../common/Header.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/i nterfaces/NotificationService.xsd'. Retrieving schema at 'HeaderVendorExtensions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl /xsd/common/Header.xsd'. Retrieving schema at 'Definitions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/common /HeaderVendorExtensions.xsd'. Retrieving schema at '../networkResources/Notifications.xsd', relative to 'file:/D:/Jeromem/Code/tes tAxis2/wsdl/xsd/interfaces/NotificationService.xsd'. Retrieving schema at 'GlobalDefinitions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/ networkResources/Notifications.xsd'. Retrieving schema at '../common/Definitions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/ xsd/networkResources/GlobalDefinitions.xsd'. Retrieving schema at 'VendorExtensions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/n etworkResources/Notifications.xsd'. Retrieving schema at '../common/Definitions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/ xsd/networkResources/VendorExtensions.xsd'. Retrieving schema at 'LayerRates.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/network Resources/Notifications.xsd'. Retrieving schema at '../common/Definitions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/ xsd/networkResources/LayerRates.xsd'. Retrieving schema at 'ProbableCauses.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/net workResources/Notifications.xsd'. Retrieving schema at '../common/Definitions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/ xsd/networkResources/ProbableCauses.xsd'. Retrieving document at 'Exceptions.wsdl', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/Notifica tionService.wsdl'. Retrieving schema at 'xsd/interfaces/Exceptions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/w sdl/Exceptions.wsdl'. Retrieving schema at '../common/Header.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/i nterfaces/Exceptions.xsd'. Retrieving schema at 'VendorExtensions.xsd', relative to 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/i nterfaces/Exceptions.xsd'. Oct 16, 2006 4:05:33 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File src\src\org\tmforum\mtosi\ws\NotificationServiceSkeleton.java will not be overwritten. Oct 16, 2006 4:05:33 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter createOutFile INFO: File src\src\org\tmforum\mtosi\ws\NotificationServiceMessageReceiverInOut.jav a will not be ove rwritten. Oct 16, 2006 4:05:33 PM
RE: SOAP/JMS document
Ali, I understand your point about JMS not being a standard part of the WSDL spec, but since supporting JMS as a transport is a stated goal of the Axis 2 project, and top-down/bottom up web service code generation are the primary use cases for the project, it should support these extensions. This doesn't seem terribly hard--it is almost there as it is--so I can't imagine any major objection to doing so. The Axis 2 code generator doesn't currently do anything with these extensions. But it doesn't throw an exception, either, which is a good start (the message seems to indicate that it was searching for another port, but since I only have one port here, it was not a problem for me). The code generated is pretty much the same as if you were specifying an HTTP transport, but the differences would be small: just need to add a default JMS endpoint and entries to the services.xml. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Friday, October 13, 2006 12:09 AM To: axis-user@ws.apache.org Subject: Re: SOAP/JMS document Hi Brennan, Before asking you, I should have tried but just couldn't wait for it :) As I understand correctly, you are using jms extentions of WSIF[1] which are not part of WSDL spec[2]. Therefore, neither http://schemas.xmlsoap.org/soap/jms namespace nor the jms extentions are available for the all platforms. Does Axis2 do anyting with jms extentions? For example, does wsdl2java handle jms:address and generates a stub which has an jms endpoint[3]? Or do you use jms extentions just to clearly say I'm using JMS, not HTTP? Thanks in advance, Ali Sadik Kumlali [1] http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html [2] http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html quotation WSIF defines extra WSDL extensions that are not part of WSDL4J itself. Amongst others, these WSDL extensions are needed for JMS. ... Currently, these WSDL extensions are valid for Soap over Jms, Axis over Jms and NativeJms. The jms namespace must be xmlns:jms=http://schemas.xmlsoap.org/wsdl/jms/; /quotation [3] String jmsEndpointURL = jms:/ + ACTIONQUEUE // destination + ? + transport.jms.ConnectionFactoryJNDIName= + QueueConnectionFactory + java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFac tory // vendor specific factory + java.naming.provider.url=tibjmsnaming://localhost:7222 // vendor specific provider URL + java.naming.security.principal=Administrator + java.naming.security.credentials=Administrator; - Original Message From: Spies, Brennan [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, October 13, 2006 12:37:03 AM Subject: RE: SOAP/JMS document Kamal, If you are designing starting from WSDL, such as (I am using TIBCO EMS)... wsdl:binding name=ActionSoapJms type=tns:ActionInterface soap:binding style=document transport=http://schemas.xmlsoap.org/soap/jms;; / wsdl:operation name=Action soap:operation soapAction=urn:ejgallo:workflow:service:action/Action / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output wsdl:fault name=Error soap:fault name=Error use=literal/ /wsdl:fault /wsdl:operation /wsdl:binding wsdl:service name=ActionMessageService wsdl:port name=ActionSoapJmsPort binding=tns:ActionSoapJms jms:address destinationStyle=queue messageType=text jndiProviderURL=tibjmsnaming://localhost:7222 initialContextFactory=com.tibco.tibjms.naming.TibjmsInitialContextFactory jndiConnectionFactoryName=QueueConnectionFactory jndiDestinationName=ACTIONQUEUE jms:propertyValue name=userid value=user/ jms:propertyValue name=password value=password/ /jms:address /wsdl:port /wsdl:service (...where the ns 'jms' is http://schemas.xmlsoap.org/wsdl/jms/) ...the WSDL2Java code generator will handle it fine. I do get the message [codegen] INFO: A SOAP port was not found - picking a random port! in my Ant build, but the generated code looks pretty close (It's basically the same as the HTTP transport equivalent, except there is no default URL specified in the ActionMessageServiceStub constructor. Would be nice if it put some of my jms:address info into my services.xml, but hey, I'm not going to push it (grin)). All you need to do from here is configure your axis2.xml and services.xml correctly as per the doc below, and it should work for you. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Davanum Srinivas [mailto
RE: SOAP/JMS document
Done. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, October 13, 2006 10:03 AM To: axis-user@ws.apache.org Subject: Re: SOAP/JMS document Is it the same as this? http://issues.apache.org/jira/browse/AXIS2-545 If it is then, please add your feedback there. -- dims On 10/13/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Brennan, Please open an enhancement request in JIRA with your example/sample. thanks, dims On 10/13/06, Spies, Brennan [EMAIL PROTECTED] wrote: Ali, I understand your point about JMS not being a standard part of the WSDL spec, but since supporting JMS as a transport is a stated goal of the Axis 2 project, and top-down/bottom up web service code generation are the primary use cases for the project, it should support these extensions. This doesn't seem terribly hard--it is almost there as it is--so I can't imagine any major objection to doing so. The Axis 2 code generator doesn't currently do anything with these extensions. But it doesn't throw an exception, either, which is a good start (the message seems to indicate that it was searching for another port, but since I only have one port here, it was not a problem for me). The code generated is pretty much the same as if you were specifying an HTTP transport, but the differences would be small: just need to add a default JMS endpoint and entries to the services.xml. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Friday, October 13, 2006 12:09 AM To: axis-user@ws.apache.org Subject: Re: SOAP/JMS document Hi Brennan, Before asking you, I should have tried but just couldn't wait for it :) As I understand correctly, you are using jms extentions of WSIF[1] which are not part of WSDL spec[2]. Therefore, neither http://schemas.xmlsoap.org/soap/jms namespace nor the jms extentions are available for the all platforms. Does Axis2 do anyting with jms extentions? For example, does wsdl2java handle jms:address and generates a stub which has an jms endpoint[3]? Or do you use jms extentions just to clearly say I'm using JMS, not HTTP? Thanks in advance, Ali Sadik Kumlali [1] http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html [2] http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html quotation WSIF defines extra WSDL extensions that are not part of WSDL4J itself. Amongst others, these WSDL extensions are needed for JMS. ... Currently, these WSDL extensions are valid for Soap over Jms, Axis over Jms and NativeJms. The jms namespace must be xmlns:jms=http://schemas.xmlsoap.org/wsdl/jms/; /quotation [3] String jmsEndpointURL = jms:/ + ACTIONQUEUE // destination + ? + transport.jms.ConnectionFactoryJNDIName= + QueueConnectionFactory + java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFac tory // vendor specific factory + java.naming.provider.url=tibjmsnaming://localhost:7222 // vendor specific provider URL + java.naming.security.principal=Administrator + java.naming.security.credentials=Administrator; - Original Message From: Spies, Brennan [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Friday, October 13, 2006 12:37:03 AM Subject: RE: SOAP/JMS document Kamal, If you are designing starting from WSDL, such as (I am using TIBCO EMS)... wsdl:binding name=ActionSoapJms type=tns:ActionInterface soap:binding style=document transport=http://schemas.xmlsoap.org/soap/jms;; / wsdl:operation name=Action soap:operation soapAction=urn:ejgallo:workflow:service:action/Action / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output wsdl:fault name=Error soap:fault name=Error use=literal/ /wsdl:fault /wsdl:operation /wsdl:binding wsdl:service name=ActionMessageService wsdl:port name=ActionSoapJmsPort binding=tns:ActionSoapJms jms:address destinationStyle=queue messageType=text jndiProviderURL=tibjmsnaming://localhost:7222 initialContextFactory=com.tibco.tibjms.naming.TibjmsInitialContextFactory jndiConnectionFactoryName=QueueConnectionFactory jndiDestinationName=ACTIONQUEUE jms:propertyValue name=userid value=user/ jms:propertyValue name=password value=password/ /jms:address /wsdl:port /wsdl:service (...where the ns 'jms
RE: Documentation for Java2WSDLTask
1. do a taskdef for org.apache.ws.java2wsdl.Java2WSDLTask 2. since in a custom Ant task, your XML attributes are represented by class properties, you have private String className; private String outputLocation; private String classpathURI; private String targetNamespace; private String targetNamespacePrefix; private String schemaTargetNamespace; private String schemaTargetNamespacePrefix; private String serviceName; private String outputFileName; these should parallel the command-line options. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft Sent: Thursday, October 12, 2006 11:47 AM To: Axis Users Subject: Re: Documentation for Java2WSDLTask I should clarify thisI'm trying to use the Ant task, not the command line. -dan On 10/12/06, D. Kreft [EMAIL PROTECTED] wrote: Is there any documentation yet on how to use Java2WSDLTask? There are a bunch of new attributes to this task that I'm not familiar with. The javadocs for the class of the same name are, of course, no help--they assume I know what I'm doing. :-) -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SOAP/JMS document
Kamal, If you are designing starting from WSDL, such as (I am using TIBCO EMS)... wsdl:binding name=ActionSoapJms type=tns:ActionInterface soap:binding style=document transport=http://schemas.xmlsoap.org/soap/jms; / wsdl:operation name=Action soap:operation soapAction=urn:ejgallo:workflow:service:action/Action / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output wsdl:fault name=Error soap:fault name=Error use=literal/ /wsdl:fault /wsdl:operation /wsdl:binding wsdl:service name=ActionMessageService wsdl:port name=ActionSoapJmsPort binding=tns:ActionSoapJms jms:address destinationStyle=queue messageType=text jndiProviderURL=tibjmsnaming://localhost:7222 initialContextFactory=com.tibco.tibjms.naming.TibjmsInitialContextFactory jndiConnectionFactoryName=QueueConnectionFactory jndiDestinationName=ACTIONQUEUE jms:propertyValue name=userid value=user/ jms:propertyValue name=password value=password/ /jms:address /wsdl:port /wsdl:service (...where the ns 'jms' is http://schemas.xmlsoap.org/wsdl/jms/) ...the WSDL2Java code generator will handle it fine. I do get the message [codegen] INFO: A SOAP port was not found - picking a random port! in my Ant build, but the generated code looks pretty close (It's basically the same as the HTTP transport equivalent, except there is no default URL specified in the ActionMessageServiceStub constructor. Would be nice if it put some of my jms:address info into my services.xml, but hey, I'm not going to push it (grin)). All you need to do from here is configure your axis2.xml and services.xml correctly as per the doc below, and it should work for you. Brennan Spies Sr. Programmer Analyst Shared Application Services -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Thursday, October 12, 2006 1:30 PM To: axis-user@ws.apache.org Subject: Re: SOAP/JMS document http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1 /jms-transport.html On 10/12/06, Kang, Kamaljeet K. [EMAIL PROTECTED] wrote: Hi, Is there a document regarding SOAP over JMS with Axis2? Thanks kamal The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Support for polymorphism in a service
No, that's WSDL 2.0, where it is replaced by Interface...
www.w3.org/2002/ws/desc/wsdl20-primer
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft
Sent: Wednesday, October 11, 2006 1:40 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: Support for polymorphism in a service
But wasn't the notion of portType supposed to be nixed in WSDL 1.1?
-dan
On 10/11/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Please see:
http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Distinctive_Ope
rations
thanks,
-- dims
On 10/11/06, D. Kreft [EMAIL PROTECTED] wrote:
I'm writing a service that I'm trying to integrate into a legacy
system bit by bit. In the old system, a request ID is a String of
the format rqMMDDHHMMSSXXX, but in the new system, a request ID
is simply a row identifier (a Long).
What I'd like to do is use the power of polymorphism to keep my
service API clean and sane:
public Request getRequestByID(String legacyRequestID) {
// ...
}
public Request getRequestByID(Long requestID) {
// ...
}
But when I try this, java2wsdl (Axis1) pukes with the following fault:
Attempted to write duplicate schema element :
{http://pkgbuild.amazon.com/PBQS}getRequestByID
...which makes me sad. :-( -- See?
Is this a WSDL 1.0 restriction or a deficiency in java2wsdl? Will such
use of polymorphism be possible under Axis2?
-dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Installing axis2 into Tomcat
Yadav, The welcome page for Axis2 should be on the welcome-file-list in the web.xml. If you go to http://localhost:8080/axis2/, it should direct you to the /axis2-web/index.jsp page. -Original Message- From: Yadav, Yogendra (IT) [mailto:[EMAIL PROTECTED] Sent: Friday, September 29, 2006 12:34 PM To: axis-user@ws.apache.org Subject: Installing axis2 into Tomcat I have installed tomcat 5.5.17. I am facing various problems with it: 1. Tomcat Administration link shows Admin Tool login page, but none of the logins given in C:\software\apache-tomcat-5.5.17\conf\tomcat-users.xml work. 2. Tomcat Manager link throws a userid/password challenge box what would be login id and password ? 3. I copied axis2.war in C:\software\apache-tomcat-5.5.17\server\webapps and restarted Tomcat. When I try to access Axis2 like this http://localhost:8080/axis2/services/, I get 404 error page. any help would be appreciated -yogen NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Faults as inner classes
Title: Proxy Ive noticed when you define a fault for your operation, the Axis code generator (using Xmlbeans databinding) creates the faults as inner classes. On the server side, as an inner class in the interface itself (because I chose ssi) and on the client side as an identical (code-wise) inner class. Seems like a curious decision. Is there a reason why these are not simply generated as top-level classes?
RE: Axis2: simple service fails to work
Dan, What Dims and Robert forgot to mention is that Axis 2.0 is really a major rewrite of the SOAP stack (hence the split of URLs, one for Axis 1 and one for Axis 2). So the same growing pains apply here as with any new project. Not that I don't feel your pain--I have been there many times before, trust me--but I can also remember a time when free software was not in such abundance. Given the excellent price of the software, it may be worthwhile to stick it out with the nightlies until version 1.1 is released (which I believe is at the end of this month, more or less). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft Sent: Monday, September 25, 2006 1:37 PM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: Axis2: simple service fails to work On 9/25/06, Davanum Srinivas [EMAIL PROTECTED] wrote: JIRA Please. Can i assume you are trying the nightly? No, I'm not using the nightly. I'm using the last good release--1.0 because I'm trying to develop a *production* application for my employer, and the thought of having core business functionality running on a nightly release of third-party software quite frankly is not a sane development practice--there is too much money on the line here. I think at this point, I'm going to have to complete give up on using Axis2. I and another developer I work with have had a number of difficulties with Axis 1.4, none of which I'll bother to go into here, but suffice to say that when we saw that Axis2 had finally reached version 1.0 (out of Beta we thought), we were optimistic that the revised Axis would obviate the need for some of the hacks we have in place to overcome some of Axis's quirks. So I got my manager's blessing to see what it takes to take the humble beginnings of my new service (already mostly functional in Axis 1.4) and make it work in Axis2. I was hoping it'd be a fairly straightforward deal, but after working on it for five solid days, I have nothing more to show for my hard work than a handful e-mails to this list, three subsequent requests for me to file JIRAs, and a crippled service. Did I misinterpret the major-number version bump? Is Axis2 really not out of Beta yet? Because if it *is* supposed to be out of Beta at this stage, then I cannot help but be profoundly disappointedthe documentation is very sparse, often times irrelevant, sometimes contradictory, counter-intuitive, and not terribly clear when it can be found (I actually found more information in artciles *about* Axis2 than I did from the actual Axis2 website). If it's still considered Beta then that needs to be *clearly* and prominently documented on the Axis2 website. But documentation woes aside, what really disappoints me is that it doesn't look as if anyone tested the seemingly simple case where the developer writes a service implementation class, let Axis2 divine its own WSDL from it, and have at least one of the methods return a simple object. Axis2 seems to have no problems returning simple data types (ints, Strings, primitive arrays of strings, etc.), but as soon as an object is returned, all Hades breaks loose. And now, writing a brain-dead simple service fails and I have to file a bug report for that! So now I've lost a full week of productivity (and a few handfuls of hair)...all because I naively thought that version 1.0 meant Okay, we're ready for the real world. It obviously isn't, and I can't help but think that someone got a little trigger-happy in promoting Axis2 to version 1.0. In my humble estimation, it could have used a bit more time baking in Beta (i.e. with a 0.x version number). If I had any idea that Axis was still so raw, I wouldn't have wasted a 40-hour work week on trying to get it to work...or the couple of hours I've spent this morning trying to come up with a simple example of Axis2 puking when an object is returned from a service method. I don't doubt that the Axis2 developers are working very hard to get all these issues resolved, but for goodness sake...you can't release a product as version 1.0--which implies a non-Beta, stable release--when the new product lacks much of the basic functionality that people are going to need and that they are used to having provided for them by the previous release (Axis 1.x). -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CodeGeneration error while using commandline batch file WSDL2Java
Darn, this delegation thing never works for me... ;) Will do. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 6:25 PM To: axis-user@ws.apache.org Subject: Re: CodeGeneration error while using commandline batch file WSDL2Java Brennan, Please file a JIRA bug with *your* wsdl :) -- dims On 9/20/06, Spies, Brennan [EMAIL PROTECTED] wrote: Sharad, This is definitely a bug (I can reproduce using similar WSDL on the latest nightly). It throws a RuntimeException complaining that Element QName is null for [/message/name/text()]! You should file a JIRA issue on this: https://issues.apache.org/jira/browse/AXIS2. -Original Message- From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 5:32 PM To: axis-user@ws.apache.org Subject: RE: CodeGeneration error while using commandline batch file WSDL2Java Hi, After removed the Fault Exception, and then it generates the classes. But it doesn't generate classes for each operation, and classes for input, output of an operation. I thing I am missing something. ! It misses the objective of code generation. Can anyone help me /Sharad From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 4:40 PM To: axis-user@ws.apache.org Subject: RE: CodeGeneration error while using commandline batch file WSDL2Java Hi All, Sorry for causing confusion in my previous. This is my first to email to this user group. I am using Axis2 nightly build (Sept-20) When using WSDL2Java, it generates runtime error : java.lang.RuntimeExcept ion: Element QName is null for CorporateActionExceptionFault [wsdl:message name=CorporateActionExceptionFault wsdl:part name=fault type=tns:CorporateActionException/ /wsdl:message]. I have attached wsdl file in my previous email. /Sharad From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 4:13 PM To: axis-user@ws.apache.org Subject: CodeGeneration error while using commandline batch file WSDL2Java Hi, I was using Axis2 1.0 WS2DL2Java was working fine, but I was getting some runtime error. So I decided to download nightly build which is giving me runtime error. I have attached the wsdl file for reference. Help need!! Thanks, /Sharad C:\apache\axis2v1night\binwsdl2Java -uri c:\ test1\corporateaction.wsdl -o c:\test1 -l java -a -s -t -ss -sd -g -u -ssi Using AXIS2_HOME: C:\apache\axis2v1night Using JAVA_HOME:C:\j2sdk1.4.2_12 Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeExcept ion: Element QName is null for CorporateActionExceptionFault! at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.Runt imeException: Element QName is null for CorporateActionExceptionFault! at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:206) ... 2 more Caused by: java.lang.RuntimeException: Element QName is null for CorporateAction ExceptionFault! at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmit ter .java:1352) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:733) ... 3 more ___ All outbound Email is scanned by Nexa Technologies Email Security Systems
RE: CodeGeneration error while using commandline batch file WSDL2Java
My mistake... Sharad, your WSDL is probably missing a fault nested in your binding...hence Axis is complaining about it. Look at the example here: http://www.gridlab.org/WorkPackages/wp-5/guide/faults.html -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 6:25 PM To: axis-user@ws.apache.org Subject: Re: CodeGeneration error while using commandline batch file WSDL2Java Brennan, Please file a JIRA bug with *your* wsdl :) -- dims On 9/20/06, Spies, Brennan [EMAIL PROTECTED] wrote: Sharad, This is definitely a bug (I can reproduce using similar WSDL on the latest nightly). It throws a RuntimeException complaining that Element QName is null for [/message/name/text()]! You should file a JIRA issue on this: https://issues.apache.org/jira/browse/AXIS2. -Original Message- From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 5:32 PM To: axis-user@ws.apache.org Subject: RE: CodeGeneration error while using commandline batch file WSDL2Java Hi, After removed the Fault Exception, and then it generates the classes. But it doesn't generate classes for each operation, and classes for input, output of an operation. I thing I am missing something. ! It misses the objective of code generation. Can anyone help me /Sharad From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 4:40 PM To: axis-user@ws.apache.org Subject: RE: CodeGeneration error while using commandline batch file WSDL2Java Hi All, Sorry for causing confusion in my previous. This is my first to email to this user group. I am using Axis2 nightly build (Sept-20) When using WSDL2Java, it generates runtime error : java.lang.RuntimeExcept ion: Element QName is null for CorporateActionExceptionFault [wsdl:message name=CorporateActionExceptionFault wsdl:part name=fault type=tns:CorporateActionException/ /wsdl:message]. I have attached wsdl file in my previous email. /Sharad From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 4:13 PM To: axis-user@ws.apache.org Subject: CodeGeneration error while using commandline batch file WSDL2Java Hi, I was using Axis2 1.0 WS2DL2Java was working fine, but I was getting some runtime error. So I decided to download nightly build which is giving me runtime error. I have attached the wsdl file for reference. Help need!! Thanks, /Sharad C:\apache\axis2v1night\binwsdl2Java -uri c:\ test1\corporateaction.wsdl -o c:\test1 -l java -a -s -t -ss -sd -g -u -ssi Using AXIS2_HOME: C:\apache\axis2v1night Using JAVA_HOME:C:\j2sdk1.4.2_12 Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeExcept ion: Element QName is null for CorporateActionExceptionFault! at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.Runt imeException: Element QName is null for CorporateActionExceptionFault! at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:206) ... 2 more Caused by: java.lang.RuntimeException: Element QName is null for CorporateAction ExceptionFault! at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmit ter .java:1352) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:733) ... 3 more ___ All outbound Email is scanned by Nexa
RE: CodeGeneration error while using commandline batch file WSDL2Java
Sharad,
You are using RPC/encoded style, which is not supported by Axis 2.0 (not WS-I
compliant). Given your schema, it doesn't really make any sense, either.
Doc/literal would be more appropriate.
-Original Message-
From: Sharad Baronia [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006 10:53 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: CodeGeneration error while using commandline batch file
WSDL2Java
Hi,
I have attached new wsdl file, which is validated with XMLSPY. Still
WSDL2Java gives error. Any thoughs!!
C:\apache\axis2v1night\binwsdl2Java -uri
D:\sbaronia\workspace\test\corporateac
tion.wsdl -o c:\test1 -l java -d adb -a -s -t -ss -sd -g -u -ssi
Using AXIS2_HOME: C:\apache\axis2v1night
Using JAVA_HOME:C:\j2sdk1.4.2_12
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolAndExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolAndExDate
Resp
onse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndExDateResponse'
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException
: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeExcept
ion: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.Runt
imeException: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:206)
... 2 more
Caused by: java.lang.RuntimeException: Element QName is null for
CorporateAction
ExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmi
tter
.java:1352)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:733)
... 3 more
Thanks,
/Sharad
-Original Message-
From: Spies, Brennan [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006 8:54 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: CodeGeneration error while using commandline batch file
WSDL2Java
Darn, this delegation thing never works for me... ;)
Will do.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 6:25 PM
To: axis-user@ws.apache.org
Subject: Re: CodeGeneration error while using commandline batch file
WSDL2Java
Brennan,
Please file a JIRA bug with *your* wsdl :)
-- dims
On 9/20/06, Spies, Brennan [EMAIL
Missing jar
I got an error when trying to upload a service to the Axis2 web application: Caused by: java.lang.NoClassDefFoundError: org/apache/commons/io/output/DeferredFileOutputStream It was easily fixed by adding commons-io-1.2.jar to the WEB-INF/lib. You may want to include this jar in the nightly build war file. FYI. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problem when running wsdl2java with axis2
Yes, it is. When running the ant code generation task, you should see debugging output as it locates each XSD file. You should be using a recent nightly build, as there were some issues with this in the 1.0 release of Axis 2. -Original Message- From: Felix Sprick [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 12:10 AM To: axis-user@ws.apache.org Subject: SV: problem when running wsdl2java with axis2 Hi all, Do you guys know if it is allowed to have several XSDs with the same targetNamespace? The XSDs I am using include each other with include schemaLocation=otherXSD.xsd where both schemas are in the same targetNamespace. Might that cause my element not found exceptions? Thanks, Felix Från: Felix Sprick [mailto:[EMAIL PROTECTED] Skickat: den 19 september 2006 16:56 Till: axis-user@ws.apache.org; 'Martin Gainty' Ämne: SV: problem when running wsdl2java with axis2 Hi Martin, Thanks a lot for your answer. I am not sure where to locate local/Schemas/Byggnader.xsd, is that kind of a temp directory? I can, however, attach the original Byggnader.xsd file, if that is of any help for you. Since I am not sure whether this mailing list allows attachments, I have put all my xsds in a zip file at http://www.oktylus.com/WSDL.rar. Thanks again, Felix Från: Martin Gainty [mailto:[EMAIL PROTECTED] Skickat: den 19 september 2006 16:21 Till: axis-user@ws.apache.org Ämne: Re: problem when running wsdl2java with axis2 Felix- the specific error seems to be located at local/Schemas/Byggnader.xsd:2:1069: (If you could show us the relevant element contents of the file we could assist you) Sverige Altid- M- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Felix Sprick To: axis-user@ws.apache.org Sent: Tuesday, September 19, 2006 9:33 AM Subject: SV: problem when running wsdl2java with axis2 Hi again, I have now successfully generated the XMLbeans for my xds file outside of the AXIS2 wsdl2java command by using scomp. Does anybody know a convenient way to include those manually built xmlbeans when invoking the wsdl2java (since I get the error-message below when running wsdl2java with xmlbeans binding!)? Thanks, Felix Från: Felix Sprick [mailto:[EMAIL PROTECTED] Skickat: den 19 september 2006 09:57 Till: axis-user@ws.apache.org Ämne: problem when running wsdl2java with axis2 Hi all, I am using the wsdl2java tool of the nightly-build from the 14th of September. I experience strange errors when trying to compile the wsdl file: element seemed to be not found, which are definitely defined in the xsd here is the error message: Z:\SGIS\WSDLc:\Program\Apache\axis2-nightly-20060914\bin\WSDL2Java -uri baggis. wsdl -pn PortalSoap -ss -sd -d xmlbeans -o .. -g Using AXIS2_HOME: C:\Program\Apache\axis2 Using JAVA_HOME: C:\Program\Java\jdk1.5.0_06 Retrieving schema at 'Schemas/PortalInterface.xsd', relative to 'file:/Z:/SGIS/W SDL/'. Retrieving schema at 'Brunnar.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/Port alInterface.xsd'. Retrieving schema at 'MessageTag.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/B runnar.xsd'. Retrieving schema at 'Byggnader.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/Po rtalInterface.xsd'. Retrieving schema at 'MessageTag.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/B yggnader.xsd'. Retrieving schema at 'OpenGis/gml/3.1.1/base/geometryBasic0d1d.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/Byggnader.xsd'. Retrieving schema at 'measures.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/Ope nGis/gml/3.1.1/base/geometryBasic0d1d.xsd'. Retrieving schema at 'units.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/OpenGi s/gml/3.1.1/base/measures.xsd'. Retrieving schema at 'dictionary.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/O penGis/gml/3.1.1/base/units.xsd'. Retrieving schema at 'gmlBase.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/Open Gis/gml/3.1.1/base/dictionary.xsd'. Retrieving schema at '../../../xlink/1.0.0/xlinks.xsd', relative to 'file:/Z:/SG IS/WSDL/Schemas/OpenGis/gml/3.1.1/base/gmlBase.xsd'. Retrieving schema at 'basicTypes.xsd', relative to 'file:/Z:/SGIS/WSDL/Schemas/O penGis/gml/3.1.1/base/gmlBase.xsd'. Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:185) at
RE: [Spam] Re: classpath
Fabio, Caused by: java.lang.ClassNotFoundException: org.apache.axis2.databinding.types.Time--this class is in the axis2-adb-SNAPSHOT.jar. -Original Message- From: Fabio Alves de Araujo Ebner - DNA Solution [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 9:28 AM To: axis-user@ws.apache.org; Martin Gainty Subject: Re: [Spam] Re: classpath ok.. i put but all there but she still return the error: C:\exemplo1java org.apache.axis2.wsdl.WSDL2Java -uri http://localhost:8080/axis 2/services/VerificaLogin?wsdl -p br.com.dnasolution log4j:WARN No appenders could be found for logger (org.apache.axis2.i18n.Project ResourceBundle). log4j:WARN Please initialize the log4j system properly. Exception in thread main java.lang.NoClassDefFoundError at org.apache.axis2.schema.typemap.JavaTypeMap.class$(JavaTypeMap.java:7 1) at org.apache.axis2.schema.typemap.JavaTypeMap.clinit(JavaTypeMap.java :99) at org.apache.axis2.schema.writer.JavaBeanWriter.init(JavaBeanWriter.j ava:78) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou rce) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.axis2.schema.util.SchemaPropertyLoader.clinit(SchemaProp ertyLoader.java:42) at org.apache.axis2.schema.SchemaCompiler.init(SchemaCompiler.java:159 ) at org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp leDBExtension.java:68) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:140) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.ClassNotFoundException: org.apache.axis2.databinding.types. Time at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) ... 15 more - Original Message - From: Martin Gainty [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, September 20, 2006 1:20 PM Subject: Re: [Spam] Re: classpath whenever you call your PrettyPrint routines in Jalopy you will need Log4J*.jar ON YOUR CLASSPATH and because Log4j reads Log4j.properties to initialise itself you will need Log4j.properties ON YOUR CLASSPATH the proper configuration of which is the developer's responsibility (ie.you need to properly configure the properties file) M- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: Fabio Alves de Araujo Ebner - DNA Solution [EMAIL PROTECTED] To: axis-user@ws.apache.org; Martin Gainty [EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 11:47 AM Subject: Re: [Spam] Re: classpath i remove the %AXIS2_LIB%\log4j-1.2.13.jar; and got that erro: C:\exemplo1java org.apache.axis2.wsdl.WSDL2Java -uri http://localhost:8080/axis 2/services/VerificaLogin?wsdl -p br.com Exception in thread main java.lang.NoClassDefFoundError at org.apache.axis2.schema.typemap.JavaTypeMap.class$(JavaTypeMap.java:7 1) at org.apache.axis2.schema.typemap.JavaTypeMap.clinit(JavaTypeMap.java :99) at org.apache.axis2.schema.writer.JavaBeanWriter.init(JavaBeanWriter.j ava:78) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou rce) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.axis2.schema.util.SchemaPropertyLoader.clinit(SchemaProp ertyLoader.java:42) at org.apache.axis2.schema.SchemaCompiler.init(SchemaCompiler.java:159 ) at
RE: [Axis2] Using 'type' attribute for the message part
Anne, I had a feeling that @type was a leftover from RPC/encoded style, but was looking in the wrong place for the answer. Thanks! Brennan -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 9:48 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Using 'type' attribute for the message part Brennan, The semantics of type vs element in wsdl:part is defined in the WS-I Basic Profile, Section 4.4.1 [1]. You must use @type when using RPC style; you must use @element when using document style. With document style, you specify the literal schema of the element contained in the SOAP Body; therefore, the message may contain at most one body part, and that part must reference an element definition. It must not reference a type definition. With RPC style, you specify the types of the parameters that must be passed in the SOAP Body, but not the literal schema. The message definition must contain a part for each parameter, and those parts must reference a type definition. At runtime, the SOAP engine is responsible for dynamically constructing the element contained in the SOAP Body as follows: - It generates a wrapper element that has the same local name as the operation, and which is qualified by the namespace specified in the soap:body definition in the binding. This wrapper element has no formally specified type or schema. - It generates an accessor element for each parameter. The accessor elements are non-qualified, and they get their local name from the @name in the wsdl:part. The type of each accessor element is the type specified in the WSDL part definition. For example, if you have: wsdl:message name=opRequest wsdl:part name=param1 type=xsd:string/ wsdl:part name=param2 type=xsd:string/ /wsdl:message ... wsdl:binding ... soap:binding style=rpc ... wsdl:operation name=op ... wsdl:input soap:body use=literal namespace=urn:example:rpc/ /wsdl:input ... /wsdl:operation /wsdl:binding The message on the wire would look like: soap:Body ns1:op xmlns:ns1=urn:example:rpc param1some string/param1 param2some string/param2 /ns1:op /soap:Body [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts On 9/18/06, Spies, Brennan [EMAIL PROTECTED] wrote: Yes, I am using the most recent nightly build. The input and output is Doc/literal... wsdl:binding name=ActionSoapHttp type=tns:ActionInterface soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=Action soap:operation soapAction=urn:ejgallo:workflow:service:action/Action / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding I can file a bug (no problem) since it's clear the lack of a return doc is a bug, but I also wanted to know what is meant when a 'type' is specified in the WSDL, i.e., what SHOULD be the result of such a configuration in terms of what is generated in the SOAP, and more specifically to Axis2, the generated classes? Brennan -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Monday, September 18, 2006 11:42 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: [Axis2] Using 'type' attribute for the message part Hi, What kind of binding do you have ? Ajith On 9/18/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Are u using the nightly build? If so, please open a issue/bug. thanks, dims On 9/18/06, Spies, Brennan [EMAIL PROTECTED] wrote: Axis devs, Got a question regarding the use of types for message parts rather than elements...specifically, what are the semantics of it? Reading the WSDL spec does not clarify this for me. For example, suppose you have an output message defined as message name=Response part name=output type=ns:responseType/ /message Using the Axis code generator with XMLBeans databinding, the ResponseType class will be generated, but there is no corresponding *Document class. Also, the methods in the generated code look more like an IN ONLY MEP rather than IN-OUT--i.e., the skeleton has no return value, hence no meaningful SOAP response is generated. Brennan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail
RE: display the xml content of a SOAP request
The getText() here just get the child text node(s) as a string. You want to use one of the serialize() methods. If you're looking to debug soap, TCPMon (http://ws.apache.org/commons/tcpmon/ ) might be an easier option. -Original Message- From: Z Chen [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 3:01 PM To: axis-user@ws.apache.org Subject: display the xml content of a SOAP request Hi, Suppose I have SOAPEnvelop, how to display the XML content of the SOAP request ? is it getBody().getText() ? Somehow I got an empty string back. Thanks John __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CodeGeneration error while using commandline batch file WSDL2Java
Sharad, This is definitely a bug (I can reproduce using similar WSDL on the latest nightly). It throws a RuntimeException complaining that Element QName is null for [/message/name/text()]! You should file a JIRA issue on this: https://issues.apache.org/jira/browse/AXIS2. -Original Message- From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 5:32 PM To: axis-user@ws.apache.org Subject: RE: CodeGeneration error while using commandline batch file WSDL2Java Hi, After removed the Fault Exception, and then it generates the classes. But it doesnt generate classes for each operation, and classes for input, output of an operation. I thing I am missing something. ! It misses the objective of code generation. Can anyone help me. /Sharad From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 4:40 PM To: axis-user@ws.apache.org Subject: RE: CodeGeneration error while using commandline batch file WSDL2Java Hi All, Sorry for causing confusion in my previous. This is my first to email to this user group. I am using Axis2 nightly build (Sept-20) When using WSDL2Java, it generates runtime error : java.lang.RuntimeExcept ion: Element QName is null for CorporateActionExceptionFault [wsdl:message name=CorporateActionExceptionFault wsdl:part name=fault type=tns:CorporateActionException/ /wsdl:message]. I have attached wsdl file in my previous email. /Sharad From: Sharad Baronia [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 4:13 PM To: axis-user@ws.apache.org Subject: CodeGeneration error while using commandline batch file WSDL2Java Hi, I was using Axis2 1.0 WS2DL2Java was working fine, but I was getting some runtime error. So I decided to download nightly build which is giving me runtime error. I have attached the wsdl file for reference. Help need!! Thanks, /Sharad C:\apache\axis2v1night\binwsdl2Java -uri c:\ test1\corporateaction.wsdl -o c:\test1 -l java -a -s -t -ss -sd -g -u -ssi Using AXIS2_HOME: C:\apache\axis2v1night Using JAVA_HOME: C:\j2sdk1.4.2_12 Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeExcept ion: Element QName is null for CorporateActionExceptionFault! at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.Runt imeException: Element QName is null for CorporateActionExceptionFault! at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:206) ... 2 more Caused by: java.lang.RuntimeException: Element QName is null for CorporateAction ExceptionFault! at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmitter .java:1352) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297) at org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:733) ... 3 more ___ All outbound Email is scanned by Nexa Technologies Email Security Systems. ___ ___ Inbound Email has been scanned by Nexa Technologies Email Security Systems. ___ ___ All outbound Email is scanned by Nexa Technologies Email Security Systems. ___ ___ Inbound Email has been scanned by Nexa Technologies Email Security Systems. ___
RE: [Axis2] Using 'type' attribute for the message part
The issue is here: https://issues.apache.org/jira/browse/AXIS2-1185 -Original Message- From: Spies, Brennan Sent: Monday, September 18, 2006 11:49 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: RE: [Axis2] Using 'type' attribute for the message part Yes, I am using the most recent nightly build. The input and output is Doc/literal... wsdl:binding name=ActionSoapHttp type=tns:ActionInterface soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=Action soap:operation soapAction=urn:ejgallo:workflow:service:action/Action / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding I can file a bug (no problem) since it's clear the lack of a return doc is a bug, but I also wanted to know what is meant when a 'type' is specified in the WSDL, i.e., what SHOULD be the result of such a configuration in terms of what is generated in the SOAP, and more specifically to Axis2, the generated classes? Brennan -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Monday, September 18, 2006 11:42 AM To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: [Axis2] Using 'type' attribute for the message part Hi, What kind of binding do you have ? Ajith On 9/18/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Are u using the nightly build? If so, please open a issue/bug. thanks, dims On 9/18/06, Spies, Brennan [EMAIL PROTECTED] wrote: Axis devs, Got a question regarding the use of types for message parts rather than elements...specifically, what are the semantics of it? Reading the WSDL spec does not clarify this for me. For example, suppose you have an output message defined as message name=Response part name=output type=ns:responseType/ /message Using the Axis code generator with XMLBeans databinding, the ResponseType class will be generated, but there is no corresponding *Document class. Also, the methods in the generated code look more like an IN ONLY MEP rather than IN-OUT--i.e., the skeleton has no return value, hence no meaningful SOAP response is generated. Brennan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 import xsd into WSDL and generator WSDL2Java
Are you using the import inside the types section of your WSDL (i.e., is it the xsd:import rather than the wsdl:import)? -Original Message- From: Sergey GMAIL [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 7:07 AM To: axis-user@ws.apache.org Subject: Axis2 import xsd into WSDL and generator WSDL2Java Hello, axis-user. I have a problem, as correctly to import *.xsd chart in WSDL and then correctly using a WSDL2Java generate code ? My code: WSDL: definitions name=CalculatorsService targetNamespace=http://com/nuance/pws/middleware/beans/calculator; . xmlns:tns1=http://com/nuance/pws/middleware/beans/calculator/schemas; import namespace=http://com/nuance/pws/middleware/beans/calculator/schemas; location=http://com/nuance/pws/middleware/beans/calculator/Calculator_new.xs d/ message name=requestHeader part name=requestHeader element=tns1:TradePriceRequest/ /message XSD: ?xml version=1.0? schema targetNamespace=http://com/nuance/pws/middleware/beans/calculator/schemas; xmlns=http://www.w3.org/2000/10/XMLSchema; element name=TradePriceRequest complexType all element name=tickerSymbol type=string/ /all /complexType /element ... doesn't work :( How do correct wsdl? Thanks. -- WBR, Sergey mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 and Soap Header and Skeleton
You'll have to change your method signature to pass in the appropriate parameter(s), then change the call in your *MessageReceiver* class invokeBusinessLogic() method to pass these in. To get a reference to your element, you need to get the appropriate OMElement from your incoming MessageContext, which is the first child of your SOAP body: messageContext.getEnvelope().getBody()...etc. If you are not using recent nightly builds, I suggest doing so because of lot of the code handling this has been improved in the last week or so. -Original Message- From: Sergey GMAIL [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 9:10 AM To: axis-user@ws.apache.org Subject: Axis2 and Soap Header and Skeleton Hello! I have the next wsdl: .. message name=requestHeader part name=requestHeader element=ns2:loginContext/ /message message name=responseHeader part name=responseHeader element=ns2:loginContext/ /message operation name=add input soap:header message=tns:requestHeader part=requestHeader use=literal/ soap:body use=literal/soap:body /input output soap:header message=tns:responseHeader part=responseHeader use=literal/ soap:body use=literal/soap:body /output /operation .. After generation, using WSDL2Java from Axis2 I get code which have loginContext in the client Stub class and in the server MessageReceiverInOut class. How get loginContext in the Skeleton? -- WBR, Sergey mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Access Addressing information
messageContext.getEnvelope().getHeader(); -Original Message- From: Punnoose, Roshan [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 12, 2006 7:01 AM To: axis-user@ws.apache.org Subject: Access Addressing information When I create a web service with WS-Addressing handlers, how do I have access to the addressing information located in the soap header, in my web service? I want to be able to manipulate and use the wsa:messageId tag. Roshan Punnoose Phone: 301-497-6039 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Purpose of resource files generated with Xmlbeans databinding
Is there a way to generate these manually, since I am currently having a problem with not all of my schemas being generated as XmlBeans classes (https://issues.apache.org/jira/browse/AXIS2-1116)? -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 06, 2006 11:22 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Purpose of resource files generated with Xmlbeans databinding Hi, These are needed for the XMLBeans runtime and should be included in the classpath for the XMLBeans classes to work Ajith On 9/6/06, Spies, Brennan [EMAIL PROTECTED] wrote: All, Can anyone tell me what is the purpose of the files generated under /resources/schemaorg_apache_xmlbeans with the file extension .xsb? These get generated by WSDL2Java when the databinding is xmlbeans... B. -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Purpose of resource files generated with Xmlbeans databinding
Actually, the latest nightly build solved my problem, so it's not an issue for me anymore--but am still curious about what these files are...XmlBeans itself does not generate them, and they are very short files, schemaorg_apache_xmlbeans.system.s4455233DA64B38DEA9E660649ACE1E73 with some unreadable chars (raw bytes?) leading and trailing. Just curious, Brennan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Greif Sent: Thursday, September 07, 2006 10:41 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Purpose of resource files generated with Xmlbeans databinding I'm using XmlBeans to go back and forth between object and dom representations in a service deployed as a message service (so axis is not used to generate any code) I just use XmlBeans outside axis and embed the generated classes in WEB-INF/lib of the webapp containing axis. Just download the latest xmlbeans distribution and run scomp on the schemas and wsdls in question with some appropriate .xsdconfig file you write. The .xsb files can be generated into the same tree that the compiled generated classes go in, and jar'ed up into the resulting archive. The xmlbeans docs explain it well enough so it can be done without much thrashing around. Jeff On 9/7/06, Spies, Brennan [EMAIL PROTECTED] wrote: Is there a way to generate these manually, since I am currently having a problem with not all of my schemas being generated as XmlBeans classes (https://issues.apache.org/jira/browse/AXIS2-1116)? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] How to write server-side implementation for doc/lit
I have a (simple) question regarding the implementation of
the server-side logic web service in Axis 2.0, which is not clear from the
documentation.
After doing the code generation (doc/literal service with
XMLBeans databinding, and server-side interface), I am left with a MessageReceiver
(in my case AbstractInOutSyncMessageReceiver) which calls the skeletons
business method from its invokeBusinessLogic() method. The generated business
method always has a method signature like: void name(). What I want to do,
since I am using a document-style service, is parse the body of the incoming
message using the *Document.Factory.parse() of the appropriate XMLBeans
generated class.
2 options stand out:
1)
Change the method signature of my skeletons
invoked message so that it passes in the appropriate MessageContext. Get the
SOAP body from it, retrieve the stream and parse.
2)
Add the following to the skeleton:
private MessageContext msgCtx;
public void setOperationContext(OperationContext
opContext) throws AxisFault {
this.msgCtx = opContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
}
This, apparently, gets invoked by reflection during this
operation:
org.apache.axis2.engine.DependencyManager
.configureBusinessLogicProvider(obj, msgContext
.getOperationContext());
Does it make a difference (or is there a preferred way of doing
this)? Is there an easier way of wiring this that I am unaware of?
Presumably, you would use the MessageContext to get the SOAPBody,
from which you could parse using the appropriate XmlObject, like so:
// Todo fill this with the necessary
business logic
SOAPBody
body = msgCtx.getEnvelope().getBody();
try {
ResultDocument
rd = ResultDocument.Factory.parse(body.getXMLStreamReader());
//etc...
}
catch (XmlException e)
{
e.printStackTrace();
}
RE: [Axis2] Purpose of resource files generated with Xmlbeans databinding
I see. I was not seeing any .xsb files when I ran the XMLBeans ant task separately (http://xmlbeans.apache.org/docs/2.0.0/guide/antXmlbean.html ), using the same jar in the Axis 2.0 distribution. But I had srconly=true, so maybe this option does not generate .xsb? But from the tool documentation, there is a viewer to view this info: dumpxsb (XSB File Dumper) Prints the contents of an XSB file in human-readable form. An XSB file contains schema meta information needed to perform tasks such as binding and validation. XSB stands for XML Schema Binary. Syntax dumpxsb myfile.xsb Options myfile.xsb The name of an XSB file. Example The following command and output example use an XSB file generated by compiling the schema (in EasyPo.xsd) that accompanies the SubstitutionGroup sample. dumpxsb PurchaseOrderDocument.xsb Output: PurchaseOrderDocument.xsb Magic cookie: da7ababe Major version: 2 Minor version: 22 Release number: 0 Filetype: FILETYPE_SCHEMAPOINTER String pool (2): 1 = schema.system.s633ECC92E6CC0ACA137B11B7B38CA3A8 Type system: schema.system.s633ECC92E6CC0ACA137B11B7B38CA3A8 -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Thursday, September 07, 2006 12:42 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Purpose of resource files generated with Xmlbeans databinding Hi, This is what I found in the XMLBeans site An XSB file contains schema meta information needed to perform tasks such as binding and validation. XSB stands for XML Schema Binary. So my undertanding is that these xsb files are needed to when binding is done and hence a must to be generated. When you invoke scomp usually things are jarred and the xsbs will be conveniently hidden from view :) XMLBeans also has a tool that lets you inspect the content of an xsb file [1] HTH Ajith [1] http://xmlbeans.apache.org/docs/2.0.0/guide/tools.html#dumpxsb On 9/7/06, robert lazarski [EMAIL PROTECTED] wrote: I've also never used xmlbeans outside of axis2 databinding ... but I do know that the schemaorg_apache_xmlbeans* dependancy is due to the TypeSystemHolder.class that is strangely created when also creating the *.java files when invoking wsdl2java . The whole thing never made sense to me or a lot of other people ... the question comes up frequently on the list. IIRC the TypeSystemHolder.class is indeed created outside of axis2 , as I wrote some of the first docs showing how to overcome the problem via searching on the xmlbeans list. HTH, Robert On 9/7/06, Ajith Ranabahu [EMAIL PROTECTED] wrote: Hi, XMLBeans does not generate them when invoked standalone ?? I'm not really sure about this but XMLBeans depends on these xsb files to parse the XMLs properly and it cannot do without them. Ajith On 9/7/06, Spies, Brennan [EMAIL PROTECTED] wrote: Actually, the latest nightly build solved my problem, so it's not an issue for me anymore--but am still curious about what these files are...XmlBeans itself does not generate them, and they are very short files, schemaorg_apache_xmlbeans.system.s4455233DA64B38DEA9E660649ACE1E73 with some unreadable chars (raw bytes?) leading and trailing. Just curious, Brennan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Greif Sent: Thursday, September 07, 2006 10:41 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Purpose of resource files generated with Xmlbeans databinding I'm using XmlBeans to go back and forth between object and dom representations in a service deployed as a message service (so axis is not used to generate any code) I just use XmlBeans outside axis and embed the generated classes in WEB-INF/lib of the webapp containing axis. Just download the latest xmlbeans distribution and run scomp on the schemas and wsdls in question with some appropriate .xsdconfig file you write. The .xsb files can be generated into the same tree that the compiled generated classes go in, and jar'ed up into the resulting archive. The xmlbeans docs explain it well enough so it can be done without much thrashing around. Jeff On 9/7/06, Spies, Brennan [EMAIL PROTECTED] wrote: Is there a way to generate these manually, since I am currently having a problem with not all of my schemas being generated as XmlBeans classes (https://issues.apache.org/jira/browse/AXIS2-1116)? - 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] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED
RE: axis versus axis2
I'm not sure if I qualify as a die hard fan of Axis, but I've chosen it over XFire because I like the pluggable architecture and some of the other features, such as more transport options (TCP). I am doing a top-down web service using XML Schema and WSDL as the starting point. The xsd is moderately complicated, with three separate files defined in the same namespace. The story goes somewhat like this: 1) Downloaded Axis 2.0 release distribution. Chose Xmlbeans as the databinding option because of its excellent support for even complex XML Schema (ADB couldn't handle my XSD). Ran WSDL2Java Ant task to generate code. Generated code did not compile (the *MessageReceiverInOut.java generated class had errors in the fromOM() and toOM()), so... 2) Downloaded Nightly build (at that time 2006-09-02), which got rid of the problem. But the WSDL2Java ant task was not generating all of the XmlBeans source files (only 1 of the xsd had classes generated for it). Also, the codegen 'namespaceToPackages' attribute was being ignored. OK, added a .xsdconfig file in the same directory as the xsd and ran separate Ant task to generate the Xmlbeans classes. No problem. 3) Deployed the .aar file using the generated build.xml. Ran into an issue because the code generator is copying my schema files as xsd0.xsd, xsx1.xsd, etc. to the /resources folder and my import tag in my WSDL file (under types section) was still referencing the file by name. OK, so I copied the original WSDL's to the /resources folder and regenerated the .aar and deployed it. It runs now, but I still have to do the same for the JMS version of the web service. My impressions are that 1.0 is still a little rough around the edges. Nothing impossible to overcome, but if you expect everything out-of-the-box, you may want to wait until 1.1. Brennan -Original Message- From: Paul Vial [mailto:[EMAIL PROTECTED] Sent: Sunday, September 03, 2006 9:33 PM To: axis-user@ws.apache.org Subject: axis versus axis2 Hi, just starting to play around with web services (and AXIS). Installed AXIS and ran some of the demos without any problems but have since discovered AXIS2 (yet to install). Should I jump to AXIS2 or are there die hard AXIS fans that would like to share their recomendations. thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Purpose of resource files generated with Xmlbeans databinding
All, Can anyone tell me what is the purpose of the files generated under /resources/schemaorg_apache_xmlbeans with the file extension .xsb? These get generated by WSDL2Java when the databinding is xmlbeans B.
RE: axis versus axis2
Davanum, Done: https://issues.apache.org/jira/browse/AXIS2-1116 I assume that the appropriate .xsb files will be generated under /resources when the bug is fixed (whatever they do...). B. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 06, 2006 1:40 PM To: axis-user@ws.apache.org Cc: [EMAIL PROTECTED] Subject: Re: axis versus axis2 Brennan, Could you please log a bug for #2 with your wsdl/xsd's? (I just checked in a change that may help!). That will help us fix both #2 and #3. thanks, dims On 9/6/06, Spies, Brennan [EMAIL PROTECTED] wrote: I'm not sure if I qualify as a die hard fan of Axis, but I've chosen it over XFire because I like the pluggable architecture and some of the other features, such as more transport options (TCP). I am doing a top-down web service using XML Schema and WSDL as the starting point. The xsd is moderately complicated, with three separate files defined in the same namespace. The story goes somewhat like this: 1) Downloaded Axis 2.0 release distribution. Chose Xmlbeans as the databinding option because of its excellent support for even complex XML Schema (ADB couldn't handle my XSD). Ran WSDL2Java Ant task to generate code. Generated code did not compile (the *MessageReceiverInOut.java generated class had errors in the fromOM() and toOM()), so... 2) Downloaded Nightly build (at that time 2006-09-02), which got rid of the problem. But the WSDL2Java ant task was not generating all of the XmlBeans source files (only 1 of the xsd had classes generated for it). Also, the codegen 'namespaceToPackages' attribute was being ignored. OK, added a .xsdconfig file in the same directory as the xsd and ran separate Ant task to generate the Xmlbeans classes. No problem. 3) Deployed the .aar file using the generated build.xml. Ran into an issue because the code generator is copying my schema files as xsd0.xsd, xsx1.xsd, etc. to the /resources folder and my import tag in my WSDL file (under types section) was still referencing the file by name. OK, so I copied the original WSDL's to the /resources folder and regenerated the .aar and deployed it. It runs now, but I still have to do the same for the JMS version of the web service. My impressions are that 1.0 is still a little rough around the edges. Nothing impossible to overcome, but if you expect everything out-of-the-box, you may want to wait until 1.1. Brennan -Original Message- From: Paul Vial [mailto:[EMAIL PROTECTED] Sent: Sunday, September 03, 2006 9:33 PM To: axis-user@ws.apache.org Subject: axis versus axis2 Hi, just starting to play around with web services (and AXIS). Installed AXIS and ran some of the demos without any problems but have since discovered AXIS2 (yet to install). Should I jump to AXIS2 or are there die hard AXIS fans that would like to share their recomendations. thanks - 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] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - 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]
