Re: [jira] Resolved: (AXIS2-3987) Axis2 Addressing treats MessageID as a required element
On Fri, Feb 27, 2009 at 10:43 AM, Brian DePradine (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/AXIS2-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian DePradine resolved AXIS2-3987. Resolution: Won't Fix As the message id may be required in some situations, according to the WS-Addressing spec, no change will be made. But if its optional, why do we make it mandatory? That seems to me to be an obvious contradiction, isn't it? It would be a violation of the spec if it couldn't be made optional, right? Rainy day here ... not that I have dog in this hunt. - R Axis2 Addressing treats MessageID as a required element --- Key: AXIS2-3987 URL: https://issues.apache.org/jira/browse/AXIS2-3987 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Addressing Environment: Ubuntu, jdk 1.5 Reporter: Isuru Eranga Suriarachchi According to both WS-Addressing final and submission specifications, the Message Id is an optional element in the header. But when I engaged Axis2 addressing to a simple client and set only the Action, it adds a message Id as well. I tried the following option as well. But it didn't work. options.setProperty(INCLUDE_OPTIONAL_HEADERS, Boolean.FALSE); So I can't create a message without the optional element MessageID using Axis2.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: axis2-1.4, xmlbeans, mtom, weblogic
On Thu, Jun 5, 2008 at 9:00 AM, Karunanidhi, Meena [EMAIL PROTECTED] wrote: I developed a web service in java with axis2-1.4 (using xmlbeans, mtom) and generated java code from eclipse plug-in. xmlbeans in axis2 doesn't support mtom. This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do. snip Don't post confidential emails to a public list. Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-1.4, xmlbeans, mtom, weblogic
On Thu, Jun 5, 2008 at 9:28 AM, Karunanidhi, Meena [EMAIL PROTECTED] wrote: Hi Robert Just wondering then how the axis2server able to execute the service successfully. The exception is only when I deploy the web service onto weblogic. Thanks Meena This is the dev list, so perhaps you should look at the source code? If not, please post userspace questions to the axis2-user list. Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3604) Spring test fails
[ https://issues.apache.org/jira/browse/AXIS2-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578311#action_12578311 ] robert lazarski commented on AXIS2-3604: Is anyone else seeing this? I can't reproduce the error. At a glance, ReflectionUtils.makeAccessible(Field field) in spring has been long stable, yet somehow you are calling ReflectionUtils.makeAccessible(Ljava/lang/reflect/Constructor;) . I'm also suprised to see all the org.springframework.beans.factory.xml.XmlBeanDefinitionReader classes being loaded - I have no idea why that would be needed. I had other problems building with jdk 6 / maven 2.0.8 and reverted to jdk 5 / maven 2.0.7 , You say you are running IBM jdk 6 . Playing option bingo may help - maven 2.0.7 and sun jdk 5 did the trick for me after a series of strange errors. Spring test fails - Key: AXIS2-3604 URL: https://issues.apache.org/jira/browse/AXIS2-3604 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.4 Environment: IBM JDK 1.6 Reporter: Brian DePradine Fix For: 1.4 I keep getting the following error when I run the integration tests: --- Test set: org.apache.axis2.spring.SpringServiceTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.25 sec FAILURE! testSpringAppContextAwareObjectSupplier(org.apache.axis2.spring.SpringServiceTest) Time elapsed: 3.609 sec ERROR! org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource [spring/applicationContext.xml]; nested exception is java.lang.NoSuchMethodError: org/springframework/util/ReflectionUtils.makeAccessible(Ljava/lang/reflect/Constructor;)V Caused by: java.lang.NoSuchMethodError: org/springframework/util/ReflectionUtils.makeAccessible(Ljava/lang/reflect/Constructor;)V at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:82) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:61) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.createBeanDefinitionDocumentReader(XmlBeanDefinitionReader.java:499) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:486) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:383) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:327) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:295) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:112) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:79) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:101) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:389) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:324) at org.apache.axis2.spring.SpringServiceTest.createSpringAppCtx(SpringServiceTest.java:184) at org.apache.axis2.spring.SpringServiceTest.setUp(SpringServiceTest.java:82) at junit.framework.TestCase.runBare(TestCase.java:132) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24
[axis2] Can't build from source
Hey devs,
I just checked out the latest svn today, and got this:
mvn clean install -U -Dtest=false
...
Embedded error: The following error occurred while executing this line:
java.io.FileNotFoundException:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/wsdl/Test01/build.xml
(No such file or directory)
Here's the problem area with JAXB-RI, any hints on how to get around this?
[INFO]
[INFO] Building Apache Axis 2.0 - JAXB-RI Data Binding
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory /home/iksrazal/workspace/axis2/modules/jaxbri/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 3 source files to
/home/iksrazal/workspace/axis2/modules/jaxbri/target/classes
[INFO] [antrun:run {execution: gen-ts}]
[INFO] Executing tasks
[mkdir] Created dir:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/schema
[mkdir] Created dir:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/schema/src
[mkdir] Created dir:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/schema/classes
[echo] Generating JAX-B classes for DocLitBareService test
[echo] Generating Service / Service Client for Test01 test
[java] Retrieving document at 'test-resources/wsdl/Test01.wsdl'.
[java] Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:278)
[java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
[java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
[java] Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
[java] at
org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:112)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:231)
[java] ... 2 more
[java] Caused by: java.lang.reflect.InvocationTargetException
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:101)
[java] ... 3 more
[java] Caused by: java.lang.LinkageError: JAXB 2.0 API is being
loaded from the bootstrap classloader, but this RI (from
jar:file:/home/iksrazal/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.6/jaxb-impl-2.1.6.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class)
needs 2.1 API. Use the endorsed directory mechanism to place
jaxb-api.jar in the bootstrap classloader. (See
http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
[java] at
com.sun.xml.bind.v2.model.impl.ModelBuilder.clinit(ModelBuilder.java:173)
[java] at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
[java] at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.init(JAXBContextImpl.java:286)
[java] at
com.sun.tools.xjc.reader.xmlschema.bindinfo.BindInfo.getJAXBContext(BindInfo.java:332)
[java] at
com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl$1.init(AnnotationParserFactoryImpl.java:80)
[java] at
com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl.create(AnnotationParserFactoryImpl.java:79)
[java] at
com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.createAnnotationParser(NGCCRuntimeEx.java:323)
[java] at
com.sun.xml.xsom.impl.parser.state.annotation.action0(annotation.java:48)
[java] at
com.sun.xml.xsom.impl.parser.state.annotation.enterElement(annotation.java:73)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElement(NGCCHandler.java:74)
[java] at
com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:294)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCHandler.revertToParentFromEnterElement(NGCCHandler.java:111)
[java] at
com.sun.xml.xsom.impl.parser.state.foreignAttributes.enterElement(foreignAttributes.java:50)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378)
[java] at
Re: [axis2] Can't build from source
Forgot to mention: using jdk1.6.0_03 on linux in case it matters.
Robert
On Wed, Mar 5, 2008 at 2:03 PM, robert lazarski
[EMAIL PROTECTED] wrote:
Hey devs,
I just checked out the latest svn today, and got this:
mvn clean install -U -Dtest=false
...
Embedded error: The following error occurred while executing this line:
java.io.FileNotFoundException:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/wsdl/Test01/build.xml
(No such file or directory)
Here's the problem area with JAXB-RI, any hints on how to get around this?
[INFO]
[INFO] Building Apache Axis 2.0 - JAXB-RI Data Binding
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
/home/iksrazal/workspace/axis2/modules/jaxbri/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 3 source files to
/home/iksrazal/workspace/axis2/modules/jaxbri/target/classes
[INFO] [antrun:run {execution: gen-ts}]
[INFO] Executing tasks
[mkdir] Created dir:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/schema
[mkdir] Created dir:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/schema/src
[mkdir] Created dir:
/home/iksrazal/workspace/axis2/modules/jaxbri/target/schema/classes
[echo] Generating JAX-B classes for DocLitBareService test
[echo] Generating Service / Service Client for Test01 test
[java] Retrieving document at 'test-resources/wsdl/Test01.wsdl'.
[java] Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:278)
[java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
[java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
[java] Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
[java] at
org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:112)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:231)
[java] ... 2 more
[java] Caused by: java.lang.reflect.InvocationTargetException
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:101)
[java] ... 3 more
[java] Caused by: java.lang.LinkageError: JAXB 2.0 API is being
loaded from the bootstrap classloader, but this RI (from
jar:file:/home/iksrazal/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.6/jaxb-impl-2.1.6.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class)
needs 2.1 API. Use the endorsed directory mechanism to place
jaxb-api.jar in the bootstrap classloader. (See
http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
[java] at
com.sun.xml.bind.v2.model.impl.ModelBuilder.clinit(ModelBuilder.java:173)
[java] at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
[java] at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.init(JAXBContextImpl.java:286)
[java] at
com.sun.tools.xjc.reader.xmlschema.bindinfo.BindInfo.getJAXBContext(BindInfo.java:332)
[java] at
com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl$1.init(AnnotationParserFactoryImpl.java:80)
[java] at
com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl.create(AnnotationParserFactoryImpl.java:79)
[java] at
com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.createAnnotationParser(NGCCRuntimeEx.java:323)
[java] at
com.sun.xml.xsom.impl.parser.state.annotation.action0(annotation.java:48)
[java] at
com.sun.xml.xsom.impl.parser.state.annotation.enterElement(annotation.java:73)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElement(NGCCHandler.java:74)
[java] at
com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:294)
[java] at
com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378)
[java
Re: [VOTE] Michele Mazzucco as Axis2 Committer
Agreed, long over due. +1 On Mon, Mar 3, 2008 at 12:41 PM, David Illsley [EMAIL PROTECTED] wrote: +1 This has been due for a while... David On Mon, Mar 3, 2008 at 9:31 AM, Davanum Srinivas [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks, I am tired of applying Michele's patches :) So Let's please invite Michele to join us as a committer Please see all of Michele's efforts here. Lot's of user mailing list participation, tons of JIRA's and Patches! http://apache.markmail.org/search/?q=Michele%20Mazzucco Thanks, dims -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFHzBnOgNg6eWEDv1kRAvDnAKCeCC/O3QqVTlSTd0lmoiaPxPyjQgCfXO2c Q4uwcvSTy7ISzs4TEHaR1fo= =nRyn -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - 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]
[jira] Commented: (AXIS2-3427) SOAPMonitorApplet/SOAPMonitorService broken
[ https://issues.apache.org/jira/browse/AXIS2-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574584#action_12574584 ] robert lazarski commented on AXIS2-3427: On my todo list - I'll look at it in the next day or so. SOAPMonitorApplet/SOAPMonitorService broken --- Key: AXIS2-3427 URL: https://issues.apache.org/jira/browse/AXIS2-3427 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: nightly Reporter: Andreas Veithen Assignee: robert lazarski Fix For: 1.4 Attachments: axis2-3427.patch.txt In revision 601605 the SOAPMonitorApplet class was moved from the default package to org.apache.axis2.soapmonitor.applet. This change needs to be reflected in SOAPMonitorService which generates the HTML to include the applet. Also the relevant documentation (modules/documentation/xdocs/@axis2_version_dir@/soapmonitor-module.xml) should be updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New to Axis2 - Need help.
On Nov 20, 2007 1:08 PM, Hosamath, Viru [EMAIL PROTECTED] wrote: All, I'm new to Apache Axis2, I have downloaded Axis 1.4 release. First step: know what you are running. There is no released 1.4 for Axis2 - you are most likely running the legacy Axis 1.x series. I recommend the latest Axis2 version 1.3 and to read the docs: http://ws.apache.org/axis2/ HTH, Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Prioritized list of 1.4 things to do
Since I'm doing a lot with axis2 / spring / hibernate at the moment, I volunteer to do the Full-on enterprise sample (hibernate/spring/etc) - once we decide what that means. By enterprise do we mean app servers? Keep in mind hibernate is LGPL so we can't include it any sample - its kind of big anyways. We could I suppose ask the users to download it and follow the sample code. Robert On Nov 13, 2007 10:59 AM, Glen Daniels [EMAIL PROTECTED] wrote: Hi folks: Deepal and I just did a quick prioritization pass on the list at [1]. Please take a look and see if it matches your view of the world. We tried to be pretty simple about it, marking things on a three-level scale where 1 = critical, 2 = important, and 3 = nice to have. Couple of quick things to note - 1) we didn't consider how easy/hard these things are; so some of the 3's are going to be 5-minute quick fixes which can get done any time. 2) some of the priorities are about making sure we finish discussion/design on things - so even if it's a (1) that doesn't necessarily mean we'll change any code, just that we MUST have the conversation soon. Thanks, --G D [1] http://wiki.apache.org/ws/FrontPage/Axis2/post-1%2e3-plans - 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: [VOTE] Sanjaya Karunasena as an Axis2 commiter
+1 Robert On Nov 14, 2007 1:15 PM, Thilina Gunarathne [EMAIL PROTECTED] wrote: +1 ~Thilina On Nov 14, 2007 12:28 PM, R J Scheuerle Jr [EMAIL PROTECTED] wrote: +1 Rich Scheuerle IBM Web Services Apache Axis2 ([EMAIL PROTECTED]) 512-838-5115 (IBM TL 678-5115) Damitha Kumarage [EMAIL PROTECTED] wrote on 11/14/2007 01:49:15 AM: +1. Damitha Deepal Jayasinghe wrote: Hi all, Sanjaya Karunasena has done enough work to become as a commiter , he has implemented fastinforset [FI] support in Axis2. And giving he commiter access will encourage him to contribute some more to the project and will make our job easier [no need to commit the patches]. Here my +1 for Sanjaya as an Axis2 commiter. Thanks Deepal - 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] -- Thilina Gunarathne - http://thilinag.blogspot.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: [VOTE] Bjorn Townsend for committer
+1 Robert On Nov 14, 2007 1:09 PM, keith chapman [EMAIL PROTECTED] wrote: +1 Thanks, Keith. On Nov 14, 2007 10:02 PM, Glen Daniels [EMAIL PROTECTED] wrote: Hi folks! As mentioned I'd like us to invite Bjorn Townsend, who's been helping out on the fringes of Axis for a while now, to become a committer so he can help us out with the Axis1 1.5 release. He's kindly volunteered to help pull together the release, and toward that end, we need him to be able to fix bugs and commit patches. Here's my +1. Thanks, --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (AXIS2-3258) Extend Spring support to accept proxies
Hmm, the Service needs to be a concrete class, ie, have an implementation and not be just an interface. Any bean dependencies, such as for beans that have methods you invoke, have been known to work in some cases as interfaces by avoiding them be spring proxies. This particular problem is that there is no proxy class that This issue has come up several times before and have had solutions, please search the forums. HTH, Robert On Nov 12, 2007 5:47 AM, BJuma [EMAIL PROTECTED] wrote: Hi, I am facing this problem now. My understanding to fix it is by having an interface for the current webservice and defining it in the services.xml as a ServiceClass, like this: service name=SpringAwareService description simple spring example /description parameter name=ServiceClassspring.SpringAwareServiceInterface/parameter parameter name=ServiceObjectSupplierorg.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier/parameter parameter name=SpringBeanNamespringAwareService/parameter operation name=getValue messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service Is this sufficient? I tried it but not worked. Did I miss any thing or should I try certain fix build. Thanks, JIRA [EMAIL PROTECTED] wrote: Extend Spring support to accept proxies --- Key: AXIS2-3258 URL: https://issues.apache.org/jira/browse/AXIS2-3258 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: deployment, wsdl Affects Versions: 1.3 Reporter: Oleg Efimov Priority: Blocker ServiceBuilder presently requires service class's byte code to obtain method parameter names. This won't work with proxies, thus making Spring support really feeble. I propose introducing additional service.xml parameter, namely ServiceInterface, to enumerate service methods and parameter names. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28AXIS2-3258%29-Extend-Spring-support-to-accept-proxies-tf4592976.html#a13703440 Sent from the Axis - Dev 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: [jira] Created: (AXIS2-3258) Extend Spring support to accept proxies
rmi is new, comming in after the 1.3 release. Try looking for axis2-rmi-*.jar and adding it to WEB-INF/lib . HTH, Robert On Nov 12, 2007 8:25 AM, BJuma [EMAIL PROTECTED] wrote: I downloaded the latest nightly build along with what I posted below and it works fine. However I am having an exception when the server is starting up which is: [exec] 17:25:51,287 ERROR org.apache.axis2.deployment.AxisConfigBuilder:319 - org.apache.axis2.rmi.deploy.RMIServiceDeployer [exec] java.lang.ClassNotFoundException: org.apache.axis2.rmi.deploy.RMIServiceDeployer [exec] at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318) [exec] at java.lang.ClassLoader.loadClass(ClassLoader.java:289) [exec] at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143) [exec] at java.lang.ClassLoader.loadClass(ClassLoader.java:235) [exec] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) [exec] at java.lang.Class.forName0(Native Method) [exec] at java.lang.Class.forName(Class.java:141) [exec] at org.apache.axis2.util.Loader.loadClass(Loader.java:261) [exec] at org.apache.axis2.deployment.AxisConfigBuilder.processDeployers(AxisConfigBuilder.java:316) [exec] at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:233) [exec] at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:628) [exec] at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:146) [exec] at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:501) [exec] at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:421) [exec] at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2354) [exec] at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4795) [exec] at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4889) [exec] at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:1015) [exec] at com.evermind.server.http.HttpApplication.init(HttpApplication.java:549) [exec] at com.evermind.server.Application.getHttpApplication(Application.java:890) [exec] at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:707) [exec] at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:625) [exec] at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:278) [exec] at com.evermind.server.http.HttpServer.setSites(HttpServer.java:278) [exec] at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:179) [exec] at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2394) [exec] at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1551) [exec] at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92) Any idea? iksrazal wrote: Hmm, the Service needs to be a concrete class, ie, have an implementation and not be just an interface. Any bean dependencies, such as for beans that have methods you invoke, have been known to work in some cases as interfaces by avoiding them be spring proxies. This particular problem is that there is no proxy class that This issue has come up several times before and have had solutions, please search the forums. HTH, Robert On Nov 12, 2007 5:47 AM, BJuma [EMAIL PROTECTED] wrote: Hi, I am facing this problem now. My understanding to fix it is by having an interface for the current webservice and defining it in the services.xml as a ServiceClass, like this: service name=SpringAwareService description simple spring example /description parameter name=ServiceClassspring.SpringAwareServiceInterface/parameter parameter name=ServiceObjectSupplierorg.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier/parameter parameter name=SpringBeanNamespringAwareService/parameter operation name=getValue messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service Is this sufficient? I tried it but not worked. Did I miss any thing or should I try certain fix build. Thanks, JIRA [EMAIL PROTECTED] wrote: Extend Spring support to accept proxies --- Key: AXIS2-3258 URL: https://issues.apache.org/jira/browse/AXIS2-3258 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: deployment, wsdl Affects Versions: 1.3 Reporter: Oleg Efimov Priority: Blocker ServiceBuilder presently requires service
Re: custom transport
On Nov 7, 2007 12:42 PM, Deepal jayasinghe [EMAIL PROTECTED] wrote: mathieu fabre wrote: hi, I would like to implement my own transport in xmpp (jabber) i write a XMPPTransportSender and a XMPPSimple Server like for the http transport. i add these sender and receiver in the axis2.xml config file. Well we have already implement the XMPP transport , will commit soon. :) Please update the wiki when committed so we can all keep track: http://wiki.apache.org/ws/StackComparison Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Understanding Axis2 dependencies
I agree there are too many jars - I just did a project and it was a drag going through all those deps. But why are we limping with commons-logging 1.1 - because its a jar dep? IIRC correctly almost all of the apache projects use it. commons-logging is so well, common, you'll probably need it anyways. Debugging via logs is a very important thing and is more complicated than it may appear. There are not only several IDE's but several JEE servers. I actually use axis2 in alot of these JEE servers. When you start trying to debug axis2 via eclipse live on things like JBoss and JPDA, some loggers like commons-logging 1.0.4 will crash hard. JBoss is a good example of a complicated and hard to override logging scheme. In short, you're probably going to need commons-logging anyways since everyone uses it, and if history is any guide its going to be left up to the users to test any other logging on everything but tomcat. Since JDK logging is not at all common, help may be hard to come by. So I see pain with little benefit. I'm fighting for this because its not at all fun to waste time on logging problems, and commons-logging 1.1 simply works everywhere axis2 has run. Robert On 10/27/07, Eran Chinthaka [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Robert, Yes it is not broken. But why do we wanna limp with it? If we had used a separate, say String class without using java.lang.String, do you wanna keep it, if java.lang.String serves the purpose. Look at how pain it is to deal with numerous jars within Axis2. I'd like to cut down whatever possible whenever possible. Also I totally agree with Tom's comments. We can come up with usecases which commons-logging becomes handy. But how many users will use it or come across that use case vs how many users find it difficult to set up Axis2 to run within their box? I agree removing just two or three jars won't solve the problem, but at least that will be a start. Thanks, Chinthaka robert lazarski wrote: Um, Axis2 has been on commons-logging 1.1 since right after Axis2 1.0 . The most common JEE server is JBoss, and Axis2 and commons-logging plays nice there. IMHO, If it aint broke, don't fix it. Robert On 10/23/07, Tom Jordahl [EMAIL PROTECTED] wrote: Of course if Axis2 switched to commons-logging 1.1 and the container it is running in uses 1.0.4 (for instance) then you are worse off than when you started. My feeling is that commons-logging is a great idea - as long as you are the only one in the pool using it. Once you try to integrate with another J2EE server/project/whatever that *also* uses it, you tend to get in to trouble. Using the JDK api just gets Axis2 out of the line of fire in the logging wars. -- Tom Jordahl -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 8:01 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Understanding Axis2 dependencies I've been stuck in classloader hell many times and moving to commons-logging 1.1 solved a lot of problems for me - there's been a lot of work put into that area. Also, everything else in apache land uses commons-logging. +1 for keeping it. Robert On 10/22/07, Tom Jordahl [EMAIL PROTECTED] wrote: [Concerning commons-logging] also what would you replace it with ? I actually think that the JDK 1.4 logging APIs would probably do the trick, not have jar hell problems, and be functional enough for most everyone. -- Tom Jordahl -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 10:39 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Understanding Axis2 dependencies Hi, On 10/17/07, Eran Chinthaka [EMAIL PROTECTED] wrote: Since the topic is about jar dependencies, I'd like to comment on two aspects. 1. As one can see there is a huge number of dependencies we have in Axis2 and I think we ship almost all of them with our releases. Why should we release both xbeans and jibx with adb? My suggestion, let's ship the minimum number of jars required for a user. If he needs to use XmlBeans, then let him download it. Same thing for JiBX. And also it is better to see the minimum set of jars required to run a client somewhere. I raised this point couple of days before also. If you need to do a SOAP call, you need to include more than 20-25 jars. Yes we can do that. We already pick up the databinding implementation by reflection and it is easy enough to print a message to print a readable error message for the absence of the jars. What I prefer to have is jar bundles for each databinding. Say for XMLBeans we have a xmlbeans bundle (Xbeans jar, the Xbeans-codegen module etc) and so on. 2. Why do we need to have commons-logging? One would say well it let's you plug any logging module. How many of the users have really
Re: Web application and Axis2 deployment issue...
Weblogic apparently has stax there somewhere. Try reading this link to see if that helps: http://ws.apache.org/axis2/1_3/app_server.html Robert On 10/24/07, Dinesh Ghutake [EMAIL PROTECTED] wrote: Hi, I am involved into the development of web service application using axis2, hibernate etc. Our front end application is built using struts. My project ear structure is as below: MYProjEAR: - APP-INF - classes -lib - axis2 (all web services deployed in this project) - ejbs - META-INF(application.xml and Weblogic-application.xml) - WEBAPP-WAR WEB-INF Lib (I have copied all axis2 jar here along with webapplication jars ) Struts classes Home -jsp Etc… In Web application I have stubs created to call web services. I am getting this exception when I am try to deploy My Proj. ear on Weblogic 9.2 server. Oct 24, 2007 2:26:56 PM EDT Error Console BEA-240003 Console encountered the followin g error weblogic.application.ModuleException: at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:292) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.ja va:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvo ker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallback Flow.java:360) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbac kFlow.java:56) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbac kFlow.java:46) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker .java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvok er.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepare Container(ActivateOperation.java:189) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(Activa teOperation.java:87) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(Abstract Operation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(Dep loymentManager.java:718) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(Deplo ymentManager.java:1185) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentMan ager.java:247) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(Deploymen tServiceDispatcher.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.d oPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.a ccess$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1 .run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java: 518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) Caused by: java.lang.ClassCastException: com.ctc.wstx.stax.WstxInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136) at weblogic.servlet.internal.WebAppHelper.addListenerElements(WebAppHelper.java:244) at weblogic.servlet.internal.WebAppHelper$IOHelperImpl.parseXML(WebAppHelper.java:224) at weblogic.descriptor.DescriptorCache.parseXML(DescriptorCache.java:324) at weblogic.servlet.internal.WebAppHelper.registerTagLibListeners(WebAppHelper.java:17 4) at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:2 54) at
Re: [Axis2] Understanding Axis2 dependencies
Um, Axis2 has been on commons-logging 1.1 since right after Axis2 1.0 . The most common JEE server is JBoss, and Axis2 and commons-logging plays nice there. IMHO, If it aint broke, don't fix it. Robert On 10/23/07, Tom Jordahl [EMAIL PROTECTED] wrote: Of course if Axis2 switched to commons-logging 1.1 and the container it is running in uses 1.0.4 (for instance) then you are worse off than when you started. My feeling is that commons-logging is a great idea - as long as you are the only one in the pool using it. Once you try to integrate with another J2EE server/project/whatever that *also* uses it, you tend to get in to trouble. Using the JDK api just gets Axis2 out of the line of fire in the logging wars. -- Tom Jordahl -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 8:01 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Understanding Axis2 dependencies I've been stuck in classloader hell many times and moving to commons-logging 1.1 solved a lot of problems for me - there's been a lot of work put into that area. Also, everything else in apache land uses commons-logging. +1 for keeping it. Robert On 10/22/07, Tom Jordahl [EMAIL PROTECTED] wrote: [Concerning commons-logging] also what would you replace it with ? I actually think that the JDK 1.4 logging APIs would probably do the trick, not have jar hell problems, and be functional enough for most everyone. -- Tom Jordahl -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 10:39 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Understanding Axis2 dependencies Hi, On 10/17/07, Eran Chinthaka [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since the topic is about jar dependencies, I'd like to comment on two aspects. 1. As one can see there is a huge number of dependencies we have in Axis2 and I think we ship almost all of them with our releases. Why should we release both xbeans and jibx with adb? My suggestion, let's ship the minimum number of jars required for a user. If he needs to use XmlBeans, then let him download it. Same thing for JiBX. And also it is better to see the minimum set of jars required to run a client somewhere. I raised this point couple of days before also. If you need to do a SOAP call, you need to include more than 20-25 jars. Yes we can do that. We already pick up the databinding implementation by reflection and it is easy enough to print a message to print a readable error message for the absence of the jars. What I prefer to have is jar bundles for each databinding. Say for XMLBeans we have a xmlbeans bundle (Xbeans jar, the Xbeans-codegen module etc) and so on. 2. Why do we need to have commons-logging? One would say well it let's you plug any logging module. How many of the users have really used a logging framework other than log4j? This is YAGNI for me. (you can also see very good comments about commons-logging from our valuable admirer here http://www.bileblog.org/?p=259) Well not really. All our logging code is based on commons-logging. If we are to remove this code it would be somewhat significant effort and also what would you replace it with ? The way it is right now is the best way. What we can do is to send the default config to use java.util logging so that we do not need to send the log4j jar along. Just my 2 cents. Thanks, Chinthaka Sanka Samaranayke wrote: Hi, Sanjiva Weerawarana wrote: Thanks Ajith. I think we should document this somewhere- we often get this question and there's obviously reasons for why we have all these dependencies. We need to clearly indicate which things are optional and indicate under what conditions they come into use. I am not a fan of going back to the seven different distributions model as that was confusing to users. Knowing the dependency reasons will help embedders decide what they really need to pull in and what's optional. One jar I didn't understand is the mex jar. Why is that around; that should only be in the mex mar I believe. You need that jar if you use MexClient in your client code. Thanks, Sanka Sanjiva. Ajith Ranabahu wrote: Hi Lawrence, Let me see whether I can make sense of some of the stuff. Others will chip in as needed and will surely holler if I make a mistake. Axis2 Third Party Dependencies -- activation-1.1.jarMIME support annogen-0.1.0.jar Annotation support axiom-api-1.2.5.jar XML pull parsing axiom-dom-1.2.5.jar XML pull parsing axiom-impl-1.2.5.jar
Re: [Axis2] Understanding Axis2 dependencies
I've been stuck in classloader hell many times and moving to commons-logging 1.1 solved a lot of problems for me - there's been a lot of work put into that area. Also, everything else in apache land uses commons-logging. +1 for keeping it. Robert On 10/22/07, Tom Jordahl [EMAIL PROTECTED] wrote: [Concerning commons-logging] also what would you replace it with ? I actually think that the JDK 1.4 logging APIs would probably do the trick, not have jar hell problems, and be functional enough for most everyone. -- Tom Jordahl -Original Message- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 10:39 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Understanding Axis2 dependencies Hi, On 10/17/07, Eran Chinthaka [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since the topic is about jar dependencies, I'd like to comment on two aspects. 1. As one can see there is a huge number of dependencies we have in Axis2 and I think we ship almost all of them with our releases. Why should we release both xbeans and jibx with adb? My suggestion, let's ship the minimum number of jars required for a user. If he needs to use XmlBeans, then let him download it. Same thing for JiBX. And also it is better to see the minimum set of jars required to run a client somewhere. I raised this point couple of days before also. If you need to do a SOAP call, you need to include more than 20-25 jars. Yes we can do that. We already pick up the databinding implementation by reflection and it is easy enough to print a message to print a readable error message for the absence of the jars. What I prefer to have is jar bundles for each databinding. Say for XMLBeans we have a xmlbeans bundle (Xbeans jar, the Xbeans-codegen module etc) and so on. 2. Why do we need to have commons-logging? One would say well it let's you plug any logging module. How many of the users have really used a logging framework other than log4j? This is YAGNI for me. (you can also see very good comments about commons-logging from our valuable admirer here http://www.bileblog.org/?p=259) Well not really. All our logging code is based on commons-logging. If we are to remove this code it would be somewhat significant effort and also what would you replace it with ? The way it is right now is the best way. What we can do is to send the default config to use java.util logging so that we do not need to send the log4j jar along. Just my 2 cents. Thanks, Chinthaka Sanka Samaranayke wrote: Hi, Sanjiva Weerawarana wrote: Thanks Ajith. I think we should document this somewhere- we often get this question and there's obviously reasons for why we have all these dependencies. We need to clearly indicate which things are optional and indicate under what conditions they come into use. I am not a fan of going back to the seven different distributions model as that was confusing to users. Knowing the dependency reasons will help embedders decide what they really need to pull in and what's optional. One jar I didn't understand is the mex jar. Why is that around; that should only be in the mex mar I believe. You need that jar if you use MexClient in your client code. Thanks, Sanka Sanjiva. Ajith Ranabahu wrote: Hi Lawrence, Let me see whether I can make sense of some of the stuff. Others will chip in as needed and will surely holler if I make a mistake. Axis2 Third Party Dependencies -- activation-1.1.jarMIME support annogen-0.1.0.jar Annotation support axiom-api-1.2.5.jar XML pull parsing axiom-dom-1.2.5.jar XML pull parsing axiom-impl-1.2.5.jar XML pull parsing backport-util-concurrent-2.2.jar ? Thread pooling support. This feature is built in for Java 1.5 and this particular jar has a backport of that code to Java 1.4 commons-codec-1.3.jar URL encoding? commons-fileupload-1.1.1.jar Used for uploading new service files in the admin client? Yes - needed only when using the webapp commons-httpclient-3.0.1.jar Used by the Axis2 kernel? Yes - but primarily on the client side. I believe it is needed in the server side if asynchronous calls are to be supported. commons-io-1.2.jar? commons-logging-1.1.jar Is this related to Log4J? Well kind of. Commons logging is a common API on multiple logging frameworks (log4j/java.util.logging) but allows the switching of the logging engine easily. All the logging code inside the Axis2 source are made using commons logging classes. geronimo-annotation_1.0_spec-1.1.jar
[jira] Commented: (AXIS2-3286) Spring AOP integration. Follow up on thread (AXIS2-3258)
[ https://issues.apache.org/jira/browse/AXIS2-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535967 ] robert lazarski commented on AXIS2-3286: Hmm, CGLIB indicates you have hibernate mixed in somehow. When you say during schema generation - are you implying java2wsdl ? Apart from the interface question - which generally is a good idea anyways as it allows a different implementation for each project, which is a nice plus for spring beans and pluggability - there isn't enough info here to understand your problem. Furthermore, could you try clarifying what you mean by Is it possible that I simply the provider class itself as the ServiceClass and also have the ServiceObjectProvider in place. Spring AOP integration. Follow up on thread (AXIS2-3258) Key: AXIS2-3286 URL: https://issues.apache.org/jira/browse/AXIS2-3286 Project: Axis 2.0 (Axis2) Issue Type: Test Affects Versions: 1.3 Environment: Java, Spring AOP Reporter: Rakesh Hi, I was looking at the resolution for the problem of using Spring AOP. I get an exception The following error occurred during schema generation: Unable to load bytecode for class abc.skl.ServiceProvider$$EnhancerByCGLIB$$4a4e81cb The thread AXIS2-3258 has a solution where you introduce an interface as ServiceClass along with ServiceObjectSupplier. My question is does this mean that my implementation class should now be split into an interface with all the method signatures and then provide an implementation class for this interface. And do this for all the services. The problem is that we are building an internal framework and will be extended by other systems. So if we do put this condition, then all subsystems will have to be modified to do the same too. Is it possible that I simply the provider class itself as the ServiceClass and also have the ServiceObjectProvider in place. Can someone please confirm my understanding. Thanks, Rakesh. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: So Long, and Thanks for All the Fish
On 9/29/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Dear WS folks, FYI, I've asked to resign from the WS PMC as i strongly believe that a PMC member should actively participates on the projects. Unfortunately due to circumstances beyond my control/comprehension, i'll not be able to spend time on the various WS projects. I'll miss each and every one of the participants here. It's been a long ride since 2001-04-19 when i first showed up on the axis-dev mailing list. I hope to be back some day (sooner than later! hope it is sooner!). You can still reach me on yahoo IM (dims) or email (davanum AT gmail.com). Wish you all the very best of luck. thanks, dims Best wishes, thanks for all the code and bug fixes - a few particular onces were damn good, and particularlty the leadership by example all these years - I don't think I'd be on this group still if it wasn't for that. Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS2 + Spring : Error registering bean with name 'applicationContext' defined in class path resource
Please ask questions like this on the users list. I doubt that you could just bring in those jars from 1.3 to 1.1 and have it work. Furthermore, you aren't clear if you are running spring from inside or outside the aar. In the former case all the spring jars from WEB-INF/lib need to be moved into the aar. In the latter case all the spring jars need to be placed in WEB-INF/lib. HTH, Robert On 9/20/07, Sushil Dodake [EMAIL PROTECTED] wrote: I switched from Axis2 1.1 to Axis2 1.3 for doing so i follwed following steps. 1.Downloaded teh Axis2.war file 2. Deployed the same in the Tomcat webapps dir 3. Started Tomcat 4. Changed the name of the exploded Axis2 folder 5. replaced jars old versions to the following version axis2-kernel-1.3.jar axis2-spring-1.3.jar axis2-saaj-1.3.jar 6. created the AAR file by adding required jars 7. deployed the AAR in teh service folder of tomcat deployment 8. started tomcat Some how the spring is not able to get the org.apache.axis2.extensions.spring.receivers.ApplicationContextHolder class reffered in the Application context file using applicationContext bean. Hence gives problem while loading the application context. The error log is as below. Exception while loading carServiceContext.xml org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'applicationContext' defined in class path resource [applicationContext.xml ]: Class that bean class [org.apache.axis2.extensions.spring.receivers.ApplicationContextHolder] depends on not found; nested exception is java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContextAware java.lang.NoClassDefFoundError: org/springframework/context/ApplicationContextAware at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass (SecureClassLoader.java:123) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1634) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307) at java.lang.ClassLoader.loadClass(ClassLoader.java:282) at java.lang.ClassLoader.loadClass(ClassLoader.java:282) at java.lang.ClassLoader.loadClass (ClassLoader.java:282) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName (Class.java:219) at org.springframework.util.ClassUtils.forName(ClassUtils.java:109) at org.springframework.beans.factory.support.BeanDefinitionReaderUtils.createBeanDefinition(BeanDefinitionReaderUtils.java:65) at org.springframework.beans.factory.xml.DefaultXmlBeanDefinitionParser.parseBeanDefinitionElement(DefaultXmlBeanDefinitionParser.java:466) at org.springframework.beans.factory.xml.DefaultXmlBeanDefinitionParser.parseBeanDefinitionElement (DefaultXmlBeanDefinitionParser.java:432) at org.springframework.beans.factory.xml.DefaultXmlBeanDefinitionParser.parseBeanDefinitions(DefaultXmlBeanDefinitionParser.java:347) at org.springframework.beans.factory.xml.DefaultXmlBeanDefinitionParser.registerBeanDefinitions (DefaultXmlBeanDefinitionParser.java:197) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:295) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions (XmlBeanDefinitionReader.java:223) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:173) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions (XmlBeanDefinitionReader.java:148) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:129) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions (AbstractBeanDefinitionReader.java:145) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:113) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions (AbstractXmlApplicationContext.java:81) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:89) at org.springframework.context.support.AbstractApplicationContext.refresh (AbstractApplicationContext.java:262) at com.toro.service.cart.CartServiceInit.startUp(CartServiceInit.java:30) at org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass(ServiceBuilder.java:357) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:139) at
Re: AXIS2 Soapmonitor
http://ws.apache.org/axis2/1_3/soapmonitor-module.html If you need anything beyond that just ask. HTH, Robert On 8/23/07, Karuppusamy, Thamayanthi (Consultant) [EMAIL PROTECTED] wrote: Hi, Can anybody what are thing we have to concentrate when we implement AXIS2 SOAPMonitor in projects. Thanks Regards Thamayanthi Karuppusamy This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Also, email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3107) REST SOAP Monitor inconsistency
[ https://issues.apache.org/jira/browse/AXIS2-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518593 ] robert lazarski commented on AXIS2-3107: The soap monitor just does messageContext.getEnvelope().toString() . There are some things - MTOM for example - that the soap monitor currently can't capture right and REST may fall into that category. You could help us track this down by using TCPMon to see if the same behavior occurs there as well. REST SOAP Monitor inconsistency - Key: AXIS2-3107 URL: https://issues.apache.org/jira/browse/AXIS2-3107 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3 Environment: Axis2-1.3-RC2 Tomcat 5.5 Linux Reporter: simishag Priority: Minor Fix For: 1.3 When debugging with the SOAP Monitor applet, REST requests don't appear to work right. I discovered this while working on another issue, and some more detail on reproducing this can be found in issue AXIS2-3106. As I understand it, REST requests are processed by Axis into actual SOAP requests, and the resulting requests can be viewed in the SOAP Monitor. I tried 3 different method/parameter combinations, each with 1 invalid parameter name. All 3 of these combinations resulted in identical SOAP requests when viewed in the monitor, with 2 parameters set properly and the 3rd invalid parameter missing, as expected. However, although the monitor shows identical SOAP requests, the requests are not in fact being delivered to Axis in this manner, which is verified by the 3 very different error responses I observed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518049 ] robert lazarski commented on AXIS2-3071: Thanks for your time Dims. For some reason, the way I use xmlbeans and wsdl2java now require my EPR to include the operation name, ie: new EndpointReference( http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno/tissSolicitacaoDemonstrativoRetorno_Operation;); And not the way I've always done it: new EndpointReference( http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno;); The latter gives me Operation not found . Maybe I'm behind the times.. Thanks for the help. XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SOLICITACAO_DEMONSTRATIVO.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3071) XMLBean problems with 1.3 RC3
XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: tissSimpleTypesV2_01_02.xsd tissGuiasV2_01_02.xsd tissComplexTypesV2_01_02.xsd XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: (was: tissComplexTypesV2_01_02.xsd) XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: build.xml tissV2_01_02.xsd tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: (was: tissGuiasV2_01_02.xsd) XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: (was: tissSimpleTypesV2_01_02.xsd) XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: SolicitacaoDemonstrativoClient.java XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: tissSimpleTypesV2_01_02.xsd tissGuiasV2_01_02.xsd tissComplexTypesV2_01_02.xsd XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: SolicitacaoDemonstrativoClient.java XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: (was: SolicitacaoDemonstrativoClient.java) XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: SOLICITACAO_DEMONSTRATIVO.xml XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: (was: SOLICITACAO_DEMONSTRATIVO.xml) XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3071) XMLBean problems with 1.3 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-3071: --- Attachment: SOLICITACAO_DEMONSTRATIVO.xml XMLBean problems with 1.3 RC3 - Key: AXIS2-3071 URL: https://issues.apache.org/jira/browse/AXIS2-3071 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: java 6, tomcat 5.5, linux Reporter: robert lazarski Fix For: 1.3 Attachments: build.xml, SOLICITACAO_DEMONSTRATIVO.xml, SolicitacaoDemonstrativoClient.java, tissComplexTypesV2_01_02.xsd, tissGuiasV2_01_02.xsd, tissSimpleTypesV2_01_02.xsd, tissSolicitacaoDemonstrativoRetornoV2_01_02.wsdl, tissV2_01_02.xsd Testing RC3 with XMLBeans is giving this error: 2007-08-04 20:35:10,304 [org.apache.axis2.transport.http.AxisServlet] - org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno and the WSA Action = I'm using the same WSDL's and XSD's that were working in a later axis2 1.2 snapshot. The listServices page is saying that the EPR is installed: tissSolicitacaoDemonstrativoRetorno Service EPR : http://localhost:9080/axis2/services/tissSolicitacaoDemonstrativoRetorno Service Description : tissSolicitacaoDemonstrativoRetorno Service Status : Active Available Operations * tissSolicitacaoDemonstrativoRetorno_Operation The URL in axis2/services/listServices matches exactly the error message URL. I'm using xmlbeans validate() in the client code, and setting the EPR and placing it in Options. Please see attached files for more info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3040) Can Axis2 support Spring-JPA configuration
[ https://issues.apache.org/jira/browse/AXIS2-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517284 ] robert lazarski commented on AXIS2-3040: We've yet to see any issues with Axis2 and spring 2.0 - that's my typical environment. Are your Spring XML files valid XML? Try validating them with xmlspy on XP or another tool. Beyond that, for some other reason you may have an invalid AAR. If your xml files are validating, please upload your AAR so we can see what's causing the issue. Can Axis2 support Spring-JPA configuration -- Key: AXIS2-3040 URL: https://issues.apache.org/jira/browse/AXIS2-3040 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: winxp , axis2 Reporter: tommy Assignee: robert lazarski I worked fine with my spring-JPA project alone, but when I add some axis2 features into this project, and upload .aar file to the server, it shows me the exception as follows: org.apache.axis2.deployment.DeploymentException: Processing Operations Modules w ith an error of sample.spring.service.SpringInit at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) Any help appreciated -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3040) Can Axis2 support Spring-JPA configuration
[ https://issues.apache.org/jira/browse/AXIS2-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516953 ] robert lazarski commented on AXIS2-3040: When you say JPA, are you running this in tomcat or some other application server? Could you clarify your environment further? Please upload your AAR or create simple test case that can be uploaded as an AAR. Can Axis2 support Spring-JPA configuration -- Key: AXIS2-3040 URL: https://issues.apache.org/jira/browse/AXIS2-3040 Project: Axis 2.0 (Axis2) Issue Type: Bug Environment: winxp , axis2 Reporter: tommy Assignee: robert lazarski I worked fine with my spring-JPA project alone, but when I add some axis2 features into this project, and upload .aar file to the server, it shows me the exception as follows: org.apache.axis2.deployment.DeploymentException: Processing Operations Modules w ith an error of sample.spring.service.SpringInit at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener(Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) Any help appreciated -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] missing artifact from maven2 conversion
Hi all, Going through the axis2 branch testing stuff that I use and I noticed that when we moved to maven2, we lost axis2-soapmonitor-1.2.jar . The soapmonitor appears unique in axis2 in that there was both a jar produced and a mar. The jar contains the compiled applet classes, so the end user doesn't have to compile them themselves, and more importantly the servlet classes needed to run it. Best I can tell maven2 doesn't support 2 artifacts from one project. I see 2 solutions here: 1) Create a separate project for the jar. 2) Some type of hack. Feedback appreciated, Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] missing artifact from maven2 conversion
Got a hack to work - new pom.xml in branch and trunk ;-) . Still need
to get the jar into the war. If no one beats me to it, I'll try to
make that happen sometime this weekend.
Thanks,
Robert
On 7/27/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
my choice #2 - a hack. I tried addint the following in soap monitor pom.xml
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
executions
execution
phaseprocess-classes/phase
goals
goaljar/goal
/goals
configuration
basedir${pom.basedir}/target/classes/basedir
/configuration
/execution
/executions
/plugin
works great! only problem is it has all the META-INF/module.xml and
other unnecessary stuff which will caus problems. So Robert, can you
please try using a maven-ant-plugin and use the ant jar task to build
a jar with just the minimal classes needed in it? Then we'd have to
integrate it into the distrribution.
thanks,
dims
On 7/27/07, robert lazarski [EMAIL PROTECTED] wrote:
Hi all,
Going through the axis2 branch testing stuff that I use and I noticed
that when we moved to maven2, we lost axis2-soapmonitor-1.2.jar . The
soapmonitor appears unique in axis2 in that there was both a jar
produced and a mar. The jar contains the compiled applet classes, so
the end user doesn't have to compile them themselves, and more
importantly the servlet classes needed to run it.
Best I can tell maven2 doesn't support 2 artifacts from one project. I
see 2 solutions here:
1) Create a separate project for the jar.
2) Some type of hack.
Feedback appreciated,
Robert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas :: http://davanum.wordpress.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] Speak Now or Forever Hold Your Peace!
So am I correct in assuming this is branch: axis2-1.3-SNAPSHOT-war.zip axis2-1.3-SNAPSHOT-src.zip axis2-1.3-SNAPSHOT-war.zip And this is head? axis2-SNAPSHOT-bin.zip axis2-SNAPSHOT-src.zip axis2-SNAPSHOT-war.zip FYI, hope to finish testing the parts I use - spring, xmlbeans and the soapmonitor - along with some doc updates today but no later than tomorrow. Robert On 7/26/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Folks, We've cut 2 RC's for 1.3 release and nightlies are up and running for the 1.3 branch as well *PLEASE* test your scenarios with the latest RC and/or nightly and log a JIRA bug with all details needed to recreate your problem if you see something wrong. 1.3 RC2 - http://people.apache.org/~deepal/axis2/1.3-RC2/ 1.3 Branch Trunk Nightly - http://people.apache.org/dist/axis2/nightly/ JIRA - https://issues.apache.org/jira/browse/AXIS2 If 1.3 Final does not work for you when we cut it, it's your own fault :) If you have a JIRA that has not gotten the attention it deserves, please speak up and let us know. thanks, dims -- Davanum Srinivas :: http://davanum.wordpress.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]
Missing spring and soapmonitor jars in RC2
Deepal, Dims et all, These jars were in the 1.2 release war, and are missing in the 1.3 RC2 axis2 war : axis2-soapmonitor-1.3.jar axis2-spring-1.2.jar Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Changes to branch
I was planning on doing a few doc changes for spring, should those be done on the head ? Robert On 7/23/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Glen , We will definitely do that , I have done one commit which I did nit commit to trunk. First I need to make sure thats working in branch after that will do the changes to trunk Thanks Deepal PLEASE, folks, don't check in changes directly to the 1.3 branch. We agreed some time ago on a set of release process guidelines which entail making all code changes on the trunk and then merging those changes over to the branch. The only time this changes is in the rare case where there are incompatible changes on the trunk that are NOT going into the release. Thanks, --Glen - 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: Return Hibernate persistence Obj from Axis2
Axis2 supports jibx and you go to its main site, last I looked, there's some examples for hibernate. HTH, Robert On 7/22/07, Sharon [EMAIL PROTECTED] wrote: Hi all, Is it possible to return Hibernate 3.0 persistence class from Axis2 (1.2/1.3) Web Service? Any code samples? Thanks!! Sharon - 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] Spring datasource inside AAR
Excellent news, glad it worked it out. FYI, there is a axis2 1.3RC1 that you may want to try. There should be an official release in a few weeks. Robert On 7/11/07, Brian Kates [EMAIL PROTECTED] wrote: I think I solved the problem. I didn't have the Oracle jar in my tomcat common/lib folder. I didn't have it there for my Axis 1.1 WAR deployment either, but anyway I put it there and my service deploys. Still not sure if I actually have a datasource (I'll test that out next), but at least it deploys! -Brian *robert lazarski [EMAIL PROTECTED]* 07/11/2007 03:01 PM Please respond to axis-dev@ws.apache.org To axis-dev@ws.apache.org cc Subject Re: [Axis2] Spring datasource inside AAR Are you saying the same exact AAR worked in axis 1.1 but doesn't in axis2 1.2 ? If so, can you try axis2 1.3 RC1 ? Robert On 7/11/07, *Brian Kates *[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I know that datasource with that driver works because I copied it directly from an Axis 1.1 project. I'm not entirely sure how to package an axis deployment outside of an AAR. I'll have to poke around for an example. I'll let you know if I can run the project outside of an AAR... Thanks. -Brian *robert lazarski [EMAIL PROTECTED][EMAIL PROTECTED] ** 07/11/2007 11:10 AM Please respond to* [EMAIL PROTECTED] axis-dev@ws.apache.org To [EMAIL PROTECTED] axis-dev@ws.apache.org cc Subject Re: [Axis2] Spring datasource inside AAR It looks like your oracle driver doesn't accept those properties. I think you need to use the 10i drivers, even with 9i. That's what I did. My version looks identical at first glance. bean id=myDataSource class=org.springframework.jdbc.datasource.DriverManagerDataSource property name=driverClassName valueoracle.jdbc.driver.OracleDriver/value /property property name=url value*jdbc:oracle:thin:@luke.copperkey.com:1521*http://jdbc:oracle:thin:@luke.copperkey.com:1521/ :zion/value /property property name=username valueSMBDEMOGUSER/value /property property name=password valueSMBDEMOGUSER/value /property /bean I know that works with axis2 1.2 and a recent svn. Note, I didn't deploy inside the AAR though. You might try outside the AAR first, and then let us know as it may be a bug. I do know I tested axis2 1.1 with mysql inside the AAR. There has been a few classloader issues with jdbc at certain points but until now those all seemed flushed out. HTH, Robert On 7/11/07, Brian Kates [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to setup a datasource to run inside an AAR. I'm using the SpringInit class from the Axis 2 documentation. I have not modified the class. My datasource defined in the application context is as follows: bean id=dataSource class=org.springframework.jdbc.datasource.DriverManagerDataSource property name=driverClassNamevalueoracle.jdbc.driver.OracleDriver /value/property property name=urlvalueURL/value/property property name=usernamevalueUSER/value/property property name=passwordvaluePASSWORD/value/property /bean The big long stack trace is below. Any ideas? org.apache.axis2.deployment.DeploymentException: Processing Operations Modules with an error of Error creating bean with name 'dataSource' defined in class path resource [applicationContext.xml]: Error setting property values; nested exception is PropertyAccessExceptionsException (1 errors) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup (ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java :79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy( DeploymentEngine.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update( WSInfoList.java:201) at org.apache.axis2.deployment.RepositoryListener.update( RepositoryListener.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices( RepositoryListener.java:189) at org.apache.axis2.deployment.DeploymentEngine.loadServices( DeploymentEngine.java:110) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices( WarBasedAxisConfigurator.java:257) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext (ConfigurationContextFactory.java:74) at org.apache.axis2.transport.http.AxisServlet.initConfigContext( AxisServlet.java:486) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406) at org.apache.catalina.core.StandardWrapper.loadServlet( StandardWrapper.java:1139) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966) at org.apache.catalina.core.StandardContext.loadOnStartup( StandardContext.java:3956) at org.apache.catalina.core.StandardContext.start
Re: [Axis2] Spring datasource inside AAR
It looks like your oracle driver doesn't accept those properties. I think you need to use the 10i drivers, even with 9i. That's what I did. My version looks identical at first glance. bean id=myDataSource class=org.springframework.jdbc.datasource.DriverManagerDataSource property name=driverClassName valueoracle.jdbc.driver.OracleDriver/value /property property name=url valuejdbc:oracle:thin:@luke.copperkey.com:1521:zion/value /property property name=username valueSMBDEMOGUSER/value /property property name=password valueSMBDEMOGUSER/value /property /bean I know that works with axis2 1.2 and a recent svn. Note, I didn't deploy inside the AAR though. You might try outside the AAR first, and then let us know as it may be a bug. I do know I tested axis2 1.1 with mysql inside the AAR. There has been a few classloader issues with jdbc at certain points but until now those all seemed flushed out. HTH, Robert On 7/11/07, Brian Kates [EMAIL PROTECTED] wrote: I'm trying to setup a datasource to run inside an AAR. I'm using the SpringInit class from the Axis 2 documentation. I have not modified the class. My datasource defined in the application context is as follows: bean id=dataSource class=org.springframework.jdbc.datasource.DriverManagerDataSource property name=driverClassNamevalueoracle.jdbc.driver.OracleDriver/value/property property name=urlvalueURL/value/property property name=usernamevalueUSER/value/property property name=passwordvaluePASSWORD/value/property /bean The big long stack trace is below. Any ideas? org.apache.axis2.deployment.DeploymentException: Processing Operations Modules with an error of Error creating bean with name 'dataSource' defined in class path resource [applicationContext.xml]: Error setting property values; nested exception is PropertyAccessExceptionsException (1 errors) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:147) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:201) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:189) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:110) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:257) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:74) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:486) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
Re: [ANN][Axis2] Axis2 1.3-RC1 release
Deepal, can we get the link the 1.3 RC1 on the main site? You previously said that was a good idea. I think we all agree that getting more RC usage by end users is a good idea, which so far hasn't really happened too much. Robert On 7/7/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi all, I have upload Axis2 1.3 RC1 artifact into my apache home location [1] , please test and make sure all the JIRAs we marked as fixed are there in the release , in addition to that if you find any issues with the release please create a JIRA [2] , then we can fix that for next RC. This release is based on the SVN version number of following projects. Axiom : - 553458 Neethi : 553469 XML Schema : 553334 We have a number of major changes from 1.2 to 1.3 and most of them are listed in apache axis2 wiki [3]. We have fixed more about 350 JIRA issues from 1.2 to 1.3 in addition to the following new feature additions ; - Clustering support - Doc-lt/bare wsdl generation and run time support (RPC MRs can handle doc-lit/ bare ) - Custom deployment support - NIO transport integration Our plan is to make Axis2 1.3 release as mush as stable and robust, so please help us by reviewing this release candidate. [1] : http://people.apache.org/~deepal/axis2/1.3-RC1/ [2] : https://issues.apache.org/jira/browse/AXIS2 [3] : http://wiki.apache.org/ws/FrontPage/Axis2/changesfrom1.2to1.3 Thanks Deepal - 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] Feedback / action item on Axis2's spring support
Long email alert! . I think the spring stuff could be easier for sure. To be accurate though, you only need a bean descripter in the 'inside the aar case' . That's not the case by using a ContextListener via the servet container to setup spring. Note that the latter case is what xfire does, since they don't have an aar and such. As I think everyone knows, Spring is configured in the AbstractMessageReceiver which was an afterthought. There were some tricky classloader issues that came up when trying to get the 'inside the AAR' case up. So really there's currently three part's of the spring / axis2 integration: 1) jaxws . I think there is / was a jira on this for spring. To be honest, I've yet to get involved in jaxws besides reading the list. In any case my understanding is it still would involve AbstractMessageReceiver. The threads from the links focused on the jaxws part. 2) Spring jars Inside the AAR. This is the tricky part, and I consider is an advanced case. It gets even trickier when using Spring to configure Hibernate, which appears on the list every few weeks. It is possible of course, but tricky the first time. 3) Spring jars in WEB-INF/lib . This is by far the easiest case. There is no separate spring bean needed. As noted, this is how xfire et all makes things simple. So the way 2 and 3 works currently is by Spring pre-loaded object that's already inside the classloader. There needs to be someway to say: a) Hey axis2, spring is in the app and giving you the Service, so don't instantiate one! Its this object here, you see. b) Hey axis2, there are different places where this object may be coming from. Get it from here! What 'Here' is, is not important at the AbstractMessageReceiver level. Really it may be from the servlet container, or in the 'inside the aar' case from a Spring trick that allows you to get a bean anywhere, anytime. So what I suggest is this: 1) Can we do spring / axis2 integration outside of services.xml ? How else could we let AbstractMessageReceiver know that it needs to get a pre-loaded object ? AbstractMessageReceiver defines the service class, so unless things change it has to happen there, right ? 2) For the complex 'inside the aar' case - Is there a way for an AAR to get things loaded from the TCCL of the Servlet container? This was discussed a lot pre 1.0 days. I'm inclined to believe that no, it cannot. 3) Perhaps move the advanced spring stuff into another doc. The idea being so this case doesn't distract the simple usage of spring / axis2. The 'inside the aar' case is really particular to axis2, and does need another bean. What this other bean does is that it implements the Spring interface ApplicationContextAware. That allows you to get any spring bean, anytime, anywhere. Note this other bean the defines the Spring interface is what is suggested on the spring list all the time for getting spring to work in a Handler and other things that are not spring aware. It was what I used before axis2 had spring. Its in axis2 because its an advanced spring case. Thoughts? Robert On 7/8/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Hi Team, Looks like we are missing a easy-to-use spring deployer [1] Please read the whole thread and let's try to incorporate any feedback possible into 1.3. thanks, dims [1] http://www.nabble.com/Re%3A-Axis2-vs-CXF-p11481341.html [2] http://www.nabble.com/Axis2-vs-CXF-tf4030139.html -- Davanum Srinivas :: http://davanum.wordpress.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]
Does this help? http://ws.apache.org/axis2/1_2/app_server.html Robert On 6/26/07, Dinesh Ghutake [EMAIL PROTECTED] wrote: Hi , I am developing web services application , I deployed *axis2war.war* on *weblogic9.2* That deployment was successful. When I tried to copy my *websericeapp.arr* file to the services folder C:\axis2war\WEB-INF\services. I got this error on weblogic console. If anybody has any idea it would be great help. Thanks in Advance. Jun 21, 2007 1:18:51 PM org.hibernate.cfg.Configuration configure INFO: configuring from resource: com/cscinfo/oms/hibernate.cfg.xml Jun 21, 2007 1:18:51 PM org.hibernate.cfg.ConfigurationgetConfigurationInputStr eam INFO: Configuration resource: com/cscinfo/oms/hibernate.cfg.xml *java.lang.LinkageError: Class org/xml/sax/InputSource violates loader constraint* *s* at org.hibernate.cfg.Configuration.doConfigure(Configuration.java :1366) at org.hibernate.cfg.Configuration.configure(Configuration.java :1310) at com.cscinfo.util.hibernate.HibernateUtil.registerSessionFactoryConfig uration(HibernateUtil.java:70) at com.cscinfo.webservice.OMS_ServiceLifeCycle.startUp (OMS_ServiceLifeCy cle.java:18) at org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass( ServiceBuilder.java:454) at org.apache.axis2.deployment.ServiceBuilder.populateService (ServiceBui lder.java:176) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup( ServiceGroupBuilder.java:98) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServic eGroup(ArchiveReader.java:106) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:140) at org.apache.axis2.deployment.ServiceDeployer.deploy( ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy (DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update (WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update (RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices (Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener (Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run (SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Jun 21, 2007 1:18:51 PM com.cscinfo.webservice.OMS_ServiceLifeCyclestartUp SEVERE: An unexpected exception has occured while starting up. Startup failing! com.cscinfo.util.hibernate.RegistrationException: SessionFactory creation failed [key = 'OMS_SESSION_FACTORY', resource 'com/cscinfo/oms/hibernate.cfg.xml'] at com.cscinfo.util.hibernate.HibernateUtil.registerSessionFactoryConfig uration(HibernateUtil.java:76) at com.cscinfo.webservice.OMS_ServiceLifeCycle.startUp (OMS_ServiceLifeCy cle.java:18) at org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass( ServiceBuilder.java:454) at org.apache.axis2.deployment.ServiceBuilder.populateService (ServiceBui lder.java:176) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup( ServiceGroupBuilder.java:98) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServic eGroup(ArchiveReader.java:106) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServ iceGroup(ArchiveReader.java:140) at org.apache.axis2.deployment.ServiceDeployer.deploy( ServiceDeployer.ja va:79) at org.apache.axis2.deployment.DeploymentEngine.doDeploy (DeploymentEngin e.java:582) at org.apache.axis2.deployment.repository.util.WSInfoList.update (WSInfoL ist.java:201) at org.apache.axis2.deployment.RepositoryListener.update (RepositoryListe ner.java:271) at org.apache.axis2.deployment.RepositoryListener.checkServices (Reposito ryListener.java:189) at org.apache.axis2.deployment.RepositoryListener.startListener (Reposito ryListener.java:265) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(S chedulerTask.java:61) at org.apache.axis2.deployment.scheduler.SchedulerTask.run (SchedulerTask .java:68) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.ru n(Scheduler.java:76) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: java.lang.LinkageError: Class org/xml/sax/InputSource violates loader constraints at
[jira] Commented: (AXIS2-1964) Null Pointer Exception in Service STUB class at _operationClient.execute(true); line for AXIS2 1.1.1
[ https://issues.apache.org/jira/browse/AXIS2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498334 ] robert lazarski commented on AXIS2-1964: You can for now edit the generated stub and MessageReceiver and do envelope.build() in 1.2 . Is this really an axiom problem as noted by WSCOMMONS-172 ? I'd really like to see this fixed for the next release, can Eran, Dims etc comment here on where the focus needs to be on fixing this? Null Pointer Exception in Service STUB class at _operationClient.execute(true); line for AXIS2 1.1.1 - Key: AXIS2-1964 URL: https://issues.apache.org/jira/browse/AXIS2-1964 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: WINDOWS, JAVA1.4, RAD IDE Reporter: Vivek Gawande Assigned To: Amila Chinthaka Suriarachchi Attachments: Jira-1964-Files.zip The recently released version 1.1.1 gives following NPE. It works fine with AXIS2 (1 and 1.1) versions though. The WorkflowServiceAdapterServiceStub is my service stub class. java.lang.NullPointerException at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:528) at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:111) at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:119) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(MTOMXMLStreamWriter.java:146) at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:243) at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:76) at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:59) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:473) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:823) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:819) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:180) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848) at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:419) at org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:190) at org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest(SOAPOverHTTPSender.java:232) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:541) at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:119) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202) at com.gnw.eprocess.svc.wf.WorkflowServiceAdapterServiceStub.createWorkItem(WorkflowServiceAdapterServiceStub.java:240) at com.gnw.eprocess.svc.wf.test.WorkflowServiceAdapterServiceStubTest.testCreateWorkItem(WorkflowServiceAdapterServiceStubTest.java:85) I compared the files generated for 1.1.1 with 1.1 and there is mismatch on the line where it sets Action attribute 1.1 Generated Code: _operationClient.getOptions().setAction(); 1.1.1 Generated Code: _operationClient.getOptions
Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
xmlbeans is broken in the 1.2 release which is a show stopper for those with complicated schemas: https://issues.apache.org/jira/browse/AXIS2-2667 While 'edit the generated code to build the envelope' is a workaround, that's a bit much for new axis2 users and It'd be nice to see a quick release to fix it. I think the larger issue is our rc releases are not getting tested, allowing things like this to slip thru. Perhaps we need something like a 1.2 release, followed by a quick 1.2.1 , so the code actually gets used and the issues get flushed out. Robert On 5/16/07, Thilina Gunarathne [EMAIL PROTECTED] wrote: Last time we did 1.1.1 due to two reason 1- We found few critical issues with that AFAIK there wasn't even any critical blocking issues... 1.1.1 Release was mainly for the performance improvements..+few small bug fixes.. Thanks, Thilina -- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Strange NPE in 1.2
OK, both the stub and the in / out MR need to have build() invoked on the soap envelope when using xmlbeans in 1.2 . Creating a jira now ... Robert On 5/13/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Quick way, edit the Stub, find the method you are invoking, inside the method, just before _operationClient.execute(true); call env.build() where env is the envelope that is being sent. thanks, dims On 5/13/07, robert lazarski [EMAIL PROTECTED] wrote: build() on the SoapEnvelope / Payload ? I should probably know this but ... How do I get a handle on that, client side, with xmlbeans ? How do I build the tree using a stub, before I send it ? Late night on sunday, hints please ;-). Robert On 5/13/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Robert, Could you try calling build() to make sure the whole thing is built (so that Streaming is not used)? thanks, dims On 5/13/07, robert lazarski [EMAIL PROTECTED] wrote: Hi all, I'm seeing this exception in the 1.2 release: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs( BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace (SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace( SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement( StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize( StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize( OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally( SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume( OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo( SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest (AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody (EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest (HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry (HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod( HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod (HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java :346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod (AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send (HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons (CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke (CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send (OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute( OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation (TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java
[jira] Created: (AXIS2-2667) xmlbeans on both client and service side throws NPE without envelope.build()
xmlbeans on both client and service side throws NPE without envelope.build()
-
Key: AXIS2-2667
URL: https://issues.apache.org/jira/browse/AXIS2-2667
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: databinding
Affects Versions: 1.2
Environment: java 6, linux
Reporter: robert lazarski
This stack trace occurs client side:
[java] java.lang.NullPointerException
[java] at
com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:529)
[java] at
com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:113)
[java] at
com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:121)
[java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace
(MTOMXMLStreamWriter.java:148)
[java] at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:238)
[java] at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode
(StreamingOMSerializer.java:71)
[java] at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:54)
[java] at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream
(OMSerializerUtil.java:490)
[java] at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:783)
[java] at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume
(OMElementImpl.java:808)
[java] at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:234)
[java] at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize
(SOAPEnvelopeImpl.java:222)
[java] at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:808)
[java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume
(OMNodeImpl.java:418)
[java] at
org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55)
[java] at
org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java
:84)
[java] at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495)
[java] at
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java
:1973)
[java] at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
[java] at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
[java] at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
[java] at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
[java] at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
[java] at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558)
[java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost
(HTTPSender.java:176)
[java] at
org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
[java] at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java
:305)
[java] at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201)
[java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
[java] at
br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation(TissLoteGuiasStub.java:215)
[java] at org.test.LotesClient.invokeLotes(LotesClient.java:56)
[java] at org.test.LotesClient.main (LotesClient.java:23)
Manually editing the generated stub to invoke envelope.build() solves the
client side issue. However, server side simply throws NPE without a stacktrace
or indication from where it occurred. Editing the in / out MR to also invoke
envelope.build() solves the server side issue as well.
wsdl2java invoked as follows:
target name=wsdl_lotes
delete dir=wsdl_lotes_output /
delete dir=${build} /
delete dir=${dist} /
mkdir dir=${build.classes} /
mkdir dir=${dist} /
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath/
arg value=-d/
arg value=xmlbeans/
arg value=-uri/
arg file=wsdl/tissLoteGuiasV2_01_01.wsdl/
arg value
[jira] Updated: (AXIS2-2667) xmlbeans on both client and service side throws NPE without envelope.build()
[ https://issues.apache.org/jira/browse/AXIS2-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-2667: --- Attachment: tissSimpleTypesV2_01_01.xsd tissComplexTypesV2_01_01.xsd tissLoteGuiasV2_01_01.wsdl xmlbeans on both client and service side throws NPE without envelope.build() - Key: AXIS2-2667 URL: https://issues.apache.org/jira/browse/AXIS2-2667 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.2 Environment: java 6, linux Reporter: robert lazarski Attachments: tissComplexTypesV2_01_01.xsd, tissLoteGuiasV2_01_01.wsdl, tissSimpleTypesV2_01_01.xsd This stack trace occurs client side: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation(TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java] at org.test.LotesClient.main (LotesClient.java:23) Manually editing the generated stub to invoke envelope.build() solves the client side issue. However, server side simply throws NPE without a stacktrace or indication from where it occurred. Editing the in / out MR to also
[jira] Updated: (AXIS2-2667) xmlbeans on both client and service side throws NPE without envelope.build()
[ https://issues.apache.org/jira/browse/AXIS2-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-2667: --- Attachment: tissSimpleTypesV2_01_01.xsd tissLoteGuiasV2_01_01.wsdl tissGuiasV2_01_01.xsd xmlbeans on both client and service side throws NPE without envelope.build() - Key: AXIS2-2667 URL: https://issues.apache.org/jira/browse/AXIS2-2667 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.2 Environment: java 6, linux Reporter: robert lazarski Attachments: tissComplexTypesV2_01_01.xsd, tissGuiasV2_01_01.xsd, tissLoteGuiasV2_01_01.wsdl, tissSimpleTypesV2_01_01.xsd This stack trace occurs client side: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation(TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java] at org.test.LotesClient.main (LotesClient.java:23) Manually editing the generated stub to invoke envelope.build() solves the client side issue. However, server side simply throws NPE without a stacktrace or indication from where it occurred. Editing the in / out
[jira] Updated: (AXIS2-2667) xmlbeans on both client and service side throws NPE without envelope.build()
[ https://issues.apache.org/jira/browse/AXIS2-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-2667: --- Attachment: (was: tissSimpleTypesV2_01_01.xsd) xmlbeans on both client and service side throws NPE without envelope.build() - Key: AXIS2-2667 URL: https://issues.apache.org/jira/browse/AXIS2-2667 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.2 Environment: java 6, linux Reporter: robert lazarski Attachments: tissComplexTypesV2_01_01.xsd, tissGuiasV2_01_01.xsd, tissLoteGuiasV2_01_01.wsdl, tissSimpleTypesV2_01_01.xsd This stack trace occurs client side: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation(TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java] at org.test.LotesClient.main (LotesClient.java:23) Manually editing the generated stub to invoke envelope.build() solves the client side issue. However, server side simply throws NPE without a stacktrace or indication from where it occurred. Editing the in / out MR to also invoke envelope.build() solves the server side issue
[jira] Updated: (AXIS2-2667) xmlbeans on both client and service side throws NPE without envelope.build()
[ https://issues.apache.org/jira/browse/AXIS2-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-2667: --- Attachment: (was: tissLoteGuiasV2_01_01.wsdl) xmlbeans on both client and service side throws NPE without envelope.build() - Key: AXIS2-2667 URL: https://issues.apache.org/jira/browse/AXIS2-2667 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.2 Environment: java 6, linux Reporter: robert lazarski Attachments: tissComplexTypesV2_01_01.xsd, tissGuiasV2_01_01.xsd, tissLoteGuiasV2_01_01.wsdl, tissSimpleTypesV2_01_01.xsd This stack trace occurs client side: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation(TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java] at org.test.LotesClient.main (LotesClient.java:23) Manually editing the generated stub to invoke envelope.build() solves the client side issue. However, server side simply throws NPE without a stacktrace or indication from where it occurred. Editing the in / out MR to also invoke envelope.build() solves the server side issue
[jira] Updated: (AXIS2-2667) xmlbeans on both client and service side throws NPE without envelope.build()
[ https://issues.apache.org/jira/browse/AXIS2-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-2667: --- Attachment: LotesClient.java tissV2_01_01.xsd tissnetV2_01_01.xsd xmlbeans on both client and service side throws NPE without envelope.build() - Key: AXIS2-2667 URL: https://issues.apache.org/jira/browse/AXIS2-2667 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.2 Environment: java 6, linux Reporter: robert lazarski Attachments: LotesClient.java, tissComplexTypesV2_01_01.xsd, tissGuiasV2_01_01.xsd, tissLoteGuiasV2_01_01.wsdl, tissnetV2_01_01.xsd, tissSimpleTypesV2_01_01.xsd, tissV2_01_01.xsd This stack trace occurs client side: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation(TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java] at org.test.LotesClient.main (LotesClient.java:23) Manually editing the generated stub to invoke envelope.build() solves the client side issue. However, server side simply throws NPE without a stacktrace or indication from where
[jira] Updated: (AXIS2-2667) xmlbeans on both client and service side throws NPE without envelope.build()
[ https://issues.apache.org/jira/browse/AXIS2-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] robert lazarski updated AXIS2-2667: --- Attachment: ENVIO_LOTE_GUIAS.xml PROTOCOLO_RECEBIMENTO.xml TissLoteGuiasSkeleton.java xmlbeans on both client and service side throws NPE without envelope.build() - Key: AXIS2-2667 URL: https://issues.apache.org/jira/browse/AXIS2-2667 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.2 Environment: java 6, linux Reporter: robert lazarski Attachments: ENVIO_LOTE_GUIAS.xml, LotesClient.java, PROTOCOLO_RECEBIMENTO.xml, tissComplexTypesV2_01_01.xsd, tissGuiasV2_01_01.xsd, TissLoteGuiasSkeleton.java, tissLoteGuiasV2_01_01.wsdl, tissnetV2_01_01.xsd, tissSimpleTypesV2_01_01.xsd, tissV2_01_01.xsd This stack trace occurs client side: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation(TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java] at org.test.LotesClient.main (LotesClient.java:23) Manually editing the generated stub to invoke envelope.build() solves
[axis2] Strange NPE in 1.2
Hi all,
I'm seeing this exception in the 1.2 release:
[java] java.lang.NullPointerException
[java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(
BaseNsStreamWriter.java:529)
[java] at
com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(
SimpleNsStreamWriter.java:113)
[java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(
SimpleNsStreamWriter.java:121)
[java] at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(
MTOMXMLStreamWriter.java:148)
[java] at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(
StreamingOMSerializer.java:238)
[java] at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(
StreamingOMSerializer.java:71)
[java] at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(
StreamingOMSerializer.java:54)
[java] at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(
OMSerializerUtil.java:490)
[java] at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:783)
[java] at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:808)
[java] at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(
SOAPEnvelopeImpl.java:234)
[java] at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
SOAPEnvelopeImpl.java:222)
[java] at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:808)
[java] at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java
:418)
[java] at
org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(
SOAPMessageFormatter.java:55)
[java] at
org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(
AxisRequestEntity.java:84)
[java] at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody
(EntityEnclosingMethod.java:495)
[java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest
(HttpMethodBase.java:1973)
[java] at org.apache.commons.httpclient.HttpMethodBase.execute(
HttpMethodBase.java:993)
[java] at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(
HttpMethodDirector.java:397)
[java] at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(
HttpMethodDirector.java:170)
[java] at org.apache.commons.httpclient.HttpClient.executeMethod(
HttpClient.java:396)
[java] at org.apache.commons.httpclient.HttpClient.executeMethod(
HttpClient.java:346)
[java] at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(
AbstractHTTPSender.java:558)
[java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost(
HTTPSender.java:176)
[java] at org.apache.axis2.transport.http.HTTPSender.send(
HTTPSender.java:73)
[java] at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons
(CommonsHTTPTransportSender.java:305)
[java] at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
CommonsHTTPTransportSender.java:201)
[java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java
:452)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:330)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(
OutInAxisOperation.java:294)
[java] at
br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation
(TissLoteGuiasStub.java:215)
[java] at org.test.LotesClient.invokeLotes(LotesClient.java:56)
[java] at org.test.LotesClient.main(LotesClient.java:23)
...
Which curiously seems to match a recent report to the users list:
http://marc.info/?l=axis-userm=117892343312805w=2
In my case this error happens on an xmlbeans client invokation which never
reaches the server - its a pretty complex, government like schema so I need
xmlbeans. Here's my code, which seems to passing a valid xmlbeans document:
package org.test;
import java.io.File;
import java.util.ArrayList;
import java.util.List;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.xmlbeans.XmlError;
import org.apache.xmlbeans.XmlOptions;
import br.gov.ans.www.padroes.tiss.schemas.MensagemTISSDocument;
import
br.gov.ans.www.tiss.ws.tipos.tissloteguias.ProtocoloRecebimentoDocument;
import br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub;
public class LotesClient {
/** Access point inside the servlet container. **/
private static EndpointReference targetEPR =
new EndpointReference(
http://localhost:9080/axis2-1.2-SNAPSHOT/services/tissLoteGuias;);
public static void main(String[] args) {
invokeLotes();
}
public static void invokeLotes() {
// lotes request document
Re: [axis2] Strange NPE in 1.2
build() on the SoapEnvelope / Payload ? I should probably know this but ... How do I get a handle on that, client side, with xmlbeans ? How do I build the tree using a stub, before I send it ? Late night on sunday, hints please ;-). Robert On 5/13/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Robert, Could you try calling build() to make sure the whole thing is built (so that Streaming is not used)? thanks, dims On 5/13/07, robert lazarski [EMAIL PROTECTED] wrote: Hi all, I'm seeing this exception in the 1.2 release: [java] java.lang.NullPointerException [java] at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs( BaseNsStreamWriter.java:529) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace ( SimpleNsStreamWriter.java:113) [java] at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace( SimpleNsStreamWriter.java:121) [java] at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace (MTOMXMLStreamWriter.java:148) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement( StreamingOMSerializer.java:238) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode (StreamingOMSerializer.java:71) [java] at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize( StreamingOMSerializer.java:54) [java] at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream (OMSerializerUtil.java:490) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize( OMElementImpl.java:783) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume (OMElementImpl.java:808) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally( SOAPEnvelopeImpl.java:234) [java] at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize (SOAPEnvelopeImpl.java:222) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume( OMElementImpl.java:808) [java] at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume (OMNodeImpl.java:418) [java] at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo( SOAPMessageFormatter.java:55) [java] at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest ( AxisRequestEntity.java :84) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody (EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest ( HttpMethodBase.java :1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java :993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry ( HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod( HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod (HttpClient.java :396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java :346) [java] at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod ( AbstractHTTPSender.java:558) [java] at org.apache.axis2.transport.http.HTTPSender.sendViaPost (HTTPSender.java:176) [java] at org.apache.axis2.transport.http.HTTPSender.send (HTTPSender.java:73) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons (CommonsHTTPTransportSender.java :305) [java] at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke ( CommonsHTTPTransportSender.java:201) [java] at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452) [java] at org.apache.axis2.description.OutInAxisOperationClient.send ( OutInAxisOperation.java:330) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute( OutInAxisOperation.java:294) [java] at br.hapvida.webservices.tissloteguias.endpoint.TissLoteGuiasStub.tissLoteGuias_Operation( TissLoteGuiasStub.java:215) [java] at org.test.LotesClient.invokeLotes(LotesClient.java:56) [java] at org.test.LotesClient.main (LotesClient.java:23) ... Which curiously seems to match a recent report to the users list: http://marc.info/?l=axis-userm=117892343312805w=2 In my case this error happens on an xmlbeans client invokation which never reaches the server - its a pretty complex, government like schema so I need xmlbeans. Here's my code, which seems to passing a valid xmlbeans document: package org.test; import java.io.File; import java.util.ArrayList; import java.util.List; import org.apache.axis2.addressing.EndpointReference; import org.apache.axis2.client.Options; import org.apache.xmlbeans.XmlError; import org.apache.xmlbeans.XmlOptions; import
Re: Eventing
Well there is ws-eventing via axis2 Savan. Wikipedia describes ws-eventing as: *WS-Eventing* defines a protocolhttp://en.wikipedia.org/wiki/Communications_protocolfor web services http://en.wikipedia.org/wiki/Web_service to subscribe to another web service, or to accept a subscriptionhttp://en.wikipedia.org/wiki/Subscriptionfrom another web service. If you are talking about events inside your jvm triggerred by a web service invokation, I myself would use custom events from the Spring Framework: http://static.springframework.org/spring/docs/2.0.x/reference/beans.html#context-functionality-events HTH, Robert On 5/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi I need to have support for events in my webservice. Can anybody suggest how to do that? Thanks And Regards Smitha Aldrin The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extracting information from soap messages.
You can place your handler in the same phases the soapmonitor uses , which sends the entire SOAPEnvelope as a String to an applet. See the soapmonitor tutorial and the source code if in doubt. HTH, Robert On 4/5/07, Inder Dhillon [EMAIL PROTECTED] wrote: Hello I am a new user of Axis2. I have one question that can we induce our handler to extract the tags from the soap messages i.e. from both headers and body into a file. And if we can then in which phase should I include this handler. Thanks in advance. Inder - 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: There are now archived Modules or Services in my War
I would post a question to the WLS list focusing on the nested jar issue. Robert On 3/31/07, Josh [EMAIL PROTECTED] wrote: Is there anything I can do to help this effort? -Josh On 3/30/07, Josh [EMAIL PROTECTED] wrote: My understanding is that loading resources from nested jar files is really a JDK issue. See: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4735639 My thinking is that this would be a limitation if I were using archived module/service files (mar/aar files). In this sample application though, I am not though. That is why I believe the issues I am experiencing and the know jdk 1.4.x feature/bug to be unrelated. Does that sound reasonable? Joshua On 3/30/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Josh, Did you see any workarounds for the Weblogic, rather JDK 1.4.x, has a known issue obtaining resources from nested jar files issue? we could try to incorporate them if we find any good ones. -- dims On 3/30/07, Josh [EMAIL PROTECTED] wrote: Robert, Taking your recomendation, I will explain what has been done so far. Looking to deploy an Axis2 based service into my existing web application, I followed the directions in this article ( http://wso2.org/library/90) to create a war file with only the Axis2 jars (Note: this does not make use of the Axis2.war file in any way). Using the sample application that could be downloaded from this page, I loaded it into Tomcat 5.5.20 and had no problems with it deployed both in war and exploded formats. I was able to view the wsdl file for the sample BookService using the following url: http://localhost:port/axis2/services/BookService?wsdl Note: axis2 in this URL is the name of this sample app, not to be confused with the axis2.war that comes with the axis2 distro. I decided it was time to test this out on Weblogic 8.1. Taking into consideration the well known class loading issue on Weblogic, I added a weblogic.xml file in the WEB-INF directory with the recommended prefer-web-inf-classes option set to true. I deployed the application as an exploded war file and it worked without a hitch. When I packaged it as a war file though, I received the following error: Error HTTP BEA-101214 Included resource or file /axis2/axis2-web/listSingleService.jsp not found from requested resource /axis2/services/BookService. The strange thing about this error is that the axis2-web folder was never included in this war. It was not required on Tomcat (archived and unarchived) and only causes an error when deploying on Weblogic in an archived format. Doing some research, I found that Weblogic, rather JDK 1.4.x, has a known issue obtaining resources from nested jar files. I believe that Tomcat gets around this issue by having its own WAR classloader that works around this issue. Though similar, I don't think the two issues are related. For one, the error messages are totally different and two, the sample BookService is not deployed in an archived aar file. It is also deployed in an exploded format. So, that brings us to where we are now. How can I help further? Regards, Josh -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services 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: There are now archived Modules or Services in my War
Josh - have you read this doc ? http://ws.apache.org/axis2/1_1_1/app_server.html HTH, Robert On 3/29/07, Josh [EMAIL PROTECTED] wrote: Ok, Granted I demonstrated that there is an issue deploying the axis2.war on weblogic when it is not exploded, I think my problem may not be related. That issue appears to be nothing new. Trouble is, I am deploying my application according to this article ( http://wso2.org/library/90) . As a result, I do not have any archived modules or services which leads to the nesting of archives problem. Still, when I deploy in an exploded format, the example application on that page works fine. When in an archived format though, I receive the following error (which I mentioned earlier): Error HTTP BEA-101214 Included resource or file /axis2/axis2-web/listSingleService.jsp not found from requested This is much different than the DeploymentException I was receiving with the axis2.war file. Funny thing is, this file, /axis2/axis2-web/listSingleService.jsp is not even contained in this example app. Why then would it work in an archived format and not an exploded format? Is there other nested archives in the Axis2 distro which I am unaware of? Regards, Joshua On 3/29/07, Josh [EMAIL PROTECTED] wrote: On further inspection, it looks like this is a JDK 1.4 bug/feature ( http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=9ddeb681fad5ece37be8215fe0660:YfiG?bug_id=4648386 ). It also appears that the only reason this works in Tomcat is because tomcat implements its own war class loader. Interesting. So does that mean people who are using JDK 1.4 and are not using Tomcat all have this problem? -Josh On 3/29/07, Josh [EMAIL PROTECTED] wrote: I exploded the services and the modules. Trouble is, the application is still looking for addressing-1.1.1.mar. Is there a way to configure the application to look for addressing-1.1.1 instead? Josh On 3/29/07, Josh [EMAIL PROTECTED] wrote: Geez, It looks like it is a weblogic limitation. I found the answer on the mailing list archives... http://www.mail-archive.com/axis-user@ws.apache.org/msg25079.html I will try and explode the archives within the war and see what happens... Josh On 3/29/07, Josh [EMAIL PROTECTED] wrote: Charitha, Interesting. I added the weblogic.xml file to the distro with the prefer-web-inf-classes option set to true. When deployed in an exploded format, it works fine. When deployed in a war format, I receive the following error: Mar 29, 2007 8:32:24 AM org.apache.axis2.deployment.WarBasedAxisConfigurator getAxisConfiguration SEVERE: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/lib/axis2.war!/WEB-INF/modules/addressing- 1.1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/lib/axis2.war!/WEB-INF/modules/addressing-1.1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/lib/axis2.war!/WEB-INF/modules/addressing-1.1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException : module.xml not found for the module : zip:C:/lib/axis2.war!/WEB-INF/modules/addressing-1.1.1.mar: loading repository from classpath Mar 29, 2007 8:32:24 AM org.apache.axis2.deployment.DeploymentEngine loadFromClassPath INFO: Module validation failed Trying to engage a module which is not available : addressing Mar 29, 2007 8:32:24 AM EDT Error HTTP BEA-101216 Servlet: AxisServlet failed to preload on startup in Web application: axis2. javax.servlet.ServletException: Trying to engage a module which is not available : addressing; nested exception is: org.apache.axis2.AxisFault: Trying to engage a module which is not available : addressing at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:348) at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1094) at weblogic.security.acl.internal.AuthenticatedSubject.doAs (AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:970) at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:949) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:888) at weblogic.servlet.internal.WebAppServletContext.preloadServlet (WebAppServletContext.java:3430) at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3375) at weblogic.servlet.internal.WebAppServletContext.preloadResources( WebAppServletContext.java :3356) at
Re: There are now archived Modules or Services in my War
Been a while since I used weblogic, sorry. However, IIRC correctly from other people on this list, the war needs to be expanded,WEB-INF/services/services.list and WEB-INF/services/module.list needs to be populated, and prefer-web-inf-classestrue/prefer-web-inf-classes needs to be correctly set in weblogic.xml . Providing you have all that, lets try something simple: what does localhost:8080/axis2 show you ? (adjust for your sever if need be) . Also, 1.2 is upcoming. You may consider trying: http://people.apache.org/~deepal/axis2/1.2-RC1/axis2-1.2-RC1.zip http://people.apache.org/~deepal/axis2/1.2-RC1/axis2.war Some weblogic issues have been fixed since 1.1.1 : http://issues.apache.org/jira/browse/AXIS2-1865 http://issues.apache.org/jira/browse/AXIS2-2005 You could help us test the release in wls, and incidently, by using the latest codebase if there is a problem it is easier to get help. HTH, Robert On 3/29/07, Josh [EMAIL PROTECTED] wrote: Robert, thanks for the link. While I already had the weblogic.xml file, Am I supposed to have an entry in this file for each folder under WEB-INF/services or am I supposed to have an entry for each service listed in each services.xml file? Either way, I tried both and I still cannot get this to work. (But I would still like to know how it is supposed to work). Any other ideas? This sample app has no datasources or other stuff to configure. It is very simplistic example app. Do you happen to have WLS 8.1? Joshua On 3/29/07, robert lazarski [EMAIL PROTECTED] wrote: Josh - have you read this doc ? http://ws.apache.org/axis2/1_1_1/app_server.html HTH, Robert On 3/29/07, Josh [EMAIL PROTECTED] wrote: Ok, Granted I demonstrated that there is an issue deploying the axis2.war on weblogic when it is not exploded, I think my problem may not be related. That issue appears to be nothing new. Trouble is, I am deploying my application according to this article ( http://wso2.org/library/90) . As a result, I do not have any archived modules or services which leads to the nesting of archives problem. Still, when I deploy in an exploded format, the example application on that page works fine. When in an archived format though, I receive the following error (which I mentioned earlier): Error HTTP BEA-101214 Included resource or file /axis2/axis2-web/listSingleService.jsp not found from requested This is much different than the DeploymentException I was receiving with the axis2.war file. Funny thing is, this file, /axis2/axis2-web/listSingleService.jsp is not even contained in this example app. Why then would it work in an archived format and not an exploded format? Is there other nested archives in the Axis2 distro which I am unaware of? Regards, Joshua On 3/29/07, Josh [EMAIL PROTECTED] wrote: On further inspection, it looks like this is a JDK 1.4 bug/feature ( http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=9ddeb681fad5ece37be8215fe0660:YfiG?bug_id=4648386 ). It also appears that the only reason this works in Tomcat is because tomcat implements its own war class loader. Interesting. So does that mean people who are using JDK 1.4 and are not using Tomcat all have this problem? -Josh On 3/29/07, Josh [EMAIL PROTECTED] wrote: I exploded the services and the modules. Trouble is, the application is still looking for addressing-1.1.1.mar . Is there a way to configure the application to look for addressing-1.1.1 instead? Josh On 3/29/07, Josh [EMAIL PROTECTED] wrote: Geez, It looks like it is a weblogic limitation. I found the answer on the mailing list archives... http://www.mail-archive.com/axis-user@ws.apache.org/msg25079.html I will try and explode the archives within the war and see what happens... Josh On 3/29/07, Josh [EMAIL PROTECTED] wrote: Charitha, Interesting. I added the weblogic.xml file to the distro with the prefer-web-inf-classes option set to true. When deployed in an exploded format, it works fine. When deployed in a war format, I receive the following error: Mar 29, 2007 8:32:24 AM org.apache.axis2.deployment.WarBasedAxisConfigurator getAxisConfiguration SEVERE: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/lib/axis2.war!/WEB-INF/modules/addressing- 1.1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/lib/axis2.war!/WEB-INF/modules/addressing-1.1.1.mar; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : zip:C:/lib/axis2.war!/WEB-INF/modules/addressing-1.1.1.mar; nested exception is: org.apache.axis2
Re: Article on using Axis2 and Spring
Well written article, uses all the axis2 code already in place. If no one objects I'd like to include the link in the site 'articles' section. Robert On 3/8/07, Paul Fremantle [EMAIL PROTECTED] wrote: In case you didn't see this. http://www.devx.com/Java/Article/33839 -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.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: Latest Axis2 performance benchmarking.... this time against XFire!
Very good news indeed! There is one sentence in the presentation that is not clear: with may be the exception of trading floors . As a native english speaker I can't parse that ;-) . Otherwise all the points made were clear and concise to this reader - good going ! Robert On 1/30/07, Paul Fremantle [EMAIL PROTECTED] wrote: FYI http://wso2.org/library/588 The good news: Axis2/ADB is at least 40% faster than XFire/JAXB. The other news: we need to tune our own JAXB its very slow on large messages. Paul - 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: [Vote][Axis2] Isuru Eranga Suriarachchi as a committer
JSON is a welcome addition to axis2 , +1 Robert On 1/31/07, Thilina Gunarathne [EMAIL PROTECTED] wrote: Hi All, I would like to propose Isuru Eranga Suriarachchi as an Apache Axis2/java committer. Isuru started with improving and contributing to Axis2 documentation. Later he implemented JSON support for Axis2 and has been adding more and more features. I am confident that he will contribute to more and more areas in Axis2. His knowledge on Axiom Axis2 (Specially the transport layers) would help us a lot in the future. Following are his contributions so far, http://marc.theaimsgroup.com/?l=axis-devw=2r=1s=Isuru+Eranga+Suriarachchiq=b Here is my vote: +1 Thanks, Thilina... -- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.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: Doubts about Axis2
This is a common error. Take a look at this article for the answer. http://wso2.org/library/104 Robert On 1/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, I'm a web developers and I'm using axis2-1.1 to developer a web service, I have developed in axis1.2 and I did'nt have any problems, but now I'm trying to useaxis2... I'm trying to deploy a WebService with Axis2 (MyService, with method echo and ping), and I am having many problems. 1. With services.xml, if I use the services.xml of the example, I have got the follow error: descriptionUnable to generate WSDL for this service/description reasonIf you wish Axis2 to automatically generate the WSDL, then please use one of the RPC message receivers for the service(s)/operation(s) in services.xml. If you have added a custom WSDL in the META-INF directory, then please make sure that the name of the service in services.xml (/serviceGroup/service/@name) is the same as in the custom wsdl's service name (/wsdl:definitions/wsdl:service/@name)./ reason I think that the error is caused bythe option messageReceiver (org.apache.axis2.receivers.RawXMLINOutMessageReceiver), but in the directory lib/ I have got axis2-kernel-1.1.jar, and the class RawXMLINOutMessageReceiver appears. 2. Then, I've changed the options messageReceiver, and I'veput: operation name=echo messageReceiver class= org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver/ actionMappingurn:echo/actionMapping /operation operation name=ping messageReceiver class= org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ actionMappingurn:ping/actionMapping /operation Now, with the change it generate the wsdl correctly. And continue... Is thisthe solution?? because after de client give me a error, and I don't know if this error is caused by this change. Thanks Regards: Esther Capilla Cuide el medio ambiente, no imprima este correo si no es necesario. * AVISO LEGAL * Este mensaje y sus documentos anexos son privados y confidenciales y estan dirigidos exclusivamente a sus destinatarios. Si por error, ha recibido este mensaje y no se encuentra entre los destinatarios, por favor, no use, informe, distribuya, imprima o copie su contenido por ningun medio. Le rogamos lo comunique al remitente y borre todo su contenido. La empresa no asume ningun tipo de responsabilidad legal por el contenido de este mensaje. Cualquier opinion manifestada en el pertenece solo al autor y no representa necesariamente la opinion de la compañÃa salvo que expresamente se especifique lo contrario. Please do not print this message to preserve environment. * DISCLAIMER ** This message and its attached files may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any other information herein. If you have received this message in error, please notify the sender immediately by reply e-mail and delete this message. The company does not assume any legal responsability for the contents of this message. Any opinion contained in it belongs exclusively to its author and does not necessarily represent the company's opinion unless it is specifically expressed on the contrary. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1998) EJB provider is not available for Axis2
[ https://issues.apache.org/jira/browse/AXIS2-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465829 ] robert lazarski commented on AXIS2-1998: Eranga, I looked briefly at the code and it looks promising. I think it would be cool if we gave axis2 users the option of using EJB if they choose to do so. Although this is a port from axis 1.x , a lot has happened since then. Frankly, the EJB provider never was widely used, perhaps because lack of docs and integration with the popular containers. I have however used EJB and axis 1.x (forked) alot with JBoss which didn't use the EJBProvider, and have some questions: 1) Do you have working code or test cases with this patch ? 2) Have you considered how this patch would integrate with popular containers such as JBoss and geronimo ? 3) EJB 3.0 ? The JAX-WS folks may also have plans here. 4) Perhaps we could delegate the responsibility of loading the EJB and its JNDI bindings to the container ? If we did that, we could also perhaps avoid extending every MR and make this a lot less work. I'm thinking ServiceObjectSupplier or something like that. Not sure if its possible yet, but its worth exploring. In short, what you have may work but I question if it would get much use. Looking forward to working with you to get the code committed, barring objections from the list. EJB provider is not available for Axis2 --- Key: AXIS2-1998 URL: https://issues.apache.org/jira/browse/AXIS2-1998 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: rpc Affects Versions: nightly Reporter: Eranga Jayasundera Priority: Minor Fix For: nightly Attachments: ejb_msg_recvr.patch Axis 1 comes with an EJB provider. But there is no EJB provider in Axis2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Just a thought
Is this an example of what you may have in mind? http://ws.apache.org/axis2/1_1/spring.html#262 HTH, Robert On 12/29/06, Ivan Latysh [EMAIL PROTECTED] wrote: Hello All, Just want to express my gratitude to all developers who is working on the project. You have done a great job ! While browsing AXIS2 code-base and mailing list I noticed some minor issues that any project has, they are insignificant and fixable, but also I noticed one large issue that (AFAIK) hasn't been addresses well enough. And I can be mistaken, but I just want to point to it. I noticed that AXIS2 does not have defined service impl. lifecycle. We can see bit's and pieces from it all over, but no concrete definition (I refer to init() method, ServiceLifeCycle interface, etc.) From mailing list I can see that many users are confused by absence of defined lifecycle. I belive that this can be solved easy with little (or none) code refactoring. For instance let's take Apache Avalon framework, and we don't even need an implementation, just interfaces (just 28k jar). Or if dev. team don't want to bring on board one more framework, just create AXIS2 own lifecycle interfaces. Now when service impl want to be aware of different events it should implement an interface. So init() method will be defined in Initializable interface, ConfigurationContext will be given when service implement Configurable interface, when service want to know about MessageContext it implement Contextualizable. Also the great asset is to serve impl. with binding events (not data binding) when impl. bound to the request, axis session or transport session. So the beauty of this approach that existing services with just a business method will be unaffected, but it will give an extra power to the AXIS2 since developers will benefit from defined lifecycle. Anyway I would like to hear if developers are interesting in proposed solution. -- Best regards, Ivan 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: qn reg. axis2 on RAD 6.0
You are following the axis2 web.xml that configures the axis2 servlet, right? I would try your custom war on something simpler like tomcat to verify that its indeed a websphere issue. I often do custom wars myself with axis2 and it takes a few tries to get it right. Its been a while since I used websphere, but all app servers have a way to delegate the jars that are used by the war to have preference over any that are in a higher classloader. If you still have the problem after the above, I would try that to see if that helps. Robert On 12/27/06, Prasad Sarma [EMAIL PROTECTED] wrote: hi All, I am starting to work on axis2. I am working on WebSphere 5.1 test environment on RAD6,I installed 2 plugins for axis2 ..java2wsdl and service archive and I have created a webservice and created aar file from it . Now I want to deploy this webservice on my current web application. I am having trouble deploying this aar file. Could some body please help me where I am going wrong. Here is what I have done so far. In my web application 1. I have created a 'services' folder under WEB-INF which I declared as repository for axis2 and kept my aar file and version.aar file, services.list in it, I listed both aars in services.list 2. I copied jars from axis2-war ( that I downloaded from axis2 website and extracted libraries) to WEB-INF/lib of my web application 3. I created a 'conf' directory in WEB-INF and placed axis2.xml in that folder 4. I placed the entry for axis2 servlet in my web.xml as -- servlet servlet-nameAxisServlet/servlet-name display-nameApache-Axis Servlet/display-name servlet-class org.apache.axis2.transport.http.AxisServlet /servlet-class init-param param-nameaxis2.xml.path/param-name param-value/WEB-INF/conf/axis2.xml/param-value /init-param init-param param-nameaxis2.xml.url/param-name param-valuehttp://localhost:9080/myrepo/axis2.xml/param-value /init-param init-param param-nameaxis2.repository.path/param-name param-value/WEB-INF/param-value /init-param init-param param-nameaxis2.repository.url/param-name param-valuehttp://localhost:9080/myrepo/param-value /init-param load-on-startup3/load-on-startup /servlet --- and I get an excpetion as -- Did not realize init() exception thrown by servlet AxisServlet: javax.servlet.ServletException -- Some mailing lists have suggested to use axis-1.3 and start from there but is there any way to configure axis2 in my current web application with out going thru axis-1.3 Any help would be greatly appreciated!! Prasad __ 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: Writing your Own Axis2 Module
The phases in axis.xml changes frequently and sometimes the docs don't keep up. Looks like the 'The text in green' part is broken also. Please file a jira. In the meantime, try adding a loggingPhase or what you are basing you code on, right below every soapmonitorPhase in the 1.1 release of axis.xml . This assumes you are following the intent of the module example. One other tip: After a quick glance of the doc it shows how you can add module ref=logging/ to services.xml . Alternatively if you'd like logging to be placed on all services you can place the ref in axis.xml - see where it does that for Addressing if interested. HTH, Robert On 12/11/06, Danny Lin [EMAIL PROTECTED] wrote: I have Axis2 v1.1 and I am learning Axis2 by following through the sample codes. I am working on the userguide sample code. After I built the module, I am supposed to modify the axis2.xml. In this document (http://ws.apache.org/axis2/1_1/modules.html) the Step 4 describes the changes. However, I cannot fing loggingPhase anywhere in the extract of axis2.xml. By comparing the one shown in the document with my installation, here are the differences in the system predefined phases. Note that the RequestURIBasedDispatcher and SOAPActionBasedDispatcher are under different phases. Can someone please explain / help? Thanks. Danny My installation: phase name=Transport handler name=RequestURIBasedDispatcher class=org.apache.axis2.engine.RequestURIBasedDispatcher order phase=Transport/ /handler handler name=SOAPActionBasedDispatcher class=org.apache.axis2.engine.SOAPActionBasedDispatcher order phase=Transport/ /handler /phase Document: phase name=TransportIn/ phase name=Dispatch class=org.apache.axis2.engine.DispatchPhase handler name=AddressingBasedDispatcher class=org.apache.axis2.engine.AddressingBasedDispatcher order phase=Dispatch/ /handler handler name=RequestURIBasedDispatcher class=org.apache.axis2.engine.RequestURIBasedDispatcher order phase=Dispatch/ /handler handler name=SOAPActionBasedDispatcher class=org.apache.axis2.engine.SOAPActionBasedDispatcher order phase=Dispatch/ /handler handler name=SOAPMessageBodyBasedDispatcher class=org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher order phase=Dispatch/ /handler handler name=InstanceDispatcher class=org.apache.axis2.engine.InstanceDispatcher order phase=PostDispatch/ /handler /phase - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Writing your Own Axis2 Module
http://issues.apache.org/jira/ Create a login for yourself and then create an issue under Axis2 As for the module doc, its probably fine except for the phases part - you just need to put your in, out, inFault, and outFault phases under the soapMonitor phase and my bet is it will work. However, you could look at the soap monitor for a full working example since its fairly simple. There are docs for it, a module, and you could look at the source distro for more info. HTH, Robert On 12/11/06, Danny Lin [EMAIL PROTECTED] wrote: Thank you, Robert. Please tell me how I can file a jira. Also, can you provide a correct loggingPhase sample or point me to a doc where I can see how they relate? I am VERY new to the AXIS2 world (only about two weeks...) Thanks again. Danny -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Monday, December 11, 2006 2:56 PM To: axis-dev@ws.apache.org Subject: Re: Writing your Own Axis2 Module The phases in axis.xml changes frequently and sometimes the docs don't keep up. Looks like the 'The text in green' part is broken also. Please file a jira. In the meantime, try adding a loggingPhase or what you are basing you code on, right below every soapmonitorPhase in the 1.1 release of axis.xml . This assumes you are following the intent of the module example. One other tip: After a quick glance of the doc it shows how you can add module ref=logging/ to services.xml . Alternatively if you'd like logging to be placed on all services you can place the ref in axis.xml - see where it does that for Addressing if interested. HTH, Robert On 12/11/06, Danny Lin [EMAIL PROTECTED] wrote: I have Axis2 v1.1 and I am learning Axis2 by following through the sample codes. I am working on the userguide sample code. After I built the module, I am supposed to modify the axis2.xml. In this document (http://ws.apache.org/axis2/1_1/modules.html) the Step 4 describes the changes. However, I cannot fing loggingPhase anywhere in the extract of axis2.xml. By comparing the one shown in the document with my installation, here are the differences in the system predefined phases. Note that the RequestURIBasedDispatcher and SOAPActionBasedDispatcher are under different phases. Can someone please explain / help? Thanks. Danny My installation: phase name=Transport handler name=RequestURIBasedDispatcher class=org.apache.axis2.engine.RequestURIBasedDispatcher order phase=Transport/ /handler handler name=SOAPActionBasedDispatcher class=org.apache.axis2.engine.SOAPActionBasedDispatcher order phase=Transport/ /handler /phase Document: phase name=TransportIn/ phase name=Dispatch class=org.apache.axis2.engine.DispatchPhase handler name=AddressingBasedDispatcher class=org.apache.axis2.engine.AddressingBasedDispatcher order phase=Dispatch/ /handler handler name=RequestURIBasedDispatcher class=org.apache.axis2.engine.RequestURIBasedDispatcher order phase=Dispatch/ /handler handler name=SOAPActionBasedDispatcher class=org.apache.axis2.engine.SOAPActionBasedDispatcher order phase=Dispatch/ /handler handler name=SOAPMessageBodyBasedDispatcher class=org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher order phase=Dispatch/ /handler handler name=InstanceDispatcher class=org.apache.axis2.engine.InstanceDispatcher order phase=PostDispatch/ /handler /phase - 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] building src distribution
Well that's not the command I typically use - and I just tried it and it didn't work for me either. Please help us by filing a jira. In the meantime, try this one: maven clean release jar -Dmaven.test.skip=true That will create everything ... my guess is you'd rather not run the tests, otherwise remove the skip command. HTH, Robert On 11/23/06, Jeremy Hughes [EMAIL PROTECTED] wrote: Hi, I just tried building the source distribution - I took instructions from here: http://ws.apache.org/axis2/faq.html#d4 the line in the table says: maven dist-std-bin Will generate the source version of Axis2 standard distribution so I guess that should be maven dist-std-src but maven complained that dist-std-src doesn't exist. Also dist-std-bin doesn't exist. This is the output: $ maven dist-std-bin __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-2 DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml Attempting to download maven-test-plugin-1.8.1-SNAPSHOT.jar. Attempting to download maven-multiproject-plugin-1.5-SNAPSHOT.jar. Attempting to download maven-jar-plugin-1.8-SNAPSHOT.jar. Attempting to download maven-plugin-plugin-1.8-SNAPSHOT.jar. [echo] 1.5 [echo] JDK 1.5 detected, including the following modules: modules/jaxbri/project.xml,modules/jaxws/project.xml BUILD FAILED Goal 'dist-std-bin' does not exist in this project. Total time : 14 seconds Finished at : 23 November 2006 22:39:08 GMT Any ideas? Thanks, Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1759) Remove spring 1.2.8 jars from axis2.war
Remove spring 1.2.8 jars from axis2.war --- Key: AXIS2-1759 URL: http://issues.apache.org/jira/browse/AXIS2-1759 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Affects Versions: 1.1 Environment: linux, java 5 Reporter: robert lazarski The spring 1.2.8 jars were removed from the 1.1 distro, but not the 1.1 war. We voted on this a few times: http://marc.theaimsgroup.com/?l=axis-devm=116084350619596w=2 The axis2-spring*.jar should be the only spring related jar in both the std distro and the war. However, the spring 1.2.8 jars still need to be maven deps as unit tests depend on them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-892) Need Documentation for MTOM data binding
[ http://issues.apache.org/jira/browse/AXIS2-892?page=comments#action_12449429 ] robert lazarski commented on AXIS2-892: --- Thilina, just tried to run the WSDL in the ADB section, and got: Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/import): faultCode=INVALID_WSDL: Encountered illegal extension attribute 'schemaLocation'. Extension attributes must be in a namespace other than WSDL's. Eclipse's WST WSDL Validator is showing: cvc-complex-type.3.2.2: Attribute 'schemaLocation' is not allowed to appear in element 'import'.mtomExample.wsdlmtom_adb3 line 15 13 de Novembro de 2006 14:35:48 813739 cvc-complex-type.4: Attribute 'location' must appear on element 'import'. mtomExample.wsdl Need Documentation for MTOM data binding Key: AXIS2-892 URL: http://issues.apache.org/jira/browse/AXIS2-892 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: documentation Reporter: Thilina Gunarathne Assigned To: Thilina Gunarathne Priority: Minor There seems to be lot of questions in the mailing list regarding MTOM data binding. It'll be great if we can provide a guide or a sample for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (AXIS2-892) Need Documentation for MTOM data binding
Inside the ADB section in xdocs/1_1/mtom-guide.htmlOn 11/13/06, Davanum Srinivas (JIRA) [EMAIL PROTECTED] wrote: [ http://issues.apache.org/jira/browse/AXIS2-892?page=comments#action_12449431 ]Davanum Srinivas commented on AXIS2-892:which wsdl?-- dims Need Documentation for MTOM data binding Key: AXIS2-892 URL: http://issues.apache.org/jira/browse/AXIS2-892 Project: Apache Axis 2.0 (Axis2)Issue Type: ImprovementComponents: documentation Reporter: Thilina Gunarathne Assigned To: Thilina GunarathnePriority: Minor There seems to be lot of questions in the mailing list regarding MTOM data binding. It'll be great if we can provide a guide or a sample for this.--This message is automatically generated by JIRA.-If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa -For more information on JIRA, see: http://www.atlassian.com/software/jira- To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Resolved: (AXIS2-892) Need Documentation for MTOM data binding
Looks great Thilina. I'm doubtful however the xmlbeans section is working though and after giving it a new spin I may take the section out if I run into problems. On 11/11/06, Thilina Gunarathne (JIRA) [EMAIL PROTECTED] wrote: [ http://issues.apache.org/jira/browse/AXIS2-892?page=all ]Thilina Gunarathne resolved AXIS2-892.-- Resolution: FixedDone...Used the XMLBeans MTOM data binding part as the template :).. Need Documentation for MTOM data binding Key: AXIS2-892 URL: http://issues.apache.org/jira/browse/AXIS2-892 Project: Apache Axis 2.0 (Axis2)Issue Type: ImprovementComponents: documentationReporter: Thilina Gunarathne Assigned To: Thilina GunarathnePriority: Minor There seems to be lot of questions in the mailing list regarding MTOM data binding. It'll be great if we can provide a guide or a sample for this.--This message is automatically generated by JIRA. -If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa-For more information on JIRA, see: http://www.atlassian.com/software/jira-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-892) Need Documentation for MTOM data binding
[ http://issues.apache.org/jira/browse/AXIS2-892?page=comments#action_12448497 ] robert lazarski commented on AXIS2-892: --- Thilina, just a reminder that the mtom guide still has a databinding section that isn't correct. I tried to look into this per my last comment a few weeks ago but was I not successful. We should either update the doc or remove the section for 1.1 . Need Documentation for MTOM data binding Key: AXIS2-892 URL: http://issues.apache.org/jira/browse/AXIS2-892 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: documentation Reporter: Thilina Gunarathne Assigned To: Thilina Gunarathne Priority: Minor There seems to be lot of questions in the mailing list regarding MTOM data binding. It'll be great if we can provide a guide or a sample for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.1-RC2 Release
The RC2 release has the springframework 1.2.8 jars in the WAR, which we voted to take out. These jars are needed for the unit tests, but should not be included in the release for reasons we agreed to such as size and the new springframework 2.0 release. The one jar that should remain is our axis2-spring-1.1-*.jar . Thanks, RobertOn 11/3/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Yep!On 11/3/06, Anthony Elder [EMAIL PROTECTED] wrote: This is still using a few snapshot jars - axiom, neethi, wss4j and XmlSchema - is that going to be changed in the final release? ...ant Thilina Gunarathne [EMAIL PROTECTED] on 02/11/2006 12:20:46 Please respond to axis-dev@ws.apache.org To:axis-dev@ws.apache.org, axis-user@ws.apache.org cc: Subject:[Axis2] Axis2 1.1-RC2 Release Hi all, I uploaded the Axis2 1.1 RC2 release artifacts to the following locations. Please help us by downloading and reviewing them. Download locations : * binary and source distributions - http://people.apache.org/~thilina/axis2/1.1-RC2/ * 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-RC2/plugins/ I uploaded a subset of Axis2 site for the benefit of the folks who are going to try out Axis2 1.1-RC2. Some links may not be working. We apologize for the inconvenience. Constructive feedback on the docs are most welcome. * Temporary site http://people.apache.org/~thilina/axis2/docs/ Please note that these releases do not include xdocs which will be available with 1.1 release as usual. Thanks, Thilina -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.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]--Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)-To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote][Axis2] Nikhil Thaker as a Committer
+1 to Nikhil On 11/3/06, Eran Chinthaka [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: +1 from me. Wish Nikhil was more prolific on the mailing list as well :)+1 from me too.BTW, I don't see that much of discussions on JAX-WS stuff in the devmailing list. Rich, can you please give us some status on that, and perhaps that might help Thilina to add some info about our JAX-WS progress.(I do not wanna highjack this voting thread. So answering to the abovequestion in a separate thread is appreciated :) )-- Chinthaka
Re: [Axis2] Shouldn't the war be included in the release?
Hmm, I found the build.xml which has a default task of creating the war, and I get: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp ant Buildfile: build.xml init: prepare.repo: BUILD FAILED /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp/build.xml:31: The pathconvert type doesn't support the nested flattenmapper element. I'm using ant 1.6.2 As for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java ... kool, although my trusty old ant task calling WSDLJava directly still works so that's good enough for me. Anyways ... why isn't the war in the release? I thought we agreed to that. And I see no docs for axis2.sh . Robert On 10/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote: search for build.xml, run ant in that directory... axis2.sh is a helperExample i use it for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java to run w2j :) it basically sets up the classpath and then you can invoke any class. Another use is to run say a client class that needs axis2 classpath set up. -- dims On 10/27/06, robert lazarski [EMAIL PROTECTED] wrote: Hi all, I just built axis2 from the latest svn the way I always do: maven clean release That way I get the std-bin and the war. This however no longer produces the war. I thought we agreed that we are going to include the war in the release? Secondly, I remember some talk about a script to generate the war. I found axis2.sh in the bin directory. Its not clear what this does either from the comments or the source. When I run it I get a confused jvm: /axis2.sh Using AXIS2_HOME: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT Using JAVA_HOME: /usr/local/jdk1.5.0_08 Usage: java [-options] class [args...] So I see no new way in the faq to generate the war, and I see nowhere in xdocs anything on axis2.sh . What am I missing? Robert - 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: [Vote][Axis2] Amila, Keith and Sandakith as committers
+1 for all three of them. Robert On 10/25/06, Rajith Attapattu [EMAIL PROTECTED] wrote: +1 from me to all 3 -Rajith On 10/25/06, Ruchith Fernando [EMAIL PROTECTED] wrote: +1 from me for all of them. Thanks, Ruchith On 10/25/06, Eran Chinthaka [EMAIL PROTECTED] wrote: Hi, Time to welcome fresh blood in to Axis2 :). Amila, Sandakith and Keith were involved in various areas of Axis2 and have been contributing very much to the project. *Amila Suriarachchi* - He was involved mainly on our most interesting area, codegen and ADB. He had done very good amount of work, and I'm pretty much sure he has a very good understanding on Ajith's magic code inside codegen. I hope he will continue to help us to improve codegen and ADB related issues leading those modules. (God bless Amila :) ) See here for his contributions so far : http://marc.theaimsgroup.com/?l=axis-devw=2r=1s=%22Amila+Suriarachchi *Sandakith Gallage* - Sandakith started with improving and contributing to Axis2 and Axiom documentation. Later he cleaned up Axis2 Eclipse plugin and has taken that to a decent state. I hope he will contribute to more and more areas in Axis2. See here for his contributions so far : https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truequery=Sandakith+sandakithsummary=truedescription=truebody=true *Keith Godwin Chapman* : He was mainly involved in Axis2 Idea plugin and has put some serious efforts on making it work. See here for his contributions so far : http://marc.theaimsgroup.com/?l=axis-devw=2r=1s=keith+chapmanq=b Here is my +1 for all three of them. Thanks, Chinthaka -- www.ruchith.org - 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]
[jira] Created: (AXIS2-1472) Options javadoc references old BASIC_AUTHENTICATION constants
Options javadoc references old BASIC_AUTHENTICATION constants - Key: AXIS2-1472 URL: http://issues.apache.org/jira/browse/AXIS2-1472 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: documentation Affects Versions: 1.1 Environment: java 5, linux Reporter: robert lazarski Lines 605-610 of modules/kernel/src/org/apache/axis2/client/Options.java show references to BasicAuthentication and BASIC_AUTHENTICATION , which no longer exist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ServiceLifeCycle changes
I personally don't need ConfigurationContext ... as you can see from
the code below, its ignored.
public void startUp(ConfigurationContext ignore, AxisService service) {
System.out.println(Starting spring init);
ClassLoader classLoader = service.getClassLoader();
ClassPathXmlApplicationContext appCtx = new
ClassPathXmlApplicationContext(new String[]
{applicationContext.xml}, false);
appCtx.setClassLoader(classLoader);
appCtx.refresh();
if (logger.isDebugEnabled()) {
logger.debug(\n\nstartUp() set spring classloader via
axisService.getClassLoader() ... );
}
System.out.println(spring loaded);
}
Now of course someone might need ConfigurationContext. Can you think
of an easy way to solve both cases, ie, startUp() called from
ServiceBuilder that does not have ConfigurationContext, and startUp()
- overloaded or another interface, etc - that includes
ConfigurationContext ?
Thanks for the help, much appreciated,
Robert
On 10/18/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Robert;
The only place that I can call startUp method is at the deployment
engine, I can modify the code to call startUp method at the
ServiceBuilder level. But the problem is that does not have access to
configuration context.
robert lazarski wrote:
Tried the two services in a service group idea, but unfortunately, the
MR is invoked before startUp() in seemingly all cases. So it loads the
MR and throws an exception, next startUp() loads the config, and then
subsequent calls will work. Still, we'd rather not have an exception
on start up.
Thanks,
Robert
On 10/15/06, robert lazarski [EMAIL PROTECTED] wrote:
OK, I can now get startUp() to work, thanks. But startUp() happens
_after_ the MR is processed. Why is that?
The use case is this: startUp() inits a dependancy that the MR will
need. The way it is now, the MR will throw because startUp() is called
after the MR is processed.
One work around I suppose is two have two services in one
ServiceGroup, one that does nothing but have startUp() , and the other
that uses the MR. I don't think that is really the right solution
though.
Thanks for working with me on this. Here's my stacktrace that shows
the problem. Notice the
'Starting spring init' after the exception, which is a print
statement in the first line in startUp(). Also I want to clarify what
I'm trying to do here is a user space way to load spring inside an AAR
- it has nothing to do with the Spring code inside Axis2 which is
working fine.
2006-10-15 12:59:59,027 [org.apache.axis2.deployment.ServiceBuilder] -
Error in schema generating null
java.lang.reflect.InvocationTargetException
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.axis2.deployment.util.Utils.fillAxisService(Utils.java:248)
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:266)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:91)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:83)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:117)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:533)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:200)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:210)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:157)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:84)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:256)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:359)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:304)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4201)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759
[jira] Created: (AXIS2-1446) MTOM docs reference old axiom code
MTOM docs reference old axiom code -- Key: AXIS2-1446 URL: http://issues.apache.org/jira/browse/AXIS2-1446 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: documentation Affects Versions: 1.1 Environment: java 5, linux Reporter: robert lazarski Lines 170-184 of the mtom-guide.html reference old axiom classes ImageDataSource and ImageIO , which no longer exist . Seemingly the docs should now reference the axiom classes FileDataSource and Attachments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-892) Need Documentation for MTOM data binding
[
http://issues.apache.org/jira/browse/AXIS2-892?page=comments#action_12443317 ]
robert lazarski commented on AXIS2-892:
---
Looking into this, I don't understand how
parse(javax.xml.stream.XMLStreamReader reader) can resolve the constant
IS_DATA_HANDLERS_AWARE :
boolean isReaderMTOMAware = false;
try{
System.out.println(isReaderMTOMAware test);
isReaderMTOMAware =
java.lang.Boolean.TRUE.equals(reader.getProperty(org.apache.axiom.om.OMConstants.IS_DATA_HANDLERS_AWARE));
}catch(java.lang.IllegalArgumentException e){
System.out.println(isReaderMTOMAware is false);
isReaderMTOMAware = false;
}
This always returns false for me. The javax.xml.stream.XMLStreamReader is
comming from stax-api-1.0.1.jar and codehaus - yet Ajith says:
In XMLStreamReader implementations provided by AXIOM, the getProperty method
returns the Boolean.TRUE object for the key
org.apache.axiom.om.OMConstants.IS_DATA_HANDLERS_AWARE
(IsDatahandlersAwareParsing) .
The axiom distro doesn't seem to provide a XMLStreamReader . If I can get this
to work I 'll add it to the mtom docs.
Need Documentation for MTOM data binding
Key: AXIS2-892
URL: http://issues.apache.org/jira/browse/AXIS2-892
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: documentation
Reporter: Thilina Gunarathne
Assigned To: robert lazarski
Priority: Minor
There seems to be lot of questions in the mailing list regarding MTOM data
binding. It'll be great if we can provide a guide or a sample for this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1448) ServiceLifeCycle.startUp should happen before MessageReciever processing
ServiceLifeCycle.startUp should happen before MessageReciever processing Key: AXIS2-1448 URL: http://issues.apache.org/jira/browse/AXIS2-1448 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Environment: linux, java 5 Reporter: robert lazarski Assigned To: Deepal Jayasinghe If ServiceLifeCycle.startUp inits a dependency that the MR needs, there will be an exception on server startup . The pasted stack trace below happens before the first print statement in startUp() , Starting spring init . It'd be helpful if startUp() is called before the MR: Error in schema generating null java.lang.reflect.InvocationTargetException 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.axis2.deployment.util.Utils.fillAxisService(Utils.java:248) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:266) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:91) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:83) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:117) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:533) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:200) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:210) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:157) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:84) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:256) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:359) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:304) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4201) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:709) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) 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.startup.Bootstrap.start(Bootstrap.java:294) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) Caused by: org.apache.axis2.AxisFault: Axis2 Can't find Spring's ApplicationContext; nested exception is: java.lang.Exception: Axis2 Can't find Spring's ApplicationContext at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318) at org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier.getServiceObject
Re: ServiceLifeCycle changes
Tried the two services in a service group idea, but unfortunately, the MR is invoked before startUp() in seemingly all cases. So it loads the MR and throws an exception, next startUp() loads the config, and then subsequent calls will work. Still, we'd rather not have an exception on start up. Thanks, Robert On 10/15/06, robert lazarski [EMAIL PROTECTED] wrote: OK, I can now get startUp() to work, thanks. But startUp() happens _after_ the MR is processed. Why is that? The use case is this: startUp() inits a dependancy that the MR will need. The way it is now, the MR will throw because startUp() is called after the MR is processed. One work around I suppose is two have two services in one ServiceGroup, one that does nothing but have startUp() , and the other that uses the MR. I don't think that is really the right solution though. Thanks for working with me on this. Here's my stacktrace that shows the problem. Notice the 'Starting spring init' after the exception, which is a print statement in the first line in startUp(). Also I want to clarify what I'm trying to do here is a user space way to load spring inside an AAR - it has nothing to do with the Spring code inside Axis2 which is working fine. 2006-10-15 12:59:59,027 [org.apache.axis2.deployment.ServiceBuilder] - Error in schema generating null java.lang.reflect.InvocationTargetException 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.axis2.deployment.util.Utils.fillAxisService(Utils.java:248) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:266) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:91) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:83) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:117) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:533) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:200) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:210) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:157) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:84) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:256) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:359) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:304) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4201) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:709) at org.apache.catalina.startup.Catalina.start(Catalina.java:551) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
Re: [axis2] dist packaging incorrect
Its been the way it is for several months I believe. I have a script that I've been using to update my environment after a build - particuarly std-bin - and nothings changed recently. It is nicer to have a root dir created though. Robert On 10/14/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: I'm offline so can't open a JIRA. It seems to me the packaging of Axis2 distro is not right. When you unpack the std bin dist I expect to get a directory called axis2-1.1 (-RC1 for now) and the stuff to be underneath that. The root dir is missing right now. 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: ServiceLifeCycle changes
is: java.lang.Exception: Axis2 Can't find Spring's ApplicationContext at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318) at org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier.getServiceObject(SpringAppContextAwareObjectSupplier.java:61) ... 44 more Caused by: java.lang.Exception: Axis2 Can't find Spring's ApplicationContext at org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier.getServiceObject(SpringAppContextAwareObjectSupplier.java:51) ... 44 more Starting spring init On 10/14/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: your services.xml should look like below; service name=SampleService3 class=org.apachecon.us.sample.ServiceLifeCycleImpl parameter name=ServiceClass locked=false org.apachecon.us.sample.SampleService3/parameter /service robert lazarski wrote: Hi all, I'm trying to test the latest svn with spring inside the aar via startUp() . This was working a few days ago with startUp() in the Service interface. Anyways, ServiceLifeCycle seems to work by reflection so I have a services.xml like so: serviceGroup service name=SpringInit description This is a sample spring init service /description parameter name=ServiceClass locked=falsespring.SpringInit/parameter operation name=springInit messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service service name=SpringAwareService description simple spring example - inside the AAR /description !-- need the TCCL param when using spring inside the AAR -- parameter name=ServiceTCCL locked=falsecomposite/parameter parameter name=ServiceObjectSupplier locked=falseorg.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier/parameter parameter name=SpringBeanName locked=falsespringAwareService/parameter operation name=getValue messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service /serviceGroup So the idea is that spring.SpringInit implements ServiceLifeCycle and will load the spring config via startUp() . And not until a client invokation the MR of SpringAwareService will be called. What I'm seeing though is the SpringAwareService MR is being called on server start, even though I have not declared any scope. And ServiceLifeCycle.startUp() is not called ever. The MR was never invoked on server start before with the default scope IIRC. This is generating a stack trace on server start as : 2006-10-13 15:07:00,997 [org.apache.axis2.deployment.ServiceBuilder] - Error in schema generating null java.lang.reflect.InvocationTargetException 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.axis2.deployment.util.Utils.fillAxisService(Utils.java:243) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:266) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:91) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:83) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:117) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:533) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:200) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:210) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:157) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:84) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:359) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:304) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3880) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4141) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild
Re: [Axis2] What to include in the Axis2 1.1 distributions??
Just to clarify, what I believe Dims and I agreed to via +1 was to remove all the spring jars from the war , and place just one 4K jar inside the std-bin dist - axis2-spring*.jar - which has the axis2 code to tie together spring and axis2 . Robert On 10/14/06, Ajith Ranabahu [EMAIL PROTECTED] wrote: Hi, And provide all aditional dependacncies of Axis2 as a one zip file from the site. Or add a minmial standard and exteneded distribution. I agree with Srinath in this. My guess is there would be users who want everything and some would want most of it but not all. Right now we have standard and minimal distributions so how about having 1. minimal 2. standard 3. full (complete) distributions ? I guess we should include a clear description of what is in and what is not in the distribution page (http://ws.apache.org/axis2/download/1_0/download.cgi). Right now what I feel is minimal to be an embeddable version with absolutely needed libs, standard to be the 80% case with most of the needed jars (hence the discussion in this thread applies to the standard distro) and complete with all the stuff in one package. Thoughts ? Ajith On 10/14/06, Srinath Perera [EMAIL PROTECTED] wrote: Just looked at the std distribution .. we have 3 axom jars 10 Axis2 jars !!! Lets bring them down to two jars .. Most of these axis2 jars are small. So no harm putting everything in the one jar I would say 1) Get rid of bcel-5.2.jar 2) jaxme-* 3) spring-* And provide all aditional dependacncies of Axis2 as a one zip file from the site. Or add a minmial standard and exteneded distribution. Thanks Srinath -- 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] What to include in the Axis2 1.1 distributions??
IMHO: 1) None of the spring stuff should be included in the WAR. These jars might be placed inside the AAR if a user chooses to do so, so its really up to the user where to put these jars. This is the way it was and is documented as such. 2) The std-bin distro should not include the spring-* jars that come from the spring framework distro. These are compile deps and runtime deps for the unit tests. The std-bin should only contain axis2-spring-*.jar . This is the way it was and is documented as such. Thanks, Robert On 10/13/06, Thilina Gunarathne [EMAIL PROTECTED] wrote: Hi Devs, We found that we have shipped some unnecessary libraries with the Axis2-RC1 distributions.. I created the following lists to capture what to include, what not to include... Please do review them and add your suggestions.. http://wiki.apache.org/ws/FrontPage/Axis2/axis2_war_build_list http://wiki.apache.org/ws/FrontPage/Axis2/axis2_min_build_list http://wiki.apache.org/ws/FrontPage/Axis2/axis2_std_build_list Thanks, Thilina -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.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]
ServiceLifeCycle changes
Hi all, I'm trying to test the latest svn with spring inside the aar via startUp() . This was working a few days ago with startUp() in the Service interface. Anyways, ServiceLifeCycle seems to work by reflection so I have a services.xml like so: serviceGroup service name=SpringInit description This is a sample spring init service /description parameter name=ServiceClass locked=falsespring.SpringInit/parameter operation name=springInit messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service service name=SpringAwareService description simple spring example - inside the AAR /description !-- need the TCCL param when using spring inside the AAR -- parameter name=ServiceTCCL locked=falsecomposite/parameter parameter name=ServiceObjectSupplier locked=falseorg.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier/parameter parameter name=SpringBeanName locked=falsespringAwareService/parameter operation name=getValue messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service /serviceGroup So the idea is that spring.SpringInit implements ServiceLifeCycle and will load the spring config via startUp() . And not until a client invokation the MR of SpringAwareService will be called. What I'm seeing though is the SpringAwareService MR is being called on server start, even though I have not declared any scope. And ServiceLifeCycle.startUp() is not called ever. The MR was never invoked on server start before with the default scope IIRC. This is generating a stack trace on server start as : 2006-10-13 15:07:00,997 [org.apache.axis2.deployment.ServiceBuilder] - Error in schema generating null java.lang.reflect.InvocationTargetException 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.axis2.deployment.util.Utils.fillAxisService(Utils.java:243) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:266) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:91) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:83) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:117) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:533) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:200) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:210) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:157) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:84) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:359) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:304) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3880) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4141) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:804) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:693) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) at
[axis2] ServiceLifeCycle changes
Forgot the prefix -- Forwarded message -- From: robert lazarski [EMAIL PROTECTED] Date: Oct 13, 2006 3:16 PM Subject: ServiceLifeCycle changes To: axis-dev@ws.apache.org Hi all, I'm trying to test the latest svn with spring inside the aar via startUp() . This was working a few days ago with startUp() in the Service interface. Anyways, ServiceLifeCycle seems to work by reflection so I have a services.xml like so: serviceGroup service name=SpringInit description This is a sample spring init service /description parameter name=ServiceClass locked=falsespring.SpringInit/parameter operation name=springInit messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service service name=SpringAwareService description simple spring example - inside the AAR /description !-- need the TCCL param when using spring inside the AAR -- parameter name=ServiceTCCL locked=falsecomposite/parameter parameter name=ServiceObjectSupplier locked=falseorg.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier/parameter parameter name=SpringBeanName locked=falsespringAwareService/parameter operation name=getValue messageReceiver class=org.apache.axis2.receivers.RawXMLINOutMessageReceiver/ /operation /service /serviceGroup So the idea is that spring.SpringInit implements ServiceLifeCycle and will load the spring config via startUp() . And not until a client invokation the MR of SpringAwareService will be called. What I'm seeing though is the SpringAwareService MR is being called on server start, even though I have not declared any scope. And ServiceLifeCycle.startUp() is not called ever. The MR was never invoked on server start before with the default scope IIRC. This is generating a stack trace on server start as : 2006-10-13 15:07:00,997 [org.apache.axis2.deployment.ServiceBuilder] - Error in schema generating null java.lang.reflect.InvocationTargetException 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.axis2.deployment.util.Utils.fillAxisService(Utils.java:243) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:266) at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:91) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:83) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:117) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:533) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:200) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:210) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:157) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:84) at org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:359) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:304) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3880) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4141) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:804) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:693) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718
Re: [axis2] Spring support broken ?????
I just tested the SpringServletContextObjectSupplier - the servlet
context one - and its working again. Thanks guys. Any ideas on getting
ServletContext from our testing env ? I sure would like to get a unit
test on SpringServletContextObjectSupplier.
I'm testing the new ServiceLifeCycle class on the 'Spring inside the
aar case' now.
Thanks,
Robert
On 10/12/06, Saminda Abeyruwan [EMAIL PROTECTED] wrote:
Hi Rajith,
Dims and myself have done some improvements to Spring to work in a servlet
container.
Please try your test. This will be available in the 1.1 branch Revision:
463340. Will add the changes to the trunk soon.
Saminda
On 10/12/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Rajith,
Could you please test one more time from 1.1 branch. I have a patch
that may work in r463307.
http://svn.apache.org/viewvc?view=revrevision=463307
Basically we were setting the servlet context *AFTER* all the services
got loaded. I changed it to set the context property as soon as
ConfigurationContext is created.
thanks,
dims
On 10/12/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Saminda,
Can you please try to recreate this problem? This could easily turn
into a showstopper for RC2.
thanks,
dims
On 10/11/06, Rajith Attapattu [EMAIL PROTECTED] wrote:
Saminda,
I tried yesterdays nightly and the problem is still there.
Apparently the servlet config is not in the AxisConfiguration
I will try to debug it tomorrow if I have some time.
Regards,
Rajith
On 10/11/06, Saminda Abeyruwan [EMAIL PROTECTED] wrote:
Hi,
AxisServelet#init(ServletConfig config);
Line 309 -- 312 ; ServletConfig has been set, thus, ServletContext
is
available.
Saminda
On 10/11/06, robert lazarski [EMAIL PROTECTED] wrote:
Its late here so I'll take a look tomorrow. In the meantime, the
reason why this wasn't caught is because I'm not sure how to get a
ServletContext from our testing environment or if its even
possible.
There are tests for the non-servlet container config. If someone
knows
how to test the former case please post to the list. I've been
mostly
focused on the latter lately, ie, non-servletContext config inside
the
AAR.
Thanks for catching that Rajith.
Robert
On 10/10/06, Rajith Attapattu [EMAIL PROTECTED] wrote:
Forwarding with the axis2 prefix.
-- Forwarded message --
From: Rajith Attapattu [EMAIL PROTECTED]
Date: Oct 10, 2006 10:17 PM
Subject: Re: Spring support broken ?
To: axis-dev@ws.apache.org
Cc: [EMAIL PROTECTED]
Hi All,
The current spring support fails with the following exception
possibly
due
to the new code change of obtaining the servlet config from the
AxisConfiguration instead from the Message Context.
Caused by: org.apache.axis2.AxisFault: Axis2 Can't find
ServletConfig;
nested exception is:
java.lang.Exception: Axis2 Can't find ServletConfig
at
org.apache.axis2.AxisFault.makeFault
(AxisFault.java:318)
at
org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier.getServiceObject(SpringServletContextObjectSupplier.java
:70)
... 43 more
Caused by: java.lang.Exception: Axis2 Can't find ServletConfig
at
org.apache.axis2.extensions.spring.receivers.SpringServletContextObjectSupplier.getServiceObject(SpringServletContextObjectSupplier.java:53)
... 43 more
Now when I look at the code I see that at revesion 426884 the
code was
obtaining the servlet config from the msgContext.
servletContext servletContext = (ServletContext)
msgContext.getOptions().
getProperty(HTTPConstants.MC_HTTP_SERVLETCONTEXT);
However the head revision was obtaining the servlet config via
the
AxisConfiguration.
ServletConfig servletConfig = (ServletConfig)
axisService.getAxisConfiguration()
.getParameter(HTTPConstants.HTTP_SERVLETCONFIG);
if (servletConfig == null) {
throw new Exception(Axis2 Can't find
ServletConfig);
}
Why did we make the change ??? If we did so are we making sure
that we
populate the AxisConfiguration with the servlet config ?
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
-
To unsubscribe, e-mail
