[jira] Resolved: (AXIS-2574) Reading an attachment (slowly) can cause resource deleted error
[ https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved AXIS-2574. --- Resolution: Fixed Assignee: Jochen Wiedmann Applied to the Axis trunk. Reading an attachment (slowly) can cause resource deleted error --- Key: AXIS-2574 URL: https://issues.apache.org/jira/browse/AXIS-2574 Project: Axis Issue Type: Bug Components: Basic Architecture Affects Versions: 1.2.1 Reporter: Steve Sowerby Assignee: Jochen Wiedmann Attachments: axis-2574.patch, Call.diff, Call.diff, Call.java When reading the data from an attachment we periodically get the following error: java.io.IOException: Resource has been deleted. at org.apache.axis.attachments.ManagedMemoryDataSource$Instream.read(ManagedMemoryDataSource.java:688) Having run this throught a debugger and had a brief look at the code it seems to me there is a race condition of sorts. The MemoryManagedDataSource that provides the InputStream has been marked as deleted by the finalize method of AttachmentPart. So basically if the client doesn't read off the attachment fast enough then the writer will have finished and the AttachmentPart gets finalized and blam, you've got a deleted MemoryManagedDataSource. I'm not sure what the best fix is. Perhaps the deletion should actually be some reference count rather than a simple boolean. That way the MemoryManagedDataSource gets deleted once all the writers and readers are done? Although perhaps then there would be an issue if the client was very slow to even open the attachment? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS-2574) Reading an attachment (slowly) can cause resource deleted error
[ https://issues.apache.org/jira/browse/AXIS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann updated AXIS-2574: -- Attachment: axis-2574.patch Updated version of Rodrigos patch. Reading an attachment (slowly) can cause resource deleted error --- Key: AXIS-2574 URL: https://issues.apache.org/jira/browse/AXIS-2574 Project: Axis Issue Type: Bug Components: Basic Architecture Affects Versions: 1.2.1 Reporter: Steve Sowerby Attachments: axis-2574.patch, Call.diff, Call.diff, Call.java When reading the data from an attachment we periodically get the following error: java.io.IOException: Resource has been deleted. at org.apache.axis.attachments.ManagedMemoryDataSource$Instream.read(ManagedMemoryDataSource.java:688) Having run this throught a debugger and had a brief look at the code it seems to me there is a race condition of sorts. The MemoryManagedDataSource that provides the InputStream has been marked as deleted by the finalize method of AttachmentPart. So basically if the client doesn't read off the attachment fast enough then the writer will have finished and the AttachmentPart gets finalized and blam, you've got a deleted MemoryManagedDataSource. I'm not sure what the best fix is. Perhaps the deletion should actually be some reference count rather than a simple boolean. That way the MemoryManagedDataSource gets deleted once all the writers and readers are done? Although perhaps then there would be an issue if the client was very slow to even open the attachment? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2676) Issues using two different implementations of JABX in Axis and WS
[ https://issues.apache.org/jira/browse/AXIS2-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved AXIS2-2676. Resolution: Won't Fix Issues using two different implementations of JABX in Axis and WS - Key: AXIS2-2676 URL: https://issues.apache.org/jira/browse/AXIS2-2676 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Environment: Reproduced on Mac OSX, Solaris 10, and Windows. Using Java 1.4.2 and 1.6 update 1. Reporter: Bruce Hitchcock Assignee: Jochen Wiedmann I believe there is a conflict issue when a client WS uses Apache JaxMe or JAXBI inside of Axis 2 1.1.1. My WS service successfully runs outside the container via junits. However, the following occurs when deployed inside Axis2 Here is a stack trace. The service operation is defined to take an xs:string and return an xs:string. Both are really XML however, the marshalling and unmarshalling is handled inside of XAOHelper. This is where the exception happens. I believe doesnt contain ObjectFactory.class or jaxb.index is particlular to the JAXB implementation inside the jar files include with Axis2 (Sun's impl ?) and not to Apache JaxMe. This might be and issue of not specifing and implementation at run time. Any help will be greatly appreciated. 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver - javax.xml.bind.JAXBException: com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 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.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:118) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.Exception: javax.xml.bind.JAXBException: com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index at com.comcast.cable.sams.tts.service.xao.XAOHelper.marshall(Unknown Source) at com.comcast.cable.sams.tts.service.xao.handler.GetCustomerTicketResponseXAOHandler.beanToXml(Unknown Source) at
[jira] Commented: (AXIS2-2676) Issues using two different implementations of JABX in Axis and WS
[ https://issues.apache.org/jira/browse/AXIS2-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507272 ] Jochen Wiedmann commented on AXIS2-2676: As indicated, I suppose the problem is on the users side. So far no response. I'll close the issue in the next two weeks, should I still receive no reply. Issues using two different implementations of JABX in Axis and WS - Key: AXIS2-2676 URL: https://issues.apache.org/jira/browse/AXIS2-2676 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Environment: Reproduced on Mac OSX, Solaris 10, and Windows. Using Java 1.4.2 and 1.6 update 1. Reporter: Bruce Hitchcock Assignee: Jochen Wiedmann I believe there is a conflict issue when a client WS uses Apache JaxMe or JAXBI inside of Axis 2 1.1.1. My WS service successfully runs outside the container via junits. However, the following occurs when deployed inside Axis2 Here is a stack trace. The service operation is defined to take an xs:string and return an xs:string. Both are really XML however, the marshalling and unmarshalling is handled inside of XAOHelper. This is where the exception happens. I believe doesnt contain ObjectFactory.class or jaxb.index is particlular to the JAXB implementation inside the jar files include with Axis2 (Sun's impl ?) and not to Apache JaxMe. This might be and issue of not specifing and implementation at run time. Any help will be greatly appreciated. 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver - javax.xml.bind.JAXBException: com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 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.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:118) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.Exception: javax.xml.bind.JAXBException: com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index at com.comcast.cable.sams.tts.service.xao.XAOHelper.marshall(Unknown Source) at
[jira] Commented: (AXIS2-2676) Issues using two different implementations of JABX in Axis and WS
[ https://issues.apache.org/jira/browse/AXIS2-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502081 ] Jochen Wiedmann commented on AXIS2-2676: First of all, let me recapitulate my understanding of the issue: Please verify whether I get this right so far. The user has generated classes using JaxMe. At runtime, the wrong implementation of JAXBContext is loaded. This implementation is looking for a file jaxb.index or an ObjectFactory class in the package com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse. At least the file isn't found, because JaxMe uses a file called Configuration.xml. The actual issue is the instantiation of the wrong JAXBContext. Basically, the classpath may safely contain as many JAXB implementations as you like as long as the proper implementation of JAXBContext is choosen. Choosing this implementation is controlled by a file com/comcast/cable/sams/tts/service/xao/getcustomerticketresponse/jaxb.properties with a property javax.xml.bind.context.factory So, my guess is that there's have another jaxb.properties file in the classpath.Perhaps you have experimented with the sun implementation and did not clean the path? Issues using two different implementations of JABX in Axis and WS - Key: AXIS2-2676 URL: https://issues.apache.org/jira/browse/AXIS2-2676 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Environment: Reproduced on Mac OSX, Solaris 10, and Windows. Using Java 1.4.2 and 1.6 update 1. Reporter: Bruce Hitchcock Assignee: Jochen Wiedmann Fix For: 1.1.1 I believe there is a conflict issue when a client WS uses Apache JaxMe or JAXBI inside of Axis 2 1.1.1. My WS service successfully runs outside the container via junits. However, the following occurs when deployed inside Axis2 Here is a stack trace. The service operation is defined to take an xs:string and return an xs:string. Both are really XML however, the marshalling and unmarshalling is handled inside of XAOHelper. This is where the exception happens. I believe doesnt contain ObjectFactory.class or jaxb.index is particlular to the JAXB implementation inside the jar files include with Axis2 (Sun's impl ?) and not to Apache JaxMe. This might be and issue of not specifing and implementation at run time. Any help will be greatly appreciated. 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR com.comcast.cable.sams.tts.service.xao.XAOHelper - com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 2007-05-15 22:27:49,651 [http-8080-Processor25] ERROR org.apache.axis2.rpc.receivers.RPCMessageReceiver - javax.xml.bind.JAXBException: com.comcast.cable.sams.tts.service.xao.getcustomerticketresponse doesnt contain ObjectFactory.class or jaxb.index 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.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:118) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at
[jira] Assigned: (AXIS2-2633) axis2-wsdl2code-maven-plugin missing extension option bindingfile for JiBX
[ https://issues.apache.org/jira/browse/AXIS2-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann reassigned AXIS2-2633: -- Assignee: Jochen Wiedmann axis2-wsdl2code-maven-plugin missing extension option bindingfile for JiBX Key: AXIS2-2633 URL: https://issues.apache.org/jira/browse/AXIS2-2633 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.2 Environment: all platforms Reporter: Armin Ehrenfels Assigned To: Jochen Wiedmann axis2-wsdl2code-maven-plugin doesn't support extension options such as -Ebindingfile for JiBX. SUGGESTION: 1. in the plugin configuration, introducing an additional option extensionOptions, similar to namespaceURIs, like this: extensionOptions extensionOption namexxx/name valueyyy/value /extensionOption ... /extensionOptions 2. in the mojo, for each extension option adding the name/value pair to optionsMap. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2429) Wrong dependency in axis2-wsdl2code-maven-plugin
[ https://issues.apache.org/jira/browse/AXIS2-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann reassigned AXIS2-2429: -- Assignee: Jochen Wiedmann Wrong dependency in axis2-wsdl2code-maven-plugin Key: AXIS2-2429 URL: https://issues.apache.org/jira/browse/AXIS2-2429 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.1.1 Environment: w2ksp4 jvm1.4.2_06 Reporter: Sergey Bespalov Assigned To: Jochen Wiedmann Priority: Critical First of all I have java.lang.NoClassDefFoundError: javax/wsdl/WSDLException when try to use it. Second I was really upset when I saw axiom-api-SNAPSHOT and axiom-parent-SNAPSHOT. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-2128) Wrong type mapping in java2wsdl for java.math.BigDecimal
[
https://issues.apache.org/jira/browse/AXIS2-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann reassigned AXIS2-2128:
--
Assignee: Jochen Wiedmann
Wrong type mapping in java2wsdl for java.math.BigDecimal
Key: AXIS2-2128
URL: https://issues.apache.org/jira/browse/AXIS2-2128
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: 1.1.1
Reporter: Mirko Zeibig
Assigned To: Jochen Wiedmann
Java2Wsdl generates 'xs:int' for 'java.math.BigDecimal' instead of
'xs:decimal'. This is wrong because of:
[Definition:] integer is - derived- from decimal by fixing the value of -
fractionDigits- to be 0and disallowing the trailing decimal point. This
results in the standard mathematical concept of the integer numbers. The -
value space- of integer is the infinite set {...,-2,-1,0,1,2,...}. The -
base type- of integer is decimal.
It is easy to fix in 'org.apache.ws.java2wsdl.utils.TypeTable' by adding this
line of code:
simpleTypetoxsd.put(java.math.BigDecimal, new
QName(Java2WSDLConstants.URI_2001_SCHEMA_XSD, decimal, xs));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2128) Wrong type mapping in java2wsdl for java.math.BigDecimal
[
https://issues.apache.org/jira/browse/AXIS2-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved AXIS2-2128.
Resolution: Fixed
Already fixed in the trunk with revision 529296.
Wrong type mapping in java2wsdl for java.math.BigDecimal
Key: AXIS2-2128
URL: https://issues.apache.org/jira/browse/AXIS2-2128
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: 1.1.1
Reporter: Mirko Zeibig
Assigned To: Jochen Wiedmann
Java2Wsdl generates 'xs:int' for 'java.math.BigDecimal' instead of
'xs:decimal'. This is wrong because of:
[Definition:] integer is - derived- from decimal by fixing the value of -
fractionDigits- to be 0and disallowing the trailing decimal point. This
results in the standard mathematical concept of the integer numbers. The -
value space- of integer is the infinite set {...,-2,-1,0,1,2,...}. The -
base type- of integer is decimal.
It is easy to fix in 'org.apache.ws.java2wsdl.utils.TypeTable' by adding this
line of code:
simpleTypetoxsd.put(java.math.BigDecimal, new
QName(Java2WSDLConstants.URI_2001_SCHEMA_XSD, decimal, xs));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2429) Wrong dependency in axis2-wsdl2code-maven-plugin
[ https://issues.apache.org/jira/browse/AXIS2-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved AXIS2-2429. Resolution: Fixed Looking at the current code (revision 533822), I note: - there are no direct dependencies on Axiom. Dependencies are inherited from exis2-kernel, etc. In other words: No need to change anything. - The NoClassDefFoundError cannot be reproduced. This is most possibly caused by the use of SNAPSHOT versions. Wrong dependency in axis2-wsdl2code-maven-plugin Key: AXIS2-2429 URL: https://issues.apache.org/jira/browse/AXIS2-2429 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.1.1 Environment: w2ksp4 jvm1.4.2_06 Reporter: Sergey Bespalov Assigned To: Jochen Wiedmann Priority: Critical First of all I have java.lang.NoClassDefFoundError: javax/wsdl/WSDLException when try to use it. Second I was really upset when I saw axiom-api-SNAPSHOT and axiom-parent-SNAPSHOT. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1301) axis2-wsdl2code-maven-plugin pom.xml missing dependencies
[ https://issues.apache.org/jira/browse/AXIS2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved AXIS2-1301. Resolution: Fixed As of revision 526955, this is already fixed. axis2-wsdl2code-maven-plugin pom.xml missing dependencies - Key: AXIS2-1301 URL: https://issues.apache.org/jira/browse/AXIS2-1301 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: nightly Reporter: Terry Cox Assigned To: Jochen Wiedmann Priority: Minor The axis2-wsdl2code-maven-plugin project pom needs the following dependencies added to support xmlbeans data binding: dependency groupIdxmlbeans/groupId artifactIdxbean/artifactId version2.1.0/version scopecompile/scope /dependency dependency groupIdaxis2/groupId artifactIdaxis2-xmlbeans/artifactId versionSNAPSHOT/version /dependency /dependencies In addition, the following goalPrefix should be declared to permit users to start the plugin with the command 'mvn wsdl2code:wsdl2code' build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixwsdl2code/goalPrefix /configuration /plugin /plugins /build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1302) axis2-aar-maven-plugin/axis2-wsdl2code-maven-plugin combination creates aar file with services.xml in wrong location
[
https://issues.apache.org/jira/browse/AXIS2-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492762
]
Jochen Wiedmann commented on AXIS2-1302:
The problem here is, that the target layout (directories resources, src, test)
isn't specified by the Maven plugin, but by the general WSDL2Code component of
Axis 2.
Nevertheless, it is also not required to have the requested layout. The
maven-resources-plugin can very well be configured to put the services.xml file
into the right location, for example like this:
resource
directory${project.build.directory}/generated-resources/wsdl2code/directory
excludes
excludeservices.xml/exclude
/excludes
/resource
resource
directory${project.build.directory}/generated-resources/wsdl2code/directory
includes
includeservices.xml/include
/includes
targetPathMETA-INF/targetPath
/resource
axis2-aar-maven-plugin/axis2-wsdl2code-maven-plugin combination creates aar
file with services.xml in wrong location
Key: AXIS2-1302
URL: https://issues.apache.org/jira/browse/AXIS2-1302
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: nightly
Reporter: Terry Cox
Assigned To: Jochen Wiedmann
Priority: Minor
If you create source code from a WSDL file using the
axis2-wsdl2code-maven-plugin, the services.xml file is created in a resources
folder, along with a copy of the WSDL.
If you now build the source using Maven2 and then package using
axis2-aar-maven-plugin, the services.xml file ends up in the root of the aar
when it should be in META-INF. The correct solution would probably be to have
axis2-wsdl2code-maven-plugin put the original files into resources/META-INF
so the Maven build copies them correctly.
Similarly, the following problem occurs during code generation:
Say we have an outputDirectory of 'src/main'. After generation, we get the
following heirarchy:
src / main / resources
src / main / src
src / main / test
however, Maven2 expects to find java source in a folder called 'java', so it
would be better to output the code into a folder that matches the language
selected:
src / main / resources
src / main / resources/META-INF
src / main / java
src / main / test
By doing this, a single Maven2 POM file can be used to generate, compile and
package the service, as shown below:
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdcom.foo.bar/groupId
artifactIdecho_service/artifactId
version1.0-SNAPSHOT/version
nameCode generation from WSDL/name
dependencies
dependency
groupIdxmlbeans/groupId
artifactIdxbean/artifactId
version2.1.0/version
scopecompile/scope
/dependency
dependency
groupIdstax/groupId
artifactIdstax-api/artifactId
version1.0.1/version
/dependency
dependency
groupIdaxis2/groupId
artifactIdaxis2-kernel/artifactId
versionSNAPSHOT/version
/dependency
dependency
groupIdws-commons/groupId
artifactIdaxiom-api/artifactId
version1.1.1/version
/dependency
dependency
groupIdws-commons/groupId
artifactIdaxiom-impl/artifactId
versionSNAPSHOT/version
/dependency
dependency
groupIdws-commons/groupId
artifactIdneethi/artifactId
version1.0.1/version
/dependency
dependency
groupIdorg.apache.ws.commons/groupId
artifactIdneethi/artifactId
versionSNAPSHOT/version
/dependency
dependency
groupIdwsdl4j/groupId
artifactIdwsdl4j/artifactId
version1.5.3/version
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.axis2.maven2/groupId
artifactIdaxis2-wsdl2code-maven-plugin/artifactId
version1.0-SNAPSHOT/version
executions
execution
phasewsdl2code/phase
goals
goalwsdl2code/goal
/goals
/execution
/executions
configuration
generateServerSidetrue/generateServerSide
generateServerSideInterfacetrue/generateServerSideInterface
generateAllClassestrue/generateAllClasses
generateServiceXmltrue/generateServiceXml
generateTestcasetrue/generateTestcase
packageNamecom.foo.bar.echo/packageName
wsdlFilewsdl/Echo.wsdl/wsdlFile
[jira] Commented: (AXIS2-1130) Build with Maven 2
[ https://issues.apache.org/jira/browse/AXIS2-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487377 ] Jochen Wiedmann commented on AXIS2-1130: Would a sample implementation help? If so, give me a pointer. Build with Maven 2 -- Key: AXIS2-1130 URL: https://issues.apache.org/jira/browse/AXIS2-1130 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: samples, build,site Reporter: Jochen Wiedmann Assigned To: Jochen Wiedmann Attachments: axis2-maven2.patch This is a tracker bug, which serves the following purposes: - Keep people informed about the ongoing efforts. - Prevent that someone else starts working on the same topic. - If possible, attract other people to start working here. - Collect dependencies on related bugs like AXIS2-1128 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1140) Axis2 AAR Plugin should allow dependencies to be added to the lib directory in the aar file
[ http://issues.apache.org/jira/browse/AXIS2-1140?page=all ] Jochen Wiedmann resolved AXIS2-1140. Fix Version/s: 1.1 Resolution: Fixed Assignee: Jochen Wiedmann Applied to the 1.1 branch. Axis2 AAR Plugin should allow dependencies to be added to the lib directory in the aar file --- Key: AXIS2-1140 URL: http://issues.apache.org/jira/browse/AXIS2-1140 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Environment: All Reporter: John Pfeifer Assigned To: Jochen Wiedmann Fix For: 1.1 Attachments: AbstractAarMojo.java Axis2 AAR files are supposed to include their dependencies in the lib file of the .aar archive. When the .aar file is deployed, any libraries in the lib directory of the aar file are included in the classpath for the web service. This feature should probably be optional since some users may not want to include the dependencies inside the .aar 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] Assigned: (AXIS2-1301) axis2-wsdl2code-maven-plugin pom.xml missing dependencies
[ http://issues.apache.org/jira/browse/AXIS2-1301?page=all ] Jochen Wiedmann reassigned AXIS2-1301: -- Assignee: Jochen Wiedmann axis2-wsdl2code-maven-plugin pom.xml missing dependencies - Key: AXIS2-1301 URL: http://issues.apache.org/jira/browse/AXIS2-1301 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: nightly Reporter: Terry Cox Assigned To: Jochen Wiedmann Priority: Minor The axis2-wsdl2code-maven-plugin project pom needs the following dependencies added to support xmlbeans data binding: dependency groupIdxmlbeans/groupId artifactIdxbean/artifactId version2.1.0/version scopecompile/scope /dependency dependency groupIdaxis2/groupId artifactIdaxis2-xmlbeans/artifactId versionSNAPSHOT/version /dependency /dependencies In addition, the following goalPrefix should be declared to permit users to start the plugin with the command 'mvn wsdl2code:wsdl2code' build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixwsdl2code/goalPrefix /configuration /plugin /plugins /build -- 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-1302) axis2-aar-maven-plugin/axis2-wsdl2code-maven-plugin combination creates aar file with services.xml in wrong location
[ http://issues.apache.org/jira/browse/AXIS2-1302?page=all ] Jochen Wiedmann reassigned AXIS2-1302: -- Assignee: Jochen Wiedmann axis2-aar-maven-plugin/axis2-wsdl2code-maven-plugin combination creates aar file with services.xml in wrong location Key: AXIS2-1302 URL: http://issues.apache.org/jira/browse/AXIS2-1302 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: nightly Reporter: Terry Cox Assigned To: Jochen Wiedmann Priority: Minor If you create source code from a WSDL file using the axis2-wsdl2code-maven-plugin, the services.xml file is created in a resources folder, along with a copy of the WSDL. If you now build the source using Maven2 and then package using axis2-aar-maven-plugin, the services.xml file ends up in the root of the aar when it should be in META-INF. The correct solution would probably be to have axis2-wsdl2code-maven-plugin put the original files into resources/META-INF so the Maven build copies them correctly. Similarly, the following problem occurs during code generation: Say we have an outputDirectory of 'src/main'. After generation, we get the following heirarchy: src / main / resources src / main / src src / main / test however, Maven2 expects to find java source in a folder called 'java', so it would be better to output the code into a folder that matches the language selected: src / main / resources src / main / resources/META-INF src / main / java src / main / test By doing this, a single Maven2 POM file can be used to generate, compile and package the service, as shown below: ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdcom.foo.bar/groupId artifactIdecho_service/artifactId version1.0-SNAPSHOT/version nameCode generation from WSDL/name dependencies dependency groupIdxmlbeans/groupId artifactIdxbean/artifactId version2.1.0/version scopecompile/scope /dependency dependency groupIdstax/groupId artifactIdstax-api/artifactId version1.0.1/version /dependency dependency groupIdaxis2/groupId artifactIdaxis2-kernel/artifactId versionSNAPSHOT/version /dependency dependency groupIdws-commons/groupId artifactIdaxiom-api/artifactId version1.1.1/version /dependency dependency groupIdws-commons/groupId artifactIdaxiom-impl/artifactId versionSNAPSHOT/version /dependency dependency groupIdws-commons/groupId artifactIdneethi/artifactId version1.0.1/version /dependency dependency groupIdorg.apache.ws.commons/groupId artifactIdneethi/artifactId versionSNAPSHOT/version /dependency dependency groupIdwsdl4j/groupId artifactIdwsdl4j/artifactId version1.5.3/version /dependency /dependencies build plugins plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.0-SNAPSHOT/version executions execution phasewsdl2code/phase goals goalwsdl2code/goal /goals /execution /executions configuration generateServerSidetrue/generateServerSide generateServerSideInterfacetrue/generateServerSideInterface generateAllClassestrue/generateAllClasses generateServiceXmltrue/generateServiceXml generateTestcasetrue/generateTestcase packageNamecom.foo.bar.echo/packageName wsdlFilewsdl/Echo.wsdl/wsdlFile outputDirectorysrc/main/outputDirectory syncModeboth/syncMode databindingNamexmlbeans/databindingName languagejava/language /configuration /plugin plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-aar-maven-plugin/artifactId version1.0-SNAPSHOT/version executions execution phasepackage/phase goals goalaar/goal /goals /execution /executions configuration outputDirectorytarget/outputDirectory aarNameecho/aarName /configuration /plugin /plugins /build /project -- This message is
[jira] Commented: (AXIS2-1111) Add Maven 2 Plugins
[ http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12434074 ] Jochen Wiedmann commented on AXIS2-: John, please be so kind to file separate issues under component tools. If possible, please assign them to me, otherwise let me know via private mail so that I can take them. Reusing this issue isn't a good idea. Add Maven 2 Plugins --- Key: AXIS2- URL: http://issues.apache.org/jira/browse/AXIS2- Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: Tools Reporter: Jochen Wiedmann Attachments: axis2-maven-tools.jar.bz2 Attached you find a first implementation of Maven 2 plugins for Axis 2: axis2-aar-maven-pluginCreates an aar file axis2-wsdl2code-maven-plugin Runs the wsdl2code generator axis2-java2wsdl-maven-plugin Runs the java2wsdl generator I'd like to contribute this to the Axis 2 project. Maintaining them would work best as soon as Axis 2 is itself built with Maven. The project needs more work. In particular, it lacks documentation. -- 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-1128) Layout of axis2/modules/tool
[ http://issues.apache.org/jira/browse/AXIS2-1128?page=comments#action_12433576 ] Jochen Wiedmann commented on AXIS2-1128: But, Dims, isn't that just another argument to break up the eclipse specific stuff into a separate directory? At least, I find it quite inconvenient to work with compiler excludes. Layout of axis2/modules/tool Key: AXIS2-1128 URL: http://issues.apache.org/jira/browse/AXIS2-1128 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Reporter: Jochen Wiedmann Hello, while working on the Maven 2 build of Axis 2, I detected a problem in the layout of the directory axis2/modules/tool. This directory contains, among others, a directory src and several directories with Maven 2 plugins. The src subdirectory means, that the directory is meant to produce artifacts, for example axis2-tools.jar. In other words, the axis2-tool project should have packaging jar. On the other hand, the presence of maven plugins below means, that the directory is a parent directory. In other words, it should have packaging pom. I see no other possibility to resolve the problem, apart from changing the directory layout. Suggested new layout: axis2 +-- modules +-- tool (I'd personally consider tools a better name.) +-- maven2 |+-- axis2-aar-maven-plugin |+-- axis2-idea-plugin |+-- axis2-java2wsdl-maven-plugin |+-- axis2-wsdl2code-maven-plugin |+-- pom.xml +-- general | +-- src | +-- conf | +-- script | +-- test | +-- pom.xml | +-- project.xml +-- pom.xml I do personally believe, that the directory general should be splitted into more subprojects. However, that could as well be done at a later point. -- 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-1130) Build with Maven 2
Build with Maven 2 -- Key: AXIS2-1130 URL: http://issues.apache.org/jira/browse/AXIS2-1130 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Reporter: Jochen Wiedmann Assigned To: Jochen Wiedmann This is a tracker bug, which serves the following purposes: - Keep people informed about the ongoing efforts. - Prevent that someone else starts working on the same topic. - If possible, attract other people to start working here. - Collect dependencies on related bugs like AXIS2-1128 -- 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] Work started: (AXIS2-1130) Build with Maven 2
[ http://issues.apache.org/jira/browse/AXIS2-1130?page=all ] Work on AXIS2-1130 started by Jochen Wiedmann. Build with Maven 2 -- Key: AXIS2-1130 URL: http://issues.apache.org/jira/browse/AXIS2-1130 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Reporter: Jochen Wiedmann Assigned To: Jochen Wiedmann Attachments: axis2-maven2.patch This is a tracker bug, which serves the following purposes: - Keep people informed about the ongoing efforts. - Prevent that someone else starts working on the same topic. - If possible, attract other people to start working here. - Collect dependencies on related bugs like AXIS2-1128 -- 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-1130) Build with Maven 2
[ http://issues.apache.org/jira/browse/AXIS2-1130?page=all ] Jochen Wiedmann updated AXIS2-1130: --- Attachment: axis2-maven2.patch Current state Build with Maven 2 -- Key: AXIS2-1130 URL: http://issues.apache.org/jira/browse/AXIS2-1130 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Reporter: Jochen Wiedmann Assigned To: Jochen Wiedmann Attachments: axis2-maven2.patch This is a tracker bug, which serves the following purposes: - Keep people informed about the ongoing efforts. - Prevent that someone else starts working on the same topic. - If possible, attract other people to start working here. - Collect dependencies on related bugs like AXIS2-1128 -- 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-1128) Layout of axis2/modules/tool
Layout of axis2/modules/tool Key: AXIS2-1128 URL: http://issues.apache.org/jira/browse/AXIS2-1128 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Reporter: Jochen Wiedmann Hello, while working on the Maven 2 build of Axis 2, I detected a problem in the layout of the directory axis2/modules/tool. This directory contains, among others, a directory src and several directories with Maven 2 plugins. The src subdirectory means, that the directory is meant to produce artifacts, for example axis2-tools.jar. In other words, the axis2-tool project should have packaging jar. On the other hand, the presence of maven plugins below means, that the directory is a parent directory. In other words, it should have packaging pom. I see no other possibility to resolve the problem, apart from changing the directory layout. Suggested new layout: axis2 +-- modules +-- tool (I'd personally consider tools a better name.) +-- maven2 |+-- axis2-aar-maven-plugin |+-- axis2-idea-plugin |+-- axis2-java2wsdl-maven-plugin |+-- axis2-wsdl2code-maven-plugin |+-- pom.xml +-- general | +-- src | +-- conf | +-- script | +-- test | +-- pom.xml | +-- project.xml +-- pom.xml I do personally believe, that the directory general should be splitted into more subprojects. However, that could as well be done at a later point. -- 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-1111) Add Maven 2 Plugins
[ http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12433218 ] Jochen Wiedmann commented on AXIS2-: Eran, I am not an Axis 2 developer. Don't know the Axis projects policies or whether I am nitpicking, but this is how I am used to behave from other projects. Add Maven 2 Plugins --- Key: AXIS2- URL: http://issues.apache.org/jira/browse/AXIS2- Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: Tools Reporter: Jochen Wiedmann Attachments: axis2-maven-tools.jar.bz2 Attached you find a first implementation of Maven 2 plugins for Axis 2: axis2-aar-maven-pluginCreates an aar file axis2-wsdl2code-maven-plugin Runs the wsdl2code generator axis2-java2wsdl-maven-plugin Runs the java2wsdl generator I'd like to contribute this to the Axis 2 project. Maintaining them would work best as soon as Axis 2 is itself built with Maven. The project needs more work. In particular, it lacks documentation. -- 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-1111) Add Maven 2 Plugins
[ http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12432778 ] Jochen Wiedmann commented on AXIS2-: I hope Axis2 project itself will move to maven2 as its build system. Gimme time. :-) As a first step, you could be so kind to pull this stuff in, for example into the modules directory. (It wouldn't need to be configured into the build system.) Add Maven 2 Plugins --- Key: AXIS2- URL: http://issues.apache.org/jira/browse/AXIS2- Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: Tools Reporter: Jochen Wiedmann Attachments: axis2-maven-tools.jar.bz2 Attached you find a first implementation of Maven 2 plugins for Axis 2: axis2-aar-maven-pluginCreates an aar file axis2-wsdl2code-maven-plugin Runs the wsdl2code generator axis2-java2wsdl-maven-plugin Runs the java2wsdl generator I'd like to contribute this to the Axis 2 project. Maintaining them would work best as soon as Axis 2 is itself built with Maven. The project needs more work. In particular, it lacks documentation. -- 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-1111) Add Maven 2 Plugins
[ http://issues.apache.org/jira/browse/AXIS2-?page=comments#action_12432816 ] Jochen Wiedmann commented on AXIS2-: I believe, that modules inside modules are fine in this particular case: Obviously, it makes sense to use a special parent POM in this case. (As soon as Axis 2 is built with Maven 2 itself, this POM should be derived from the Axis 2 parent POM itself.) However, I understand your concern. So, if you don't like the layout, I can change this and replace the parent folder on top with a separate module, for example axis2-tools-parent, or something like that. On the other hand, one should keep in mind, that most probably many more Maven 2 plugins will arise in the future: For example deployment modules, c2wsdl, or whatever. Doing this will be much more convenient, if we accept the concept of modules inside this very special module. As for ws-commons: I do not view these plugins as a shareable component. IMO, these are depending on Axis 2 and should be maintained together with the Axis 2 kernel, just like the Ant generators. However, if the final decision should be to reject the plugins from Axis 2, I could them to ws-commons, of course. Add Maven 2 Plugins --- Key: AXIS2- URL: http://issues.apache.org/jira/browse/AXIS2- Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: Tools Reporter: Jochen Wiedmann Attachments: axis2-maven-tools.jar.bz2 Attached you find a first implementation of Maven 2 plugins for Axis 2: axis2-aar-maven-pluginCreates an aar file axis2-wsdl2code-maven-plugin Runs the wsdl2code generator axis2-java2wsdl-maven-plugin Runs the java2wsdl generator I'd like to contribute this to the Axis 2 project. Maintaining them would work best as soon as Axis 2 is itself built with Maven. The project needs more work. In particular, it lacks documentation. -- 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-1111) Add Maven 2 Plugins
Add Maven 2 Plugins --- Key: AXIS2- URL: http://issues.apache.org/jira/browse/AXIS2- Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: Tools Reporter: Jochen Wiedmann Attachments: axis2-maven-tools.jar.bz2 Attached you find a first implementation of Maven 2 plugins for Axis 2: axis2-aar-maven-pluginCreates an aar file axis2-wsdl2code-maven-plugin Runs the wsdl2code generator axis2-java2wsdl-maven-plugin Runs the java2wsdl generator I'd like to contribute this to the Axis 2 project. Maintaining them would work best as soon as Axis 2 is itself built with Maven. The project needs more work. In particular, it lacks documentation. -- 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-1038) Removing an unnecessary statement
Removing an unnecessary statement - Key: AXIS2-1038 URL: http://issues.apache.org/jira/browse/AXIS2-1038 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Jochen Wiedmann Priority: Trivial The patch below removes an unnecessary statement: Index: modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java === --- modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(revision 431324) +++ modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(working copy) @@ -99,7 +99,6 @@ result = (OMElement) method.invoke(obj, args); AxisService service = msgContext.getAxisService(); -service.getTargetNamespace(); result.declareNamespace(service.getTargetNamespace(), service.getTargetNamespacePrefix()); OMElement bodyContent; -- 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-1038) Removing an unnecessary statement
[ http://issues.apache.org/jira/browse/AXIS2-1038?page=comments#action_12428375 ] Jochen Wiedmann commented on AXIS2-1038: Dims, I might have the necessary permissions in terms of SVN and Unix. Nevertheless, I am no voted member of the Axis2 project and I would personally consider it to be abusing my privileges. Removing an unnecessary statement - Key: AXIS2-1038 URL: http://issues.apache.org/jira/browse/AXIS2-1038 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: core Reporter: Jochen Wiedmann Priority: Trivial The patch below removes an unnecessary statement: Index: modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java === --- modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(revision 431324) +++ modules/core/src/org/apache/axis2/receivers/RawXMLINOutMessageReceiver.java(working copy) @@ -99,7 +99,6 @@ result = (OMElement) method.invoke(obj, args); AxisService service = msgContext.getAxisService(); -service.getTargetNamespace(); result.declareNamespace(service.getTargetNamespace(), service.getTargetNamespacePrefix()); OMElement bodyContent; -- 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-1020) WSDL location service.wsdl is unsupported
WSDL location service.wsdl is unsupported - Key: AXIS2-1020 URL: http://issues.apache.org/jira/browse/AXIS2-1020 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: deployment Reporter: Jochen Wiedmann Attachments: axis2-service-wsdl-location.patch By reading the method DeploymentEngine.populateService, one might come to the conclusion, that it should be possible to deploy the WSDL as META-INF/service.wsdl. Of course, being able to use such a generic location might make quite some sense, at least for the simple case, where only one WSDL is involved. Unfortunately that location doesn't work, because of an obvious programming bug. Patch file attached. -- 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-813) Automatically generated WSDL fails to generate complex type for inner classes
Automatically generated WSDL fails to generate complex type for inner classes - Key: AXIS2-813 URL: http://issues.apache.org/jira/browse/AXIS2-813 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: wsdl Reporter: Jochen Wiedmann Priority: Minor I have created a class AddressManager, which uses an inner class Address. The inner class is used as a parameter and result type in AddressManager. As a next step, I have created a services.xml, in order to make the AddressManager available as a web service. I followed the descriptions in the section on Use Axis2's primary interfaces (APIs) and implement the business logic. from userguide2.html. Deploying this web service works fine. The automatically generated WSDL looks good at first glance. However, closer inspection shows that the complexType, which is created for Address doesn't contain any elements, or attributes. This is caused by the fact that Address is an inner class: If you refactor the inner class as an outer class, then everything works fine. -- 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]
