[jira] Issue Comment Edited: (AXIS2-3003) Unable to engage addressing at client side, want to know the specific location of addressing.mar in the project
[
https://issues.apache.org/jira/browse/AXIS2-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516142
]
tommy edited comment on AXIS2-3003 at 7/27/07 11:50 PM:
Now I added addressing.mar 1.3 manually to the classpath, but the program
popped out the warning 'org.apache.axis2.AxisFault: Time out while waiting for
the server to send the response.' I googled it , all the articles say that may
be the problem of blocking transport, but I've already set it async by
"stub._getServiceClient().getOptions().setUseSeparateListener(true);"
was:
Nothing Suprised happened so far!!
> Unable to engage addressing at client side, want to know the specific
> location of addressing.mar in the project
> ---
>
> Key: AXIS2-3003
> URL: https://issues.apache.org/jira/browse/AXIS2-3003
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
>Affects Versions: 1.2
> Environment: winxp, axis2
>Reporter: tommy
>
> I got the same problem with "Unable to engage module : addressing ", I've
> added the line 'stub._getServiceClient().engageModule(new
> QName("addressing"));' in my client codes. Could anyone be kind to tell where
> I should place addressing-1.2.mar in my class-path. I copyed it everywhere it
> could be, but the program still cannot recognize the .mar file in my project.
> Ask for help, thanks in advance.
> [ Show » ] tommy - [22/Jul/07 11:28 PM ] I got the same problem with "Unable
> to engage module : addressing ", I've added the line
> 'stub._getServiceClient().engageModule(new QName("addressing"));' in my
> client codes. Could anyone be kind to tell where I should place
> addressing-1.2.mar in my class-path. I copyed it everywhere it could be, but
> the program still cannot recognize the .mar file in my project. Ask for help,
> thanks in advance.
--
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] Reopened: (AXIS2-3003) Unable to engage addressing at client side, want to know the specific location of addressing.mar in the project
[
https://issues.apache.org/jira/browse/AXIS2-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tommy reopened AXIS2-3003:
--
Nothing Suprised happened so far!!
> Unable to engage addressing at client side, want to know the specific
> location of addressing.mar in the project
> ---
>
> Key: AXIS2-3003
> URL: https://issues.apache.org/jira/browse/AXIS2-3003
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
>Affects Versions: 1.2
> Environment: winxp, axis2
>Reporter: tommy
>
> I got the same problem with "Unable to engage module : addressing ", I've
> added the line 'stub._getServiceClient().engageModule(new
> QName("addressing"));' in my client codes. Could anyone be kind to tell where
> I should place addressing-1.2.mar in my class-path. I copyed it everywhere it
> could be, but the program still cannot recognize the .mar file in my project.
> Ask for help, thanks in advance.
> [ Show » ] tommy - [22/Jul/07 11:28 PM ] I got the same problem with "Unable
> to engage module : addressing ", I've added the line
> 'stub._getServiceClient().engageModule(new QName("addressing"));' in my
> client codes. Could anyone be kind to tell where I should place
> addressing-1.2.mar in my class-path. I copyed it everywhere it could be, but
> the program still cannot recognize the .mar file in my project. Ask for help,
> thanks in advance.
--
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: Axis 1.4: How to suppress stack trace and hostname in the details of a Soap fault
I looked at that the provided link but I'm still not sure how you suppress the stack trace and hostname from the Soap fault response. Could you be more specific. I did it by modifying the AxisFault class source and recompiling but I'd prefer not to do that. On 7/27/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > axis.development.system > > http://ws.apache.org/axis/java/reference.html > > On 7/27/07, Lord Halbert <[EMAIL PROTECTED]> wrote: > > How do you suppress the stack trace and the hostname from the detail > > section of a soap fault response in Axis 1.4 ? > > > > - > > 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]
[jira] Commented: (AXIS2-2903) Documentation needs to be added regarding Axis2 clustering
[ https://issues.apache.org/jira/browse/AXIS2-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516135 ] Rajith Attapattu commented on AXIS2-2903: - I have added documentation to the 1.3 branch and the trunk. Please review and let me your comments. Regards, Rajith > Documentation needs to be added regarding Axis2 clustering > -- > > Key: AXIS2-2903 > URL: https://issues.apache.org/jira/browse/AXIS2-2903 > Project: Axis 2.0 (Axis2) > Issue Type: Task > Components: documentation >Affects Versions: 1.3 > Environment: Windows XP, JDK 1.5 >Reporter: Chatra Nakkawita >Assignee: Rajith Attapattu >Priority: Critical > Fix For: 1.3 > > > Kindly provide documentation which is lacking on Axis2 1.3 clustering in the > Axis2/Java trunk/xdocs/@axis2_version_dir@ > Also update the documentation Index pages - > https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/@axis2_version_dir@/toc.html > and > https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/@axis2_version_dir@/contents.html > with description and link to the document > Thanks, > Chatra -- 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: Axis 1.4: How to suppress stack trace and hostname in the details of a Soap fault
axis.development.system http://ws.apache.org/axis/java/reference.html On 7/27/07, Lord Halbert <[EMAIL PROTECTED]> wrote: > How do you suppress the stack trace and the hostname from the detail > section of a soap fault response in Axis 1.4 ? > > - > 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]
[jira] Assigned: (AXIS2-3030) SAAJ Implementation - SOAPBodyImpl.toSAAJNode fails when source node has unqualified attribute (at least, with Xerces parser)
[
https://issues.apache.org/jira/browse/AXIS2-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sumedha rubasinghe reassigned AXIS2-3030:
-
Assignee: sumedha rubasinghe
> SAAJ Implementation - SOAPBodyImpl.toSAAJNode fails when source node has
> unqualified attribute (at least, with Xerces parser)
> -
>
> Key: AXIS2-3030
> URL: https://issues.apache.org/jira/browse/AXIS2-3030
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: All
>Reporter: Jeff Faath
>Assignee: sumedha rubasinghe
>Priority: Minor
>
> The SOAPBodyImpl.toSAAJNode contains a bug at this block of code that
> converts the source DOM node attributes to SAAJ element attributes:
> NamedNodeMap domAttrs = domEle.getAttributes();
> for (int i = 0; i < domAttrs.getLength(); i++) {
> org.w3c.dom.Node attrNode = domAttrs.item(i);
> saajEle.addAttribute(new PrefixedQName(attrNode.getNamespaceURI(),
>attrNode.getLocalName(),
>attrNode.getPrefix()),
> attrNode.getNodeValue());
>}
> The problem is that when the current attrNode isn't qualified, the
> getLocalName method returns null (using Xerces parser). Then, when trying to
> create the new PrefixedQName, an exception is thrown for trying to create a
> QName with a null LocalName.
> The solution is to either just use attrNode.getName() (not sure if this is
> thorough enough?) or to test if attrNode is of type AttrNSImpl or AttrImpl.
> If AttrNSImpl, the current block works, otherwise, the getName() must be used
> instead of getLocalName().
--
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-3030) SAAJ Implementation - SOAPBodyImpl.toSAAJNode fails when source node has unqualified attribute (at least, with Xerces parser)
SAAJ Implementation - SOAPBodyImpl.toSAAJNode fails when source node has
unqualified attribute (at least, with Xerces parser)
-
Key: AXIS2-3030
URL: https://issues.apache.org/jira/browse/AXIS2-3030
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Environment: All
Reporter: Jeff Faath
Priority: Minor
The SOAPBodyImpl.toSAAJNode contains a bug at this block of code that converts
the source DOM node attributes to SAAJ element attributes:
NamedNodeMap domAttrs = domEle.getAttributes();
for (int i = 0; i < domAttrs.getLength(); i++) {
org.w3c.dom.Node attrNode = domAttrs.item(i);
saajEle.addAttribute(new PrefixedQName(attrNode.getNamespaceURI(),
attrNode.getLocalName(),
attrNode.getPrefix()),
attrNode.getNodeValue());
}
The problem is that when the current attrNode isn't qualified, the getLocalName
method returns null (using Xerces parser). Then, when trying to create the new
PrefixedQName, an exception is thrown for trying to create a QName with a null
LocalName.
The solution is to either just use attrNode.getName() (not sure if this is
thorough enough?) or to test if attrNode is of type AttrNSImpl or AttrImpl. If
AttrNSImpl, the current block works, otherwise, the getName() must be used
instead of getLocalName().
--
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: [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
>
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> process-classes
>
> jar
>
>
> ${pom.basedir}/target/classes
>
>
>
>
>
> 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]
Axis 1.4: How to suppress stack trace and hostname in the details of a Soap fault
How do you suppress the stack trace and the hostname from the detail section of a soap fault response in Axis 1.4 ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3029) wsd2java no-namespace import error
[ https://issues.apache.org/jira/browse/AXIS2-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodriguez updated AXIS2-3029: -- Description: I have a wsdl that imports a schema with no namespace; I've attached a sample wsdl that generates the error. Trying to generate a client stub fails with both xmlbeans and adb, the error is: Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:103) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:209) ... 2 more Caused by: 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.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: src-resolve.a: Could not find element '[EMAIL PROTECTED]://some.namespace'. Do you mean to refer to the element named AccountBOS? at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:310) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: src-resolve.a: Could not find element '[EMAIL PROTECTED]://some.namespace'. Do you mean to refer to the element named AccountBOS? at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) 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.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:174) I've independently run xmlbeans generation on this and it succeeds, correctly generating AccountBOS in noNamespace. The problem with wsdl2java is that the reference to AccountBOS is being assigned a namespace when it shouldn't be, this is an import, not an include. was: I have a wsdl that imports a schema with no namespace; I've included a sample at the bottom of this email. Trying to generate a client stub fails with both xmlbeans and adb, the error is: Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:103) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:209) ... 2 more Caused by: 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.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: src-resolve.a: Could not find element '[EMAIL PROTECTED]://some.namespace'. Do you mean to refer to the element named AccountBOS? at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:310) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: src-resolve.a: Could not find element '[EMAIL PROTECTED]://some.namespace'. Do you mean to refer to the element named AccountBOS? at org.apache.xmlbeans.impl.schema.SchemaTypeSystem
[jira] Updated: (AXIS2-3029) wsd2java no-namespace import error
[ https://issues.apache.org/jira/browse/AXIS2-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodriguez updated AXIS2-3029: -- Attachment: test.wsdl Sample wsdl that generates error. > wsd2java no-namespace import error > -- > > Key: AXIS2-3029 > URL: https://issues.apache.org/jira/browse/AXIS2-3029 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.2 > Environment: WinXP, jdk1.5 >Reporter: Alex Rodriguez > Attachments: test.wsdl > > > I have a wsdl that imports a schema with no namespace; I've included a sample > at the bottom of this email. Trying to generate a client stub fails with both > xmlbeans and adb, the error is: > Exception in thread "main" > org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) > Caused by: java.lang.RuntimeException: > java.lang.reflect.InvocationTargetException > at > org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:103) > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:209) > ... 2 more > Caused by: 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.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) > ... 3 more > Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: > error: src-resolve.a: Could not find element '[EMAIL > PROTECTED]://some.namespace'. Do you mean to refer to the element named > AccountBOS? > at > org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:310) > ... 8 more > Caused by: org.apache.xmlbeans.XmlException: error: src-resolve.a: Could not > find element '[EMAIL PROTECTED]://some.namespace'. Do you mean to refer to > the element named AccountBOS? > at > org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) > 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.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) > at > org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:174) > I've independently run xmlbeans generation on this and it succeeds, correctly > generating AccountBOS in noNamespace. The problem with wsdl2java is that the > reference to AccountBOS is being assigned a namespace when it shouldn't be, > this is an import, not an include. > > xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/"; > xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/"; > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; > xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/"; > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; > xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:s0="http://some.namespace"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > targetNamespace="http://some.namespace";> > > http://www.w3.org/2001/XMLSchema";> > > > > > > > > > targetNamespace="http://some.namespace"; > xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:acc="http://some.namespace";> > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http"; > style="document"/> > > http://some.namespace/getAccount"; > style="document"/> > > > > > > > > > > > http://localhost:7001/AccountService.jws"/> > > > -- This message is automatically generated by JIRA. - You can reply to
[jira] Created: (AXIS2-3029) wsd2java no-namespace import error
wsd2java no-namespace import error -- Key: AXIS2-3029 URL: https://issues.apache.org/jira/browse/AXIS2-3029 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.2 Environment: WinXP, jdk1.5 Reporter: Alex Rodriguez Attachments: test.wsdl I have a wsdl that imports a schema with no namespace; I've included a sample at the bottom of this email. Trying to generate a client stub fails with both xmlbeans and adb, the error is: Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:256) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:103) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:209) ... 2 more Caused by: 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.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: src-resolve.a: Could not find element '[EMAIL PROTECTED]://some.namespace'. Do you mean to refer to the element named AccountBOS? at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:310) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: src-resolve.a: Could not find element '[EMAIL PROTECTED]://some.namespace'. Do you mean to refer to the element named AccountBOS? at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) 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.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:174) I've independently run xmlbeans generation on this and it succeeds, correctly generating AccountBOS in noNamespace. The problem with wsdl2java is that the reference to AccountBOS is being assigned a namespace when it shouldn't be, this is an import, not an include. http://www.openuri.org/2002/04/soap/conversation/"; xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:s0="http://some.namespace"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; targetNamespace="http://some.namespace";> http://www.w3.org/2001/XMLSchema";> http://some.namespace"; xmlns:s="http://www.w3.org/2001/XMLSchema"; xmlns:acc="http://some.namespace";> http://schemas.xmlsoap.org/soap/http"; style="document"/> http://some.namespace/getAccount"; style="document"/> http://localhost:7001/AccountService.jws"/> -- 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-3018) ServiceDescriptionImpl.updateEndpointDescription() re-creates EndpointDescription objects when portQName is not specified
[ https://issues.apache.org/jira/browse/AXIS2-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516090 ] Roy A. Wood Jr. commented on AXIS2-3018: Hi Jarek, This makes sense for the GET_PORT case (otherwise SEI is null). But this will only work when there is one endpoint for the service description. > ServiceDescriptionImpl.updateEndpointDescription() re-creates > EndpointDescription objects when portQName is not specified > - > > Key: AXIS2-3018 > URL: https://issues.apache.org/jira/browse/AXIS2-3018 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor >Assignee: Ann Robinson > Attachments: AXIS2-3018.patch > > > ServiceDescriptionImpl.updateEndpointDescription() looks for existing > EndpointDescription objects only when portQName is specified. When portQName > is not specified, the updateEndpointDescription() function will create a new > EndpointDescription each time it is called. This can lead to a memory leak > when the client configuration context is reused because somehow the > EndpointDescription objects remain retained (through AxisConfiguration). I > can provide more info on that later. -- 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-3028) Generated ADBBean: Issue with getPullParser() method for optional attributes
Generated ADBBean: Issue with getPullParser() method for optional attributes
Key: AXIS2-3028
URL: https://issues.apache.org/jira/browse/AXIS2-3028
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.2
Reporter: Tobias Jordan
A complexType in my XSD file contains a optional attribute. For example:
The generated ADBBean class Foo_T.java has the following code part in the
getPullParser() method:
attribList.add(new javax.xml.namespace.QName("", "bla"));
attribList.add(localBla.toString());
And here comes the issue:
I wrote a custom handler to print the SOAP messages to stdout:
SOAPEnvelope env = msgContext.getEnvelope();
System.out.println(env.toString());
For messages containing an optional attribute as described above, the
toString() call on the SOAP envelope results in a NullPointerException. The
NullPointer occurs because toString() ends up in the getPullParser() method and
the localBla variable isn't set (since it is optional!).
So I guess there is a missing check against null in the generated code.
--
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-2994) Problem when trying to move service from axis 1.4 to axis 2 1.3RC2
[ https://issues.apache.org/jira/browse/AXIS2-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Kruse updated AXIS2-2994: --- Attachment: TrackLiteDataHandlerWSServiceStub.java TrackLiteDataHandlerWSServiceSkeleton.java Here are the skeleton and stub files... > Problem when trying to move service from axis 1.4 to axis 2 1.3RC2 > -- > > Key: AXIS2-2994 > URL: https://issues.apache.org/jira/browse/AXIS2-2994 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding >Affects Versions: 1.3 > Environment: XP Professional, Tomcat App server 5.5 >Reporter: Steve Kruse >Assignee: Amila Chinthaka Suriarachchi >Priority: Blocker > Fix For: 1.3 > > Attachments: TrackLiteDataHandlerWSServiceMessageReceiverInOut.java, > TrackLiteDataHandlerWSServiceSkeleton.java, > TrackLiteDataHandlerWSServiceStub.java, wsdl_schema.zip > > > I use a wsdl file which works in 1.4 and run it thru wsdl2java in axis2 > 1.3rc2 and everything builds properly. The service deploys fine and then > when I try to use the service I get the following stack trace from the soap > monitor: > > http://schemas.xmlsoap.org/soap/envelope/";> > > > soapenv:Client > org.apache.xmlbeans.impl.values.XmlComplexContentImpl > cannot be cast to > peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument > > > org.apache.axis2.AxisFault: > org.apache.xmlbeans.impl.values.XmlComplexContentImpl cannot be cast to > peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) > at > com.am.service.xmlbeans.TrackLiteDataHandlerWSServiceMessageReceiverInOut.fromOM(TrackLiteDataHandlerWSServiceMessageReceiverInOut.java:322) > at > com.am.service.xmlbeans.TrackLiteDataHandlerWSServiceMessageReceiverInOut.invokeBusinessLogic(TrackLiteDataHandlerWSServiceMessageReceiverInOut.java:42) > at > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42) > at > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:95) > at > org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:276) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:119) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.ClassCastException: > org.apache.xmlbeans.impl.values.XmlComplexContentImpl cannot be cast to > peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument > at > peoiws5.mdiapps.soap.HandleTrackInfoLiteEventDocument$Factory.parse(HandleTrackInfoLiteEventDocument.java:128) > at > com.am.service.xmlbeans.TrackLiteDataHandlerWSServiceMessageReceiverInOut.fromOM(TrackLiteDataHandlerWSServiceMessageReceiverInOut.java:220) > ... 22 more > > > > > > The wsdl I am using is below: > > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > xmlns:impl="urn:soap.mdiapps.peoiws5" > xmlns:c
[jira] Assigned: (AXIS2-3022) Axis2 not handle wsdl deployed to a dir that contains a space (like program files)
[ https://issues.apache.org/jira/browse/AXIS2-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ann Robinson reassigned AXIS2-3022: --- Assignee: Jarek Gawor (was: Ann Robinson) Re-assigning this to Jarek, since he committed the patch. > Axis2 not handle wsdl deployed to a dir that contains a space (like program > files) > -- > > Key: AXIS2-3022 > URL: https://issues.apache.org/jira/browse/AXIS2-3022 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.3 > Environment: winxp + sun jdk 1.5 >Reporter: Lin Sun >Assignee: Jarek Gawor > Fix For: 1.3 > > Attachments: Axis2-3022.patch, Axis2-3022.patch > > > Here is the example I got. Testing a possible fix for this.. > 00:58:38,062 DEBUG [ExceptionFactory] stack:javax.wsdl.WSDLException: > WSDLException: faultCode=WSDL4JWrapper : : Illegal character in path at index > 16: file:/C:/Program > Files/Geronimo/org/apache/geronimo/samples/jws/Calculator/2.0/Calculator-2.0.car/CalculatorService.wsdl > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.(WSDL4JWrapper.java:186) > at > org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupWsdlDefinition(ServiceDescriptionImpl.java:512) > at > org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.(ServiceDescriptionImpl.java:143) > at > org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:101) > at > org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(DescriptionFactory.java:69) > at > org.apache.axis2.jaxws.spi.ServiceDelegate.(ServiceDelegate.java:87) > at > org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:45) > at javax.xml.ws.Service.(Service.java:36) > at > org.apache.geronimo.jaxws.client.GenericService.(GenericService.java:27) > at > org.apache.geronimo.jaxws.client.GenericService$$EnhancerByCGLIB$$ba501ee.() > at > org.apache.geronimo.jaxws.client.GenericService$$EnhancerByCGLIB$$ba501ee$$FastClassByCGLIB$$cb90d621.newInstance() > at > net.sf.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.createServiceProxy(JAXWSServiceReference.java:174) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.getContent(JAXWSServiceReference.java:129) > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:112) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597) > at javax.naming.InitialContext.lookup(InitialContext.java:363) > at org.apache.jsp.addResult_jsp._jspService(addResult_jsp.java:90) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja
[jira] Closed: (AXIS2-3011) ServiceDescription caching leads to memory leak
[ https://issues.apache.org/jira/browse/AXIS2-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ann Robinson closed AXIS2-3011. --- Resolution: Fixed This problem has been resolved through some other changes, including Jarek's changes committed in axis2 rev 560086. > ServiceDescription caching leads to memory leak > --- > > Key: AXIS2-3011 > URL: https://issues.apache.org/jira/browse/AXIS2-3011 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor >Assignee: Ann Robinson > Attachments: AXIS2-3011.patch > > > The DescriptionFactoryImpl.createServiceDescription() function attempts to > cache/reuse the ServiceDescription objects and that leads to memory leaks. > First, a Hashtable is used for the cache. That means, any ServiceDescription > created will always live in the cache and won't ever be reclaimed (and there > is no clear cache function). Some sort of WeakHashMap could help the problem > so that at least some unused ServiceDescription objects could be reclaimed. > Second, the createServiceDescription() uses the > DescriptionFactory.createClientConfigurationFactory().getClientConfigurationContext() > to get the client configuration context. It looks like by default the > ClientConfigurationFactory.getClientConfigurationContext() does NOT cache the > configuration context. Therefore, each call creates a new configuration > object. That means, that by default ServiceDescription will NOT be reused > since the configuration context object instance is used to determine if the > ServiceDescription should be reused or not (see DescriptionKey.equals() > function). > So, a simple program that calls createServiceDescription() repeatably in a > loop (with the same arguments) will quickly run out of memory. -- 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-3011) ServiceDescription caching leads to memory leak
[ https://issues.apache.org/jira/browse/AXIS2-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516078 ] Lin Sun commented on AXIS2-3011: I've ran my test over an hour not hitting the Two services cannot have same name now, with a recent change in geronimo that would cache the service client. So we can ignore that error now. > ServiceDescription caching leads to memory leak > --- > > Key: AXIS2-3011 > URL: https://issues.apache.org/jira/browse/AXIS2-3011 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor >Assignee: Ann Robinson > Attachments: AXIS2-3011.patch > > > The DescriptionFactoryImpl.createServiceDescription() function attempts to > cache/reuse the ServiceDescription objects and that leads to memory leaks. > First, a Hashtable is used for the cache. That means, any ServiceDescription > created will always live in the cache and won't ever be reclaimed (and there > is no clear cache function). Some sort of WeakHashMap could help the problem > so that at least some unused ServiceDescription objects could be reclaimed. > Second, the createServiceDescription() uses the > DescriptionFactory.createClientConfigurationFactory().getClientConfigurationContext() > to get the client configuration context. It looks like by default the > ClientConfigurationFactory.getClientConfigurationContext() does NOT cache the > configuration context. Therefore, each call creates a new configuration > object. That means, that by default ServiceDescription will NOT be reused > since the configuration context object instance is used to determine if the > ServiceDescription should be reused or not (see DescriptionKey.equals() > function). > So, a simple program that calls createServiceDescription() repeatably in a > loop (with the same arguments) will quickly run out of memory. -- 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: [axis2] missing artifact from maven2 conversion
my choice #2 - a hack. I tried addint the following in soap monitor pom.xml
org.apache.maven.plugins
maven-jar-plugin
process-classes
jar
${pom.basedir}/target/classes
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]
Re: Thread pool in Axis2 (and Synapse)
Ok. I still think it would be better to expose: http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/edu/emory/mathcs/backport/java/util/concurrent/ExecutorService.html Paul On 7/27/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Because, the baseline for Axis2 is JDK 1.4 > > -- dims > > On 7/27/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > Hi > > > > I'm looking at how to add ThreadPool support to Synapse and I've > > looked at the Axis2 support. What I'm trying to figure out is why we > > don't reuse the java.util.Concurrent interfaces but instead create our > > own? > > > > In particular I'd like to be able to track items that are started (so > > I can stop them when Synapse closes down or needs to clean up that > > config). > > > > The obvious interface to do this is this one: > > http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ExecutorService.html > > > > Because when you submit work you get back a Future which allows me to > > cancel running work that is running. > > > > Paul > > > > -- > > Paul Fremantle > > Co-Founder and VP of Technical Sales, WSO2 > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [EMAIL PROTECTED] > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > - > > 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] > > -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3022) Axis2 not handle wsdl deployed to a dir that contains a space (like program files)
[ https://issues.apache.org/jira/browse/AXIS2-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved AXIS2-3022. Resolution: Fixed Patch committed to trunk and 1_3 branch. Thanks! Trunk: Committed revision 560281 1_3 branch: Committed revision 560286. > Axis2 not handle wsdl deployed to a dir that contains a space (like program > files) > -- > > Key: AXIS2-3022 > URL: https://issues.apache.org/jira/browse/AXIS2-3022 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.3 > Environment: winxp + sun jdk 1.5 >Reporter: Lin Sun >Assignee: Ann Robinson > Fix For: 1.3 > > Attachments: Axis2-3022.patch, Axis2-3022.patch > > > Here is the example I got. Testing a possible fix for this.. > 00:58:38,062 DEBUG [ExceptionFactory] stack:javax.wsdl.WSDLException: > WSDLException: faultCode=WSDL4JWrapper : : Illegal character in path at index > 16: file:/C:/Program > Files/Geronimo/org/apache/geronimo/samples/jws/Calculator/2.0/Calculator-2.0.car/CalculatorService.wsdl > at > org.apache.axis2.jaxws.util.WSDL4JWrapper.(WSDL4JWrapper.java:186) > at > org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.setupWsdlDefinition(ServiceDescriptionImpl.java:512) > at > org.apache.axis2.jaxws.description.impl.ServiceDescriptionImpl.(ServiceDescriptionImpl.java:143) > at > org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(DescriptionFactoryImpl.java:101) > at > org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(DescriptionFactory.java:69) > at > org.apache.axis2.jaxws.spi.ServiceDelegate.(ServiceDelegate.java:87) > at > org.apache.axis2.jaxws.spi.Provider.createServiceDelegate(Provider.java:45) > at javax.xml.ws.Service.(Service.java:36) > at > org.apache.geronimo.jaxws.client.GenericService.(GenericService.java:27) > at > org.apache.geronimo.jaxws.client.GenericService$$EnhancerByCGLIB$$ba501ee.() > at > org.apache.geronimo.jaxws.client.GenericService$$EnhancerByCGLIB$$ba501ee$$FastClassByCGLIB$$cb90d621.newInstance() > at > net.sf.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.createServiceProxy(JAXWSServiceReference.java:174) > at > org.apache.geronimo.jaxws.client.JAXWSServiceReference.getContent(JAXWSServiceReference.java:129) > at > org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:112) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:611) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:152) > at > org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:597) > at javax.naming.InitialContext.lookup(InitialContext.java:363) > at org.apache.jsp.addResult_jsp._jspService(addResult_jsp.java:90) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at > org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) > at > org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:351) > at > org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) > at > org.apache.catalina.core.StandardEngineVa
Re: Thread pool in Axis2 (and Synapse)
Because, the baseline for Axis2 is JDK 1.4 -- dims On 7/27/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: > Hi > > I'm looking at how to add ThreadPool support to Synapse and I've > looked at the Axis2 support. What I'm trying to figure out is why we > don't reuse the java.util.Concurrent interfaces but instead create our > own? > > In particular I'd like to be able to track items that are started (so > I can stop them when Synapse closes down or needs to clean up that > config). > > The obvious interface to do this is this one: > http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ExecutorService.html > > Because when you submit work you get back a Future which allows me to > cancel running work that is running. > > Paul > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > 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]
Re: [Axis2] Axis2 1.3 branch created
Jarek, Sure. Please go ahead. -- dims On 7/27/07, Jarek Gawor <[EMAIL PROTECTED]> wrote: > Deepal, > > Is it ok to commit the patch in > https://issues.apache.org/jira/browse/AXIS2-3022 to trunk & branch? > > Thanks, > Jarek > > On 7/20/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > > Hi Devs, > > > > I created a branch [1] for Axis2 1.3 release since we are too close to > > the release. So please do not do ant major changes to do the branch if > > you find any issues with the code base then please create a JIRA and > > attach the patch then I will review that and apply. If you do so only we > > can make sure that the branch is in stable state to do the release. In > > the meantime if you do any changes to branch then PLEASE do the changes > > to trunk immediately as well. > > > > Creating a branch does not mean we can change the trunk as we wish, > > please be patient until we finish the release if you want to do a major > > changes to trunk. Specially please do not do any major changes to kernel > > , addressing , java2wsdl , adb , adb-codegen , codegen modules. > > > > [1] : https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_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] > > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Thread pool in Axis2 (and Synapse)
Hi I'm looking at how to add ThreadPool support to Synapse and I've looked at the Axis2 support. What I'm trying to figure out is why we don't reuse the java.util.Concurrent interfaces but instead create our own? In particular I'd like to be able to track items that are started (so I can stop them when Synapse closes down or needs to clean up that config). The obvious interface to do this is this one: http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ExecutorService.html Because when you submit work you get back a Future which allows me to cancel running work that is running. Paul -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Axis2 1.3 branch created
Deepal, Is it ok to commit the patch in https://issues.apache.org/jira/browse/AXIS2-3022 to trunk & branch? Thanks, Jarek On 7/20/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > Hi Devs, > > I created a branch [1] for Axis2 1.3 release since we are too close to > the release. So please do not do ant major changes to do the branch if > you find any issues with the code base then please create a JIRA and > attach the patch then I will review that and apply. If you do so only we > can make sure that the branch is in stable state to do the release. In > the meantime if you do any changes to branch then PLEASE do the changes > to trunk immediately as well. > > Creating a branch does not mean we can change the trunk as we wish, > please be patient until we finish the release if you want to do a major > changes to trunk. Specially please do not do any major changes to kernel > , addressing , java2wsdl , adb , adb-codegen , codegen modules. > > [1] : https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_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]
[jira] Resolved: (AXIS2-3014) java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3
[ https://issues.apache.org/jira/browse/AXIS2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3014. - Resolution: Fixed Fixed in svn trunk (560263). Please drop the stax api jar from the axis2 WEB-INF/lib into tomcat's common/lib directory as well. thanks, dims > java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3 > > > Key: AXIS2-3014 > URL: https://issues.apache.org/jira/browse/AXIS2-3014 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: winxp, jdk14, tomcat 4.0.3, Axis2-1.3-RC2 >Reporter: Charitha Kankanamge >Assignee: Davanum Srinivas > > Following exception thrown when accessing axis2 admin page > (http://localhost:8080/axis2) if axis2.war is deployed on tomcat4.0.3. > java.lang.IllegalStateException > at > org.apache.jasper.runtime.ServletResponseWrapperInclude.getOutputStream(ServletResponseWrapperInclude.java:109) > at > org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1146) > at > org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:819) > at org.apache.jsp.index$jsp._jspService(index$jsp.java:76) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.connector.http.
[jira] Commented: (AXIS2-3017) WSDL generation error - lowercasing 1st char in element names
[
https://issues.apache.org/jira/browse/AXIS2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516025
]
nadir amra commented on AXIS2-3017:
---
Dims, thanks. But the problem should be fixed. This has nothing to with what
the property is. This has simply to do with how we resolve to the getter and
setter methods, which I think is a bug.
> WSDL generation error - lowercasing 1st char in element names
> -
>
> Key: AXIS2-3017
> URL: https://issues.apache.org/jira/browse/AXIS2-3017
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
>Reporter: nadir amra
>Assignee: Deepal Jayasinghe
>Priority: Critical
> Attachments: ConvertTemp.zip
>
>
> Here is the problem. I deploy a POJO and when AXIS2 (using nightly build
> 2007/07/25) automatically generated WSDL via ?wsdl it produces a WSDL file
> the includes the following:
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
> The problem is with the element names. It seems that AXIS2 is lowercasing
> the "t" in TEMPIN and TEMPOUT, which makes the service unusable. The
> CONVERTTEMPInput class is as follows:
> public class CONVERTTEMPInput implements Serializable
> {
> private static final long serialVersionUID = -884605419035002637L;
> public CONVERTTEMPInput() { }
> public void setTEMPIN( String TEMPIN )
> {
> _TEMPIN = TEMPIN;
> }
> public String getTEMPIN( )
> {
>return _TEMPIN;
> }
> public void setTEMPOUT( String TEMPOUT )
> {
> _TEMPOUT = TEMPOUT;
> }
> public String getTEMPOUT( )
> {
>return _TEMPOUT;
> }
>private String _TEMPIN = "";
>private String _TEMPOUT = "";
> }
> If I add an underscore prior to TEMPIN and TEMPOUT in the method names,
> things start to work.
--
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-3017) WSDL generation error - lowercasing 1st char in element names
[
https://issues.apache.org/jira/browse/AXIS2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-3017:
Priority: Critical (was: Blocker)
Nadir,
We need a fix in annogen. We can't hold up the 1.3 release for that. So
downgrading from blocker. As you rightly pointed out, there is a workaround, so
it's definitely not a blocker.
thanks,
dims
> WSDL generation error - lowercasing 1st char in element names
> -
>
> Key: AXIS2-3017
> URL: https://issues.apache.org/jira/browse/AXIS2-3017
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
>Reporter: nadir amra
>Assignee: Deepal Jayasinghe
>Priority: Critical
> Attachments: ConvertTemp.zip
>
>
> Here is the problem. I deploy a POJO and when AXIS2 (using nightly build
> 2007/07/25) automatically generated WSDL via ?wsdl it produces a WSDL file
> the includes the following:
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
> The problem is with the element names. It seems that AXIS2 is lowercasing
> the "t" in TEMPIN and TEMPOUT, which makes the service unusable. The
> CONVERTTEMPInput class is as follows:
> public class CONVERTTEMPInput implements Serializable
> {
> private static final long serialVersionUID = -884605419035002637L;
> public CONVERTTEMPInput() { }
> public void setTEMPIN( String TEMPIN )
> {
> _TEMPIN = TEMPIN;
> }
> public String getTEMPIN( )
> {
>return _TEMPIN;
> }
> public void setTEMPOUT( String TEMPOUT )
> {
> _TEMPOUT = TEMPOUT;
> }
> public String getTEMPOUT( )
> {
>return _TEMPOUT;
> }
>private String _TEMPIN = "";
>private String _TEMPOUT = "";
> }
> If I add an underscore prior to TEMPIN and TEMPOUT in the method names,
> things start to work.
--
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] Reopened: (AXIS2-3017) WSDL generation error - lowercasing 1st char in element names
[
https://issues.apache.org/jira/browse/AXIS2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra reopened AXIS2-3017:
---
I guess I want to discuss before closing issue.
>From my point of view, this is an AXIS 2 bug if you want to state that POJOs
>are supported as a service.
I am OK with stating that element names have to be lowercasebut I do not
understand when a request coming in why AXIS2 is looking for settEMPIN since
this is not a java convention. It should ensure the first character in the
element name is uppercased, no?
I really disagree with you about not fixing this since I do not see what the
alternative is?
> WSDL generation error - lowercasing 1st char in element names
> -
>
> Key: AXIS2-3017
> URL: https://issues.apache.org/jira/browse/AXIS2-3017
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
>Reporter: nadir amra
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Attachments: ConvertTemp.zip
>
>
> Here is the problem. I deploy a POJO and when AXIS2 (using nightly build
> 2007/07/25) automatically generated WSDL via ?wsdl it produces a WSDL file
> the includes the following:
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
> The problem is with the element names. It seems that AXIS2 is lowercasing
> the "t" in TEMPIN and TEMPOUT, which makes the service unusable. The
> CONVERTTEMPInput class is as follows:
> public class CONVERTTEMPInput implements Serializable
> {
> private static final long serialVersionUID = -884605419035002637L;
> public CONVERTTEMPInput() { }
> public void setTEMPIN( String TEMPIN )
> {
> _TEMPIN = TEMPIN;
> }
> public String getTEMPIN( )
> {
>return _TEMPIN;
> }
> public void setTEMPOUT( String TEMPOUT )
> {
> _TEMPOUT = TEMPOUT;
> }
> public String getTEMPOUT( )
> {
>return _TEMPOUT;
> }
>private String _TEMPIN = "";
>private String _TEMPOUT = "";
> }
> If I add an underscore prior to TEMPIN and TEMPOUT in the method names,
> things start to work.
--
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]
[jira] Assigned: (AXIS2-3014) java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3
[ https://issues.apache.org/jira/browse/AXIS2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas reassigned AXIS2-3014: --- Assignee: Davanum Srinivas > java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3 > > > Key: AXIS2-3014 > URL: https://issues.apache.org/jira/browse/AXIS2-3014 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: winxp, jdk14, tomcat 4.0.3, Axis2-1.3-RC2 >Reporter: Charitha Kankanamge >Assignee: Davanum Srinivas > > Following exception thrown when accessing axis2 admin page > (http://localhost:8080/axis2) if axis2.war is deployed on tomcat4.0.3. > java.lang.IllegalStateException > at > org.apache.jasper.runtime.ServletResponseWrapperInclude.getOutputStream(ServletResponseWrapperInclude.java:109) > at > org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1146) > at > org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:819) > at org.apache.jsp.index$jsp._jspService(index$jsp.java:76) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012) > at > org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java
Re: Supporting content types in Synapse and Axiom
Asankha
I thought of this because Esper is creating Map messages and I had to
create my own mapping from Map to Axiom. So it would make my life
easier :-)
Paul
On 7/27/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
>
> Paul
>
> I may be wrong, however, I haven't seen many people actually using JMS Map
> messages.. The Axis2 JMS transport thus supports bytes and text messages. So
> I would think this is a cool feature, but only few many find it actually
> useful...
>
> asankha
>
> Paul Fremantle wrote:
> One more thought. A number of systems use a java Map message as a core
> data type. Especially a Map where Object is actually a
> simple type object such as Float, Double, String, Boolean
>
> In particular JMS supports these. I think it would be valuable to
> define this as a core Synapse datatype. For example, it would be cool
> to be able to mediate between a JMS Map message and another JMS Map
> message, and have a well-defined schema for what the Axiom
> representation would look like in Synapse.
>
> Paul
>
> On 7/26/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
>
> Hi
>
> As Synapse is getting more interest I see a number of people looking
> to use it and extend it for binary and text content types as well as
> XML.
>
> We already support those from some transports (e.g. JMS) but each
> transport defines its own way of handling these things, and so I can't
> be sure that a message coming in as binary/jms can go out correctly as
> binary/http post.
>
> So here is what I'd like to do:
>
> I'd like to have explicit methods:
>
> OMElement get/setPayload()
> DataHandler get/setBytesPayload()
> String get/setTextPayload()
> boolean isBinary();
> boolean isText();
> int getPayloadType()
>
> In order to make this work, we should have two well defined QNames -
> one for binary and one for text.
>
> For example binary payload will be in a wrapper element called:
> xmlns:a="http://ws.apache.org/commons/axiom/ns/data";>
>
> And text payload could be in
> xmlns:a="http://ws.apache.org/commons/axiom/ns/data";>
>
> So if I setBinaryPayload, basically what happens (under the covers is)
>
> OMElement el = fac.createOMElement("binary", axNS);
> OMText bin = fac.createOMText(dh, true);
> el.addChild(bin);
> getBody().setFirstChild(el);
>
> Now I'd be very happy to do this just in Synapse, but it makes much
> more sense to do it in Axiom. That would mean everyone using this
> (axis2 transports, synapse mediators, etc) would inherit the same
> definitions and use the data in a consistent way. Which is the point
> of this.
>
> Paul
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2564) Wrong type mapping for java.lang.Long
[
https://issues.apache.org/jira/browse/AXIS2-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2564.
--
Resolution: Fixed
fixed in current SVN and RC2
> Wrong type mapping for java.lang.Long
> -
>
> Key: AXIS2-2564
> URL: https://issues.apache.org/jira/browse/AXIS2-2564
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
>Reporter: Eugeniy Nizhinskiy
>Assignee: Deepal Jayasinghe
>Priority: Critical
> Fix For: 1.3
>
>
> 1. Wrong java2wsdl mapping occurs when try to use java.lang.Long types in web
> service.
> java.lang.Long mappes to long instead of nilable long.
> 2. Problem with complex types. If we use long (not java.lang.Long) as in/out
> parameter in web service methods java2wsdl mappes it as nilable. But if we
> use in/out complex type with long field we will get not nilable in wsdl.
> Example:
> From the following classes java2wsdl generates wrong WSDL.
> [BatchManagerService.java]
> package x;
> public class BatchManagerService {
>
> public x.Person getPerson(java.lang.Long personINTN)
> {
> return null;
> };
> public x.Person getPersonSimple(long personSIMPLEINTN)
> {
> return null;
> };
> }
> [Person.java]
> package x;
> public class Person {
> public java.lang.Long getLong(){return null;};
> public long getSimpleLong(){return 0;};
> }
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
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-2965) Review Documentation generated by m2 build
[ https://issues.apache.org/jira/browse/AXIS2-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516015 ] Deepal Jayasinghe commented on AXIS2-2965: -- Chathra Any update on this issues ? Thanks Deepal > Review Documentation generated by m2 build > -- > > Key: AXIS2-2965 > URL: https://issues.apache.org/jira/browse/AXIS2-2965 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: documentation >Reporter: Davanum Srinivas >Assignee: Chatra Nakkawita >Priority: Blocker > Fix For: 1.3 > > > Chatra, > Please run "mvn -N site:site" from the root directory and look at the > generated contents in target/site directory. I had to generate xhtmls from > the ordinary html's that we had in m1. and the file name extensions are not > .xml as well instead of .html (under xdocs). > thanks, > dims -- 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: [jira] Commented: (AXIS2-3002) Axis 1.3RC2 does not work properly on websphere
Dustin, Can you please tell me how to configure classloader for axis2.war in websphere? Can it be done using Websphere admin console? thank you! Charitha Dustin Amrhein (JIRA) wrote: [ https://issues.apache.org/jira/browse/AXIS2-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514951 ] Dustin Amrhein commented on AXIS2-3002: --- Charitha, One thing that you will have to do (and you may have already done this) is to configure the classloader for the axis2.war. The default classloader policy for deployed WARs on WebSphere is PARENT_FIRST. In order to load classes within your module first you need to change this policy to PARENT_LAST. You may have already done this, but I hope it helps. Axis 1.3RC2 does not work properly on websphere --- Key: AXIS2-3002 URL: https://issues.apache.org/jira/browse/AXIS2-3002 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.3 Environment: Websphere 6.0.2 Reporter: Kent Watanabe Assignee: Charitha Kankanamge Attachments: Websphere-axis2.JPG The new axis2.war does not work properly on websphere. There are problems with the wsdl2 generation, and the wsdl 1.1 genaration. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3017) WSDL generation error - lowercasing 1st char in element names
[
https://issues.apache.org/jira/browse/AXIS2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3017.
--
Resolution: Won't Fix
I can safely mark this as Wont fix :)
> WSDL generation error - lowercasing 1st char in element names
> -
>
> Key: AXIS2-3017
> URL: https://issues.apache.org/jira/browse/AXIS2-3017
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
>Reporter: nadir amra
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Attachments: ConvertTemp.zip
>
>
> Here is the problem. I deploy a POJO and when AXIS2 (using nightly build
> 2007/07/25) automatically generated WSDL via ?wsdl it produces a WSDL file
> the includes the following:
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
> The problem is with the element names. It seems that AXIS2 is lowercasing
> the "t" in TEMPIN and TEMPOUT, which makes the service unusable. The
> CONVERTTEMPInput class is as follows:
> public class CONVERTTEMPInput implements Serializable
> {
> private static final long serialVersionUID = -884605419035002637L;
> public CONVERTTEMPInput() { }
> public void setTEMPIN( String TEMPIN )
> {
> _TEMPIN = TEMPIN;
> }
> public String getTEMPIN( )
> {
>return _TEMPIN;
> }
> public void setTEMPOUT( String TEMPOUT )
> {
> _TEMPOUT = TEMPOUT;
> }
> public String getTEMPOUT( )
> {
>return _TEMPOUT;
> }
>private String _TEMPIN = "";
>private String _TEMPOUT = "";
> }
> If I add an underscore prior to TEMPIN and TEMPOUT in the method names,
> things start to work.
--
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-3017) WSDL generation error - lowercasing 1st char in element names
[
https://issues.apache.org/jira/browse/AXIS2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516013
]
Deepal Jayasinghe commented on AXIS2-3017:
--
http://www.stylusstudio.com/xmldev/21/post70580.html
is specifically mentioned about the property names.
Thanks
Deepal
> WSDL generation error - lowercasing 1st char in element names
> -
>
> Key: AXIS2-3017
> URL: https://issues.apache.org/jira/browse/AXIS2-3017
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
>Reporter: nadir amra
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Attachments: ConvertTemp.zip
>
>
> Here is the problem. I deploy a POJO and when AXIS2 (using nightly build
> 2007/07/25) automatically generated WSDL via ?wsdl it produces a WSDL file
> the includes the following:
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
> The problem is with the element names. It seems that AXIS2 is lowercasing
> the "t" in TEMPIN and TEMPOUT, which makes the service unusable. The
> CONVERTTEMPInput class is as follows:
> public class CONVERTTEMPInput implements Serializable
> {
> private static final long serialVersionUID = -884605419035002637L;
> public CONVERTTEMPInput() { }
> public void setTEMPIN( String TEMPIN )
> {
> _TEMPIN = TEMPIN;
> }
> public String getTEMPIN( )
> {
>return _TEMPIN;
> }
> public void setTEMPOUT( String TEMPOUT )
> {
> _TEMPOUT = TEMPOUT;
> }
> public String getTEMPOUT( )
> {
>return _TEMPOUT;
> }
>private String _TEMPIN = "";
>private String _TEMPOUT = "";
> }
> If I add an underscore prior to TEMPIN and TEMPOUT in the method names,
> things start to work.
--
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: Supporting content types in Synapse and Axiom
Paul
I may be wrong, however, I haven't seen many people actually using JMS
Map messages.. The Axis2 JMS transport thus supports bytes and text
messages. So I would think this is a cool feature, but only few many
find it actually useful...
asankha
Paul Fremantle wrote:
One more thought. A number of systems use a java Map message as a core
data type. Especially a Map where Object is actually a
simple type object such as Float, Double, String, Boolean
In particular JMS supports these. I think it would be valuable to
define this as a core Synapse datatype. For example, it would be cool
to be able to mediate between a JMS Map message and another JMS Map
message, and have a well-defined schema for what the Axiom
representation would look like in Synapse.
Paul
On 7/26/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Hi
As Synapse is getting more interest I see a number of people looking
to use it and extend it for binary and text content types as well as
XML.
We already support those from some transports (e.g. JMS) but each
transport defines its own way of handling these things, and so I can't
be sure that a message coming in as binary/jms can go out correctly as
binary/http post.
So here is what I'd like to do:
I'd like to have explicit methods:
OMElement get/setPayload()
DataHandler get/setBytesPayload()
String get/setTextPayload()
boolean isBinary();
boolean isText();
int getPayloadType()
In order to make this work, we should have two well defined QNames -
one for binary and one for text.
For example binary payload will be in a wrapper element called:
"http://ws.apache.org/commons/axiom/ns/data">
And text payload could be in
"http://ws.apache.org/commons/axiom/ns/data">
So if I setBinaryPayload, basically what happens (under the covers is)
OMElement el = fac.createOMElement("binary", axNS);
OMText bin = fac.createOMText(dh, true);
el.addChild(bin);
getBody().setFirstChild(el);
Now I'd be very happy to do this just in Synapse, but it makes much
more sense to do it in Axiom. That would mean everyone using this
(axis2 transports, synapse mediators, etc) would inherit the same
definitions and use the data in a consistent way. Which is the point
of this.
Paul
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3017) WSDL generation error - lowercasing 1st char in element names
[
https://issues.apache.org/jira/browse/AXIS2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516011
]
Deepal Jayasinghe commented on AXIS2-3017:
--
No dims , we wont be able to fix this. The bug is due to annogen issue. It
converts first character of nay give property in to upper case, so I have
written a method to convert that back. So if the original property name stating
from Upper case then we have this issues. In the meantime according the the
bean Introspector you can not have property name stating with upper case. So I
will not consider this as a bug in Axis2 either.
Thanks
Deepal
> WSDL generation error - lowercasing 1st char in element names
> -
>
> Key: AXIS2-3017
> URL: https://issues.apache.org/jira/browse/AXIS2-3017
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
>Reporter: nadir amra
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Attachments: ConvertTemp.zip
>
>
> Here is the problem. I deploy a POJO and when AXIS2 (using nightly build
> 2007/07/25) automatically generated WSDL via ?wsdl it produces a WSDL file
> the includes the following:
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
> The problem is with the element names. It seems that AXIS2 is lowercasing
> the "t" in TEMPIN and TEMPOUT, which makes the service unusable. The
> CONVERTTEMPInput class is as follows:
> public class CONVERTTEMPInput implements Serializable
> {
> private static final long serialVersionUID = -884605419035002637L;
> public CONVERTTEMPInput() { }
> public void setTEMPIN( String TEMPIN )
> {
> _TEMPIN = TEMPIN;
> }
> public String getTEMPIN( )
> {
>return _TEMPIN;
> }
> public void setTEMPOUT( String TEMPOUT )
> {
> _TEMPOUT = TEMPOUT;
> }
> public String getTEMPOUT( )
> {
>return _TEMPOUT;
> }
>private String _TEMPIN = "";
>private String _TEMPOUT = "";
> }
> If I add an underscore prior to TEMPIN and TEMPOUT in the method names,
> things start to work.
--
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-3014) java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3
[ https://issues.apache.org/jira/browse/AXIS2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516007 ] Charitha Kankanamge commented on AXIS2-3014: Deepal, Tested against latest Axis2 build and i'm getting following exception when accessing admin page. javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:653) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107) at java.lang.Thread.run(Thread.java:534) root cause java.lang.NoClassDefFoundError: org/w3c/dom/DOMError at org.apache.xerces.jaxp.DocumentBuilderImpl.(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source) at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserUtils.java:197) at org.apache.jasper.compiler.TldLocationsCache.processWebDotXml(TldLocationsCache.java:165) at org.apache.jasper.compiler.TldLocationsCache.(TldLocationsCache.java:138) at org.apache.jasper.EmbededServletOptions.(EmbededServletOptions.java:345) at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:266) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:916) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:653) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:18
[jira] Assigned: (AXIS2-3020) Support serialization of java.util.Map when using POJO service with RPCMessageReceiver.
[ https://issues.apache.org/jira/browse/AXIS2-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3020: Assignee: Deepal Jayasinghe > Support serialization of java.util.Map when using POJO service with > RPCMessageReceiver. > --- > > Key: AXIS2-3020 > URL: https://issues.apache.org/jira/browse/AXIS2-3020 > Project: Axis 2.0 (Axis2) > Issue Type: New Feature > Components: adb >Reporter: Sathija Pavuluri >Assignee: Deepal Jayasinghe >Priority: Minor > > At one point serialization of java.util.Map was on Axis' TODO list but has > since fallen through the cracks. > When using POJO approach, Map serialization/deserialization is not supported. > Would be nice to add that support. -- 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] Assigned: (AXIS2-3005) [7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set header. Response already committed. is logged when ever a Axis2 based webservice is called
[ https://issues.apache.org/jira/browse/AXIS2-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3005: Assignee: Charitha Kankanamge > [7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set > header. Response already committed. is logged when ever a Axis2 based > webservice is called > -- > > Key: AXIS2-3005 > URL: https://issues.apache.org/jira/browse/AXIS2-3005 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.2 > Environment: WebSphere 5.1.1.14 > HP UX operating system >Reporter: Muhammad Hamza Hakim >Assignee: Charitha Kankanamge >Priority: Minor > > We have implemented Web Services using Axis2 and facing the below mentioned > problem when ever the a request is made to Web Service: > We now installed WebSphere 5.1.1.14 > In the logs we still see below error-messages filling our logs. So the > fixpack did not solve this issue. Can you please arrange that these > messages do not appear anymore in the logs? > > [7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set > header. Response already committed. > Our Finding: > WebSphere logs the warning message "SRTServletRes W WARNING: Cannot set > header. Response already committed." in SystemOut.log due to Axis2. Axis2 > processes the incomming request sends the response and then tries to set a > header property in response. Because at this point WebSphere has already > committed the response so it logs a warning in the log. -- 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] Assigned: (AXIS2-3026) New AxisConfigurator that operates within the aar file
[ https://issues.apache.org/jira/browse/AXIS2-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3026: Assignee: Deepal Jayasinghe > New AxisConfigurator that operates within the aar file > -- > > Key: AXIS2-3026 > URL: https://issues.apache.org/jira/browse/AXIS2-3026 > Project: Axis 2.0 (Axis2) > Issue Type: Wish > Components: kernel >Affects Versions: nightly > Environment: Not specific >Reporter: Mark Badorrek >Assignee: Deepal Jayasinghe > Fix For: nightly > > > Currently there are several AxisConfigurators: > FileSystemConfigurator > URLBasedAxisConfigurator > etc > I feel that we also need an AxisConfigurator that can read an axis_client.xml > file and client repository that are stored in the aar file. This would allow > an axis service to make client-calls to other axis services using different > configurations from the parent configuration. > For example: > I have an axis service 'foo' that is a plain old websevice - nothing special. > Now consider that it has been invoked by a client. > 'foo' must now make a couple of webservice calls of its own, but this time it > will (for example) engage 'rampart' and disengage'addressing' for both of its > client calls. As such each configuration will have its own rampart callback > classes etc. > Currently there is no way to include the required 'client1_axis2.xml', > client1_repository', 'client2_axis2.xml', client2_repository', within the aar > file and have them loaded. > I'd like to see an 'ServiceClassloaderAxisConfigurator' to allow these > artifacts to be stored within the aar file so that the entire 'foo' > webservice is a single file deploy. > The 'client1_AxisConfiguration' and 'client1_AxisConfiguration' should also > be cached as there is a high probability that they will be required agin and > again. -- 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] Resolved: (AXIS2-3015) ERROR can not find read method for : defaultAssertionStatus. Bug with Class-type properties.
[
https://issues.apache.org/jira/browse/AXIS2-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3015.
--
Resolution: Won't Fix
You class is not a valid Java bean , so what we are doing is correct.
Thanks
Deepal
> ERROR can not find read method for : defaultAssertionStatus. Bug with
> Class-type properties.
> -
>
> Key: AXIS2-3015
> URL: https://issues.apache.org/jira/browse/AXIS2-3015
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
>Affects Versions: 1.3
> Environment: Axis 2 1.3-RC2 (20.7.2007), JBoss 4.0.5 GA with Spring
> 1.2 and Hibernate 3 integrated inside AAR modules.
>Reporter: Vesa Varimo
> Attachments: LogResponseImpl.java
>
>
> I have simple domain class generated with Hyperjaxb2 0.6.2.
> The class is called LogResponseImpl (included as an attachment) and the XSD
> for it is following:
>
>
>nillable="true" />
>
>
> Besides the method get/setSucceeded HyperJAXB2 generates method
> getPrimaryInterface() that returns java.lang.Class as a return value.
> ADB in Axis2 tries to solve this property and ends up giving the error
> message: "can not find read method for : defaultAssertionStatus".
> I fixed this issue by adding following condition to BeanUtil.java line 110:
> for (int i = 0; i < properties.length; i++) {
> JProperty property = properties[i];
> if (property.getType().getQualifiedName().indexOf("Class") == -1) {
> propertyList.add(property);
> }
> }
>
--
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]
IllegalStateException: Current state not START_ELEMENT
Hi I am getting the following exception IllegalStateException: Current state not START_ELEMENT when I sent the request to the server. Anybody has any idea why this is coming? 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
Re: Supporting content types in Synapse and Axiom
One more thought. A number of systems use a java Map message as a core
data type. Especially a Map where Object is actually a
simple type object such as Float, Double, String, Boolean
In particular JMS supports these. I think it would be valuable to
define this as a core Synapse datatype. For example, it would be cool
to be able to mediate between a JMS Map message and another JMS Map
message, and have a well-defined schema for what the Axiom
representation would look like in Synapse.
Paul
On 7/26/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> Hi
>
> As Synapse is getting more interest I see a number of people looking
> to use it and extend it for binary and text content types as well as
> XML.
>
> We already support those from some transports (e.g. JMS) but each
> transport defines its own way of handling these things, and so I can't
> be sure that a message coming in as binary/jms can go out correctly as
> binary/http post.
>
> So here is what I'd like to do:
>
> I'd like to have explicit methods:
>
> OMElement get/setPayload()
> DataHandler get/setBytesPayload()
> String get/setTextPayload()
> boolean isBinary();
> boolean isText();
> int getPayloadType()
>
> In order to make this work, we should have two well defined QNames -
> one for binary and one for text.
>
> For example binary payload will be in a wrapper element called:
> http://ws.apache.org/commons/axiom/ns/data";>
>
> And text payload could be in
> http://ws.apache.org/commons/axiom/ns/data";>
>
> So if I setBinaryPayload, basically what happens (under the covers is)
>
> OMElement el = fac.createOMElement("binary", axNS);
> OMText bin = fac.createOMText(dh, true);
> el.addChild(bin);
> getBody().setFirstChild(el);
>
> Now I'd be very happy to do this just in Synapse, but it makes much
> more sense to do it in Axiom. That would mean everyone using this
> (axis2 transports, synapse mediators, etc) would inherit the same
> definitions and use the data in a consistent way. Which is the point
> of this.
>
> Paul
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-3009) Problem in returning comples type by WebService
[
https://issues.apache.org/jira/browse/AXIS2-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3009.
--
Resolution: Incomplete
There is no enough data to recreate the issue
> Problem in returning comples type by WebService
> ---
>
> Key: AXIS2-3009
> URL: https://issues.apache.org/jira/browse/AXIS2-3009
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
>Affects Versions: 1.2
> Environment: Axis2 -1.2
>Reporter: Amit Panwar
>
> Hi
> I am using axis2-1.2 . When i m trying to call the webservice it
> giving a RunTimeException.
> Exception in thread "main" java.lang.RuntimeException:
> java.lang.RuntimeException: Unexpected subelement Text
> at
> com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.fromOM(IlsAdminPublicAPIWSHttpportStub.java:46923)
> at
> com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.findMatchingProducts(IlsAdminPublicAPIWSHttpportStub.java:3380)
> at
> com.agilis.ils.ws.clientcode.IlsProductAdminWSClient.main(IlsProductAdminWSClient.java:203)
> Caused by: java.lang.RuntimeException: Unexpected subelement Text
> at
> com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub$FindMatchingProductsResponse$Factory.parse(IlsAdminPublicAPIWSHttpportStub.java:33121)
> at
> com.agilis.ils.ws.IlsAdminPublicAPIWSHttpportStub.fromOM(IlsAdminPublicAPIWSHttpportStub.java:46861)
> I think this is beacuse of returning a complex type from webservice .
>
> if (reader.isStartElement() && new
> javax.xml.namespace.QName("http://ws.ils.agilis.com/xsd","return";).equals(reader.getName()))
> I think this code is giving error.
> If anybody have any idea , then please reply.
>
> Thanks in advance.
>
>Thanks and regards
> Amit Panwar
--
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-3014) java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3
[ https://issues.apache.org/jira/browse/AXIS2-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516001 ] Deepal Jayasinghe commented on AXIS2-3014: -- Charitha, Can you please test with Axis2 nightly builds , I think Dims has fixed the issues Thanks Deepal > java.lang.IllegalStateException when deploying axis2.war on tomcat 4.0.3 > > > Key: AXIS2-3014 > URL: https://issues.apache.org/jira/browse/AXIS2-3014 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: winxp, jdk14, tomcat 4.0.3, Axis2-1.3-RC2 >Reporter: Charitha Kankanamge > > Following exception thrown when accessing axis2 admin page > (http://localhost:8080/axis2) if axis2.war is deployed on tomcat4.0.3. > java.lang.IllegalStateException > at > org.apache.jasper.runtime.ServletResponseWrapperInclude.getOutputStream(ServletResponseWrapperInclude.java:109) > at > org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.java:1146) > at > org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:819) > at org.apache.jsp.index$jsp._jspService(index$jsp.java:76) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012) > at > org.a
[jira] Resolved: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces
[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2990. -- Resolution: Fixed seems like issues is fixed. Thanks Deepal > WSDL port address is not correctly generated for machines having multiple > network interfaces > > > Key: AXIS2-2990 > URL: https://issues.apache.org/jira/browse/AXIS2-2990 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: 1.2 > Environment: Windows >Reporter: Haneef Ali > > WSDL portAddress is filled with machines IP address. The code to get the IP > address org.apache.axis2.transport.http.sever.HTTPUtils.getIpAddress() always > takes the first available network interfaces ip address. > This may not work in machine which has vmvare installed, or machines having > multiple network interfaces or just a laptop which has wireless and wired > lan. I believe that Correct way to do that it, is to use the hostName and > resolve it to ipAddress. -- 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] Resolved: (AXIS2-3003) Unable to engage addressing at client side, want to know the specific location of addressing.mar in the project
[
https://issues.apache.org/jira/browse/AXIS2-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3003.
--
Resolution: Fixed
I think the issues is fixed in RC2.
[Please reopen the issue if you still have that ]
Thanks
Deepal
> Unable to engage addressing at client side, want to know the specific
> location of addressing.mar in the project
> ---
>
> Key: AXIS2-3003
> URL: https://issues.apache.org/jira/browse/AXIS2-3003
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
>Affects Versions: 1.2
> Environment: winxp, axis2
>Reporter: tommy
>
> I got the same problem with "Unable to engage module : addressing ", I've
> added the line 'stub._getServiceClient().engageModule(new
> QName("addressing"));' in my client codes. Could anyone be kind to tell where
> I should place addressing-1.2.mar in my class-path. I copyed it everywhere it
> could be, but the program still cannot recognize the .mar file in my project.
> Ask for help, thanks in advance.
> [ Show » ] tommy - [22/Jul/07 11:28 PM ] I got the same problem with "Unable
> to engage module : addressing ", I've added the line
> 'stub._getServiceClient().engageModule(new QName("addressing"));' in my
> client codes. Could anyone be kind to tell where I should place
> addressing-1.2.mar in my class-path. I copyed it everywhere it could be, but
> the program still cannot recognize the .mar file in my project. Ask for help,
> thanks in advance.
--
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: ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver
Hi Deepal , Actually rDatasource is created before and stub of this webservice is using in many place. Now we reuire to create one webservice for system n tracking purpose.n this system webservise is going to imple ment in axis2 because we want asycronous webservice. Thats y we r having two type of stub..is there any solution.. it is just like image which i am sending please see once So is there any possibility for this situation.Because if we migrate Rdatasource in axis2.1.2,then it will take long time to impact because this Rdatasource is using in many place. thanks ruchira Deepal Jayasinghe wrote: > > Hi ruchira , > As i understand correct you have service hots in somewhere and you have > two client stubs on in Axis1 and one in Axis2. If so why do you want two > types of stubs , why cant you use only one stub. > > Thanks > Deepal >> Hi, >> can you please let me know what is JIRA and how can i create JIRA... >> >> Here i am trying to explain you. >> >> 1)we have one webservice rDatasource which deal with database part such >> as >> create ,delete, update from data base.For rDatasource we r using axis >> 1.3 >> to generate client stub which is rdatasourceclient. >> >> 2)we have one more webservice systemservice for this we r using axis2.1.2 >> to >> generate clint stub whos name is systemserviceclientstub >> >> >> now flow is like that systemserviceclientstub(created by axis2.1.2) >> interact with rdatasourceclientstub(created by axis1.3). >> >> >> i m getting many problem in above situation. >> is it possible abve situat or we have to all webservice in same asix >> either >> in axis1.3 or axis2.1.2 >> >> >> >> >> Deepal Jayasinghe-2 wrote: >> > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > http://www.nabble.com/file/p11826185/situation.jpg -- View this message in context: http://www.nabble.com/ERROR-org.apache.axis2.rpc.receivers.RPCMessageReceiver-tf4156226.html#a11826185 Sent from the Axis - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2999) Remove one of MEX maven module
[ https://issues.apache.org/jira/browse/AXIS2-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2999: Assignee: sumedha rubasinghe > Remove one of MEX maven module > -- > > Key: AXIS2-2999 > URL: https://issues.apache.org/jira/browse/AXIS2-2999 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement >Reporter: Deepal Jayasinghe >Assignee: sumedha rubasinghe > > In the current source tree I can find two maven module for MEX , I think we > can do easily create and continue the development with one maven module. So > let's merge the two and have one module for that (like addressing) -- 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] Resolved: (AXIS2-2989) ServiceTCCL=service but org.apache.commons.logging.LogFactory uses WebappClassLoader
[
https://issues.apache.org/jira/browse/AXIS2-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2989.
--
Resolution: Won't Fix
I do not think that Axis2 can switch back to 1.0.4 so , I have to mark this as
wont fix.
Thanks
Deepal
> ServiceTCCL=service but org.apache.commons.logging.LogFactory uses
> WebappClassLoader
>
>
> Key: AXIS2-2989
> URL: https://issues.apache.org/jira/browse/AXIS2-2989
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Linux (unknown) i386 2.6.5-7.282-bigsmp
> Java(TM) 2 Runtime Environment, Standard Edition 1.5.0_12-b04 Java
> HotSpot(TM) Server VM)
> Apache Tomcat/5.5.23
>Reporter: Fred Hauschel
>
> I'd like to use a commons-logging (log4j) for each service in axis2
> container. But SimpleLog for the axis2 stuff.
> In
> "apache-tomcat-5.5.23/webapps/axis2/WEB-INF/classes/commons-logging.propertiesI've
> aktivated:
> org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog. In
> the root of my aar there is a "commons-logging.properties" with
> "org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger".
> The commons-logging LogFactory:
> sample: private static final Log LOG =
> LogFactory.getLog(ReportServiceMessageReceiver.class.getName());
> Uses the SimpleLog and not the Log4j! The following Code is from
> LogFactory.getContextClassLoader():
> Method method = Thread.class.getMethod("getContextClassLoader", null);
> classLoader = (ClassLoader)method.invoke(Thread.currentThread(), null);
> It returns me the "WebappClassLoader" not your axis classloader. I think it
> should be somethink like DeploymentClassLoader?!
> I found this blog: http://wso2.org/blog/dims/1131 and understand it like
> service should set the axis
> classloader as TCCL. So the code above should return the axis classloader,
> shouldn't it?
> Thanks Fredy
> There is my services.xml:
>
>
>
> class="de.xyz.reporting.startup.ServiceLifeCycle">
>
> de.xyz.reporting.startup.ServiceLifeCycle
>
> composite
>
>
> class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver" />
>
>
>
> true
> service
>
>
> org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier
>
>
> ReportService
>
>
> http://www.w3.org/ns/wsdl/in-out";
>
> class="de.xyz.reporting.glue.ReportServiceMessageReceiver" />
>
>
> http://www.w3.org/ns/wsdl/in-out";
>
> class="de.xyz.reporting.glue.ReportServiceMessageReceiver" />
>
>
>
--
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] Assigned: (AXIS2-3017) WSDL generation error - lowercasing 1st char in element names
[
https://issues.apache.org/jira/browse/AXIS2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-3017:
Assignee: Deepal Jayasinghe
> WSDL generation error - lowercasing 1st char in element names
> -
>
> Key: AXIS2-3017
> URL: https://issues.apache.org/jira/browse/AXIS2-3017
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
>Reporter: nadir amra
>Assignee: Deepal Jayasinghe
>Priority: Blocker
> Attachments: ConvertTemp.zip
>
>
> Here is the problem. I deploy a POJO and when AXIS2 (using nightly build
> 2007/07/25) automatically generated WSDL via ?wsdl it produces a WSDL file
> the includes the following:
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
>
>
> type="xs:string"/>
> type="xs:string"/>
>
>
> The problem is with the element names. It seems that AXIS2 is lowercasing
> the "t" in TEMPIN and TEMPOUT, which makes the service unusable. The
> CONVERTTEMPInput class is as follows:
> public class CONVERTTEMPInput implements Serializable
> {
> private static final long serialVersionUID = -884605419035002637L;
> public CONVERTTEMPInput() { }
> public void setTEMPIN( String TEMPIN )
> {
> _TEMPIN = TEMPIN;
> }
> public String getTEMPIN( )
> {
>return _TEMPIN;
> }
> public void setTEMPOUT( String TEMPOUT )
> {
> _TEMPOUT = TEMPOUT;
> }
> public String getTEMPOUT( )
> {
>return _TEMPOUT;
> }
>private String _TEMPIN = "";
>private String _TEMPOUT = "";
> }
> If I add an underscore prior to TEMPIN and TEMPOUT in the method names,
> things start to work.
--
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] Assigned: (AXIS2-3024) CodegenToolReference.html totally out of date
[ https://issues.apache.org/jira/browse/AXIS2-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3024: Assignee: Amila Chinthaka Suriarachchi > CodegenToolReference.html totally out of date > - > > Key: AXIS2-3024 > URL: https://issues.apache.org/jira/browse/AXIS2-3024 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: documentation >Reporter: Davanum Srinivas >Assignee: Amila Chinthaka Suriarachchi >Priority: Blocker > Fix For: 1.3 > > > Ant task documentation is totally out of date. (CodegenToolReference.html). > Need to add documentation for m2 task as well. -- 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] Assigned: (AXIS2-3025) Update documentation about builds from m1 to m2
[ https://issues.apache.org/jira/browse/AXIS2-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-3025: Assignee: sumedha rubasinghe > Update documentation about builds from m1 to m2 > --- > > Key: AXIS2-3025 > URL: https://issues.apache.org/jira/browse/AXIS2-3025 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: documentation >Reporter: Davanum Srinivas >Assignee: sumedha rubasinghe >Priority: Blocker > > http://marc.info/?l=axis-user&m=118531066900497&w=2 > "I actually tried to build axis2 from svn sources and found out that > the build must be done using maven 2. I think that the build > documentation also needs a brush-up before a release to > reflect the use of maven 2, e.g. in > xdocs/maven-help.xml, svn.xml, faq.xml. > - Erik" -- 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-2898) Probelm of SOAP with JMS transport in axis2
[
https://issues.apache.org/jira/browse/AXIS2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515997
]
Amila Chinthaka Suriarachchi commented on AXIS2-2898:
-
please take a nighly build from the branch. even RC2 would not work. this is a
very latest fix
> Probelm of SOAP with JMS transport in axis2
> ---
>
> Key: AXIS2-2898
> URL: https://issues.apache.org/jira/browse/AXIS2-2898
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
>Affects Versions: 1.2
> Environment: Deploy axis2 in tomcat6.
> Use JMS of AcitiveMQ 4.1.0.
>Reporter: lizhao chen
>Assignee: Asankha C. Perera
>Priority: Blocker
> Attachments: jms_example.zip
>
>
> I am trying to test a webservice with JMS transport. The service works
> perfectly fine with HTTP but with JMS it gives the following exception during
> unmarshling. Looks like localName is incorrect.
> 2007-07-04 10:11:08,213 DEBUG org.apache.axiom.om.impl.builder.StAXOMBuilder
> - S
> TART_ELEMENT: {tmf854.v1}TopicExpression_T:TopicExpression_T
> 2007-07-04 10:11:08,213 DEBUG
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBu
> ilder - Build the OMElelment TopicExpression_TBy the StaxSOAPModelBuilder
> 2007-07-04 10:11:08,253 ERROR
> org.apache.axis2.transport.jms.JMSMessageReceiver
> - JMS Worker [JMSWorker-1] Encountered an Axis Fault :
> java.lang.RuntimeExceptio
> n: Unexpected subelement TopicExpression_T; nested exception is:
> java.lang.RuntimeException: java.lang.RuntimeException: Unexpected
> subel
> ement TopicExpression_T
> org.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected subelement
> To
> picExpression_T; nested exception is:
> java.lang.RuntimeException: java.lang.RuntimeException: Unexpected
> subel
> ement TopicExpression_T
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:55)
> at
> org.apache.axis2.receivers.AbstractInMessageReceiver.receive(Abstract
> InMessageReceiver.java:35)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:177)
> at
> org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessa
> geReceiver.java:204)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
> ker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
> ker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Unexpected
> su
> belement TopicExpression_T
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.fromOM(NotificationConsumerMessageReceiverInOnly.java:110)
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:42)
> ... 6 more
> Caused by: java.lang.RuntimeException: Unexpected subelement TopicExpression_T
> at org.tmforum.tmf854.v1.Notify_T$Factory.parse(Notify_T.java:540)
> at org.tmforum.tmf854.v1.Notify$Factory.parse(Notify.java:292)
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.fromOM(NotificationConsumerMessageReceiverInOnly.java:97)
> ... 7 more
--
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] Reopened: (AXIS2-2352) XMLBeans client getting org.apache.axis2.AxisFault: First Element must contain the local name, Envelope
[ https://issues.apache.org/jira/browse/AXIS2-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reopened AXIS2-2352: -- Assignee: Amila Chinthaka Suriarachchi (was: Davanum Srinivas) Seems like we still have the issue, Amila any idea abt this ? Thanks Deepal > XMLBeans client getting org.apache.axis2.AxisFault: First Element must > contain the local name, Envelope > --- > > Key: AXIS2-2352 > URL: https://issues.apache.org/jira/browse/AXIS2-2352 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: client-api, codegen, wsdl >Affects Versions: 1.2 > Environment: Windows XP, JDK 1.4.2_09 >Reporter: Raghu >Assignee: Amila Chinthaka Suriarachchi >Priority: Blocker > Fix For: 1.3 > > Attachments: axis2.log, TestWS.zip > > > This does not seem to be related to the REST problem mentioned in some of > the other issues. since on the server side (a non-Axis server) I see the > following: > POST / HTTP/1.1 > SOAPAction: "bookstore.echoMe" > User-Agent: Axis2 > Host: localhost: > Transfer-Encoding: chunked > Content-Type: text/xml; charset=UTF-8 > [Fatal Error] :-1:-1: Premature end of file. > This is the process I followed: > I installed the said version of Axis2 today. > I have my own wsdl (produced below). > I set up JAVA_HOME, AXIS2_HOME. > Then I ran: > c:\axis2-1.1.1\bin\wsdl2java.bat -f -d xmlbeans -uri c:\wsdl\bookstore.wsdl > which produced dirs/files under my current directory. > Then I wrote a client class to invoke the operation (produced below). > When I run it I get this exception on the client side I get the following > exception. > org.apache.axis2.AxisFault: First Element must contain the local name, > Envelope; nested exception is: > org.apache.axiom.soap.SOAPProcessingException: First Element must > contain the local name, Envelope > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:126) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:252) > at > org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202) > at bookstore.BookstoreStub.echoMe(BookstoreStub.java:141) > at client_pkg.MyAxisClient.thisEchoMe(MyAxisClient.java:43) > at client_pkg.MyAxisClient.main(MyAxisClient.java:22) > 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:324) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78) > Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element must > contain the local name, Envelope > at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:217) > at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:175) > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:120) > at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:159) > at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.identifySOAPVersion(StAXSOAPModelBuilder.java:133) > at > org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.(StAXSOAPModelBuilder.java:108) > at > org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:120) > ... 11 more > Here is the wsdl file: > xmlns:tns="bookstore" xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:tns="bookstore"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > >
Re: ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver
Hi ruchira , As i understand correct you have service hots in somewhere and you have two client stubs on in Axis1 and one in Axis2. If so why do you want two types of stubs , why cant you use only one stub. Thanks Deepal > Hi, > can you please let me know what is JIRA and how can i create JIRA... > > Here i am trying to explain you. > > 1)we have one webservice rDatasource which deal with database part such as > create ,delete, update from data base.For rDatasource we r using axis 1.3 > to generate client stub which is rdatasourceclient. > > 2)we have one more webservice systemservice for this we r using axis2.1.2 to > generate clint stub whos name is systemserviceclientstub > > > now flow is like that systemserviceclientstub(created by axis2.1.2) > interact with rdatasourceclientstub(created by axis1.3). > > > i m getting many problem in above situation. > is it possible abve situat or we have to all webservice in same asix either > in axis1.3 or axis2.1.2 > > > > > Deepal Jayasinghe-2 wrote: > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2898) Probelm of SOAP with JMS transport in axis2
[
https://issues.apache.org/jira/browse/AXIS2-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515994
]
Amila Chinthaka Suriarachchi commented on AXIS2-2898:
-
Can you try with a nightly build?
there were some problems with the when building the OMElement with ADB. Now ADB
uses the serialize method to buil the OMElement as well.
> Probelm of SOAP with JMS transport in axis2
> ---
>
> Key: AXIS2-2898
> URL: https://issues.apache.org/jira/browse/AXIS2-2898
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
>Affects Versions: 1.2
> Environment: Deploy axis2 in tomcat6.
> Use JMS of AcitiveMQ 4.1.0.
>Reporter: lizhao chen
>Assignee: Asankha C. Perera
>Priority: Blocker
> Attachments: jms_example.zip
>
>
> I am trying to test a webservice with JMS transport. The service works
> perfectly fine with HTTP but with JMS it gives the following exception during
> unmarshling. Looks like localName is incorrect.
> 2007-07-04 10:11:08,213 DEBUG org.apache.axiom.om.impl.builder.StAXOMBuilder
> - S
> TART_ELEMENT: {tmf854.v1}TopicExpression_T:TopicExpression_T
> 2007-07-04 10:11:08,213 DEBUG
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBu
> ilder - Build the OMElelment TopicExpression_TBy the StaxSOAPModelBuilder
> 2007-07-04 10:11:08,253 ERROR
> org.apache.axis2.transport.jms.JMSMessageReceiver
> - JMS Worker [JMSWorker-1] Encountered an Axis Fault :
> java.lang.RuntimeExceptio
> n: Unexpected subelement TopicExpression_T; nested exception is:
> java.lang.RuntimeException: java.lang.RuntimeException: Unexpected
> subel
> ement TopicExpression_T
> org.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected subelement
> To
> picExpression_T; nested exception is:
> java.lang.RuntimeException: java.lang.RuntimeException: Unexpected
> subel
> ement TopicExpression_T
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367)
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:55)
> at
> org.apache.axis2.receivers.AbstractInMessageReceiver.receive(Abstract
> InMessageReceiver.java:35)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:177)
> at
> org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessa
> geReceiver.java:204)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
> ker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
> ker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Unexpected
> su
> belement TopicExpression_T
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.fromOM(NotificationConsumerMessageReceiverInOnly.java:110)
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.invokeBusinessLogic(NotificationConsumerMessageReceiverInOnly.java:42)
> ... 6 more
> Caused by: java.lang.RuntimeException: Unexpected subelement TopicExpression_T
> at org.tmforum.tmf854.v1.Notify_T$Factory.parse(Notify_T.java:540)
> at org.tmforum.tmf854.v1.Notify$Factory.parse(Notify.java:292)
> at
> org.tmforum.tmf854.v1.ws.notif.NotificationConsumerMessageReceiverInO
> nly.fromOM(NotificationConsumerMessageReceiverInOnly.java:97)
> ... 7 more
--
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: ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver
Hi, can you please let me know what is JIRA and how can i create JIRA... Here i am trying to explain you. 1)we have one webservice rDatasource which deal with database part such as create ,delete, update from data base.For rDatasource we r using axis 1.3 to generate client stub which is rdatasourceclient. 2)we have one more webservice systemservice for this we r using axis2.1.2 to generate clint stub whos name is systemserviceclientstub now flow is like that systemserviceclientstub(created by axis2.1.2) interact with rdatasourceclientstub(created by axis1.3). i m getting many problem in above situation. is it possible abve situat or we have to all webservice in same asix either in axis1.3 or axis2.1.2 Deepal Jayasinghe-2 wrote: > > Hi Ruchira , > The issue you are facing is not clear to me , could you please create a > JIRA and attach whatever need to re-create the issues. > > Thanks > Deepal >> Hi, >> >> Is it possible that axis 2 client code can use axis1.3 client code. >> means like this Project1->axis1.3 client stub and 1 webservice (this part >> is >> workinng fine) >> >> project2 which contain project1 webservice stub which is generated by >> axis2. >> but when i am running rroject2 it is giving mainy error like >> >> ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver >> Exception in thread "main" java.lang.RuntimeException: >> java.lang.RuntimeException: Unexpected subelement >> getStartedReadersResponse >> at >> com.canarys.rfid.webservice.service.SystemControlWSStub.fromOM(SystemControlWSStub.java:63292) >> at >> com.canarys.rfid.webservice.service.SystemControlWSStub.getStartedReaders(SystemControlWSStub.java:1212) >> at >> com.canarys.rfid.webservice.service.SystemControlAndTrackingClient.main(SystemControlAndTrackingClient.java:36) >> Caused by: java.lang.RuntimeException: Unexpected subelement >> getStartedReadersResponse >> at >> com.canarys.rfid.webservice.service.SystemControlWSStub$GetStartedReadersResponse$Factory.parse(SystemControlWSStub.java:4660) >> at >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/ERROR-org.apache.axis2.rpc.receivers.RPCMessageReceiver-tf4156226.html#a11825687 Sent from the Axis - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Re: svn commit: r559011 - in /webservices/axis2/trunk/java/modules: addressing/src/META-INF/ integration/conf/ integration/test-resources/deployment/ integration/test-resources/mtom/ integ
In the case of WS-Security there are instance that the only way to dispatch is using addressing , and service and operation must be found before running the security handlers. If you take transport like SMTP the only way to dispatch is using addressing so we need to run addressing before security. May be Ruchith can add some more infor into this. Thanks Deepal > Um deepal, can you explain why we should have the > AddressingBased*Dispatcher* running before the *Dispatch* phase? > Thanks, > David > > On 25/07/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > >> Hi Glen, >> Yes I have to agree with you , but let's do that for next release. I >> would like to consider that as the first item to be fixed. >> >> Thanks >> Deepal >> >>> [Forward with correct prefix] >>> >>> Gosh. If only Modules ... >>> >>> http://marc.info/?l=axis-dev&m=118117804705440&w=2 >>> >>> ... could define their own Phases >>> >>> http://marc.info/?l=axis-dev&m=114404998012486&w=2 >>> >>> this commit could have consisted of a simple change to the Addressing >>> module's module.xml, and that would basically be it. This demonstrates, >>> once again, exactly the problem with the current overly-static design. >>> >>> I still stand by the position I wrote up last year: >>> >>> http://marc.info/?l=axis-dev&m=114417377917696&w=2 >>> >>> This needs to be fixed after 1.3, folks. >>> >>> --Glen >>> >>> >>> [EMAIL PROTECTED] wrote: >>> Author: deepal Date: Tue Jul 24 04:41:00 2007 New Revision: 559011 URL: http://svn.apache.org/viewvc?view=rev&rev=559011 Log: -Add a phase called Addressing as I mentioned in the mailing list - Move all the addressing handlers into Addressing phase - Had to modify a set of axis2.xml and test cases to cope this chang [This is a big commit but no need to worry :) ] Modified: webservices/axis2/trunk/java/modules/addressing/src/META-INF/module.xml webservices/axis2/trunk/java/modules/integration/conf/axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/deployment/deployment.both.axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/mtom/MTOM-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/mtom/MTOM-fileCache-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/swa/SwA-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test-resources/swa/SwA-fileCache-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/HandlerExecutionTest.java webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/chunking-disabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/chunking-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/commons-http-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/jms-enabled-client-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/jms-enabled-server-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-client-axis2.xml webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-server-axis2.xml webservices/axis2/trunk/java/modules/kernel/conf/axis2.xml webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/axis2_default.xml webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/deployment/ModuleDisengagementTest.java >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > -- Thanks, Deepal "The highest tower is built one brick at a time" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver
Hi Ruchira , The issue you are facing is not clear to me , could you please create a JIRA and attach whatever need to re-create the issues. Thanks Deepal > Hi, > > Is it possible that axis 2 client code can use axis1.3 client code. > means like this Project1->axis1.3 client stub and 1 webservice (this part is > workinng fine) > > project2 which contain project1 webservice stub which is generated by axis2. > but when i am running rroject2 it is giving mainy error like > > ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver > Exception in thread "main" java.lang.RuntimeException: > java.lang.RuntimeException: Unexpected subelement getStartedReadersResponse > at > com.canarys.rfid.webservice.service.SystemControlWSStub.fromOM(SystemControlWSStub.java:63292) > at > com.canarys.rfid.webservice.service.SystemControlWSStub.getStartedReaders(SystemControlWSStub.java:1212) > at > com.canarys.rfid.webservice.service.SystemControlAndTrackingClient.main(SystemControlAndTrackingClient.java:36) > Caused by: java.lang.RuntimeException: Unexpected subelement > getStartedReadersResponse > at > com.canarys.rfid.webservice.service.SystemControlWSStub$GetStartedReadersResponse$Factory.parse(SystemControlWSStub.java:4660) > at > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver
Hi, Is it possible that axis 2 client code can use axis1.3 client code. means like this Project1->axis1.3 client stub and 1 webservice (this part is workinng fine) project2 which contain project1 webservice stub which is generated by axis2. but when i am running rroject2 it is giving mainy error like ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement getStartedReadersResponse at com.canarys.rfid.webservice.service.SystemControlWSStub.fromOM(SystemControlWSStub.java:63292) at com.canarys.rfid.webservice.service.SystemControlWSStub.getStartedReaders(SystemControlWSStub.java:1212) at com.canarys.rfid.webservice.service.SystemControlAndTrackingClient.main(SystemControlAndTrackingClient.java:36) Caused by: java.lang.RuntimeException: Unexpected subelement getStartedReadersResponse at com.canarys.rfid.webservice.service.SystemControlWSStub$GetStartedReadersResponse$Factory.parse(SystemControlWSStub.java:4660) at com.canarys.rfid.webservice.service.SystemControlWSStub.fromOM(SystemControlWSStub.java:63244) ... 2 more so is there any possibility for this situation. -- View this message in context: http://www.nabble.com/ERROR-org.apache.axis2.rpc.receivers.RPCMessageReceiver-tf4156226.html#a11825287 Sent from the Axis - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Re: svn commit: r559011 - in /webservices/axis2/trunk/java/modules: addressing/src/META-INF/ integration/conf/ integration/test-resources/deployment/ integration/test-resources/mtom/ integ
Um deepal, can you explain why we should have the AddressingBased*Dispatcher* running before the *Dispatch* phase? Thanks, David On 25/07/07, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > Hi Glen, > Yes I have to agree with you , but let's do that for next release. I > would like to consider that as the first item to be fixed. > > Thanks > Deepal > > [Forward with correct prefix] > > > > Gosh. If only Modules ... > > > > http://marc.info/?l=axis-dev&m=118117804705440&w=2 > > > > ... could define their own Phases > > > > http://marc.info/?l=axis-dev&m=114404998012486&w=2 > > > > this commit could have consisted of a simple change to the Addressing > > module's module.xml, and that would basically be it. This demonstrates, > > once again, exactly the problem with the current overly-static design. > > > > I still stand by the position I wrote up last year: > > > > http://marc.info/?l=axis-dev&m=114417377917696&w=2 > > > > This needs to be fixed after 1.3, folks. > > > > --Glen > > > > > > [EMAIL PROTECTED] wrote: > >> Author: deepal > >> Date: Tue Jul 24 04:41:00 2007 > >> New Revision: 559011 > >> > >> URL: http://svn.apache.org/viewvc?view=rev&rev=559011 > >> Log: > >> -Add a phase called Addressing as I mentioned in the mailing list - > >> Move all the addressing handlers into Addressing phase > >> - Had to modify a set of axis2.xml and test cases to cope this chang > >> > >> [This is a big commit but no need to worry :) ] > >> > >> Modified: > >> > >> webservices/axis2/trunk/java/modules/addressing/src/META-INF/module.xml > >> webservices/axis2/trunk/java/modules/integration/conf/axis2.xml > >> > >> webservices/axis2/trunk/java/modules/integration/test-resources/deployment/deployment.both.axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test-resources/mtom/MTOM-enabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test-resources/mtom/MTOM-fileCache-enabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test-resources/swa/SwA-enabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test-resources/swa/SwA-fileCache-enabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/HandlerExecutionTest.java > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/chunking-disabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/chunking-enabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/engine/commons-http-enabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/jms-enabled-client-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/jms/jms-enabled-server-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-client-axis2.xml > >> > >> > >> webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/mail/mail-enabled-server-axis2.xml > >> > >> webservices/axis2/trunk/java/modules/kernel/conf/axis2.xml > >> > >> webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/axis2_default.xml > >> > >> > >> webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/deployment/ModuleDisengagementTest.java > >> > >> > > > - > 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]
