[jira] Resolved: (AXIS2-461) JAXB2 unmarshaling(XMLStramWriter) leads to java.langUnsupportedOperationException
[ http://issues.apache.org/jira/browse/AXIS2-461?page=all ] Davanum Srinivas resolved AXIS2-461: Resolution: Fixed Fix in Axiom rev 412440 > JAXB2 unmarshaling(XMLStramWriter) leads to > java.langUnsupportedOperationException > -- > > Key: AXIS2-461 > URL: http://issues.apache.org/jira/browse/AXIS2-461 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: databinding > Versions: 0.95 > Environment: Apache Axis2 0.95-snaphot from 14-02-2006 > Reporter: Tobias Israel > Attachments: Axis2JAXBBinding.java, Person.java, Person.java > > The use of a XMLStramReader, received from OMElement.getXMLStreamReader(), > for performing a JAXB2 unmarshal(XMLStreamReader) operation leads to the > following Exception: > Exception in thread "main" java.lang.UnsupportedOperationException > at > org.apache.ws.commons.om.impl.llom.OMStAXWrapper.getNamespaceContext(OMStAXWrapper.java:983) > at > com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:125) > at > com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:332) > at > com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:304) > at > com.signsoft.eval.axis2.databinding.Axis2JAXBBinding.main(Axis2JAXBBinding.java:50) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-810) Axis2 1.0 server remove nillable attributes
[ http://issues.apache.org/jira/browse/AXIS2-810?page=comments#action_12415331 ] Davanum Srinivas commented on AXIS2-810: Please upload your complete wsdl. thanks, dims > Axis2 1.0 server remove nillable attributes > --- > > Key: AXIS2-810 > URL: http://issues.apache.org/jira/browse/AXIS2-810 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: wsdl > Versions: 1.0 > Environment: Widows XP > JDK 1.5.0_06 > apache-tomcat-5.5.12 > Axis2 1.0 webapp > Reporter: Sébastien Arod > Priority: Critical > > When I deploy a web service with a specified WSDL in the Axis2 webapp the xsd > nillable attributes are removed from WSDL by Axis2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-761) SimpleHttpServer based on Jakarta HttpComponents HttpCore
[ http://issues.apache.org/jira/browse/AXIS2-761?page=comments#action_12415464 ] Davanum Srinivas commented on AXIS2-761: Please try now. you should have karma now. -- dims > SimpleHttpServer based on Jakarta HttpComponents HttpCore > - > > Key: AXIS2-761 > URL: http://issues.apache.org/jira/browse/AXIS2-761 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: transports > Versions: 1.0 > Reporter: Oleg Kalnichevski > Attachments: ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.consolidated.patch, > ConfigurableSimpleHTTPServer.patch, simplehttpserver.patch > > The following patch replaces the SimpleHttpServer implementation based on the > testing framework of Commons HttpClient 3.x with a one based on Jakarta > HttpComponents HttpCore. Compiled against Axis2 trunk and HttpCore trunk > * Removes all references to Commons HttpClient classes > * Enables streaming of schema definitions and similar content > * Improves content buffering of SOAP response > * Improves handling of fault conditions and exception handling > * Fixes a number of NPEs in AxisEngine > * Improves performance and reliability of the HTTP transport -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-761) SimpleHttpServer based on Jakarta HttpComponents HttpCore
[ http://issues.apache.org/jira/browse/AXIS2-761?page=comments#action_12415477 ] Davanum Srinivas commented on AXIS2-761: could u please log out and try log back in? -- dims > SimpleHttpServer based on Jakarta HttpComponents HttpCore > - > > Key: AXIS2-761 > URL: http://issues.apache.org/jira/browse/AXIS2-761 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: transports > Versions: 1.0 > Reporter: Oleg Kalnichevski > Attachments: ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.complete.patch, > ConfigurableSimpleHTTPServer.consolidated.patch, > ConfigurableSimpleHTTPServer.patch, simplehttpserver.patch > > The following patch replaces the SimpleHttpServer implementation based on the > testing framework of Commons HttpClient 3.x with a one based on Jakarta > HttpComponents HttpCore. Compiled against Axis2 trunk and HttpCore trunk > * Removes all references to Commons HttpClient classes > * Enables streaming of schema definitions and similar content > * Improves content buffering of SOAP response > * Improves handling of fault conditions and exception handling > * Fixes a number of NPEs in AxisEngine > * Improves performance and reliability of the HTTP transport -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-668) AntCodegenTask throws exception
[ http://issues.apache.org/jira/browse/AXIS2-668?page=all ] Davanum Srinivas resolved AXIS2-668: Resolution: Fixed Fixed in 413082 2 days back http://marc.theaimsgroup.com/?l=axis-cvs&m=114986900104751&w=2 thanks, dims > AntCodegenTask throws exception > --- > > Key: AXIS2-668 > URL: http://issues.apache.org/jira/browse/AXIS2-668 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: Tools > Versions: 1.0 > Environment: axis2-1.0 svn 2005-05-04 (noon) > Reporter: Bryan Brouckaert > Assignee: Ajith Harshana Ranabahu > Attachments: build-test.xml, jars.txt > > The AntCodegenTask throws following error: > "javax.xml.stream.FactoryConfigurationError: Provider > com.bea.xml.stream.MXParserFactory not found" > All jars of the Axis2 library are included in the class path. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-697) fetching WSDL description using aService?wsdl does not work in Jetty
[ http://issues.apache.org/jira/browse/AXIS2-697?page=all ]
Davanum Srinivas resolved AXIS2-697:
Resolution: Invalid
Looks like they fixed the problem in jetty-6.0.0beta17
thanks,
dims
> fetching WSDL description using aService?wsdl does not work in Jetty
>
>
> Key: AXIS2-697
> URL: http://issues.apache.org/jira/browse/AXIS2-697
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: deployment
> Environment: Jdk 1.5, Jetty 6.0.0 Beta14
> Reporter: Wang PengChao
> Assignee: Deepal Jayasinghe
>
>
> Phenomenon:
> Service 'aService' deployed in Jetty, when user fetches aService's WSDL
> description using http://domain/services/aService?wsdl, axis2 will return 404
> ERROR. But request url like http://domain/services/aService?wsdl= or
> http://domain/services/aService?wsdl=anything can work.
> Analysis:
> The code here in ListAgent.handle()
> if (httpServletRequest.getParameter("wsdl") != null ||
> httpServletRequest.getParameter("xsd") != null) {
> processListService(httpServletRequest, httpServletResponse);
> } else {
> super.handle(httpServletRequest, httpServletResponse);
> }
> It use request.getParameter() to determin whether the request is a WSDL or
> XSD description request. It works fine in tomcat. But Jetty has different way
> to process request like http://.../servlet?parameterName, which has no '='
> followed. In tomcat, while processing this kind of link, parameterName will
> be put in paramter map with the value set to an empty string, but in Jetty it
> will be simply thrown away. It is not a bug of Jetty, because how to deal
> with this kind of request parameters is not mentioned in the servlet
> specification.
> Suggest:
> I think using feature which different between servlet containers is not
> smart. So I suggest using request.getQueryString() to replace the
> getParameter():
> in ListAgent.handle() before code snip change to..
> if (isWSDLOrXSDRequest(httpServletRequest)) {
> processListService(httpServletRequest, httpServletResponse);
> } else {
> super.handle(httpServletRequest, httpServletResponse);
> }
> add method in ListAgent..
> private boolean isWSDLOrXSDRequest(HttpServletRequest httpServletRequest)
> {
> String query = httpServletRequest.getQueryString();
> if(query == null){
> return false;
> }
> return query.indexOf("wsdl") >=0 || query.indexOf("xsd") >=0;
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-814) unwrapping support in codegen
unwrapping support in codegen - Key: AXIS2-814 URL: http://issues.apache.org/jira/browse/AXIS2-814 Project: Apache Axis 2.0 (Axis2) Type: New Feature Reporter: Davanum Srinivas Please see the discussion here: http://marc.theaimsgroup.com/?t=11500696423&r=1&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-815) Update ADB codegen to use OMDataSource
Update ADB codegen to use OMDataSource -- Key: AXIS2-815 URL: http://issues.apache.org/jira/browse/AXIS2-815 Project: Apache Axis 2.0 (Axis2) Type: Improvement Reporter: Davanum Srinivas We need to make ADB databinding use OMDataSource, so that there is an optionto write directly to stream (right now we always pull events and write the events to the stream). thanks, dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-758) Generated xmlbeans code is not handling elementFormDefault correctly
[ http://issues.apache.org/jira/browse/AXIS2-758?page=all ] Davanum Srinivas resolved AXIS2-758: Resolution: Fixed Please try latest nightly builds and let us know if we have to repoen this bug. thanks, dims > Generated xmlbeans code is not handling elementFormDefault correctly > > > Key: AXIS2-758 > URL: http://issues.apache.org/jira/browse/AXIS2-758 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: databinding > Versions: 1.0 > Environment: WinXP > Reporter: Kent Tong > Assignee: Ajith Harshana Ranabahu > Attachments: FileClient.java, FileService2.wsdl, FileServiceSkeleton.java, > build.xml > > In the in my WSDL file (as attached), no matter elementFormDefault > is set to unqualified or qualified, the request SOAP message is the same: > > http://schemas.xmlsoap.org/soap/envelope/";> > > > http://foo.com/FileService/schema";> > f01 > R0lGODlhQwJ... > > > > Obviously this is incorrect when elementFormDefault="unqualified". Probably > as a result, the generated skeleton works only when > elementFormDefault="qualified". Otherwise if will fail to find an unqualified > or child element. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-542) Implement W3C WSDL 2.0 CR
[ http://issues.apache.org/jira/browse/AXIS2-542?page=all ] Davanum Srinivas resolved AXIS2-542: Resolution: Fixed We have some support now. Let's close the catch all issue and open specific ones. thanks, dims > Implement W3C WSDL 2.0 CR > - > > Key: AXIS2-542 > URL: http://issues.apache.org/jira/browse/AXIS2-542 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: wsdl, Tools > Versions: 1.0 > Reporter: Arthur Ryman > > I am opening a JIRA for this work to give us a place to track it. Glen took > an action in the WSDL 2.0 Working Group Implementors call a few weeks ago to > do this but he must be too busy. See > http://marc.theaimsgroup.com/?l=axis-dev&m=114252720713194&w=2 for a > discussion. > The requirement is to support WSDL 2.0 alongside WSDL 1.1. This means to > upgrade the WSDL2Java and Java2WSDL tools and to generate WSDL at runtime (if > there is no WSDL deployed with a Web service). > Work is underway already. Chathura is looking at replacing the Axis2 WOM with > the Woden Component Model. That would achieve WSDL 2.0 support. For backward > support of WSDL 1.1, some new extensions would have to be defined for WSDL > 2.0, i.e. the WSDL 2.0 Component Model could be extended to express the > features of WSDL 1.1 not supported by the core WSDL 2.0 spec and its > adjuncts. I asked Matthew to look into this. > It would greatly help the current W3C WSDL 2.0 Candidate Recommendation > advance to the Proposed Recommendation stage if Axis2 could provide an > implementation and participate in an interop event within the next few months. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-757) XMLbeans code generation fails with ArrayStoreException in Ant but works from WSDL2Code.main()
[ http://issues.apache.org/jira/browse/AXIS2-757?page=all ] Davanum Srinivas resolved AXIS2-757: Resolution: Fixed Please try latest SVN. we think we've fixed this now. thanks, dims > XMLbeans code generation fails with ArrayStoreException in Ant but works from > WSDL2Code.main() > -- > > Key: AXIS2-757 > URL: http://issues.apache.org/jira/browse/AXIS2-757 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: databinding > Versions: 1.0 > Environment: WinXP. jdk1.5.0_02. Eclipse 3.1.2. > Reporter: Kent Tong > Attachments: FileService.wsdl, build.xml > > Given a very simple WSDL (attached), the following Ant task fails: > wsdlfilename="FileService.wsdl" > databindingname="xmlbeans" > serverside="true" > generateallclasses="true" > generateservicexml="true" > packagename="com.foo.fs" > > namespacetopackages="http://foo.com/FileService/=com.foo.fs,http://foo.com/FileService/schema=com.foo.schema"; > /> > The stack trace is shown below. However, if I run WSDL2Code.main() directly, > then it works. I suspect this may be a classloader issue and could be related > to AXIS2-668. Changing databindingname to "adb" in build.xml also works. > Stack trace: > C:\Books\DWSAA\v20\workspace\FileService\build.xml:21: > org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at > org.apache.axis2.tool.ant.AntCodegenTask.execute(AntCodegenTask.java:266) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > at org.apache.tools.ant.Task.perform(Task.java:364) > at org.apache.tools.ant.Target.execute(Target.java:341) > at org.apache.tools.ant.Target.performTasks(Target.java:369) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) > at org.apache.tools.ant.Project.executeTarget(Project.java:1185) > at > org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) > at > org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) > at org.apache.tools.ant.Project.executeTargets(Project.java:1068) > at > org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423) > at > org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137) > Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185) > at > org.apache.axis2.tool.ant.AntCodegenTask.execute(AntCodegenTask.java:264) > ... 11 more > Caused by: java.lang.RuntimeException: > java.lang.reflect.InvocationTargetException > at > org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:93) > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:140) > ... 12 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:83) > ... 13 more > Caused by: java.lang.RuntimeException: java.lang.ArrayStoreException > at > org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:192) > ... 18 more > Caused by: java.lang.ArrayStoreException > at java.lang.System.arraycopy(Native Method) > at java.util.ArrayList.toArray(Unknown Source) > at > org.apache.axis2.xmlbeans.CodeGenerationUtility.convertToSchemaDocumentArray(CodeGenerationUtility.java:369) > at > org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:157) > ... 18 more > --- Nested Exception --- > org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185) > at > org.apache.axis2.tool.ant.AntCodegenTask.execute(AntCodegenTask.java:264) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) > at org.apache.tools.ant.Task.perform(Task.java:364) > at org.apache.t
[jira] Commented: (AXIS2-542) Implement W3C WSDL 2.0 CR
[ http://issues.apache.org/jira/browse/AXIS2-542?page=comments#action_12415890 ] Davanum Srinivas commented on AXIS2-542: In latest SVN, Please try the option "-wv 2" when running wsdl2java and at runtime try "?wsdl2" instead of the usual "?wsdl" thanks, -- dims > Implement W3C WSDL 2.0 CR > - > > Key: AXIS2-542 > URL: http://issues.apache.org/jira/browse/AXIS2-542 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: Tools, wsdl > Versions: 1.0 > Reporter: Arthur Ryman > > I am opening a JIRA for this work to give us a place to track it. Glen took > an action in the WSDL 2.0 Working Group Implementors call a few weeks ago to > do this but he must be too busy. See > http://marc.theaimsgroup.com/?l=axis-dev&m=114252720713194&w=2 for a > discussion. > The requirement is to support WSDL 2.0 alongside WSDL 1.1. This means to > upgrade the WSDL2Java and Java2WSDL tools and to generate WSDL at runtime (if > there is no WSDL deployed with a Web service). > Work is underway already. Chathura is looking at replacing the Axis2 WOM with > the Woden Component Model. That would achieve WSDL 2.0 support. For backward > support of WSDL 1.1, some new extensions would have to be defined for WSDL > 2.0, i.e. the WSDL 2.0 Component Model could be extended to express the > features of WSDL 1.1 not supported by the core WSDL 2.0 spec and its > adjuncts. I asked Matthew to look into this. > It would greatly help the current W3C WSDL 2.0 Candidate Recommendation > advance to the Proposed Recommendation stage if Axis2 could provide an > implementation and participate in an interop event within the next few months. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-812) Improve SimpleHTTPServer code structure, configuraiton, cookie use, and remove unused classes
[ http://issues.apache.org/jira/browse/AXIS2-812?page=all ] Davanum Srinivas resolved AXIS2-812: Resolution: Fixed Applied. (in rev 413740) thanks, dims > Improve SimpleHTTPServer code structure, configuraiton, cookie use, and > remove unused classes > - > > Key: AXIS2-812 > URL: http://issues.apache.org/jira/browse/AXIS2-812 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: transports > Reporter: Chuck Williams > Assignee: Chuck Williams > Attachments: simplehttpserver-cleanup-2.patch, simplehttpserver-cleanup.patch > > We need to clean up the code for the new HttpCore based SimpleHTTPServer. > Per Oleg: > I still would like to clean things up a little here and there (at the very > least the old classes from HttpClient testing framework should be removed). I > would also like to refactor the session context management code and improve > cookie handling. Presently Set-Cookie2 headers generated by the HTTPWorker > are not spec compliant. > Per my commit message: > Still to do: > 1. Identify and remove any Commons classes that are no longer referenced > 2. Extend HttpFactory and config parameters for additional options > 3. Document in xdocs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-806) Compilation errors in Axis2 tools package.
[ http://issues.apache.org/jira/browse/AXIS2-806?page=all ] Davanum Srinivas reassigned AXIS2-806: -- Assign To: Ajith Harshana Ranabahu > Compilation errors in Axis2 tools package. > -- > > Key: AXIS2-806 > URL: http://issues.apache.org/jira/browse/AXIS2-806 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: Tools > Versions: 1.0 > Environment: Win XP > Reporter: Samuel Isokpunwu > Assignee: Ajith Harshana Ranabahu > Priority: Blocker > Attachments: WSDL2JavaGenerator-patch.txt > > > 1. The org.apache.axis2.tool.codegen.WSDL2JavaGenerator is referencing > org.apache.axis2.description.WSDL2AxisServiceBuilder builder class that no > longer exist in the current org.apache.axis2.description package. The > description package now contains WSDLToAxisServiceBuilder.java as parent > builder class with WSDL11ToAxisServiceBuilder and WSDL20ToAxisServiceBuilder > as subclasses. > 2. Also, the following line of code in > org.apache.axis2.tool.codegen.WSDL2JavaGenerator class -- > WSDL2AxisServiceBuilder builder = new > WSDL2AxisServiceBuilder(url.openConnection().getInputStream()); > will not only fail to compile because the class no longer exist in the Axis2 > description package, it will also fail to compile because the one-argument > Constructor that is being referenced in this line of code does not exist in > the newly created builder classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-809) StAXOMBuilder.next() throws IllegalArgumentException
[ http://issues.apache.org/jira/browse/AXIS2-809?page=all ] Davanum Srinivas resolved AXIS2-809: Resolution: Cannot Reproduce Could u please add some code / test case for us to recreate the problem? thanks, dims > StAXOMBuilder.next() throws IllegalArgumentException > > > Key: AXIS2-809 > URL: http://issues.apache.org/jira/browse/AXIS2-809 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: om > Versions: 1.0 > Environment: Windows 2000 Professional > JSDK 1.4.2_05 > WebLogic Server 8.1 SP4 > Reporter: Marc Forget > > StAXOMBuilder.next() throws IllegalArgumentException:"invalid QName prefix" > when debug is turned on, add parser.getName() is invoked. > org.apache.axiom.om.OMException: java.lang.IllegalArgumentException: invalid > QName prefix > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206) > at > org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:144) > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:322) > at > org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:85) > at > org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:58) > at > org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:783) > at > org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:113) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:38) > at > org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:90) > The stream that is being parsed is the axis2.xml configuration file that is > included in axis2-kernel-1.0.jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-807) For an interface with a complex type parameter for the method, incorrect WSDL is generated
[ http://issues.apache.org/jira/browse/AXIS2-807?page=comments#action_12415911 ] Davanum Srinivas commented on AXIS2-807: Could u please try a nightly build? http://people.apache.org/dist/axis2/nightly/ -- dims > For an interface with a complex type parameter for the method, incorrect WSDL > is generated > -- > > Key: AXIS2-807 > URL: http://issues.apache.org/jira/browse/AXIS2-807 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: wsdl > Versions: 1.0 > Environment: Windows XP Professional, Eclipse 3.1.2, JDK 1.5.0 > Reporter: James Bender > Attachments: FoodDescription.java, IWWPointsCalculator.java > > I am working on converting an existing Axis2 0.93 web service generator that > uses facilities for Java2WSDL and WSDL2Java, by running Ant tasks > programmatically with Leafcutter. I started a conversion, yesterday > afternoon, to Axis2 Std 1.0, and wanted to use my toy example that has a > class with an interface with one method that takes a complex type as a > parameter. In Axis2 0.93, I am able to successfully generate the WSDL file, > successfully run WSDL2Java, and after programmatically updating the skeleton, > compile, and eventually generate a jar and .aar file. The driver is a TestNG > test that uses embedded Tomcat 5.5 for testing the generated service. > When I try to do the same thing with Axis2 Std 1.0, an incorrect WSDL file is > generated that is rejected by WSDL2Java: > INFO Running: java classname=org.apache.axis2.wsdl.WSDL2Java fork=true > classpathref (arg value= > -uri ) (arg > file=c:\Java\projects2\axis2-std-1.0testbed\build\wsdl\WWPointsCalculator.wsdl > ) (arg va > lue=-s ) (arg value=-ss ) (arg value=-sd ) (arg value=-o ) (arg > file=c:\Java\projects2\axis2-std-1.0 > testbed\build\output ) (arg value=-p ) (arg value=testexamples.types ) > WARN Exception in thread "main" > org.apache.axis2.wsdl.codegen.CodeGenerationException: Error par > sing WSDL > WARN at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:94) > WARN at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > WARN at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) > WARN Caused by: org.apache.axis2.AxisFault: Schema for namespace > 'http://PointsCalculator.ve.rec > ursionsw.com/types' already contains type 'FoodDescription; nested exception > is: > WARN java.lang.RuntimeException: Schema for namespace > 'http://PointsCalculator.ve.recursionsw.c > om/types' already contains type 'FoodDescription > WARN at > org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBu > ilder.java:243) > WARN at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:87) > WARN ... 2 more > WARN Caused by: java.lang.RuntimeException: Schema for namespace > 'http://PointsCalculator.ve.rec > ursionsw.com/types' already contains type 'FoodDescription > WARN at > org.apache.ws.commons.schema.XmlSchema.addType(XmlSchema.java:237) > WARN at > org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:10 > 3) > WARN at > org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:233) > WARN at > org.apache.axis2.description.WSDL2AxisServiceBuilder.getXMLSchema(WSDL2AxisServiceBuild > er.java:959) > WARN at > org.apache.axis2.description.WSDL2AxisServiceBuilder.copyExtensibleElements(WSDL2AxisSe > rviceBuilder.java:1067) > WARN at > org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBu > ilder.java:221) > The Java2WSDL generator puts two copies of the complex type definition in the > file, and that is what is bad. 0.93 did not have that problem, although to > produce compilable files, the interface supplied had to be in the default > package, a problem seemingly solved in 1.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-816) WSDL2Java throws NullPointer
[ http://issues.apache.org/jira/browse/AXIS2-816?page=comments#action_12415921 ] Davanum Srinivas commented on AXIS2-816: please upload schema/wsdls. thx, dims > WSDL2Java throws NullPointer > > > Key: AXIS2-816 > URL: http://issues.apache.org/jira/browse/AXIS2-816 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: wsdl, Tools > Versions: 1.0 > Environment: WinXP / JDK 1.4.2 > Reporter: Michael Connor > > org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeException: > org.apache.axis2.schema.SchemaCompilationException: > java.lang.NullPointerException > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185) > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > Caused by: java.lang.RuntimeException: > org.apache.axis2.schema.SchemaCompilationException: > java.lang.NullPointerException > at > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:117) > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:140) > ... 1 more > Caused by: org.apache.axis2.schema.SchemaCompilationException: > java.lang.NullPointerException > at > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:186) > at > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:70) > ... 2 more > Caused by: java.lang.NullPointerException > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:360) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:344) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:410) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:334) > at > org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:915) > at > org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:878) > at > org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:643) > at > org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:616) > at > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:577) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:366) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:344) > at > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:226) > at > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:181) > ... 3 more > Exception in thread "main" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-812) Improve SimpleHTTPServer code structure, configuraiton, cookie use, and remove unused classes
[ http://issues.apache.org/jira/browse/AXIS2-812?page=comments#action_12415922 ] Davanum Srinivas commented on AXIS2-812: Oleg, sure! please create a new jira and we'll take care of it. Thanks for ur tremendous efforts. -- dims > Improve SimpleHTTPServer code structure, configuraiton, cookie use, and > remove unused classes > - > > Key: AXIS2-812 > URL: http://issues.apache.org/jira/browse/AXIS2-812 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: transports > Reporter: Chuck Williams > Assignee: Chuck Williams > Attachments: simplehttpserver-cleanup-2.patch, simplehttpserver-cleanup.patch > > We need to clean up the code for the new HttpCore based SimpleHTTPServer. > Per Oleg: > I still would like to clean things up a little here and there (at the very > least the old classes from HttpClient testing framework should be removed). I > would also like to refactor the session context management code and improve > cookie handling. Presently Set-Cookie2 headers generated by the HTTPWorker > are not spec compliant. > Per my commit message: > Still to do: > 1. Identify and remove any Commons classes that are no longer referenced > 2. Extend HttpFactory and config parameters for additional options > 3. Document in xdocs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-802) Possible header formation bug
[ http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12415932 ] Davanum Srinivas commented on AXIS2-802: Can u please post the whole stack trace? may be a test case for us to recreate the problem as well? Alternatively, please try the nightly builds (http://people.apache.org/dist/axis2/nightly/) thanks, dims > Possible header formation bug > - > > Key: AXIS2-802 > URL: http://issues.apache.org/jira/browse/AXIS2-802 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: core > Versions: 1.0 > Environment: Linux Fedora Core 5, JBoss 4.1 > Reporter: Denis Orlov > > I am trying to test a service with the header. I auto generated stubs > and every time I invoke the service it returns the following message: > org.apache.axis2.AxisFault: SOAPEnvelope must contain a body element > which is either first or second child element of the SOAPEnvelope. > The service works fine if the header is not set. The header is a simple > object with 3 string fields. I do not have a header handler on the > server side. > Here is the SOAP message: > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > xmlns:ns1="http://tests.ws.dbvr.com/types";>1egehh > xmlns:ns1="http://tests.ws.dbvr.com/types";>erewtr4sfddffcewefewfde -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-720) Data binding Error after using WSDL2Java to generate xmlbeans code
[
http://issues.apache.org/jira/browse/AXIS2-720?page=comments#action_12415980 ]
Davanum Srinivas commented on AXIS2-720:
Christopher,
Could u please help by creating a new JIRA issue. and upload your wsdl / test
case? Please add a note in the comment that it is related to this jira issue.
Thanks,
dims
> Data binding Error after using WSDL2Java to generate xmlbeans code
> --
>
> Key: AXIS2-720
> URL: http://issues.apache.org/jira/browse/AXIS2-720
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding
> Versions: 1.0
> Environment: Server: Axis2 1.0 inside a Tomcat 5.5.15 under Scientific
> Linux, 2.6.x kernel
> Client: Windows XP SP2 with JDK 1.5.0_06
> Reporter: Rincewind Wizard
> Assignee: Ajith Harshana Ranabahu
> Attachments: EpiLocService.wsdl, EpiLocService.wsdl, TextLocService.aar,
> TextLocServiceSkeleton.java, TextLocServiceTest.java
>
> We've used the attached WSDL to create a service & client by means of
> the WSDL2Java tool (xmlbeans databinding). After implementing the
> simplest of business logics in the server, we deployed the service .aar
> in the axis2 install inside a tomcat server. According to the status
> page, the service is running error free.
> The client was also created by WSDL2Java, where we wrote a simple main()
> class to test the client. We've pasted it below.
> public static void main(String[] args) {
>try {
> PredictLocalizationRequestDocument pdoc =
> PredictLocalizationRequestDocument.Factory.newInstance();
> pdoc.addNewPredictLocalizationRequest();
> pdoc.getPredictLocalizationRequest().setSequence("ASDF");
> pdoc.getPredictLocalizationRequest().setOrganism("ANIMAL");
> TextLocServiceStub sender = new
> TextLocServiceStub("http://localhost/axis2/services/TextLocService";);
> PredictLocalizationResponseDocument res =
> sender.predictLocalization(pdoc);
> System.out.println(res.toString());
>} catch (Exception e) {
> e.printStackTrace();
>}
> }
> The client now runs up until the document is being sent, where it throws
> an Exception. The stack trace is below. We think it is still a
> client-side problem, although the client does complain if it is not
> connected to the server and doesn't throw this exception.
> Please let us know if we should change anything about our client
> generation procedure, or how we can use the test client jar that is also
> generated by the WSDL2Java tool.
> Thanks a lot for your time!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-816) WSDL2Java throws NullPointer
[ http://issues.apache.org/jira/browse/AXIS2-816?page=all ] Davanum Srinivas closed AXIS2-816: -- Resolution: Incomplete Please upload the schema/wsdl's and we'll reopen the bug. thanks, dims > WSDL2Java throws NullPointer > > > Key: AXIS2-816 > URL: http://issues.apache.org/jira/browse/AXIS2-816 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: wsdl, Tools > Versions: 1.0 > Environment: WinXP / JDK 1.4.2 > Reporter: Michael Connor > > org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeException: > org.apache.axis2.schema.SchemaCompilationException: > java.lang.NullPointerException > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185) > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > Caused by: java.lang.RuntimeException: > org.apache.axis2.schema.SchemaCompilationException: > java.lang.NullPointerException > at > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:117) > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:140) > ... 1 more > Caused by: org.apache.axis2.schema.SchemaCompilationException: > java.lang.NullPointerException > at > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:186) > at > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:70) > ... 2 more > Caused by: java.lang.NullPointerException > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:360) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:344) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:410) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:334) > at > org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:915) > at > org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:878) > at > org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:643) > at > org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:616) > at > org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:577) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:366) > at > org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:344) > at > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:226) > at > org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:181) > ... 3 more > Exception in thread "main" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-806) Compilation errors in Axis2 tools package.
[ http://issues.apache.org/jira/browse/AXIS2-806?page=all ] Davanum Srinivas resolved AXIS2-806: Resolution: Fixed Applied. thanks, dims > Compilation errors in Axis2 tools package. > -- > > Key: AXIS2-806 > URL: http://issues.apache.org/jira/browse/AXIS2-806 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: Tools > Versions: 1.0 > Environment: Win XP > Reporter: Samuel Isokpunwu > Assignee: Ajith Harshana Ranabahu > Priority: Blocker > Attachments: WSDL2JavaGenerator-patch.txt > > > 1. The org.apache.axis2.tool.codegen.WSDL2JavaGenerator is referencing > org.apache.axis2.description.WSDL2AxisServiceBuilder builder class that no > longer exist in the current org.apache.axis2.description package. The > description package now contains WSDLToAxisServiceBuilder.java as parent > builder class with WSDL11ToAxisServiceBuilder and WSDL20ToAxisServiceBuilder > as subclasses. > 2. Also, the following line of code in > org.apache.axis2.tool.codegen.WSDL2JavaGenerator class -- > WSDL2AxisServiceBuilder builder = new > WSDL2AxisServiceBuilder(url.openConnection().getInputStream()); > will not only fail to compile because the class no longer exist in the Axis2 > description package, it will also fail to compile because the one-argument > Constructor that is being referenced in this line of code does not exist in > the newly created builder classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-760) AXIS2 generates un-compilable source with WSDL2Java - Looks like it refers to old version of method signature in the generated code
[
http://issues.apache.org/jira/browse/AXIS2-760?page=comments#action_12416202 ]
Davanum Srinivas commented on AXIS2-760:
Looks like we don't handle rpc/lit well with XmlBeans Databinding.
-- dims
> AXIS2 generates un-compilable source with WSDL2Java - Looks like it refers to
> old version of method signature in the generated code
> ---
>
> Key: AXIS2-760
> URL: http://issues.apache.org/jira/browse/AXIS2-760
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding
> Versions: 1.0
> Environment: Windows XP
> Reporter: Arun Nagaraj
> Assignee: Ajith Harshana Ranabahu
> Attachments: MovieGridApp.wsdl
>
> I am trying to compile and get the source code for both client and server for
> last month from the day 1.0 is released.
> I am unsuccesful.
> I am using the following command in Microsoft DOS
> wsdl2java -uri MovieGridApp.wsdl -ss -sd -g -d xmlbeans -p
> com.ibm.grid.moviegridapp
> I get the following code for "MovieGridAppStub.java" and
> "MovieGridAppMessageReceiverInOut.java" - which IBM Rational Application
> Developer does not understand.
> -- in method 1->
> public org.apache.xmlbeans.XmlObject fromOM(
> org.apache.axiom.om.OMElement param,
> java.lang.Class type,
> java.util.Map extraNamespaces){
> try{
>
> if (org.apache.axiom.om.OMElement.class.equals(type)){
> if (extraNamespaces!=null){
> return org.apache.axiom.om.OMElement.Factory.parse(
>param.getXMLStreamReaderWithoutCaching(),
>new
> org.apache.xmlbeans.XmlOptions().setLoadAdditionalNamespaces(extraNamespaces));
> }else{
> return org.apache.axiom.om.OMElement.Factory.parse(
>param.getXMLStreamReaderWithoutCaching());
> }
> }
>
> }catch(java.lang.Exception e){
> throw new RuntimeException("Data binding error",e);
> }
> return null;
> }
> &
> in method 2-->
> private org.apache.axiom.om.OMElement toOM(org.apache.axiom.om.OMElement
> param, boolean optimizeContent){
> org.apache.axiom.om.impl.builder.StAXOMBuilder builder = new
> org.apache.axiom.om.impl.builder.StAXOMBuilder
> (org.apache.axiom.om.OMAbstractFactory.getOMFactory(),new
> org.apache.axis2.util.StreamWrapper(param.newXMLStreamReader())) ;
> org.apache.axiom.om.OMElement documentElement =
> builder.getDocumentElement();
>
> ((org.apache.axiom.om.impl.OMNodeEx)documentElement).setParent(null);
> return documentElement;
> }
> BOTH THE CASE in Method 1, refer to
> "org.apache.axiom.om.OMElement.Factory.parse", in OMElement does not have
> Factory and parse method.
> IN THE CASE of method 2, refer to newXMLStreamReader(), which does not exists.
> I herewith attaching the WSDL file -moviegridapp.wsdl.
> Some has answered for BUG # 649, asking us to download the latest code,
> however, the latest downloaded on 21 May 2006 @ 4PM does not work as well.
> If anyone has cracked the bug, please let me know where I am going wrong or
> how to correct the mistake.
> Regards
> Arun
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-734) Log4j settings and configuration
[
http://issues.apache.org/jira/browse/AXIS2-734?page=comments#action_12416294 ]
Davanum Srinivas commented on AXIS2-734:
Please remove log4j.jar and you will not see #1
> Log4j settings and configuration
>
>
> Key: AXIS2-734
> URL: http://issues.apache.org/jira/browse/AXIS2-734
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas
> Assignee: Eran Chinthaka
>
> Original email:
> http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200605.mbox/[EMAIL
> PROTECTED]
> 1. Annoyance: WSDL2Java.bat issues a warning because Log4J cannot be
> properly configured.
> When running WSDL2Java.bat, the following warning is displayed:
> log4j:WARN No appenders could be found for logger
> (org.apache.axis2.i18n.ProjectResourceBundle).
> log4j:WARN Please initialize the log4j system properly.
> To fix this, add the following line:
> set
> AXIS2_CLASS_PATH=%AXIS2_CLASS_PATH%;%AXIS2_HOME%\modules\core\conf
> into the WSDL2Java.bat file, after these lines:
> rem loop through the libs and add them to the class path
> set AXIS2_CLASS_PATH=%AXIS2_HOME%
> FOR %%c in ("%AXIS2_HOME%\lib\*.jar") DO set
> AXIS2_CLASS_PATH=!AXIS2_CLASS_PATH!;%%c
> %AXIS2_HOME%\modules\core\conf is the location of the Axis2-distributed
> log4j.properties file.
> 14. Annoyance: The log4j.properties file shipped with Axis2 circumvents
> the ability for the developers to change the logging level of their
> classes.
> I have included a modified log4j.properties file that actually allows me
> to put my classes into DEBUG level while leaving Axis2 and Tomcat logging
> at their levels.
> 15. Annoyance: Axis2 only allows for Log4J.properties to configure
> logging, not Log4J.xml
> Log4J can be configured using either a properties or an xml file. There
> is a growing number of Logging capabilities that are only configurable
> using the XML file. The code that sets up configuration of Log4J in Axis2
> should allow for both types of configuration files.
> 16. Annoyance: Axis2 does not use ConfigureAndWatch capabilities of
> Log4J
> Log4J can be configured using a ConfigureAndWatch method that causes Log4J
> to monitor its configuration file and automatically apply changes made to
> that file to its configuration. This means that if support personnel need
> to modify the logging configuration of a production application, only the
> log4j configuration file needs to be modified and the Application server
> does not need to be restarted.
> Following is a snippet of code for a Log4jUtils class that addresses
> Annoyances 15 and 16.
> The configureAndWatch method of this utility class should be called by an
> initialization servelet or some other configuration and initialization
> class.
> --
> import org.apache.log4j.BasicConfigurator;
> import org.apache.log4j.PropertyConfigurator;
> import org.apache.log4j.helpers.FileWatchdog;
> import org.apache.log4j.net.SyslogAppender;
> import org.apache.log4j.xml.DOMConfigurator;
> .
> .
> .
> /**
> * A collection of static utility methods for logging with Log4J.
> */
> public final class Log4jUtils {
> private static final Logger LOG =
> Logger.getInstance(Log4jUtils.class);
> private static loggingConfigured = false;
> private Log4jUtils() {
> // All methods are static, this class should not be instantiated
> }
> .
> .
> .
> /**
> * Implements configureAndWatch for the current ClassLoader hierarchy
> using the Log4J
> * default number of seconds.
> */
> public static void configureAndWatch() {
> configureAndWatch(FileWatchdog.DEFAULT_DELAY);
> }
>
> /**
> * Implements configureAndWatch for the current ClassLoader hierarchy.
> *
> * @param watchMillisecs The number of milliseconds to wait between
> checking to see if the
> * log4j configuration file has changed.
> */
> public static void configureAndWatch(long watchMillisecs) {
> if (loggingConfigured) return;
> Class myClass = Log4jUtils.class;
> ClassLoader classLoader = myClass.getClassLoader();
> // Initialize LOG4J
> URL resourceUrl = classLoader.getResource("log4j.xml");
> if (resourceUrl != null) {
> String configFile = resourceUrl.getFile();
> DOMConfigurator.configureAndWatch(configFile, watchMillisecs);
> } else {
> resourceUrl = classLoader.getResource("log4j.properties");
> if (resourceUrl != null) {
> String configFile = resourceUrl.getFile();
> PropertyConfigurator.configureAndWatch(configFile,
> watchMillisecs);
> } else {
> // Since we aren't going to be able to pull our "real"
> settings,
> // let's at least make sure we get so
[jira] Commented: (AXIS2-533) Axiom is heavy-weight and slow
[ http://issues.apache.org/jira/browse/AXIS2-533?page=comments#action_12416358 ] Davanum Srinivas commented on AXIS2-533: And my reply :) The suite was developed by Dennis, the code is here: http://svn.apache.org/repos/asf/webservices/axis2/archive/java/scratch/dennis/ Details on the tests are here: http://issues.apache.org/jira/browse/AXIS2-533 No, i just ran the tests that he provided. He did not have a driver for XOM. > Axiom is heavy-weight and slow > -- > > Key: AXIS2-533 > URL: http://issues.apache.org/jira/browse/AXIS2-533 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: om > Versions: 0.95 > Environment: n/a > Reporter: Dennis Sosnoski > Attachments: ombench.zip, perf.xls, sizes1.ods, sizes1.xls, sizes2.ods, > sizes2.xls, times1.ods, times1.xls, times2.ods, times2.xls, try.sh > > In performance tests comparing Axiom with JDOM, dom4j, and Xerces DOM > document models Axiom was consistently both slower and bulkier than the other > OMs when the tree was expanded. Axiom delivered good performance for the > initial "parse" operation only by virtue of not building the tree. Here are > some time comparison figures for Axiom vs. dom4j on a fairly large SOAP > response (from the MS interop suite): > Running Axiom with 10 passes on file docs/xmlformatter.xml (274920 bytes): > Build mn=563Build av=5110 Walk mn=33360 Walk av=60885 Build-Walk > mn=33923 > Build-Walk av=65995 Write mn=31774 Write av=52782 Mod mn=5 Mod av=6 > Running dom4j with 10 passes on file docs/xmlformatter.xml (274920 bytes): > Build mn=24816 Build av=28843 Walk mn=2839Walk av=3055Build-Walk > mn=27655 > Build-Walk av=31898 Write mn=18866 Write av=19369 Mod mn=5 Mod av=6 > The most interesting figures here are the Build-Walk time (sum of > microseconds for the initial parse operation plus walking the document tree, > which forces Axiom expansion) and the Write time. The average times are > especially bad by comparison with dom4j, which I'd suspect is caused by a lot > of temporary object creation. The write times may be at least partially > caused by the XMLStreamWriter API, since only Axiom uses this approach for > output. Here are memory comparisons: > Running Axiom memory test with 4 passes on file docs/xmlformatter.xml (274920 > bytes): > Init mem=451872 Chg mem=928 First sz=15192 Avg sz=15261Walked > sz=2071960 > Avg+Walked sz=2087221 > Running dom4j memory test with 4 passes on file docs/xmlformatter.xml (274920 > bytes): > Init mem=829968 Chg mem=3120First sz=1031760 Avg sz=971976 Walked sz=0 > Avg+Walked sz=971976 > The interesting figures here are the Avg+Walked sz values, which give the > total bytes of memory in use after parsing and walking the document > representation. > Here are the same time and memory test results for a collection of smaller > SOAP documents: > Running Axiom with 10 passes on directory docs/soaps (30 files totaling 19407 > bytes): > Build mn=13610 Build av=16897 Walk mn=2332Walk av=10523 Build-Walk > mn=15942 > Build-Walk av=27420 Write mn=16079 Write av=22565 Mod mn=9 Mod av=9 > Running dom4j with 10 passes on directory docs/soaps (30 files totaling 19407 > bytes): > Build mn=7507 Build av=12354 Walk mn=121 Walk av=134 Build-Walk > mn=7628 > Build-Walk av=12488 Write mn=4226 Write av=5012 Mod mn=10 Mod av=10 > Running Axiom memory test with 4 passes on directory docs/soaps (30 files > totaling 19407 bytes): > Init mem=456104 Chg mem=1640First sz=451960 Avg sz=449760 Walked > sz=103520 > Avg+Walked sz=553280 > Running dom4j memory test with 4 passes on directory docs/soaps (30 files > totaling 19407 bytes): > Init mem=836392 Chg mem=7944First sz=103824 Avg sz=33768Walked sz=0 > Avg+Walked sz=33768 > Note the huge memory usage in this case. It appears that Axiom has a high > per-document memory overhead, perhaps caused by holding on to the > XMLStreamReader (which suggests the references to the reader should be > cleared as the tree is constructed, so that once the tree is complete the > reader can be garbage collected). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-673) aar file is locked in Tomcat
[ http://issues.apache.org/jira/browse/AXIS2-673?page=all ] Davanum Srinivas resolved AXIS2-673: Resolution: Fixed Fix in SVN revision 414736 -- dims > aar file is locked in Tomcat > > > Key: AXIS2-673 > URL: http://issues.apache.org/jira/browse/AXIS2-673 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: deployment > Versions: 1.0 > Environment: Axis2 1.0 RC4. Tomcat 5.5.7. Win XP. > Reporter: Kent Tong > Assignee: Deepal Jayasinghe > > 1) Start Tomcat. > 2) Put an aar file such as test.aar into webapps/Axis2/WEB-INF/services to > hot-deploy it. > 3) Try to delete the aar file. It says something to the effect of "file is > being used by another process and can't be deleted". > It means one can never hot-undeploy a service by deleting the aar file. This > issue should have nothing to do with antiJARLocking as Axis2 is using a > ZipInputStream to access the aar file. In fact, I've even tried setting > antiJARLocking to true but the problem persists. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-833) org.apache.axis2.util.StreamWraper.getTextLength() returns wrong value
[ http://issues.apache.org/jira/browse/AXIS2-833?page=all ]
Davanum Srinivas resolved AXIS2-833:
Resolution: Fixed
Applied.
thanks,
dims
> org.apache.axis2.util.StreamWraper.getTextLength() returns wrong value
> --
>
> Key: AXIS2-833
> URL: http://issues.apache.org/jira/browse/AXIS2-833
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: core
> Reporter: Raymond Feng
> Priority: Critical
> Attachments: rfeng.txt
>
> org.apache.axis2.util.StreamWraper .getTextLength()
> public int getTextLength() {
> if (prevState != STATE_INIT) {
> return realReader.getTextStart(); // Obviously it's a typo,
> should call realReader.getTextLength(0
> } else {
> return 0;
> }
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-837) Java2WSDL should generate a WSDL interface that accepts an empty SOAP Body
Java2WSDL should generate a WSDL interface that accepts an empty SOAP Body
--
Key: AXIS2-837
URL: http://issues.apache.org/jira/browse/AXIS2-837
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
Java code:
public class TestAxis {
public String getDate(){
return new java.util.Date().toString();
}
}
Quote from Anne at
http://marc.theaimsgroup.com/?l=axis-user&m=115089935000189&w=2:
Java2WSDL should generate a WSDL interface that accepts an empty SOAP Body.
e.g.,
But based on a bunch of recent messages I've seen, Axis2 barfs on an empty SOAP
Body. This is a bug that needs to be fixed. I don't know if anyone has created
a JIRA for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-838) No previous releases prior to 1.0 available from any of the download sites/mirrors
[ http://issues.apache.org/jira/browse/AXIS2-838?page=all ] Davanum Srinivas resolved AXIS2-838: Resolution: Fixed They have been archived. http://archive.apache.org/dist/ws/axis2/ -- -dims > No previous releases prior to 1.0 available from any of the download > sites/mirrors > -- > > Key: AXIS2-838 > URL: http://issues.apache.org/jira/browse/AXIS2-838 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: samples, build,site & docs > Versions: 0.94, 0.95 > Environment: All > Reporter: Vijay Phadke > > The previous axis2 releases i.e. 0.95/0.94 are unavailable to download from > the apache website and ALL of its mirrors. > e.g. > http://apache.hoxt.com/ws/axis2/0_95/axis2-std-0.95-bin.zip > http://apache.mirrors.pair.com/ws/axis2/0_94/axis2-std-0.94-bin.zip > Since there are issues with the wsdl tool in 1.0, previous releases are > needed to continue project work (please see issue > http://issues.apache.org/jira/browse/AXIS2-823 on this wsdl issue). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding -- Key: AXIS2-843 URL: http://issues.apache.org/jira/browse/AXIS2-843 Project: Apache Axis 2.0 (Axis2) Type: Bug Reporter: Davanum Srinivas Service Generated using: w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o samples -p org.apache.axis2.userguide Client Generated using: w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d xmlbeans -o samples -p org.apache.axis2.userguide Stack traces: > echoStringArray > > > java.lang.RuntimeException: Data binding error > > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > Caused by: > org.apache.xmlbeans.XmlException: error: The document is not a [EMAIL > PROTECTED]://userguide.axis2.apache.org/xsd: document element local name > mismatch expected echoStringArrayReturn got stringat > org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) > > at > org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) > > at > org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) > >at > org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) > >... 3 more > > > > echoStruct > > > java.lang.RuntimeException: Data binding > error > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > >
[jira] Updated: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
[ http://issues.apache.org/jira/browse/AXIS2-843?page=all ] Davanum Srinivas updated AXIS2-843: --- Description: Service Generated using: w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o samples -p org.apache.axis2.userguide Client Generated using: w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d xmlbeans -o samples -p org.apache.axis2.userguide Stack traces: > echoStringArray > > > java.lang.RuntimeException: Data binding error > > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > Caused by: > org.apache.xmlbeans.XmlException: error: The document is not a [EMAIL > PROTECTED]://userguide.axis2.apache.org/xsd: document element local name > mismatch expected echoStringArrayReturn got stringat > org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) > > at > org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) > > at > org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) > >at > org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) > >... 3 more > > > > echoStruct > > > java.lang.RuntimeException: Data binding error > > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStruct(Axis2SampleDocLitServiceStub.java:331) >
[jira] Updated: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
[ http://issues.apache.org/jira/browse/AXIS2-843?page=all ] Davanum Srinivas updated AXIS2-843: --- Description: Service Generated using: w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o samples -p org.apache.axis2.userguide Client Generated using: w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d xmlbeans -o samples -p org.apache.axis2.userguide Stack traces: > echoStringArray > > > java.lang.RuntimeException: Data binding error > > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > Caused by: org.apache.xmlbeans.XmlException: error: The document is not a [EMAIL PROTECTED]://userguide.axis2.apache.org/xsd: document element local name mismatch expected echoStringArrayReturn got stringat org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) at org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) at org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) ... 3 more > echoStruct > > > java.lang.RuntimeException: Data binding error > > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStruct(Axis2SampleDocLitServiceStub.java:331) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.t
[jira] Updated: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
[ http://issues.apache.org/jira/browse/AXIS2-843?page=all ] Davanum Srinivas updated AXIS2-843: --- Attachment: Axis2SampleDocLitServiceSkeleton.java Skeleton > Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans > databinding > -- > > Key: AXIS2-843 > URL: http://issues.apache.org/jira/browse/AXIS2-843 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > Attachments: Axis2SampleDocLitServiceSkeleton.java > > Service Generated using: > w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd > -d xmlbeans -o samples -p org.apache.axis2.userguide > Client Generated using: > w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d > xmlbeans -o samples -p org.apache.axis2.userguide > Stack traces: > > echoStringArray > > > > > > java.lang.RuntimeException: Data binding error > > > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > > > > Caused by: org.apache.xmlbeans.XmlException: error: The document is not a > [EMAIL PROTECTED]://userguide.axis2.apache.org/xsd: document element local > name mismatch expected echoStringArrayReturn got stringat > org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) > > at > org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) > > at > org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) > >at > org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) > >... 3 more > > > > > echoStruct > > > java.lang.RuntimeException: Data binding error > > at > org.apache.
[jira] Updated: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
[ http://issues.apache.org/jira/browse/AXIS2-843?page=all ] Davanum Srinivas updated AXIS2-843: --- Attachment: Axis2SampleDocLitServiceTest.java Test Client > Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans > databinding > -- > > Key: AXIS2-843 > URL: http://issues.apache.org/jira/browse/AXIS2-843 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > Attachments: Axis2SampleDocLitServiceSkeleton.java, > Axis2SampleDocLitServiceTest.java > > Service Generated using: > w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd > -d xmlbeans -o samples -p org.apache.axis2.userguide > Client Generated using: > w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d > xmlbeans -o samples -p org.apache.axis2.userguide > Stack traces: > > echoStringArray > > > > > > java.lang.RuntimeException: Data binding error > > > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > > > > Caused by: org.apache.xmlbeans.XmlException: error: The document is not a > [EMAIL PROTECTED]://userguide.axis2.apache.org/xsd: document element local > name mismatch expected echoStringArrayReturn got stringat > org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) > > at > org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) > > at > org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) > >at > org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) > >... 3 more > > > > > echoStruct > > > java.lang.RuntimeException: Data binding error > >
[jira] Assigned: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
[ http://issues.apache.org/jira/browse/AXIS2-843?page=all ] Davanum Srinivas reassigned AXIS2-843: -- Assign To: Ajith Harshana Ranabahu > Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans > databinding > -- > > Key: AXIS2-843 > URL: http://issues.apache.org/jira/browse/AXIS2-843 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > Assignee: Ajith Harshana Ranabahu > Attachments: Axis2SampleDocLitServiceSkeleton.java, > Axis2SampleDocLitServiceTest.java > > Service Generated using: > w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd > -d xmlbeans -o samples -p org.apache.axis2.userguide > Client Generated using: > w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d > xmlbeans -o samples -p org.apache.axis2.userguide > Stack traces: > > echoStringArray > > > > > > java.lang.RuntimeException: Data binding error > > > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > > > > Caused by: org.apache.xmlbeans.XmlException: error: The document is not a > [EMAIL PROTECTED]://userguide.axis2.apache.org/xsd: document element local > name mismatch expected echoStringArrayReturn got stringat > org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) > > at > org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) > > at > org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) > >at > org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) > >... 3 more > > > > > echoStruct > > > java.lang.RuntimeException: Data binding error > >
[jira] Updated: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
[ http://issues.apache.org/jira/browse/AXIS2-843?page=all ] Davanum Srinivas updated AXIS2-843: --- Description: Service Generated using: w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd -d xmlbeans -o samples -p org.apache.axis2.userguide Client Generated using: w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d xmlbeans -o samples -p org.apache.axis2.userguide Stack traces: > echoStringArray > > > java.lang.RuntimeException: Data binding error > > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > Caused by: org.apache.xmlbeans.XmlException: error: The document is not a [EMAIL PROTECTED]://userguide.axis2.apache.org/xsd: document element local name mismatch expected echoStringArrayReturn got string at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) at org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) at org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) at org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) ... 3 more > echoStruct > > > java.lang.RuntimeException: Data binding error > > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStruct(Axis2SampleDocLitServiceStub.java:331) > > at > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.t
[jira] Resolved: (AXIS2-843) Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans databinding
[ http://issues.apache.org/jira/browse/AXIS2-843?page=all ] Davanum Srinivas resolved AXIS2-843: Resolution: Fixed Fixed WSDL in rev 416860. tiny typo...this is a doc/lit wsdl and the /binding/operation/soap:operation/@style said that it was "rpc" instead of "document" thanks, dims > Axis2SampleDocLit.wsdl fails with "Data binding error" when using xmlbeans > databinding > -- > > Key: AXIS2-843 > URL: http://issues.apache.org/jira/browse/AXIS2-843 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > Assignee: Ajith Harshana Ranabahu > Attachments: Axis2SampleDocLitServiceSkeleton.java, > Axis2SampleDocLitServiceTest.java > > Service Generated using: > w2j -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -ss -sd > -d xmlbeans -o samples -p org.apache.axis2.userguide > Client Generated using: > w2j -t -uri c:\APACHE\axis2\modules\samples\wsdl\Axis2SampleDocLit.wsdl -u -d > xmlbeans -o samples -p org.apache.axis2.userguide > Stack traces: > > echoStringArray > > > > > > java.lang.RuntimeException: Data binding error > > > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:844) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.echoStringArray(Axis2SampleDocLitServiceStub.java:167) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.testechoStringArray(Axis2SampleDocLitServiceTest.java:40) > > > > at > > org.apache.axis2.userguide.Axis2SampleDocLitServiceTest.main(Axis2SampleDocLitServiceTest.java:100) > > > > > Caused by: org.apache.xmlbeans.XmlException: error: The document is not a > [EMAIL PROTECTED]://userguide.axis2.apache.org/xsd: document element local > name mismatch expected echoStringArrayReturn got string > at org.apache.xmlbeans.impl.store.Locale.verifyDocumentType(Locale.java:452) > > at > org.apache.xmlbeans.impl.store.Locale.autoTypeDocument(Locale.java:357) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:850) > > at > org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:826) > > at > org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:231) > >at > org.apache.axis2.userguide.xsd.EchoStringArrayReturnDocument$Factory.parse(EchoStringArrayReturnDocument.java:86) > >at > org.apache.axis2.userguide.Axis2SampleDocLitServiceStub.fromOM(Axis2SampleDocLitServiceStub.java:812) > >... 3 more > > > > > echoStruct > > > java.lang.RuntimeException: Data bind
[jira] Commented: (AXIS2-751) Easier customization of message receivers needed
[ http://issues.apache.org/jira/browse/AXIS2-751?page=comments#action_12417707 ] Davanum Srinivas commented on AXIS2-751: Robert, Please check it in. +1 from me. -- dims > Easier customization of message receivers needed > > > Key: AXIS2-751 > URL: http://issues.apache.org/jira/browse/AXIS2-751 > Project: Apache Axis 2.0 (Axis2) > Type: Wish > Components: core > Versions: 1.0 > Reporter: robert lazarski > Attachments: patch.txt > > To override method AbstractMessageReceiver.makeNewServiceObject() , one would > need to create a new Class - SpringAbstractMessageReceiver for example - and > all classes that implement the MEP types need to do an extends of that class. > The current implementation makes it hard to override makeNewServiceObject() > in a way that doesn't require a message receiver in services.xml that has, > for example, SpringRawXMLINOutMessageReceiver: > AbstractMessageReceiver > ^ > | > | > SpringAbstractMessageReceiver -- override > makeNewServiceObject() > ^ > | > | > SpringAbstractInOutSyncMessageReceiver > ^ > | > | > SpringRawXMLINOutMessageReceiver > > There should be a less intrusive way to override makeNewServiceObject() and > get the class loaded in an alternative way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-852) Stub has checks for "rpc" and "document"
Stub has checks for "rpc" and "document"
Key: AXIS2-852
URL: http://issues.apache.org/jira/browse/AXIS2-852
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
Here's the snippet from Stub.java:
protected OMElement getElement(SOAPEnvelope env, String type) {
SOAPBody body = env.getBody();
OMElement element = body.getFirstElement();
if (WSDLConstants.STYLE_RPC.equals(type)) {
return element.getFirstElement();// todo this needs to be fixed
} else if (WSDLConstants.STYLE_DOC.equals(type)) {
return element;
} else {
throw new UnsupportedOperationException(Messages
.getMessage("unsupportedType"));
}
}
Do we need this? The previous bug AXIS2-843 was caused by this piece of code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-854) documentation elements in custom wsdl are lost during "?wsdl"
documentation elements in custom wsdl are lost during "?wsdl" - Key: AXIS2-854 URL: http://issues.apache.org/jira/browse/AXIS2-854 Project: Apache Axis 2.0 (Axis2) Type: Bug Reporter: Davanum Srinivas documentation elements in a custom wsdl are lost when someone tries to look at the wsdl using "?wsdl" -- dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-855) javax.xml.ws.handler.MessageContext constant fields need update
[ http://issues.apache.org/jira/browse/AXIS2-855?page=all ] Davanum Srinivas resolved AXIS2-855: Resolution: Fixed Fixed. thanks, dims > javax.xml.ws.handler.MessageContext constant fields need update > --- > > Key: AXIS2-855 > URL: http://issues.apache.org/jira/browse/AXIS2-855 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: jaxws > Environment: Windows XP SP2 > Reporter: Brent Ulbricht > Attachments: patch.txt > > The javax.xml.ws.handler.MessageContext class is missing the following fields: > - INBOUND_MESSAGE_ATTACHMENTS > - OUTBOUND_MESSAGE_ATTACHMENTS > - PATH_INFO > - QUERY_STRING > It looks like MESSAGE_ATTACHMENTS can be removed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-859) Improve checks for required WS-Addressing headers in inbound handlers
[ http://issues.apache.org/jira/browse/AXIS2-859?page=comments#action_12418946 ] Davanum Srinivas commented on AXIS2-859: looks good to me as all are tests. > Improve checks for required WS-Addressing headers in inbound handlers > - > > Key: AXIS2-859 > URL: http://issues.apache.org/jira/browse/AXIS2-859 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: core > Reporter: Brian DePradine > Attachments: myPatch.txt > > Perform more rigorous checks on WS-Addressing headers to validate that all > required headers have been included on inbound messages. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-859) Improve checks for required WS-Addressing headers in inbound handlers
[ http://issues.apache.org/jira/browse/AXIS2-859?page=comments#action_12418948 ] Davanum Srinivas commented on AXIS2-859: for spec compliance. > Improve checks for required WS-Addressing headers in inbound handlers > - > > Key: AXIS2-859 > URL: http://issues.apache.org/jira/browse/AXIS2-859 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: core > Reporter: Brian DePradine > Attachments: myPatch.txt > > Perform more rigorous checks on WS-Addressing headers to validate that all > required headers have been included on inbound messages. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-857) Administrator create server error
[ http://issues.apache.org/jira/browse/AXIS2-857?page=all ] Davanum Srinivas resolved AXIS2-857: Resolution: Fixed looks like it's working in latest nightly/svn. thanks, dims > Administrator create server error > - > > Key: AXIS2-857 > URL: http://issues.apache.org/jira/browse/AXIS2-857 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: deployment > Versions: 1.0 > Environment: JRE 1.5.0_6-b05, Tomcat 5.0.27 XP > Reporter: Tom Debevoise > > When I run the Axis2 Administrator I get an Internal Server Error > The Tomcat log says: > - Error dispatching request /axis2/axis2-admin/login > 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.transport.http.AbstractAgent.handle(AbstractAgent.java:77) > at org.apache.axis2.transport.http.AdminAgent.handle(AdminAgent.java:93) > at > org.apache.axis2.transport.http.AxisAdminServlet.doGet(AxisAdminServlet.java:41) > at > org.apache.axis2.transport.http.AxisAdminServlet.doPost(AxisAdminServlet.java:35) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) > at > org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) > at java.lang.Thread.run(Thread.java:595) > Caused by: java.lang.NullPointerException > at > org.apache.axis2.transport.http.AdminAgent.processLogin(AdminAgent.java:167) > ... 34 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-886) New JMS sender should take account of WS-Addressing destination even on the server
[ http://issues.apache.org/jira/browse/AXIS2-886?page=all ] Davanum Srinivas resolved AXIS2-886: Resolution: Fixed Applied. thanks, dims > New JMS sender should take account of WS-Addressing destination even on the > server > -- > > Key: AXIS2-886 > URL: http://issues.apache.org/jira/browse/AXIS2-886 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: transports > Reporter: Brian DePradine > Attachments: patch.txt > > The new JMS implementation of JMSSender does not take account of the > WS-Addressing destination on the server. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-887) Old JMS sender needs to take account of WS-Addressing none URI.
[ http://issues.apache.org/jira/browse/AXIS2-887?page=all ] Davanum Srinivas resolved AXIS2-887: Resolution: Fixed applied. -- dims > Old JMS sender needs to take account of WS-Addressing none URI. > --- > > Key: AXIS2-887 > URL: http://issues.apache.org/jira/browse/AXIS2-887 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: transports > Reporter: Brian DePradine > Attachments: patch.txt > > Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS-1771) Excessive Memory Use During Serialization/Deserialization
[ http://issues.apache.org/jira/browse/AXIS-1771?page=comments#action_12420932 ] Davanum Srinivas commented on AXIS-1771: Peter, did you forget this messsage? (http://marc.theaimsgroup.com/?l=axis-dev&m=09719701313&w=2) Tony, I'd recommend opening a new issue with *YOUR* test case / problem info. thanks, dims > Excessive Memory Use During Serialization/Deserialization > - > > Key: AXIS-1771 > URL: http://issues.apache.org/jira/browse/AXIS-1771 > Project: Apache Axis > Type: Bug > Components: Basic Architecture > Versions: 1.2RC2 > Environment: JDK 1.4.2, Mac OS X, Linux, Windows > Reporter: Peter Molettiere > Assignee: Venkat Reddy > Priority: Blocker > Attachments: MTC_venkat.java, MemoryTesterClient.java, > MemoryTesterClient.java, SOAPmsg_multiref_false.xml, > SOAPmsg_multiref_true.xml, SerializationContext.java.diff, > axis-memory-use.gif, memory-use-test.tgz, memory-use-test.tgz, recursion.png > > Axis uses pathological amounts of memory during the > serialization/deserialization process. > We see about a 30 to 1 ratio of memory used during (de)serialization to > in-memory representation of the objects being (de)serialized. So ser/deser in > axis of a 2M graph of objects uses 288M of memory! Further, the memory used > seems to scale linearly with the size of the object graph being serialized. > The memory used does seem to be released once serialization is done, so this > isn't a leak. > Using the attached example code, (based on the code used to demonstrate > AXIS-1423) you can see this behavior. The test automatically runs with a max > heap size of 1024M, and runs out of memory serializing a 28M object graph. > As provided, it generates the following output: > Buildfile: build.xml > build: > [javac] Compiling 1 source file to /Users/pietro/Work/Axis Memory > Test/build/classes > run: > [java] - Unable to find required classes (javax.activation.DataHandler > and javax.mail.internet.MimeMultipart). Attachment support is disabled. > [java] Created tree with 5 levels and 3 children at each level > [java] Axis used 13 MBytes to serialize 230 KBytes, a ratio of 30.0 > [java] GC freed 13 MBytes > [java] Created tree with 5 levels and 4 children at each level > [java] Axis used 71 MBytes to serialize 1 MBytes, a ratio of 31.0 > [java] GC freed 71 MBytes > [java] Created tree with 5 levels and 5 children at each level > [java] Axis used 288 MBytes to serialize 2 MBytes, a ratio of 51.0 > [java] GC freed 287 MBytes > [java] Created tree with 5 levels and 6 children at each level > [java] Axis used 671 MBytes to serialize 11 MBytes, a ratio of 29.0 > [java] GC freed 675 MBytes > [java] Created tree with 5 levels and 7 children at each level > [java] Out of Memory serializing 28 MBytes tree. > [java] Java Result: 1 > BUILD SUCCESSFUL > Total time: 2 minutes 51 seconds > Note that the ratios are halved from the reported values, since it includes > both serialization and deserialization of the object graph. So axis uses > 30.5M to serialize a 1M message, and another 30.5M to deserialize it, > resulting in the reported 71M reported above. Also, notice that the ratio > stays close to 30 to 1 regardless of object graph size. This is the linear > scaling I mention above. > Note also, that if you tweak the code to generate very small object graphs, > you see extremely high ratios, but I would expect this due to simple one-time > overhead to operate on very small amounts of data. That's why I start with > the graph size that I do. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS-1771) Excessive Memory Use During Serialization/Deserialization
[ http://issues.apache.org/jira/browse/AXIS-1771?page=comments#action_12420939 ] Davanum Srinivas commented on AXIS-1771: Tony, That would be 1.4. *but* there are flags and setting etc. So i'd recommend you try 1.4 and open a new issue against that with your specific test / problem info. thanks, dims > Excessive Memory Use During Serialization/Deserialization > - > > Key: AXIS-1771 > URL: http://issues.apache.org/jira/browse/AXIS-1771 > Project: Apache Axis > Type: Bug > Components: Basic Architecture > Versions: 1.2RC2 > Environment: JDK 1.4.2, Mac OS X, Linux, Windows > Reporter: Peter Molettiere > Assignee: Venkat Reddy > Priority: Blocker > Attachments: MTC_venkat.java, MemoryTesterClient.java, > MemoryTesterClient.java, SOAPmsg_multiref_false.xml, > SOAPmsg_multiref_true.xml, SerializationContext.java.diff, > axis-memory-use.gif, memory-use-test.tgz, memory-use-test.tgz, recursion.png > > Axis uses pathological amounts of memory during the > serialization/deserialization process. > We see about a 30 to 1 ratio of memory used during (de)serialization to > in-memory representation of the objects being (de)serialized. So ser/deser in > axis of a 2M graph of objects uses 288M of memory! Further, the memory used > seems to scale linearly with the size of the object graph being serialized. > The memory used does seem to be released once serialization is done, so this > isn't a leak. > Using the attached example code, (based on the code used to demonstrate > AXIS-1423) you can see this behavior. The test automatically runs with a max > heap size of 1024M, and runs out of memory serializing a 28M object graph. > As provided, it generates the following output: > Buildfile: build.xml > build: > [javac] Compiling 1 source file to /Users/pietro/Work/Axis Memory > Test/build/classes > run: > [java] - Unable to find required classes (javax.activation.DataHandler > and javax.mail.internet.MimeMultipart). Attachment support is disabled. > [java] Created tree with 5 levels and 3 children at each level > [java] Axis used 13 MBytes to serialize 230 KBytes, a ratio of 30.0 > [java] GC freed 13 MBytes > [java] Created tree with 5 levels and 4 children at each level > [java] Axis used 71 MBytes to serialize 1 MBytes, a ratio of 31.0 > [java] GC freed 71 MBytes > [java] Created tree with 5 levels and 5 children at each level > [java] Axis used 288 MBytes to serialize 2 MBytes, a ratio of 51.0 > [java] GC freed 287 MBytes > [java] Created tree with 5 levels and 6 children at each level > [java] Axis used 671 MBytes to serialize 11 MBytes, a ratio of 29.0 > [java] GC freed 675 MBytes > [java] Created tree with 5 levels and 7 children at each level > [java] Out of Memory serializing 28 MBytes tree. > [java] Java Result: 1 > BUILD SUCCESSFUL > Total time: 2 minutes 51 seconds > Note that the ratios are halved from the reported values, since it includes > both serialization and deserialization of the object graph. So axis uses > 30.5M to serialize a 1M message, and another 30.5M to deserialize it, > resulting in the reported 71M reported above. Also, notice that the ratio > stays close to 30 to 1 regardless of object graph size. This is the linear > scaling I mention above. > Note also, that if you tweak the code to generate very small object graphs, > you see extremely high ratios, but I would expect this due to simple one-time > overhead to operate on very small amounts of data. That's why I start with > the graph size that I do. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-895) By default, the server should not set the WS-Addressing From header
[ http://issues.apache.org/jira/browse/AXIS2-895?page=all ] Davanum Srinivas resolved AXIS2-895. Resolution: Fixed Applied. thanks, dims > By default, the server should not set the WS-Addressing From header > --- > > Key: AXIS2-895 > URL: http://issues.apache.org/jira/browse/AXIS2-895 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core >Reporter: Brian DePradine > Attachments: patch.txt > > > Currently, the server always sets a value in MessageContext.setFrom() for the > message context of a response message. When WS-Addressing is engaged this > results in a WS-Addressing From header being generated for the response > message. As a performance improvement, the server should not automatically > set the MessageContext.setFrom(), as this would mean one less header to be > generated and ultimately processed by the receiver. As far as WS-Addressing > is concerned, this header is entirely optional and won't make a difference to > the delivery of the message. Other handlers will still be able to set this > value, if they so choose. Finally, it will make the behaviour consistent with > that of fault response messages which currently do not have the > MessageContext.setFrom() automatically set. > Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-124) Support for JAX-WS 2.0
[ http://issues.apache.org/jira/browse/AXIS2-124?page=all ] Davanum Srinivas resolved AXIS2-124. Resolution: Invalid Now that we have the contrib and active dev on the contrib. closing this catch-all bug report. thanks, dims > Support for JAX-WS 2.0 > -- > > Key: AXIS2-124 > URL: http://issues.apache.org/jira/browse/AXIS2-124 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature >Reporter: Davanum Srinivas > Assigned To: Afkham Azeez > > Eventually we'll need to support JAX-WS 2.0 > (http://www.jcp.org/en/jsr/detail?id=224). We should decide on hooks for > example, how to inject infromation from annotations into the service > description. (even though we may not implement JSR 181 in the 1.0 time frame, > there should be enough room in the implementation to drop in support for JSR > 181 say via the beehive project - IF they decide to do it :) > -- dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-808) Axis2/Woden integration - Reading a WSDL2.0 into Axis2
[ http://issues.apache.org/jira/browse/AXIS2-808?page=all ] Davanum Srinivas resolved AXIS2-808. Resolution: Invalid Looks like we are past the point :) -- dims > Axis2/Woden integration - Reading a WSDL2.0 into Axis2 > -- > > Key: AXIS2-808 > URL: http://issues.apache.org/jira/browse/AXIS2-808 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core >Reporter: Oshani Seneviratne >Priority: Minor > Attachments: WSDLVersionDeterminer.patch > > > This issue will be used to attach patches from the work I do on Axis2/Woden > integration. Specifically this includes reading a WSDL2.0 into Axis2 and > populating the AxisService based on that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-863) Upgrade to commons-logging 1.1
[ http://issues.apache.org/jira/browse/AXIS2-863?page=all ] Davanum Srinivas resolved AXIS2-863. Resolution: Fixed in revision 421995 > Upgrade to commons-logging 1.1 > -- > > Key: AXIS2-863 > URL: http://issues.apache.org/jira/browse/AXIS2-863 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Wish > Environment: Java 5.0 , Linux >Reporter: robert lazarski > Fix For: 1.0 > > > Commons-logging 1.1 solves complicated classloader issues present in 1.0.4 > and it would be nice if Axis2 could upgrade to 1.1 . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-863) Upgrade to commons-logging 1.1
[ http://issues.apache.org/jira/browse/AXIS2-863?page=all ] Davanum Srinivas updated AXIS2-863: --- Fix Version/s: (was: 1.0) > Upgrade to commons-logging 1.1 > -- > > Key: AXIS2-863 > URL: http://issues.apache.org/jira/browse/AXIS2-863 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Wish > Environment: Java 5.0 , Linux >Reporter: robert lazarski > > Commons-logging 1.1 solves complicated classloader issues present in 1.0.4 > and it would be nice if Axis2 could upgrade to 1.1 . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-867) HowTo debug a web service
[ http://issues.apache.org/jira/browse/AXIS2-867?page=all ] Davanum Srinivas resolved AXIS2-867. Resolution: Invalid > HowTo debug a web service > - > > Key: AXIS2-867 > URL: http://issues.apache.org/jira/browse/AXIS2-867 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Wish >Affects Versions: 1.0 >Reporter: Jean-Michel PATER > > Hi, > I'm looking for a way other than using log4j to debug a web service. > Is there an eclipse plugin for this ? > Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-900) Support C# Stub code generation using WSDLs using Axis2/Java codegen tool
[ http://issues.apache.org/jira/browse/AXIS2-900?page=comments#action_12421597 ] Davanum Srinivas commented on AXIS2-900: Nandana, According to this page: http://sourceforge.net/mailarchive/forum.php?thread_id=14580953&forum_id=13102 You can use "[EMAIL PROTECTED]" instead of "javax.xml.namespace.QName" to overcode the reserved keyword problem. Could you please try that and if that works submit a new set of sources/diffs? thanks, dims > Support C# Stub code generation using WSDLs using Axis2/Java codegen tool > - > > Key: AXIS2-900 > URL: http://issues.apache.org/jira/browse/AXIS2-900 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement >Reporter: NandanaMihindukulasooriya > Attachments: csharp_codegen_src.tar.gz > > > These java files and xsl templates will extend the functionality of the > Axis2-Java WSDL2Java code generation tool to generate C# client stubs. ADB > databinding also supported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS-2497) Axis modifies SOAP request making digital signature invalid
[ http://issues.apache.org/jira/browse/AXIS-2497?page=comments#action_12422090 ] Davanum Srinivas commented on AXIS-2497: Please try Axis 1.4 -- dims > Axis modifies SOAP request making digital signature invalid > --- > > Key: AXIS-2497 > URL: http://issues.apache.org/jira/browse/AXIS-2497 > Project: Apache Axis > Issue Type: Bug > Components: Basic Architecture >Affects Versions: 1.3 > Environment: Windows XP Pro, SUSE Linux, Tomcat 5.0.28 >Reporter: Peter Bacik >Priority: Critical > > I'm using Apache XMLSec 1.3.0 to validate signature of incoming SOAP requests > on the server side. XMLSec API is invoked from inside of Axis BasicHandler. > Problem is, that Axis modifies the request (removes new lines), which makes > the digest value and therefore also the signature invalid. > DisablePrettyXML flag is set to true. > I sent the same SOAP request to the server using Axis 1.2 and Axis 1.3. > Signature of the message sent to Axis 1.2 was validated successfully, message > sent to Axis 1.3 had invalid signature. > -- > Message traced on the TCP (I removed the header): > > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>... Id="Body"> > > > 12345678901234561234567890123456 > 01234567890123456789 > > > > Message received by Axis 1.2: > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>... Id="Body"> > > > 12345678901234561234567890123456 > 01234567890123456789 > > > > Message received by Axis 1.3: > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>... Id="Body"> > > 12345678901234561234567890123456 > 01234567890123456789 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-908) Need a flag for "?wsdl" to show the user's custom wsdl as-is
Need a flag for "?wsdl" to show the user's custom wsdl as-is Key: AXIS2-908 URL: http://issues.apache.org/jira/browse/AXIS2-908 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas We do a lot of processing, flattening, enhancing the user wsdl. At some point, the user says i *REALLY* need *FULL* control over the dynamic wsdl, please use the wsdl in my AAR as-is. So we need a flag in axis2.xml to allow the user complete control. thanks, dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-908) Need a flag for "?wsdl" to show the user's custom wsdl as-is
[ http://issues.apache.org/jira/browse/AXIS2-908?page=comments#action_12422178 ] Davanum Srinivas commented on AXIS2-908: as-is implies that :) -- dims > Need a flag for "?wsdl" to show the user's custom wsdl as-is > > > Key: AXIS2-908 > URL: http://issues.apache.org/jira/browse/AXIS2-908 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas > > We do a lot of processing, flattening, enhancing the user wsdl. At some > point, the user says i *REALLY* need *FULL* control over the dynamic wsdl, > please use the wsdl in my AAR as-is. So we need a flag in axis2.xml to allow > the user complete control. > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-906) Adding Complex Content Restriction Support to ADB
[
http://issues.apache.org/jira/browse/AXIS2-906?page=comments#action_12422232 ]
Davanum Srinivas commented on AXIS2-906:
Maryam,
the text got corrupted...could you please click on "Attach file to this issue"
on the left hand side and use that to upload your diff file?
thanks,
dims
> Adding Complex Content Restriction Support to ADB
> -
>
> Key: AXIS2-906
> URL: http://issues.apache.org/jira/browse/AXIS2-906
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
>Reporter: Maryam Moazeni
>Priority: Minor
>
> Regarding the implementation of complex content restriction:
> These are the changes of code in the JavaBeanWriter. Changes in
> SchemaCompiler and BeanWriterMetaInfoHandler are not shown.
> 1) Missing Elements
> 2) Missing Attributes *
> 3) Changes in Type
> 3) Changes in Occurance
> are supporte sofar.
> * Attributes still needs more work.
>
> /* JavaBeanWriter.java */
> private void addPropertyEntries(BeanWriterMetaInfoHolder metainf, Document
> model, Element rootElt, ArrayList propertyNames,
> Map typeMap,
> boolean isInherited) throws
> SchemaCompilationException {
> // go in the loop and add the part elements
> QName[] qName;
> ArrayList missingQNames = new ArrayList();
> ArrayList qNames = new ArrayList();
>
> BeanWriterMetaInfoHolder parentMetaInf = metainf.getParent();
>
> if (metainf.isOrdered()) {
> qName = metainf.getOrderedQNameArray();
> } else {
> qName= metainf.getQNameArray();
> }
>
> for (int i = 0; i < qName.length; i++) {
> qNames.add(qName[i]);
> }
> //adding missing QNames to the end, including elements & attributes.
> if (metainf.isRestriction()) {
> addMissingQNames(metainf, qNames);
> }
> QName name;
> for (int i = 0; i < qNames.size(); i++) {
> name = (QName) qNames.get(i);
>
> Element property = XSLTUtils.addChildElement(model, "property",
> rootElt);
>
> String xmlName = name.getLocalPart();
> XSLTUtils.addAttribute(model, "name", xmlName, property);
> XSLTUtils.addAttribute(model, "nsuri", name.getNamespaceURI(),
> property);
> String javaName = makeUniqueJavaClassName(propertyNames, xmlName);
> XSLTUtils.addAttribute(model, "javaname", javaName, property);
> String javaClassNameForElement =
> metainf.getClassNameForQName(name);
> if (javaClassNameForElement == null) {
> throw new
> SchemaCompilationException(SchemaCompilerMessages.getMessage("schema.typeMissing"));
> }
>
> if (metainf.isRestriction() && typeChanged(name, metainf)) {
> XSLTUtils.addAttribute(model, "typeChanged", "yes", property);
> XSLTUtils.addAttribute(model, "rewrite", "yes", property);
> }
>
> XSLTUtils.addAttribute(model, "type", javaClassNameForElement,
> property);
> if (PrimitiveTypeFinder.isPrimitive(javaClassNameForElement)) {
> XSLTUtils.addAttribute(model, "primitive", "yes", property);
> }
> //add an attribute that says the type is default
> if (isDefault(javaClassNameForElement)) {
> XSLTUtils.addAttribute(model, "default", "yes", property);
> }
> if (typeMap.containsKey(metainf.getSchemaQNameForQName(name))) {
> XSLTUtils.addAttribute(model, "ours", "yes", property);
> }
> if (metainf.getAttributeStatusForQName(name)) {
> XSLTUtils.addAttribute(model, "attribute", "yes", property);
> }
> if (metainf.isNillable(name)) {
> XSLTUtils.addAttribute(model, "nillable", "yes", property);
> }
> String shortTypeName;
> if (metainf.getSchemaQNameForQName(name) != null) {
> //see whether the QName is a basetype
> if
> (baseTypeMap.containsKey(metainf.getSchemaQNameForQName(name))){
> shortTypeName=
> metainf.getSchemaQNameForQName(name).getLocalPart();
> }else{
> shortTypeName =
> getShortTypeName(javaClassNameForElement);
> }
> }else{
> shortTypeName = getShortTypeName(javaClassNameForElement);
> }
> XSLTUtils.addAttribute(model, "sh
[jira] Reopened: (AXIS-2139) SAX recorder is dirty after deserialization
[ http://issues.apache.org/jira/browse/AXIS-2139?page=all ] Davanum Srinivas reopened AXIS-2139: Assignee: (was: Venkat Reddy) > SAX recorder is dirty after deserialization > --- > > Key: AXIS-2139 > URL: http://issues.apache.org/jira/browse/AXIS-2139 > Project: Apache Axis > Issue Type: Bug > Components: Serialization/Deserialization >Affects Versions: current (nightly) >Reporter: Steve Green >Priority: Blocker > Attachments: SOAPEnvelope.patch.txt, test.java, test.java, > Test2139.java > > > During parsing of a message, SAX events are stored in the recorder, and > MessageElement objects are created. The insertion of the new MessageElements > are setting _isDirty, and thus invalidating the recorder for serialization. > In my particular case, this breaks digital signatures becuase the > MessageElement DOM is incomplete (it's missing some whitespace text nodes). > It seems to me that it doesn't make sense to dirty the recorder during > recording itself. This problem seemed to be created at version 1.13 of > NodeImpl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-916) Command line WSDL Validator tool
Command line WSDL Validator tool Key: AXIS2-916 URL: http://issues.apache.org/jira/browse/AXIS2-916 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Looks like the WTP folks have a jar that we can use: http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200606.mbox/[EMAIL PROTECTED] Here's a small writeup: http://wiki.eclipse.org/index.php/Using_the_WSDL_Validator_Outside_of_Eclipse Recently Eclipse folks started distributing their javac compiler equivalent..So if we can get something working, we can try to work with them about this as well. thanks, dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-916) Command line WSDL Validator tool
[ http://issues.apache.org/jira/browse/AXIS2-916?page=comments#action_12422634 ] Davanum Srinivas commented on AXIS2-916: I can spot a command line ui in their attic as well: http://dev.eclipse.org/viewcvs/index.cgi/wst/components/wsdl/plugins/org.eclipse.wst.wsdl.validation/src/wsdlvalidateui/org/eclipse/wst/wsdl/validation/internal/ui/text/Attic/WSDLValidate.java?cvsroot=WebTools_Project -- dims > Command line WSDL Validator tool > > > Key: AXIS2-916 > URL: http://issues.apache.org/jira/browse/AXIS2-916 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas > > Looks like the WTP folks have a jar that we can use: > http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200606.mbox/[EMAIL > PROTECTED] > Here's a small writeup: > http://wiki.eclipse.org/index.php/Using_the_WSDL_Validator_Outside_of_Eclipse > Recently Eclipse folks started distributing their javac compiler > equivalent..So if we can get something working, we can try to work with them > about this as well. > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-814) unwrapping support in codegen
[ http://issues.apache.org/jira/browse/AXIS2-814?page=comments#action_12422700 ] Davanum Srinivas commented on AXIS2-814: Nope. Please check the code, there is ONLY one schema construct that unwrap supports. So i don't think this item is complete :( -- dims > unwrapping support in codegen > - > > Key: AXIS2-814 > URL: http://issues.apache.org/jira/browse/AXIS2-814 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature >Reporter: Davanum Srinivas > > Please see the discussion here: > http://marc.theaimsgroup.com/?t=11500696423&r=1&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-927) ADBXMLStreamReaderTest Failure....Appears to OM Related
[ http://issues.apache.org/jira/browse/AXIS2-927?page=comments#action_12423508 ] Davanum Srinivas commented on AXIS2-927: Rich, Can we please close this now? thanks, dims > ADBXMLStreamReaderTest FailureAppears to OM Related > --- > > Key: AXIS2-927 > URL: http://issues.apache.org/jira/browse/AXIS2-927 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: om >Reporter: Rich Scheuerle > Assigned To: Rich Scheuerle > > I am getting the following error while using OM with the new WSCOMMONS-64 > change applied. > junit.framework.AssertionFailedError: Exception in parsing documents > org.xml.sax.SAXParseException: The prefix "axis2" for element > "axis2:SecondOMElement" is not bound. > at > org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderTest.testWithOMElements(ADBXMLStreamReaderTest.java:351) > After some investigation, I believe that the problem is in the woodstox > XMLStreamWriter not propertly cleaning up the NamespaceContext after a > writerEndElement. This is related to the interpretation of the scope of > setPrefix calls. I am working on a fix in WSCOMMONS-66, but I wanted to > raise this issue for tracking purposes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-933) IntegrationTest in saaj failing
IntegrationTest in saaj failing Key: AXIS2-933 URL: http://issues.apache.org/jira/browse/AXIS2-933 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Priority: Blocker Not sure if this is related to Eran's email: http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200607.mbox/[EMAIL PROTECTED] But the org.apache.axis2.saaj.integration.IntegrationTest is failing as it is sending a bad soap request: http://schemas.xmlsoap.org/soap/envelope/";> http://fakeNamespace.org"/> http://fakeNamespace.org"/> http://fakeNamespace.org";> http://fakeNamespace.org"; xmlns:swa="http://fakeNamespace.org";>Im Header Element of header3 http://fakeNamespace.org"; xmlns=""> This is simple plain text Nested1 Plain TextNested2 Plain Text -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-933) IntegrationTest in saaj failing
[ http://issues.apache.org/jira/browse/AXIS2-933?page=comments#action_12423650 ] Davanum Srinivas commented on AXIS2-933: Full test case output is as follows: Testsuite: org.apache.axis2.saaj.integration.IntegrationTest Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 5.735 sec - Standard Output --- Server started on port .[SimpleHTTPServer] Stop called Server stopped .[SimpleHTTPServer] Stop called - --- - Standard Error - Jul 26, 2006 9:42:58 AM org.apache.axis2.deployment.DeploymentEngine prepareRepository INFO: no services directory found , new one created Jul 26, 2006 9:42:59 AM org.apache.axis2.deployment.DeploymentEngine prepareRepository INFO: no modules directory found , new one created Jul 26, 2006 9:42:59 AM org.apache.axis2.transport.http.server.DefaultConnectionListener run INFO: Listening on port req OM Soap Env=http://schemas.xmlsoap.org/soap/envelope/";>http://test.apach.org/test";>This is header1http://fakeNamespace2.org";>This is some texthttp://fakeNamespace3.org";>This is another text req OM Soap Env=http://schemas.xmlsoap.org/soap/envelope/";>http://fakeNamespace.org"; />http://fakeNamespace.org"; />http://fakeNamespace.org";>http://fakeNamespace.org"; xmlns:swa="http://fakeNamespace.org";>Im Header Element of header3http://fakeNamespace.org"; xmlns="">This is simple plain textNested1 Plain TextNested2 Plain Text req OM Soap Env=http://schemas.xmlsoap.org/soap/envelope/";>http://test.apach.org/test";>This is header1http://fakeNamespace2.org";>This is some texthttp://fakeNamespace3.org"; xmlns="">This is another text Jul 26, 2006 9:43:03 AM org.apache.axis2.transport.http.server.SimpleHttpServer destroy INFO: Shut down connection listener Jul 26, 2006 9:43:03 AM org.apache.axis2.transport.http.server.SimpleHttpServer destroy INFO: Shut down HTTP processors Jul 26, 2006 9:43:03 AM org.apache.axis2.transport.http.server.SimpleHttpServer destroy INFO: HTTP protocol handler shut down Jul 26, 2006 9:43:03 AM org.apache.axis2.transport.http.server.SimpleHttpServer destroy INFO: Shut down connection listener Jul 26, 2006 9:43:03 AM org.apache.axis2.transport.http.server.SimpleHttpServer destroy INFO: Shut down HTTP processors Jul 26, 2006 9:43:03 AM org.apache.axis2.transport.http.server.SimpleHttpServer destroy INFO: HTTP protocol handler shut down - --- Testcase: testSendReceiveNonRefAttachment(org.apache.axis2.saaj.integration.IntegrationTest): Caused an ERROR java.lang.IllegalStateException: Current state not START_ELEMENT org.apache.axiom.om.OMException: java.lang.IllegalStateException: Current state not START_ELEMENT at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206) at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:554) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:564) at org.apache.axiom.om.impl.llom.OMElementImpl.getChildren(OMElementImpl.java:278) at org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getChildWithName(SOAPFaultImpl.java:185) at org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:289) at org.apache.axis2.saaj.SOAPConnectionImpl.handleSOAPMessage(SOAPConnectionImpl.java:149) at org.apache.axis2.saaj.SOAPConnectionImpl.call(SOAPConnectionImpl.java:116) at org.apache.axis2.saaj.integration.IntegrationTest.testSendReceiveNonRefAttachment(IntegrationTest.java:227) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.lang.IllegalStateException: Current state not START_ELEMENT at com.ctc.wstx.sr.BasicStreamReader.getAttributeCount(BasicStreamReader.java:559) at org.apache.axiom.om.impl.builder.StAXBuilder.processAttributes(StAXBuilder.java:141) at org.apache.axiom.om.impl.mtom.MTOMStAXSOAPModelBuilder.createOMElement(MTOMStAXSOAPModelBuilder.java:142) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:132) at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:554) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:564) at org.apache.axiom.om.impl.llom.OMElementImpl.getChildren(OMElementImpl.java:278) at org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getChildWithName(SOAPFaultImpl.java:185) at
[jira] Assigned: (AXIS2-933) IntegrationTest in saaj failing
[ http://issues.apache.org/jira/browse/AXIS2-933?page=all ] Davanum Srinivas reassigned AXIS2-933: -- Assignee: Rich Scheuerle Rich, Could u please take a look? thanks, dims > IntegrationTest in saaj failing > --- > > Key: AXIS2-933 > URL: http://issues.apache.org/jira/browse/AXIS2-933 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas > Assigned To: Rich Scheuerle >Priority: Blocker > > Not sure if this is related to Eran's email: > http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200607.mbox/[EMAIL > PROTECTED] > But the org.apache.axis2.saaj.integration.IntegrationTest is failing as it is > sending a bad soap request: > > http://schemas.xmlsoap.org/soap/envelope/";> > > http://fakeNamespace.org"/> > http://fakeNamespace.org"/> > http://fakeNamespace.org";> > http://fakeNamespace.org"; > xmlns:swa="http://fakeNamespace.org";>Im Header Element of header3 > > > > http://fakeNamespace.org"; xmlns=""> >xmlns=""> >href="cid:submitSampleText@apache.org"/> > >href="cid:submitSampleImage@apache.org"/> > > This is simple > plain text > Nested1 > Plain TextNested2 Plain Text > > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-933) IntegrationTest in saaj failing
[ http://issues.apache.org/jira/browse/AXIS2-933?page=comments#action_12423704 ] Davanum Srinivas commented on AXIS2-933: your call :) thanks. -- dims > IntegrationTest in saaj failing > --- > > Key: AXIS2-933 > URL: http://issues.apache.org/jira/browse/AXIS2-933 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas > Assigned To: Rich Scheuerle >Priority: Blocker > > Not sure if this is related to Eran's email: > http://mail-archives.apache.org/mod_mbox/ws-commons-dev/200607.mbox/[EMAIL > PROTECTED] > But the org.apache.axis2.saaj.integration.IntegrationTest is failing as it is > sending a bad soap request: > > http://schemas.xmlsoap.org/soap/envelope/";> > > http://fakeNamespace.org"/> > http://fakeNamespace.org"/> > http://fakeNamespace.org";> > http://fakeNamespace.org"; > xmlns:swa="http://fakeNamespace.org";>Im Header Element of header3 > > > > http://fakeNamespace.org"; xmlns=""> >xmlns=""> >href="cid:submitSampleText@apache.org"/> > >href="cid:submitSampleImage@apache.org"/> > > This is simple > plain text > Nested1 > Plain TextNested2 Plain Text > > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-789) A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not passed to the service object
[ http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423756 ] Davanum Srinivas commented on AXIS2-789: looks good to me. -- dims > A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not > passed to the service object > > > Key: AXIS2-789 > URL: http://issues.apache.org/jira/browse/AXIS2-789 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: core >Reporter: David Illsley > Assigned To: Deepal Jayasinghe >Priority: Minor > Attachments: patch.txt, patch2.txt, patch3.txt > > > A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not > passed to the service object. It currently passes the message through the > InFaultFlow and then processing stops. This prevents Axis2 from being used to > host a 'FaultTo' service which processes faults generated in other services. > I have copied the invocation code from AxisEngine.receive() to > AxisEngine.receiveFault() and all unit tests continue to pass as well as > allowing the fault to be propagated to the service object. > Patch to follow momentarily -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-789) A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not passed to the service object
[ http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423819 ] Davanum Srinivas commented on AXIS2-789: Eran, +1 from me FWIW, there was push back from Sanjiva (http://marc.theaimsgroup.com/?l=axis-dev&m=114912344830552&w=2) that led to this check (and throwing of exception). Let's see if he wants to chime in. thanks, dims > A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not > passed to the service object > > > Key: AXIS2-789 > URL: http://issues.apache.org/jira/browse/AXIS2-789 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: core >Reporter: David Illsley > Assigned To: Deepal Jayasinghe >Priority: Minor > Attachments: patch.txt, patch2.txt, patch3.txt > > > A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not > passed to the service object. It currently passes the message through the > InFaultFlow and then processing stops. This prevents Axis2 from being used to > host a 'FaultTo' service which processes faults generated in other services. > I have copied the invocation code from AxisEngine.receive() to > AxisEngine.receiveFault() and all unit tests continue to pass as well as > allowing the fault to be propagated to the service object. > Patch to follow momentarily -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-936) Maven build fail for org.apache.axis2.jibx.Test
[ http://issues.apache.org/jira/browse/AXIS2-936?page=comments#action_12423820 ] Davanum Srinivas commented on AXIS2-936: it fails for me 100% of the time when i use JROCKIT 1.5. Basically i need to run it twice, first to compile the Customer/Person classes and then run maven again to run the tests. Otherwise it fails. It somehow picks up a undecorated (jibx uses BCEL to decorate the classes) Customer/Person in some jdk's. -- dims > Maven build fail for org.apache.axis2.jibx.Test > --- > > Key: AXIS2-936 > URL: http://issues.apache.org/jira/browse/AXIS2-936 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: samples, build,site & docs >Affects Versions: 1.0 > Environment: HP-UX B.11.11 U 9000/800; JDK 1.5.0.02 >Reporter: lo ti > > test:test: > [junit] Running org.apache.axis2.jibx.Test > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.178 sec > [junit] [ERROR] TEST org.apache.axis2.jibx.Test FAILED > BUILD FAILED > File.. /sis/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly > Element... maven:reactor > Line.. 217 > Column 9 > Unable to obtain goal [multiproject:install-callback] -- > /sis/.maven/cache/maven-test-plugin-1.6.2/plugin.jelly:181:54: There > were test failures. > Total time: 7 minutes 8 seconds > Finished at: Wed Jul 26 17:16:28 CDT 2006 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-922) WSDL2Java generates incorrect code for multiple faults
[ http://issues.apache.org/jira/browse/AXIS2-922?page=all ]
Davanum Srinivas resolved AXIS2-922.
Resolution: Invalid
marking as invalid as per reporter's comments.
> WSDL2Java generates incorrect code for multiple faults
> --
>
> Key: AXIS2-922
> URL: http://issues.apache.org/jira/browse/AXIS2-922
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Tools
>Reporter: Dave Cowing
> Attachments: Services.wsdl, Services.wsdl, UpdateMemberSkeleton.java
>
>
> When I run WSDL2Java on a wsdl that has 3 faults for a service, the generated
> skeleton is incorrect.
> 1) the service method declaration in the skeleton has the right number of
> faults in the throws portion, but they're all the same:
>throws
> com.example.cis.UpdateMemberSkeleton.InvalidMemberIdFaultException,com.example.cis.UpdateMemberSkeleton.InvalidMemberIdFaultException,com.example.cis.UpdateMemberSkeleton.InvalidMemberIdFaultException{
> 2) Only one fault exception class is generated in the skeleton, when there
> should be three.
> I'm attaching my wsdl, as well as the generated skeleton.
> My wsdl call is:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-938) Plugpoint to allow for migration between context and TLS
[ http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12423995 ] Davanum Srinivas commented on AXIS2-938: Here's my train of thought: - 3 changes to classes under jaxws look ok. - 3 new classes (ThreadContext*.java) look ok. - But, those 3 classes are not used in modules/core so they can be moved to modules/jaxws (addThreadContextMigrator can take in an Object - if push comes to shove) - Now, there is only one change left in modules/core which is the change to AxisConfiguration.java - There are 3 methods in that change, which is to maintain the List of threadContextMigrators. - First of all, that LinkedList can be added as a get/set property with a special key in ConfigurationContext, then you won't need to touch AxisConfiguration.java at all. - Since AxisConfiguration is not meant to hold runtime information (AxisConfiguration is only for loading and deploying stuff) and ConfigurationContext is...So ConfigurationContext is a better location to store that LinkedList. So, if you move the LinkedList to ConfigurationContext, then all the changes will be limited to modules/jaxws which is perfect because the new Interface class is not really usable by anyone else other than jaxws as the hooks are not called/used anywhere in the core anyways. What do you think? thanks, dims > Plugpoint to allow for migration between context and TLS > > > Key: AXIS2-938 > URL: http://issues.apache.org/jira/browse/AXIS2-938 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core, jaxws >Reporter: Bill Nagy > Assigned To: Bill Nagy > Attachments: tlsmigrator.patch > > > We have an issue with some APIs (e.g. security, Tx) requiring that data be > present on Thread Local Storage (TLS). I believe that we can work around (at > least for now) needing to migrate information between threads, and can simply > get away with storing it in one of the contexts and then moving it to TLS > before we get into user space (i.e. up through the service programming model) > and then back again if need be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-891) Allow the WS-Addressing action to be set, in the client, without also setting the SOAP action
[ http://issues.apache.org/jira/browse/AXIS2-891?page=all ] Davanum Srinivas resolved AXIS2-891. Resolution: Fixed Applied a slightly modified version in rev 426539 thanks, dims > Allow the WS-Addressing action to be set, in the client, without also setting > the SOAP action > - > > Key: AXIS2-891 > URL: http://issues.apache.org/jira/browse/AXIS2-891 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core >Reporter: Brian DePradine > Attachments: newerpatch.txt, newpatch.txt, patch.txt > > > Modify the Options class to allow a user to set the WS-Addressing action > without also setting the soap action. This is important as, according to the > WS-Addressing 1.0 SOAP Binding Spec, it will allow the ability to obscure the > action through SOAP-level security mechanisms, without having to resort to > transport level security mechanisms. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-938) Plugpoint to allow for migration between context and TLS
[ http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12424299 ] Davanum Srinivas commented on AXIS2-938: Rich, It would be useful if the hooks were called from core module, right now it isn't. All the calls to the interface methods are in jaxws layer only. Yes, +1 to org.apache.axis2..jaxws.corepm.utils.ThreadContextMigrator though i prefer (org.apache.axis2..jaxws.core.utils.ThreadContextMigrator) without the PM. thanks, dims > Plugpoint to allow for migration between context and TLS > > > Key: AXIS2-938 > URL: http://issues.apache.org/jira/browse/AXIS2-938 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core, jaxws >Reporter: Bill Nagy > Assigned To: Bill Nagy > Attachments: tlsmigrator.patch > > > We have an issue with some APIs (e.g. security, Tx) requiring that data be > present on Thread Local Storage (TLS). I believe that we can work around (at > least for now) needing to migrate information between threads, and can simply > get away with storing it in one of the contexts and then moving it to TLS > before we get into user space (i.e. up through the service programming model) > and then back again if need be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-936) Maven build fail for org.apache.axis2.jibx.Test
[ http://issues.apache.org/jira/browse/AXIS2-936?page=comments#action_12424382 ] Davanum Srinivas commented on AXIS2-936: Sorry Dennis. I was just lazy and switch compilers. Yes, it was happening from the time the test was added. Plz look at all the maven.xml's you can run any ant task from there. -- dims > Maven build fail for org.apache.axis2.jibx.Test > --- > > Key: AXIS2-936 > URL: http://issues.apache.org/jira/browse/AXIS2-936 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: samples, build,site & docs >Affects Versions: 1.0 > Environment: HP-UX B.11.11 U 9000/800; JDK 1.5.0.02 >Reporter: lo ti > > test:test: > [junit] Running org.apache.axis2.jibx.Test > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.178 sec > [junit] [ERROR] TEST org.apache.axis2.jibx.Test FAILED > BUILD FAILED > File.. /sis/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly > Element... maven:reactor > Line.. 217 > Column 9 > Unable to obtain goal [multiproject:install-callback] -- > /sis/.maven/cache/maven-test-plugin-1.6.2/plugin.jelly:181:54: There > were test failures. > Total time: 7 minutes 8 seconds > Finished at: Wed Jul 26 17:16:28 CDT 2006 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-906) Adding Complex Content Restriction Support to ADB
[
http://issues.apache.org/jira/browse/AXIS2-906?page=comments#action_12424394 ]
Davanum Srinivas commented on AXIS2-906:
Maryam,
can u please upload the wsdl that you are testing with also?
thanks,
dims
> Adding Complex Content Restriction Support to ADB
> -
>
> Key: AXIS2-906
> URL: http://issues.apache.org/jira/browse/AXIS2-906
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
>Reporter: Maryam Moazeni
>Priority: Minor
> Attachments: patchfile, patchfile.txt
>
>
> Regarding the implementation of complex content restriction:
> These are the changes of code in the JavaBeanWriter. Changes in
> SchemaCompiler and BeanWriterMetaInfoHandler are not shown.
> 1) Missing Elements
> 2) Missing Attributes *
> 3) Changes in Type
> 3) Changes in Occurance
> are supporte sofar.
> * Attributes still needs more work.
>
> /* JavaBeanWriter.java */
> private void addPropertyEntries(BeanWriterMetaInfoHolder metainf, Document
> model, Element rootElt, ArrayList propertyNames,
> Map typeMap,
> boolean isInherited) throws
> SchemaCompilationException {
> // go in the loop and add the part elements
> QName[] qName;
> ArrayList missingQNames = new ArrayList();
> ArrayList qNames = new ArrayList();
>
> BeanWriterMetaInfoHolder parentMetaInf = metainf.getParent();
>
> if (metainf.isOrdered()) {
> qName = metainf.getOrderedQNameArray();
> } else {
> qName= metainf.getQNameArray();
> }
>
> for (int i = 0; i < qName.length; i++) {
> qNames.add(qName[i]);
> }
> //adding missing QNames to the end, including elements & attributes.
> if (metainf.isRestriction()) {
> addMissingQNames(metainf, qNames);
> }
> QName name;
> for (int i = 0; i < qNames.size(); i++) {
> name = (QName) qNames.get(i);
>
> Element property = XSLTUtils.addChildElement(model, "property",
> rootElt);
>
> String xmlName = name.getLocalPart();
> XSLTUtils.addAttribute(model, "name", xmlName, property);
> XSLTUtils.addAttribute(model, "nsuri", name.getNamespaceURI(),
> property);
> String javaName = makeUniqueJavaClassName(propertyNames, xmlName);
> XSLTUtils.addAttribute(model, "javaname", javaName, property);
> String javaClassNameForElement =
> metainf.getClassNameForQName(name);
> if (javaClassNameForElement == null) {
> throw new
> SchemaCompilationException(SchemaCompilerMessages.getMessage("schema.typeMissing"));
> }
>
> if (metainf.isRestriction() && typeChanged(name, metainf)) {
> XSLTUtils.addAttribute(model, "typeChanged", "yes", property);
> XSLTUtils.addAttribute(model, "rewrite", "yes", property);
> }
>
> XSLTUtils.addAttribute(model, "type", javaClassNameForElement,
> property);
> if (PrimitiveTypeFinder.isPrimitive(javaClassNameForElement)) {
> XSLTUtils.addAttribute(model, "primitive", "yes", property);
> }
> //add an attribute that says the type is default
> if (isDefault(javaClassNameForElement)) {
> XSLTUtils.addAttribute(model, "default", "yes", property);
> }
> if (typeMap.containsKey(metainf.getSchemaQNameForQName(name))) {
> XSLTUtils.addAttribute(model, "ours", "yes", property);
> }
> if (metainf.getAttributeStatusForQName(name)) {
> XSLTUtils.addAttribute(model, "attribute", "yes", property);
> }
> if (metainf.isNillable(name)) {
> XSLTUtils.addAttribute(model, "nillable", "yes", property);
> }
> String shortTypeName;
> if (metainf.getSchemaQNameForQName(name) != null) {
> //see whether the QName is a basetype
> if
> (baseTypeMap.containsKey(metainf.getSchemaQNameForQName(name))){
> shortTypeName=
> metainf.getSchemaQNameForQName(name).getLocalPart();
> }else{
> shortTypeName =
> getShortTypeName(javaClassNameForElement);
> }
> }else{
> shortTypeName = getShortTypeName(javaClassNameForElement);
> }
> XSLTUtils.addAttribute(model, "shorttypename", shortTypeName,
[jira] Reopened: (AXIS2-400) Classloader doesn't work with Spring inside an AAR
[ http://issues.apache.org/jira/browse/AXIS2-400?page=all ] Davanum Srinivas reopened AXIS2-400: Assignee: Davanum Srinivas I know this is marked as won't fix..i am gonna reopen it to see if there's a way to set the TCL and keep service/module isolation. -- dims > Classloader doesn't work with Spring inside an AAR > -- > > Key: AXIS2-400 > URL: http://issues.apache.org/jira/browse/AXIS2-400 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: core >Affects Versions: 0.94 > Environment: Tomcat 5.5, Axis 0.94, Windows XP, Java 5 >Reporter: Inigo Surguy > Assigned To: Davanum Srinivas > Fix For: 0.95 > > Attachments: ClasspathTest.java, MyBean.java, testClasspath.aar > > > The classloader used for AAR doesn't work with Spring - when I put Spring > inside the lib directory of the AAR, it's not able to access its > applicationContext.xml. If I move the applicationContext to the > WEB-INF/classes directory, then Spring is able to find it, but not to load > the classes defined in it from the AAR. > However, I am able to access files in the AAR from within my own code > directly inside the .AAR. > When I initially tried to reproduce this, I thought I wasn't able to access > the contents of the .AAR at all - but I think this was because I was > connecting to Tomcat via a debugger and running the "getResource" code in the > context of the debug session, which seems to have given different results > than when I call getResource from code. > This sounds like the behaviour I'd expect if Spring was in the Axis lib > directory - but it isn't. > -- > Error: > org.springframework.beans.factory.BeanDefinitionStoreException: Error > registering bean with name 'myBean' defined in class path resource > [testApplicationContext.xml]: Bean class [classpathtest.MyBean] not found; > nested exception is java.lang.ClassNotFoundException: classpathtest.MyBean > Full error: > ? > > > ? > > ? > > Client > ? > > IOException parsing XML document from class path resource > [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist; > nested exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: > IOException parsing XML document from class path resource > [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist > > http://myAxisServer/role/default > ? > > ? > > org.apache.axis2.AxisFault: IOException parsing XML document from class path > resource [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist; > nested exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: > IOException parsing XML document from class path resource > [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:254) > at > org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:118) > at > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:331) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPGetRequest(HTTPTransportUtils.java:147) > at > org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:103) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyot
[jira] Reopened: (AXIS2-537) Service classloader problem
[ http://issues.apache.org/jira/browse/AXIS2-537?page=all ]
Davanum Srinivas reopened AXIS2-537:
Assignee: Davanum Srinivas
> Service classloader problem
> ---
>
> Key: AXIS2-537
> URL: http://issues.apache.org/jira/browse/AXIS2-537
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core, deployment
>Affects Versions: 0.95
> Environment: Bea Weblogic 8.1 SP5, All OS, Java 1.4.2_05
>Reporter: Dmitriy Kiriy
> Assigned To: Davanum Srinivas
>
> I have axi2.war\WEB-INF\services\AssetService.aar
> in that file I have:
> org/apache/axis2/
> AssetServiceStub.class
> AssetServiceStub$1.class - AssetServiceStub$30.class
> AssetServiceSkeleton.class
> AssetServiceMessageReceiverInOut.class
> AssetServiceCallbackHandler.class
> com.mypackage/
> AssetServiceImpl (extends AssetServiceSkeleton)
> META-INF/
> services.xml
> AsserService.wsdl
> (
> com.mypackage.AssetServiceImpl
> )
> All classes excluding com.mypackage.AssetServiceImpl was generated by
> WSDL2Java tool.
> We have a class loading problem. So, I little bit change
> AbstractMessageReceiver.java:
> protected Object makeNewServiceObject(MessageContext msgContext) throws
> AxisFault {
> try {
> AxisService service =
>
> msgContext.getOperationContext().getServiceContext().getAxisService();
> ClassLoader classLoader = service.getClassLoader();
> Parameter implInfoParam = service.getParameter(SERVICE_CLASS);
> if (implInfoParam != null) {
> try {
> Class implClass = classLoader.loadClass(((String)
> implInfoParam.getValue()));
> return implClass.newInstance();
> } catch (Throwable e)
> {
> System.err.println("While tring to load class "+(String)
> implInfoParam.getValue()+" got the following problem: "+e);
> e.printStackTrace(System.err);
> throw AxisFault.makeFault(new Exception(e));
> }
> } else {
> throw new
> AxisFault(Messages.getMessage("paramIsNotSpecified", "SERVICE_CLASS"));
> }
> } catch (Exception e) {
> throw AxisFault.makeFault(e);
> }
> }
> So, in lines:
> System.err.println("While tring to load class "+(String)
> implInfoParam.getValue()+" got the following problem: "+e);
> e.printStackTrace(System.err);
> throw AxisFault.makeFault(new Exception(e));
> I got:
> While tring to load class com.mypackage.AssetServiceImpl got the following
> problem: java.lang.NoClassDefFoundError: org/apache/axis2/AssetServiceSkeleton
> java.lang.NoClassDefFoundError: org/apache/axis2/AssetServiceSkeleton
> at
> java.lang.ClassLoader.defineClass(Ljava/lang/String;[BIILjava/security/ProtectionDomain;)Ljava/lang/Class;(Unknown
> Source)
> at
> java.security.SecureClassLoader.defineClass(Ljava/lang/String;[BIILjava/security/CodeSource;)Ljava/lang/Class;(SecureClassLoader.java:123)
> at
> weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Ljava/lang/String;)Ljava/lang/Class;(GenericClassLoader.java:480)
> at
> weblogic.utils.classloaders.GenericClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;(GenericClassLoader.java:182)
> at
> weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;(ChangeAwareClassLoader.java:61)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class;(Unknown
> Source)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(Lorg/apache/axis2/context/MessageContext;)Ljava/lang/Object;(AbstractMessageReceiver.java:52)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(Lorg/apache/axis2/context/MessageContext;)Ljava/lang/Object;(AbstractMessageReceiver.java:95)
> at
> org.apache.axis2.AssetServiceMessageReceiverInOut.invokeBusinessLogic(Lorg/apache/axis2/context/MessageContext;Lorg/apache/axis2/context/MessageContext;)V(AssetServiceMessageReceiverInOut.java:24)
> at
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Lorg/apache/axis2/context/MessageContext;)V(AbstractInOutSyncMessageReceiver.java:37)
> at
> org.apa
[jira] Closed: (AXIS2-400) Classloader doesn't work with Spring inside an AAR
[ http://issues.apache.org/jira/browse/AXIS2-400?page=all ] Davanum Srinivas closed AXIS2-400. -- Fix Version/s: (was: 0.95) Resolution: Fixed Fixed in 427662 > Classloader doesn't work with Spring inside an AAR > -- > > Key: AXIS2-400 > URL: http://issues.apache.org/jira/browse/AXIS2-400 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: core >Affects Versions: 0.94 > Environment: Tomcat 5.5, Axis 0.94, Windows XP, Java 5 >Reporter: Inigo Surguy > Assigned To: Davanum Srinivas > Attachments: ClasspathTest.java, MyBean.java, testClasspath.aar > > > The classloader used for AAR doesn't work with Spring - when I put Spring > inside the lib directory of the AAR, it's not able to access its > applicationContext.xml. If I move the applicationContext to the > WEB-INF/classes directory, then Spring is able to find it, but not to load > the classes defined in it from the AAR. > However, I am able to access files in the AAR from within my own code > directly inside the .AAR. > When I initially tried to reproduce this, I thought I wasn't able to access > the contents of the .AAR at all - but I think this was because I was > connecting to Tomcat via a debugger and running the "getResource" code in the > context of the debug session, which seems to have given different results > than when I call getResource from code. > This sounds like the behaviour I'd expect if Spring was in the Axis lib > directory - but it isn't. > -- > Error: > org.springframework.beans.factory.BeanDefinitionStoreException: Error > registering bean with name 'myBean' defined in class path resource > [testApplicationContext.xml]: Bean class [classpathtest.MyBean] not found; > nested exception is java.lang.ClassNotFoundException: classpathtest.MyBean > Full error: > ? > > > ? > > ? > > Client > ? > > IOException parsing XML document from class path resource > [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist; > nested exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: > IOException parsing XML document from class path resource > [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist > > http://myAxisServer/role/default > ? > > ? > > org.apache.axis2.AxisFault: IOException parsing XML document from class path > resource [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist; > nested exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: > IOException parsing XML document from class path resource > [testApplicationContext.xml]; nested exception is > java.io.FileNotFoundException: class path resource > [testApplicationContext.xml] cannot be opened because it does not exist > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:254) > at > org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:118) > at > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:331) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPGetRequest(HTTPTransportUtils.java:147) > at > org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:103) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc
[jira] Closed: (AXIS2-537) Service classloader problem
[ http://issues.apache.org/jira/browse/AXIS2-537?page=all ]
Davanum Srinivas closed AXIS2-537.
--
Resolution: Fixed
Fixed in SVN revision 427662
> Service classloader problem
> ---
>
> Key: AXIS2-537
> URL: http://issues.apache.org/jira/browse/AXIS2-537
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core, deployment
>Affects Versions: 0.95
> Environment: Bea Weblogic 8.1 SP5, All OS, Java 1.4.2_05
>Reporter: Dmitriy Kiriy
> Assigned To: Davanum Srinivas
>
> I have axi2.war\WEB-INF\services\AssetService.aar
> in that file I have:
> org/apache/axis2/
> AssetServiceStub.class
> AssetServiceStub$1.class - AssetServiceStub$30.class
> AssetServiceSkeleton.class
> AssetServiceMessageReceiverInOut.class
> AssetServiceCallbackHandler.class
> com.mypackage/
> AssetServiceImpl (extends AssetServiceSkeleton)
> META-INF/
> services.xml
> AsserService.wsdl
> (
> com.mypackage.AssetServiceImpl
> )
> All classes excluding com.mypackage.AssetServiceImpl was generated by
> WSDL2Java tool.
> We have a class loading problem. So, I little bit change
> AbstractMessageReceiver.java:
> protected Object makeNewServiceObject(MessageContext msgContext) throws
> AxisFault {
> try {
> AxisService service =
>
> msgContext.getOperationContext().getServiceContext().getAxisService();
> ClassLoader classLoader = service.getClassLoader();
> Parameter implInfoParam = service.getParameter(SERVICE_CLASS);
> if (implInfoParam != null) {
> try {
> Class implClass = classLoader.loadClass(((String)
> implInfoParam.getValue()));
> return implClass.newInstance();
> } catch (Throwable e)
> {
> System.err.println("While tring to load class "+(String)
> implInfoParam.getValue()+" got the following problem: "+e);
> e.printStackTrace(System.err);
> throw AxisFault.makeFault(new Exception(e));
> }
> } else {
> throw new
> AxisFault(Messages.getMessage("paramIsNotSpecified", "SERVICE_CLASS"));
> }
> } catch (Exception e) {
> throw AxisFault.makeFault(e);
> }
> }
> So, in lines:
> System.err.println("While tring to load class "+(String)
> implInfoParam.getValue()+" got the following problem: "+e);
> e.printStackTrace(System.err);
> throw AxisFault.makeFault(new Exception(e));
> I got:
> While tring to load class com.mypackage.AssetServiceImpl got the following
> problem: java.lang.NoClassDefFoundError: org/apache/axis2/AssetServiceSkeleton
> java.lang.NoClassDefFoundError: org/apache/axis2/AssetServiceSkeleton
> at
> java.lang.ClassLoader.defineClass(Ljava/lang/String;[BIILjava/security/ProtectionDomain;)Ljava/lang/Class;(Unknown
> Source)
> at
> java.security.SecureClassLoader.defineClass(Ljava/lang/String;[BIILjava/security/CodeSource;)Ljava/lang/Class;(SecureClassLoader.java:123)
> at
> weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Ljava/lang/String;)Ljava/lang/Class;(GenericClassLoader.java:480)
> at
> weblogic.utils.classloaders.GenericClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;(GenericClassLoader.java:182)
> at
> weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;(ChangeAwareClassLoader.java:61)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class;(Unknown
> Source)
> at
> java.lang.ClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class;(Unknown
> Source)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(Lorg/apache/axis2/context/MessageContext;)Ljava/lang/Object;(AbstractMessageReceiver.java:52)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(Lorg/apache/axis2/context/MessageContext;)Ljava/lang/Object;(AbstractMessageReceiver.java:95)
> at
> org.apache.axis2.AssetServiceMessageReceiverInOut.invokeBusinessLogic(Lorg/apache/axis2/context/MessageContext;Lorg/apache/axis2/context/MessageContext;)V(AssetServiceMessageReceiverInOut.java:24)
> at
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Lorg/apache/axis2/context/MessageContext;)V(AbstractInOutSyncMessageReceiver.java:37)
> at
> org.ap
[jira] Commented: (AXIS2-938) Plugpoint to allow for migration between context and TLS
[ http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12424963 ] Davanum Srinivas commented on AXIS2-938: Looks good Bill. Thanks. -- dims > Plugpoint to allow for migration between context and TLS > > > Key: AXIS2-938 > URL: http://issues.apache.org/jira/browse/AXIS2-938 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core, jaxws >Reporter: Bill Nagy > Assigned To: Bill Nagy > Attachments: tlsmigrator.patch, tlsmigratortake2.patch > > > We have an issue with some APIs (e.g. security, Tx) requiring that data be > present on Thread Local Storage (TLS). I believe that we can work around (at > least for now) needing to migrate information between threads, and can simply > get away with storing it in one of the contexts and then moving it to TLS > before we get into user space (i.e. up through the service programming model) > and then back again if need be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-938) Plugpoint to allow for migration between context and TLS
[ http://issues.apache.org/jira/browse/AXIS2-938?page=all ] Davanum Srinivas resolved AXIS2-938. Resolution: Fixed i can see the changes in svn. closing bug as fixed. -- dims > Plugpoint to allow for migration between context and TLS > > > Key: AXIS2-938 > URL: http://issues.apache.org/jira/browse/AXIS2-938 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core, jaxws >Reporter: Bill Nagy > Assigned To: Bill Nagy > Attachments: tlsmigrator.patch, tlsmigratortake2.patch > > > We have an issue with some APIs (e.g. security, Tx) requiring that data be > present on Thread Local Storage (TLS). I believe that we can work around (at > least for now) needing to migrate information between threads, and can simply > get away with storing it in one of the contexts and then moving it to TLS > before we get into user space (i.e. up through the service programming model) > and then back again if need be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-960) Client-side support for SwA
Client-side support for SwA --- Key: AXIS2-960 URL: http://issues.apache.org/jira/browse/AXIS2-960 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Please see discussion here: http://marc.theaimsgroup.com/?t=11533395151&r=1&w=2 -- dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-940) Ability to load/init services during container startup
[ http://issues.apache.org/jira/browse/AXIS2-940?page=comments#action_12425196 ] Davanum Srinivas commented on AXIS2-940: Deepal, I'd say it should be the following because there is no ServiceContext or MessageContext setup at startup time. init(ConfigurationContext) This is similar to servlets if you specify load-on-startup then "init(ServletConfig config)" is called. This would be a one time call only irrespective of scope. What do you think? -- dims > Ability to load/init services during container startup > -- > > Key: AXIS2-940 > URL: http://issues.apache.org/jira/browse/AXIS2-940 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: deployment >Affects Versions: 1.0 > Environment: n/a >Reporter: Tony Dean > > I think users will want an option (load-on-startup=on|off) to either load > scope="application" services on container startup or upon the first request. > I personally would want my service loaded and ready to go before the first > request is issued. Users will certainly be willing to take the hit waiting > for the container to initialize rather than during a real-time request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-940) Ability to load/init services during container startup
[ http://issues.apache.org/jira/browse/AXIS2-940?page=comments#action_12425197 ] Davanum Srinivas commented on AXIS2-940: Hi Dims; When you deploy a service , deploymentEngine does not have access to configuration context (it has only access to AxisConfiguration). Any way we have a work around for the services at the system startup time , but if some one drop a service at the runtime (service hot deployment) , then we can not call that method since there is no way to get access to configuration context from AxisConfiguratation. So is that ok if we give this feature only for service which are in the repository when system startup ? Thanks Deepal > Ability to load/init services during container startup > -- > > Key: AXIS2-940 > URL: http://issues.apache.org/jira/browse/AXIS2-940 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: deployment >Affects Versions: 1.0 > Environment: n/a >Reporter: Tony Dean > > I think users will want an option (load-on-startup=on|off) to either load > scope="application" services on container startup or upon the first request. > I personally would want my service loaded and ready to go before the first > request is issued. Users will certainly be willing to take the hit waiting > for the container to initialize rather than during a real-time request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-940) Ability to load/init services during container startup
[ http://issues.apache.org/jira/browse/AXIS2-940?page=all ] Davanum Srinivas reassigned AXIS2-940: -- Assignee: Deepal Jayasinghe > Ability to load/init services during container startup > -- > > Key: AXIS2-940 > URL: http://issues.apache.org/jira/browse/AXIS2-940 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: deployment >Affects Versions: 1.0 > Environment: n/a >Reporter: Tony Dean > Assigned To: Deepal Jayasinghe > > I think users will want an option (load-on-startup=on|off) to either load > scope="application" services on container startup or upon the first request. > I personally would want my service loaded and ready to go before the first > request is issued. Users will certainly be willing to take the hit waiting > for the container to initialize rather than during a real-time request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-965) Need a way to build AxisServices for all ports/services in a wsld.
[ http://issues.apache.org/jira/browse/AXIS2-965?page=comments#action_12426100 ] Davanum Srinivas commented on AXIS2-965: Lori, Does this pass all the tests? thanks, dims > Need a way to build AxisServices for all ports/services in a wsld. > -- > > Key: AXIS2-965 > URL: http://issues.apache.org/jira/browse/AXIS2-965 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core >Reporter: Lori VanGulick > Attachments: AXIS2-965patch.txt > > > WSDL 11 allows multiple services per wsdl file, and multiple ports per > service. Currently unless a service and port name are specified, > WSDL11ToAxisServiceBuilder will only return the first port on the first > service. > I would like to provide an extension to WSDL11ToAxisServiceBuilder that would > take a wsdl file and return a List of AxisService objects, one for each port > in the wsdl. > To make this more efficient I will need to make some minor changes to > org.apache.axis2.description.WSDL11ToAxisServiceBuilder.java, i.e. >- restructuring in the populateService method so that all the processing > that is not specific to an AxisService is only done one time. Move this code > to a new method, setup(). Setup code will include reading in the wsdl file, > processing policies, imports, etc. >- make some methods and fields protected instead of private so they can > be accessed by subclasses. > The new extension is proposed to be > org.appache.axis2.description.WSDL11ToAllAxisServicesBuilder. It has a > public method, popluateAllServices() which operates as follows > - calls the setup() method on the parent. > - iterates through all the services and all the ports in the wsdl, setting > serviceName and portName on the parent. > - calls up to populateService() on the parent. This will return an > AxisService specific to the service and port name specified. > - changes the name on the AxisService to the port name instead of the > service name, so it can be uniquely identified. > - returns the List of AxisService objects, one for each port in the wsdl > I will also make corresponding changes for WSDL 2.0 in > org.apache.axis2.description.WSDL20ToAxisServiceBuilder.java and create > WSDL20ToAllAxisServicesBuilder.java. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-946) Adding Simple Content Extension Support to ADB
[ http://issues.apache.org/jira/browse/AXIS2-946?page=comments#action_12426126 ] Davanum Srinivas commented on AXIS2-946: Have you looked at a bit more complicated examples like the one below: http://developer.ebay.com/webservices/latest/eBaySvc.wsdl thanks, dims > Adding Simple Content Extension Support to ADB > -- > > Key: AXIS2-946 > URL: http://issues.apache.org/jira/browse/AXIS2-946 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement >Reporter: Maryam Moazeni >Priority: Minor > Attachments: axis2-418.wsdl, patchfile.txt, SchemaCompiler.java, > Test5.xsd > > > Hi, > I implemented the simple content extension. > Any comments are appreciated ... > Thanks, > Maryam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-946) Adding Simple Content Extension Support to ADB
[ http://issues.apache.org/jira/browse/AXIS2-946?page=all ] Davanum Srinivas updated AXIS2-946: --- Attachment: axis2-418.wsdl Maryam, Here's a WSDL (modified version from AXIS2-418). Are u dealing with defaults for attributes yet? thanks, dims > Adding Simple Content Extension Support to ADB > -- > > Key: AXIS2-946 > URL: http://issues.apache.org/jira/browse/AXIS2-946 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement >Reporter: Maryam Moazeni >Priority: Minor > Attachments: axis2-418.wsdl, patchfile.txt, SchemaCompiler.java, > Test5.xsd > > > Hi, > I implemented the simple content extension. > Any comments are appreciated ... > Thanks, > Maryam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-946) Adding Simple Content Extension Support to ADB
[ http://issues.apache.org/jira/browse/AXIS2-946?page=comments#action_12426124 ] Davanum Srinivas commented on AXIS2-946: Another problem..In the following wsdl [1], there is a construct as follows, but in the generated code i don't see any handling for attribute stuff. [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/security/interop/ping.wsdl > Adding Simple Content Extension Support to ADB > -- > > Key: AXIS2-946 > URL: http://issues.apache.org/jira/browse/AXIS2-946 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement >Reporter: Maryam Moazeni >Priority: Minor > Attachments: axis2-418.wsdl, patchfile.txt, SchemaCompiler.java, > Test5.xsd > > > Hi, > I implemented the simple content extension. > Any comments are appreciated ... > Thanks, > Maryam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-946) Adding Simple Content Extension Support to ADB
[ http://issues.apache.org/jira/browse/AXIS2-946?page=comments#action_12426123 ] Davanum Srinivas commented on AXIS2-946: Maryam, I've checked in the code. Please cross check. added the Test5.xsd as well as modules\adb-codegen\test-resources\xsd\simple_content_extension.xsd with a test : modules\adb-codegen\test\org\apache\axis2\schema\compile\SimpleContentExtensionTest.java thanks, dims > Adding Simple Content Extension Support to ADB > -- > > Key: AXIS2-946 > URL: http://issues.apache.org/jira/browse/AXIS2-946 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement >Reporter: Maryam Moazeni >Priority: Minor > Attachments: axis2-418.wsdl, patchfile.txt, SchemaCompiler.java, > Test5.xsd > > > Hi, > I implemented the simple content extension. > Any comments are appreciated ... > Thanks, > Maryam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-946) Adding Simple Content Extension Support to ADB
[ http://issues.apache.org/jira/browse/AXIS2-946?page=comments#action_12426149 ] Davanum Srinivas commented on AXIS2-946: Maryam, Fixed one bug: http://svn.apache.org/viewvc?view=rev&revision=429252 Added one test case: http://svn.apache.org/viewvc?view=rev&revision=429255 Thanks, dims > Adding Simple Content Extension Support to ADB > -- > > Key: AXIS2-946 > URL: http://issues.apache.org/jira/browse/AXIS2-946 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement >Reporter: Maryam Moazeni >Priority: Minor > Attachments: axis2-418.wsdl, patchfile.txt, SchemaCompiler.java, > Test5.xsd > > > Hi, > I implemented the simple content extension. > Any comments are appreciated ... > Thanks, > Maryam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-906) Adding Complex Content Restriction Support to ADB
[
http://issues.apache.org/jira/browse/AXIS2-906?page=comments#action_12426189 ]
Davanum Srinivas commented on AXIS2-906:
Maryam,
Could you please upload a new zip with "svn diff" against latest SVN? Looks
like some of the code in this patch is common wiht the other patch which i
already checked in.
thanks,
dims
> Adding Complex Content Restriction Support to ADB
> -
>
> Key: AXIS2-906
> URL: http://issues.apache.org/jira/browse/AXIS2-906
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
>Reporter: Maryam Moazeni
>Priority: Minor
> Attachments: ModifiedSrc.zip, patchfile, patchfile.txt, TestCases.zip
>
>
> Regarding the implementation of complex content restriction:
> These are the changes of code in the JavaBeanWriter. Changes in
> SchemaCompiler and BeanWriterMetaInfoHandler are not shown.
> 1) Missing Elements
> 2) Missing Attributes *
> 3) Changes in Type
> 3) Changes in Occurance
> are supporte sofar.
> * Attributes still needs more work.
>
> /* JavaBeanWriter.java */
> private void addPropertyEntries(BeanWriterMetaInfoHolder metainf, Document
> model, Element rootElt, ArrayList propertyNames,
> Map typeMap,
> boolean isInherited) throws
> SchemaCompilationException {
> // go in the loop and add the part elements
> QName[] qName;
> ArrayList missingQNames = new ArrayList();
> ArrayList qNames = new ArrayList();
>
> BeanWriterMetaInfoHolder parentMetaInf = metainf.getParent();
>
> if (metainf.isOrdered()) {
> qName = metainf.getOrderedQNameArray();
> } else {
> qName= metainf.getQNameArray();
> }
>
> for (int i = 0; i < qName.length; i++) {
> qNames.add(qName[i]);
> }
> //adding missing QNames to the end, including elements & attributes.
> if (metainf.isRestriction()) {
> addMissingQNames(metainf, qNames);
> }
> QName name;
> for (int i = 0; i < qNames.size(); i++) {
> name = (QName) qNames.get(i);
>
> Element property = XSLTUtils.addChildElement(model, "property",
> rootElt);
>
> String xmlName = name.getLocalPart();
> XSLTUtils.addAttribute(model, "name", xmlName, property);
> XSLTUtils.addAttribute(model, "nsuri", name.getNamespaceURI(),
> property);
> String javaName = makeUniqueJavaClassName(propertyNames, xmlName);
> XSLTUtils.addAttribute(model, "javaname", javaName, property);
> String javaClassNameForElement =
> metainf.getClassNameForQName(name);
> if (javaClassNameForElement == null) {
> throw new
> SchemaCompilationException(SchemaCompilerMessages.getMessage("schema.typeMissing"));
> }
>
> if (metainf.isRestriction() && typeChanged(name, metainf)) {
> XSLTUtils.addAttribute(model, "typeChanged", "yes", property);
> XSLTUtils.addAttribute(model, "rewrite", "yes", property);
> }
>
> XSLTUtils.addAttribute(model, "type", javaClassNameForElement,
> property);
> if (PrimitiveTypeFinder.isPrimitive(javaClassNameForElement)) {
> XSLTUtils.addAttribute(model, "primitive", "yes", property);
> }
> //add an attribute that says the type is default
> if (isDefault(javaClassNameForElement)) {
> XSLTUtils.addAttribute(model, "default", "yes", property);
> }
> if (typeMap.containsKey(metainf.getSchemaQNameForQName(name))) {
> XSLTUtils.addAttribute(model, "ours", "yes", property);
> }
> if (metainf.getAttributeStatusForQName(name)) {
> XSLTUtils.addAttribute(model, "attribute", "yes", property);
> }
> if (metainf.isNillable(name)) {
> XSLTUtils.addAttribute(model, "nillable", "yes", property);
> }
> String shortTypeName;
> if (metainf.getSchemaQNameForQName(name) != null) {
> //see whether the QName is a basetype
> if
> (baseTypeMap.containsKey(metainf.getSchemaQNameForQName(name))){
> shortTypeName=
> metainf.getSchemaQNameForQName(name).getLocalPart();
> }else{
> shortTypeName =
> getShortTypeName(javaClassNameForElement);
> }
> }else{
> shortType
[jira] Created: (AXIS2-981) Support for Enumeration
Support for Enumeration --- Key: AXIS2-981 URL: http://issues.apache.org/jira/browse/AXIS2-981 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Reporter: Davanum Srinivas Attachments: PlaceType.java WSDL: https://svn.apache.org/repos/asf/webservices/axis/trunk/java/test/wsdl/terra/TerraService.WSDL Schema Snippet: Problem: Axis2 generated code does not generate an ADBBean for PlaceType.java. It just creates methods using String since that is the restriction base. Axis1.X generates a bean for PlaceType.java and has the list of possible values as well (and allows only those to be get/set on the field). See enclosed java file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-983) Support for Simple Type Union and Simple Type List
[ http://issues.apache.org/jira/browse/AXIS2-983?page=comments#action_12426230 ] Davanum Srinivas commented on AXIS2-983: Please upload a complete wsdl. That would help immensely. thanks, dims > Support for Simple Type Union and Simple Type List > -- > > Key: AXIS2-983 > URL: http://issues.apache.org/jira/browse/AXIS2-983 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Reporter: Fabian Christ > > The latest SVN version of WSDL2Java and so the SchemaCompiler does not > support Simple Type Union and List in XML Schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-983) Support for Simple Type Union and Simple Type List
[ http://issues.apache.org/jira/browse/AXIS2-983?page=comments#action_12426247 ] Davanum Srinivas commented on AXIS2-983: Hmm, You are writing an STS. Have you looked at code in security/rampart modules? I believe Ruchith is actually participating in the OASIS WSSX working group's virutal interop as we speak. thanks, dims > Support for Simple Type Union and Simple Type List > -- > > Key: AXIS2-983 > URL: http://issues.apache.org/jira/browse/AXIS2-983 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Reporter: Fabian Christ > Attachments: sample-wsdl.zip > > > The latest SVN version of WSDL2Java and so the SchemaCompiler does not > support Simple Type Union and List in XML Schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-975) Classpath/Classloader issue with packaging
[ http://issues.apache.org/jira/browse/AXIS2-975?page=all ] Davanum Srinivas resolved AXIS2-975. Resolution: Invalid Debashish was able to do this using the nightly. -- dims > Classpath/Classloader issue with packaging > -- > > Key: AXIS2-975 > URL: http://issues.apache.org/jira/browse/AXIS2-975 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: deployment >Affects Versions: 1.0 > Environment: Tomcat 5.0, Axis2 1.0, Eclipse, iBATIS >Reporter: Debasish Duttaroy >Priority: Blocker > Attachments: PhoenixWebServices.aar > > > I have one single java project in eclipse environment. It is called > PhoenixWebServices. > 1. There is a file folder called "lib" that contains all the required jar > files. > 2. There is a folder called "xml" which contains all the iBATIS related xml > files. > 3. There is a folder called "META-INF" which contains all the wsdl files and > the services.xml > There are separate packages for delegate, dao, dto etc. > I prepare the wsdl files by my own and then use WSDL2Java with eclipse to > generate all the code. Till now all is fine (apparently). > 1. Now I export my only java project from eclipse as a .jar file. > 2. Then I rename it to .aar file. > 3. Deploy it in Axis2 > All is still fine. I have test servlet which calls the service. > 1. Inside the client Skeleton code in server side, I call the delegate to do > all the task and return a dto. > 2. The delegate and dao needs the iBATIS xml files which I have packaged > inside the .aar, as described above. > Problem is delegate does not find the xml/*.xml files. > Please find the .aar attached. It contains all the files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-982) org.apache.axis2.AxisFault: java.lang.NoSuchMethodError: org.apache.axis2.databinding.utils.ConverterUtil.convertTolong(Ljava/lang/String;)
[ http://issues.apache.org/jira/browse/AXIS2-982?page=all ] Davanum Srinivas resolved AXIS2-982. Resolution: Invalid This was also a pilot error :) using Eclipse plugin generated code with nightly is not a good thing :) -- dims > org.apache.axis2.AxisFault: java.lang.NoSuchMethodError: > org.apache.axis2.databinding.utils.ConverterUtil.convertTolong(Ljava/lang/String;) > --- > > Key: AXIS2-982 > URL: http://issues.apache.org/jira/browse/AXIS2-982 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.0 > Environment: Nightly build for 7th August >Reporter: Debasish Duttaroy >Priority: Blocker > > Here is a stack trace. This is when I call a webservice via a generated > client code. > SEVERE: java.lang.NoSuchMethodError: > org.apache.axis2.databinding.utils.ConverterUtil.convertTolong(Ljava/lang/String;)J > org.apache.axis2.AxisFault: java.lang.NoSuchMethodError: > org.apache.axis2.databinding.utils.ConverterUtil.convertTolong(Ljava/lang/String;)J > at > org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287) > at > com.debasish.remote.axis2.client.request.RequestWSStub.getRequestDetails(RequestWSStub.java:119) > at > com.debasish.remote.test.RemoteAxis2Servlet.doGet(RemoteAxis2Servlet.java:46) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) > at > org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) > at java.lang.Thread.run(Thread.java:534) > Caused by: java.lang.Exception: org.apache.axis2.AxisFault: > java.lang.NoSuchMethodError: > org.apache.axis2.databinding.utils.ConverterUtil.convertTolong(Ljava/lang/String;)J; > nested exception is: > java.lang.NoSuchMethodError: > org.apache.axis2.databinding.utils.ConverterUtil.convertTolong(Ljava/lang/String;)J > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:174) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) > at > org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) > at > org.apache.cat
[jira] Commented: (AXIS2-983) Support for Simple Type Union and Simple Type List
[ http://issues.apache.org/jira/browse/AXIS2-983?page=comments#action_12426549 ] Davanum Srinivas commented on AXIS2-983: STS = SecurityTokenService > Support for Simple Type Union and Simple Type List > -- > > Key: AXIS2-983 > URL: http://issues.apache.org/jira/browse/AXIS2-983 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Reporter: Fabian Christ > Attachments: sample-wsdl.zip > > > The latest SVN version of WSDL2Java and so the SchemaCompiler does not > support Simple Type Union and List in XML Schema. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
