Re: [Vote] [Axis2] Samisa as Release Manager for Apache Axis2/C 1.1.0 Release
+1 -sahan On 6/19/07, Damitha Kumarage [EMAIL PROTECTED] wrote: +1 Damitha Kaushalye Kapuruge wrote: Hi All, I would like to propose Samisa Abeysinghe as the release manager for Apache Axis2/C 1.1.0 release. Samisa, who is an active committer for Apache Axis2/C, has a good experience as a Release Manager for earlier releases including the 1.0. He has volunteered to be the release manager for Apache Axis2/C 1.1.0. :) Here is my +1. Cheers, Kaushalye - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2C-617) Inconsistent macros in the axutil_log
Inconsistent macros in the axutil_log - Key: AXIS2C-617 URL: https://issues.apache.org/jira/browse/AXIS2C-617 Project: Axis2-C Issue Type: Bug Components: util Affects Versions: Current (Nightly) Reporter: Sahan Gamage Priority: Minor Since we have renamed the axis2 prefix in the util project to axutil we should rename the macros' prefixes also from AXIS2 to AXUTIL to be consistent. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] [Axis2] Samisa as Release Manager for Apache Axis2/C 1.1.0 Release
+1 Thanks, Ruchith On 6/19/07, Sahan Gamage [EMAIL PROTECTED] wrote: +1 -sahan On 6/19/07, Damitha Kumarage [EMAIL PROTECTED] wrote: +1 Damitha Kaushalye Kapuruge wrote: Hi All, I would like to propose Samisa Abeysinghe as the release manager for Apache Axis2/C 1.1.0 release. Samisa, who is an active committer for Apache Axis2/C, has a good experience as a Release Manager for earlier releases including the 1.0. He has volunteered to be the release manager for Apache Axis2/C 1.1.0. :) Here is my +1. Cheers, Kaushalye - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org www.wso2.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Mark, Asankha, I believe that developerworks does provide a free 90 day trial version of WebSphere MQ [1]. Does that satisfy your needs? Cheers, David [1] http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10S_CMP=LP On 18/06/07, Mark Badorrek [EMAIL PROTECTED] wrote: Hi asankha, As far as I know, IBM does not offer a free version of WebsphereMQ. It's their flagship messaging product and they always collect on it. Having said that, it is obviously in Axis2's interest to support WebsphereMQ as it is one of two dominant messaging products in the world today. More importantly, it is in IBM's interest to have Axis2 supporting WebsphereMQ. I'm an IBM business partner so I obviously can't just send over a copy, but I do note that there are quite a few Axis2 committers that work for IBM - can they source a copy? If we can get a copy sent to you I can certainly write up a quick one-page run-sheet outling how to setup QueueManagers, Queues, Authorities etc to conduct a test. Alternatively, in the meantime, if the changes are made, I can confirm whether they succeeded or not. Is this sufficient or do you wish to have this become a part of the standard regression test suite? Unfortunately I'm having no end of trouble getting maven to behave properly with our proxy so I can't build locally at the moment. :-( Mark B From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Mon 6/18/2007 10:01 PM To: axis-dev@ws.apache.org Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections Mark Does WebSphere have a community edition (i.e. that does not require the purchase of a license) that could be used to test this fix? asankha Mark Badorrek (JIRA) wrote: [ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Badorrek updated AXIS2-2816: - Attachment: Axis2-websphereMQ-fix.zip Can't test as I can't build Axis2 under maven at the moment. If this is included in the nightly build I can run it through a websphereMQ test. Current functionality remains unchanged; there is no logical or API modification. The new functionality is only activated if the new parameters are present in the JNDI tree. JMS over WebsphereMQ doesn't support 'CLIENT' connections - Key: AXIS2-2816 URL: https://issues.apache.org/jira/browse/AXIS2-2816 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0 Reporter: Mark Badorrek Attachments: Axis2-websphereMQ-fix.zip Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API. This is insufficient for WebspherMQ CLIENT connections, where the administrator must nominate a particular userID and password per connectionfactory, resulting in the following call which is unsupported in the Axis2 JMS code: factory.createConnection(userID, password) The attached Axis2 JMS files contain the fix to allow the deployer to specify a nominated userID and password through the standard Axis2 JNDI lookup mechanism. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Hi David, Mark I think for right now this would work fine - if Mark can validate that the fixes does work as expected, and not break anything else. However in the longer run, and to ensure that we could support MQ as well as ActiveMQ and any other JMS implementation the best we can, it would make sense for me and any others to get that copy installed. Hopefully, I will not need Websphere, DB2 etc..etc.. to just get MQ running ;-) thanks asankha David Illsley wrote: Mark, Asankha, I believe that developerworks does provide a free 90 day trial version of WebSphere MQ [1]. Does that satisfy your needs? Cheers, David [1] http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10S_CMP=LP On 18/06/07, Mark Badorrek [EMAIL PROTECTED] wrote: Hi asankha, As far as I know, IBM does not offer a free version of WebsphereMQ. It's their flagship messaging product and they always collect on it. Having said that, it is obviously in Axis2's interest to support WebsphereMQ as it is one of two dominant messaging products in the world today. More importantly, it is in IBM's interest to have Axis2 supporting WebsphereMQ. I'm an IBM business partner so I obviously can't just send over a copy, but I do note that there are quite a few Axis2 committers that work for IBM - can they source a copy? If we can get a copy sent to you I can certainly write up a quick one-page run-sheet outling how to setup QueueManagers, Queues, Authorities etc to conduct a test. Alternatively, in the meantime, if the changes are made, I can confirm whether they succeeded or not. Is this sufficient or do you wish to have this become a part of the standard regression test suite? Unfortunately I'm having no end of trouble getting maven to behave properly with our proxy so I can't build locally at the moment. :-( Mark B From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Mon 6/18/2007 10:01 PM To: axis-dev@ws.apache.org Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections Mark Does WebSphere have a community edition (i.e. that does not require the purchase of a license) that could be used to test this fix? asankha Mark Badorrek (JIRA) wrote: [ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Badorrek updated AXIS2-2816: - Attachment: Axis2-websphereMQ-fix.zip Can't test as I can't build Axis2 under maven at the moment. If this is included in the nightly build I can run it through a websphereMQ test. Current functionality remains unchanged; there is no logical or API modification. The new functionality is only activated if the new parameters are present in the JNDI tree. JMS over WebsphereMQ doesn't support 'CLIENT' connections - Key: AXIS2-2816 URL: https://issues.apache.org/jira/browse/AXIS2-2816 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0 Reporter: Mark Badorrek Attachments: Axis2-websphereMQ-fix.zip Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API. This is insufficient for WebspherMQ CLIENT connections, where the administrator must nominate a particular userID and password per connectionfactory, resulting in the following call which is unsupported in the Axis2 JMS code: factory.createConnection(userID, password) The attached Axis2 JMS files contain the fix to allow the deployer to specify a nominated userID and password through the standard Axis2 JNDI lookup mechanism. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
Hi Asankha, David, If you can get the fix into the nightly build I'll give it a run and confirm that everything is OK. Additionally, I'll see if I can get local IBM sales to donate a WebsphereMQ copy. If that work's out I'll outline what sort of work is required to perform a test. You can relax, you will only need WebsphereMQ, not WebsphereEverythingAnd TheKitchenSink. Mark B From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Tue 19/06/2007 6:30 PM To: axis-dev@ws.apache.org Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections Hi David, Mark I think for right now this would work fine - if Mark can validate that the fixes does work as expected, and not break anything else. However in the longer run, and to ensure that we could support MQ as well as ActiveMQ and any other JMS implementation the best we can, it would make sense for me and any others to get that copy installed. Hopefully, I will not need Websphere, DB2 etc..etc.. to just get MQ running ;-) thanks asankha David Illsley wrote: Mark, Asankha, I believe that developerworks does provide a free 90 day trial version of WebSphere MQ [1]. Does that satisfy your needs? Cheers, David [1] http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10S_CMP=LP On 18/06/07, Mark Badorrek [EMAIL PROTECTED] wrote: Hi asankha, As far as I know, IBM does not offer a free version of WebsphereMQ. It's their flagship messaging product and they always collect on it. Having said that, it is obviously in Axis2's interest to support WebsphereMQ as it is one of two dominant messaging products in the world today. More importantly, it is in IBM's interest to have Axis2 supporting WebsphereMQ. I'm an IBM business partner so I obviously can't just send over a copy, but I do note that there are quite a few Axis2 committers that work for IBM - can they source a copy? If we can get a copy sent to you I can certainly write up a quick one-page run-sheet outling how to setup QueueManagers, Queues, Authorities etc to conduct a test. Alternatively, in the meantime, if the changes are made, I can confirm whether they succeeded or not. Is this sufficient or do you wish to have this become a part of the standard regression test suite? Unfortunately I'm having no end of trouble getting maven to behave properly with our proxy so I can't build locally at the moment. :-( Mark B From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Mon 6/18/2007 10:01 PM To: axis-dev@ws.apache.org Subject: Re: [jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections Mark Does WebSphere have a community edition (i.e. that does not require the purchase of a license) that could be used to test this fix? asankha Mark Badorrek (JIRA) wrote: [ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Badorrek updated AXIS2-2816: - Attachment: Axis2-websphereMQ-fix.zip Can't test as I can't build Axis2 under maven at the moment. If this is included in the nightly build I can run it through a websphereMQ test. Current functionality remains unchanged; there is no logical or API modification. The new functionality is only activated if the new parameters are present in the JNDI tree. JMS over WebsphereMQ doesn't support 'CLIENT' connections - Key: AXIS2-2816 URL: https://issues.apache.org/jira/browse/AXIS2-2816 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0 Reporter: Mark Badorrek Attachments: Axis2-websphereMQ-fix.zip Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API. This is insufficient for WebspherMQ CLIENT connections, where the administrator must nominate a particular userID and password per connectionfactory, resulting in the following call which is unsupported in the Axis2 JMS code: factory.createConnection(userID, password) The attached Axis2 JMS files contain the fix to allow the deployer to specify a nominated userID and password through the standard Axis2 JNDI lookup mechanism. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] WSDL generation.
Hi Devs, If a WSDL is not given for a service, and if the service's message receiver is not RPCMessageReceiver what would be the WSDL generation behavior. I'm using the current Axis2 trunk head, and I've using services with custom MR, and when I try to do ?wsdl I'm receiving the following exception, org.apache.axis2.dataretrieval.DataRetrievalException org.apache.axis2.dataretrieval.AxisDataLocatorImpl.getData(AxisDataLocatorImpl.java:81) org.apache.axis2.description.AxisService.getData(AxisService.java:2017) org.apache.axis2.description.AxisService.getWSDL(AxisService.java:995) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:939) org.wso2.wsas.transport.util.Wsdl11Processor$1.printWSDL(Wsdl11Processor.java:40) org.wso2.wsas.transport.util.AbstractWsdlProcessor.printWSDL(AbstractWsdlProcessor.java:51) org.wso2.wsas.transport.util.Wsdl11Processor.process(Wsdl11Processor.java:48) IMHO if the default behavior is not to generate a suitable WSDL, above should show an error message rather an exception. Thank you -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org
Re: svn commit: r547760 - in /webservices/axis2/trunk/java/modules/kernel: src/org/apache/axis2/deployment/ src/org/apache/axis2/deployment/repository/util/ test-resources/deployment/CustomDeployerRep
Jira-2626 is not about the *extension*... It is about *HotUpdate*
failing on custom deployers.. Also on a side note, it would have
been really great if you sent a mail about this change, as this broke
the downstream projects which are using custom deployers..
You have also removed the workaround which I used to get the hotUpdate
working :(.. Now once again HotUpdate on custom deployers fails
miserably...
Thanks,
Thilina
On 6/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: deepal
Date: Fri Jun 15 11:26:39 2007
New Revision: 547760
URL: http://svn.apache.org/viewvc?view=revrev=547760
Log:
fixing AXIS2-2626
now the extension is . (snt like .class)
Modified:
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/RepositoryListener.java
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/WSInfo.java
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/WSInfoList.java
webservices/axis2/trunk/java/modules/kernel/test-resources/deployment/CustomDeployerRepo/axis2.xml
webservices/axis2/trunk/java/modules/kernel/test/org/apache/axis2/deployment/CustomDeployerTest.java
Modified:
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/RepositoryListener.java
URL:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/RepositoryListener.java?view=diffrev=547760r1=547759r2=547760
==
---
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/RepositoryListener.java
(original)
+++
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/RepositoryListener.java
Fri Jun 15 11:26:39 2007
@@ -29,10 +29,8 @@
import java.net.URL;
import java.net.URLClassLoader;
import java.net.URLDecoder;
-import java.net.URI;
import java.util.HashMap;
import java.util.Iterator;
-import java.util.Enumeration;
public class RepositoryListener implements DeploymentConstants {
protected static final Log log =
LogFactory.getLog(RepositoryListener.class);
@@ -250,7 +248,6 @@
if (isSourceControlDir(file)) {
continue;
}
-// TODO: Should this allow expanded directories like
services/modules do?
if (!file.isDirectory() extension.equals(
DeploymentFileData.getFileExtension(file.getName( {
addFileToDeploy(file,
Modified:
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java
URL:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java?view=diffrev=547760r1=547759r2=547760
==
---
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java
(original)
+++
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java
Fri Jun 15 11:26:39 2007
@@ -96,7 +96,7 @@
public static String getFileExtension(String fileName) {
int index = fileName.lastIndexOf('.');
-return fileName.substring(index + 1);
+return fileName.substring(index);
}
public void setClassLoader(ClassLoader classLoader) {
Modified:
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/WSInfo.java
URL:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/WSInfo.java?view=diffrev=547760r1=547759r2=547760
==
---
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/WSInfo.java
(original)
+++
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/WSInfo.java
Fri Jun 15 11:26:39 2007
@@ -51,9 +51,9 @@
this.lastModifiedDate = lastModifiedDate;
this.deployer = deployer;
//TODO: This is a temporary fix for the hot update in custom deployers
-if (!(deployer instanceof ServiceDeployer)) {
- this.type=2;
-}
+//if (!(deployer instanceof ServiceDeployer)) {
+// this.type=2;
+//}
}
public String getFileName() {
Modified:
webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/repository/util/WSInfoList.java
URL:
[jira] Reopened: (AXIS2-2626) HotUpdate fails on custom deployers
[ https://issues.apache.org/jira/browse/AXIS2-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Gunarathne reopened AXIS2-2626: --- What's fixed in the revision 547760 does not fix Jira-2626 ... Rather it breaks the things again, as you have even removed the workaround I have put.. Now once again HotUpdate fails miserably on custom deployers .. This Jira is not about the *extension*... It is about *HotUpdate* failing on custom deployers.. You have also removed the workaround which I used to get the hotUpdate working :(.. Thanks, Thilina [1] http://svn.apache.org/viewvc?view=revrev=547760 HotUpdate fails on custom deployers --- Key: AXIS2-2626 URL: https://issues.apache.org/jira/browse/AXIS2-2626 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Thilina Gunarathne Assignee: Deepal Jayasinghe Priority: Blocker +public static final int TYPE_SERVICE = 0; +public static final int TYPE_MODULE = 1; + /** * To check whether the file is a module or a servise */ +private int type = TYPE_SERVICE; Above make the hot deploy logic to treat all the deployed services as .aar or equivalent (TYPE_SERVICE).. Hot update on custom deployers fails to undeploy service before deploying again, which gives rise to an Exception. -- 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-2626) HotUpdate fails on custom deployers
[
https://issues.apache.org/jira/browse/AXIS2-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506159
]
Thilina Gunarathne commented on AXIS2-2626:
---
Once again I added the above mentioned work around... Please make sure to fix
this properly before removing the workaround
Steps to regenerate...
*Comment the hack I've put...
1. Enable hotupdate in axis2.xml
2. Add a custom deployer
3. Deploy a service using the custom deployer...
4. Do some change to the service while it's running...
You will get the following exception..
ERROR [2007-06-19 15:41:11,521] The echo.js service, which is not valid,
caused Two services cannot have same name. A service with the echo name
already exists in the system.
org.apache.axis2.AxisFault: Two services cannot have same name. A service with
the echo name already exists in the system.
at
org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:274)
at
org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:442)
line 611-623 in the DeploymentEngine...
if (wsInfo.getType() == WSInfo.TYPE_SERVICE) {
if (isHotUpdate()) {
serviceDeployer.unDeploy(wsInfo.getFileName());
} else {
axisConfig.removeFaultyService(wsInfo.getFileName());
}
} else {
if (isHotUpdate()) {
Deployer deployer = wsInfo.getDeployer();
if (deployer != null) {
deployer.unDeploy(wsInfo.getFileName());
}
}
}
Currently all the services deployed using the custom deployers were assigned
the type as WSInfo.TYPE_SERVICE.. then Axis2 tries to undeploy that service
using the serviceDeployer, which is incorrect...
HotUpdate fails on custom deployers
---
Key: AXIS2-2626
URL: https://issues.apache.org/jira/browse/AXIS2-2626
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Thilina Gunarathne
Assignee: Deepal Jayasinghe
Priority: Blocker
+public static final int TYPE_SERVICE = 0;
+public static final int TYPE_MODULE = 1;
+
/**
* To check whether the file is a module or a servise
*/
+private int type = TYPE_SERVICE;
Above make the hot deploy logic to treat all the deployed services as .aar or
equivalent (TYPE_SERVICE).. Hot update on custom deployers fails to undeploy
service before deploying again, which gives rise to an Exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] WSDL generation.
Agreed. Can you please log a JIRA? and upload some sample that we can turn into a test case. thanks, dims On 6/19/07, Saminda Abeyruwan [EMAIL PROTECTED] wrote: Hi Devs, If a WSDL is not given for a service, and if the service's message receiver is not RPCMessageReceiver what would be the WSDL generation behavior. I'm using the current Axis2 trunk head, and I've using services with custom MR, and when I try to do ?wsdl I'm receiving the following exception, org.apache.axis2.dataretrieval.DataRetrievalException org.apache.axis2.dataretrieval.AxisDataLocatorImpl.getData(AxisDataLocatorImpl.java:81) org.apache.axis2.description.AxisService.getData(AxisService.java :2017) org.apache.axis2.description.AxisService.getWSDL(AxisService.java:995) org.apache.axis2.description.AxisService.printWSDL(AxisService.java:939) org.wso2.wsas.transport.util.Wsdl11Processor$1.printWSDL(Wsdl11Processor.java :40) org.wso2.wsas.transport.util.AbstractWsdlProcessor.printWSDL(AbstractWsdlProcessor.java:51) org.wso2.wsas.transport.util.Wsdl11Processor.process(Wsdl11Processor.java:48) IMHO if the default behavior is not to generate a suitable WSDL, above should show an error message rather an exception. Thank you -- Saminda Abeyruwan Software Engineer WSO2 Inc. - www.wso2.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2819) Faulty handling of JMS asynchronous calls
[ https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2819: Assignee: Asankha C. Perera Faulty handling of JMS asynchronous calls - Key: AXIS2-2819 URL: https://issues.apache.org/jira/browse/AXIS2-2819 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Addressing Affects Versions: 1.2 Environment: Windows XP / Active MQ 4.1.1 / Tomcat 5.5.17 Reporter: Mathieu Chauvin Assignee: Asankha C. Perera Priority: Blocker When a JMS client gets its response from the reply queue, addressing module fails with the following Exception: Exception in thread JMSWorker-1 java.lang.UnsupportedOperationException at java.util.AbstractList.add(AbstractList.java:151) at java.util.AbstractList.add(AbstractList.java:89) at org.apache.axis2.client.Options.addRelatesTo(Options.java:835) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractRelatesToInformation(AddressingInHandler.java:248) at org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:169) at org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:95) at org.apache.axis2.engine.Phase.invoke(Phase.java:383) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131) at org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:249) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) It seems that the wsa:RelatesTo header (that is, by the way, already set in the relationships field of the Options class...) is beeing inserted in a List that cannot be modified. The Exception is raised from within the JMS listener thread, and can therefore not be caught nor handled in another Thread, which is, actually, another problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2817) Create AttachmentDescription objects in the JAX-WS Metadata layer
[ https://issues.apache.org/jira/browse/AXIS2-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2817: Assignee: Nick Gallardo Create AttachmentDescription objects in the JAX-WS Metadata layer - Key: AXIS2-2817 URL: https://issues.apache.org/jira/browse/AXIS2-2817 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.3 Reporter: Dustin Amrhein Assignee: Nick Gallardo Fix For: 1.3 The JAX-WS metadata layer needs to create AttachmentDescription objects if the WSDL indicates that the input or output message contains attachments. This will be used later on by the marshalling code to determine the correct information to marshall/demarshall. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections
[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2816: Assignee: Asankha C. Perera JMS over WebsphereMQ doesn't support 'CLIENT' connections - Key: AXIS2-2816 URL: https://issues.apache.org/jira/browse/AXIS2-2816 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2 Environment: Tomcat 6, WindowsXP, WebsphereMQ 6.0 Reporter: Mark Badorrek Assignee: Asankha C. Perera Attachments: Axis2-websphereMQ-fix.zip Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API. This is insufficient for WebspherMQ CLIENT connections, where the administrator must nominate a particular userID and password per connectionfactory, resulting in the following call which is unsupported in the Axis2 JMS code: factory.createConnection(userID, password) The attached Axis2 JMS files contain the fix to allow the deployer to specify a nominated userID and password through the standard Axis2 JNDI lookup mechanism. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2814: Assignee: Amila Chinthaka Suriarachchi XSI:TYPE not being generated for SOAP JMS client requests - Key: AXIS2-2814 URL: https://issues.apache.org/jira/browse/AXIS2-2814 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Win XP, AXIS2 (1.2) Reporter: balaji iyer Assignee: Amila Chinthaka Suriarachchi Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip I'm trying to run the SOAP JMS webservice which is hosted in businessworks. I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding. However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP. The issues is that the xsi type is not being generated for JMS requests. Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2820) SimpleHTTP server can not handle multiple threads (more than 20)
SimpleHTTP server can not handle multiple threads (more than 20) Key: AXIS2-2820 URL: https://issues.apache.org/jira/browse/AXIS2-2820 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Deepal Jayasinghe Priority: Blocker When use two channel to invoke a service deploy in tomcat I ran into problem , what I did was I fire up 100 threads and invoke the service 100 times. Then the invocation become very slow , when I debug the code I realized that is due to limitation in SimpleHttp server. So how if we switch to jetty or embedded tomcat. To demonstrate the issue I will create and attach the test case. -- 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-2548) Handler test with fault causes exception
[ https://issues.apache.org/jira/browse/AXIS2-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506179 ] Nick Gallardo commented on AXIS2-2548: -- Glen, This problem surfaced because of some of the conversions that we were having to do between SAAJ and Axiom for the JAX-WS handler support. When a fault is stored in a SOAP Axiom structure, it is always represented as a SOAP 1.2 fault. So, if I walked that and tried to build a SOAP 1.1 fault, I'd be creating elements with the wrong QName. For now, the solution is to serialize the whole structure and then read it back in. That's horribly non-performant, but at least a step to get us going. Once I get the patch integrated, I'll build a small sample that shows what I'm talking about and we can see how to solve that at the Axiom level. Handler test with fault causes exception Key: AXIS2-2548 URL: https://issues.apache.org/jira/browse/AXIS2-2548 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Assignee: Nick Gallardo This is most likely an axiom problem, but opened against JAXWS until such determination is made. When I enable the AddNumbersHandlerTests.testAddNumbersWithFault, I get: javax.xml.ws.soap.SOAPFaultException: java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMSourcedElementImpl incompatible with org.apache.axiom.soap.SOAPFault at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1057) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:811) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedPlusMethodMarshaller.demarshalFaultResponse(DocLitWrappedPlusMethodMarshaller.java:725) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:394) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:369) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:291) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:141) at $Proxy19.addNumbersHandler(Unknown Source) at org.apache.axis2.jaxws.sample.AddNumbersHandlerTests.testAddNumbersHandlerWithFault(AddNumbersHandlerTests.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) I believe Nick has worked on this code before and can address it. If not, I'll take a look. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Cleanup of AxisConfigurators / API change alert (Re: Too many open file with Axis2 1.2)
Jerome, You are right! Team, I am reviewing the code and running the tests, i can see that org.apache.axis2.deployment.scheduler.Scheduler needs to cancel a timer. So this means that we have to add cleanup methods in various layers. Here's a diff that i got working with help from Glen and Deepal. Unfortunately it means adding a cleanup method in AxisConfigurator interface. I'll run some more tests before i checkin. thanks, dims On 6/19/07, Jerome Camilleri [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: Please don't call createConfigurationContextFromFileSystem multiple times. just call once when the daemon starts. thanks for this workaround...but don't you think that we should have a way to clean up the ressources used by the ConfigurationContext ? Regards Jérôme - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Cleanup of AxisConfigurators / API change alert (Re: Too many open file with Axis2 1.2)
oops! forgot the diff.
-- dims
On 6/19/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
Jerome,
You are right!
Team,
I am reviewing the code and running the tests, i can see that
org.apache.axis2.deployment.scheduler.Scheduler needs to cancel a
timer. So this means that we have to add cleanup methods in various
layers. Here's a diff that i got working with help from Glen and
Deepal. Unfortunately it means adding a cleanup method in
AxisConfigurator interface. I'll run some more tests before i checkin.
thanks,
dims
On 6/19/07, Jerome Camilleri [EMAIL PROTECTED] wrote:
Davanum Srinivas wrote:
Please don't call createConfigurationContextFromFileSystem multiple
times. just call once when the daemon starts.
thanks for this workaround...but don't you think that we should have a
way to clean up the ressources used by the ConfigurationContext ?
Regards
Jérôme
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas :: http://davanum.wordpress.com
--
Davanum Srinivas :: http://davanum.wordpress.com
Index: src/org/apache/axis2/deployment/WarBasedAxisConfigurator.java
===
--- src/org/apache/axis2/deployment/WarBasedAxisConfigurator.java (revision 548719)
+++ src/org/apache/axis2/deployment/WarBasedAxisConfigurator.java (working copy)
@@ -144,6 +144,9 @@
}
axisConfig = populateAxisConfiguration(axis2Stream);
+if(axis2Stream != null){
+axis2Stream.close();
+}
Parameter param = new Parameter();
param.setName(Constants.Configuration.ARTIFACTS_TEMP_DIR);
param.setValue(config.getServletContext().getAttribute(javax.servlet.context.tempdir));
@@ -233,6 +236,7 @@
log.error(ex + : loading repository from classpath);
loadFromClassPath();
}
+axisConfig.setConfigurator(this);
return axisConfig;
}
Index: src/org/apache/axis2/deployment/DeploymentEngine.java
===
--- src/org/apache/axis2/deployment/DeploymentEngine.java (revision 548719)
+++ src/org/apache/axis2/deployment/DeploymentEngine.java (working copy)
@@ -53,6 +53,7 @@
//to keep the web resource location if any
protected static String webLocationString = null;
+protected Scheduler scheduler;
public static void setWebLocationString(String webLocationString) {
DeploymentEngine.webLocationString = webLocationString;
@@ -598,7 +599,7 @@
* @param listener : RepositoryListener
*/
protected void startSearch(RepositoryListener listener) {
-Scheduler scheduler = new Scheduler();
+scheduler = new Scheduler();
scheduler.schedule(new SchedulerTask(listener), new DeploymentIterator());
}
@@ -1071,4 +1072,13 @@
public Deployer getDeployerForExtension(String extension) {
return (Deployer)extensionToDeployerMappingMap.get(extension);
}
+
+/**
+ * Clean up the mess
+ */
+public void cleanup() {
+if(scheduler != null){
+scheduler.cleanup();
+}
+}
}
Index: src/org/apache/axis2/deployment/FileSystemConfigurator.java
===
--- src/org/apache/axis2/deployment/FileSystemConfigurator.java (revision 548719)
+++ src/org/apache/axis2/deployment/FileSystemConfigurator.java (working copy)
@@ -13,6 +13,7 @@
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.InputStream;
+import java.io.IOException;
/*
* Copyright 2004,2005 The Apache Software Foundation.
@@ -103,7 +104,7 @@
* @throws AxisFault
*/
public synchronized AxisConfiguration getAxisConfiguration() throws AxisFault {
-InputStream configStream;
+InputStream configStream = null;
try {
if (axis2xml != null !.equals(axis2xml)) {
configStream = new FileInputStream(axis2xml);
@@ -114,6 +115,14 @@
axisConfig = populateAxisConfiguration(configStream);
} catch (FileNotFoundException e) {
throw new AxisFault(System can not find the given axis2.xml + axis2xml);
+} finally {
+if(configStream != null) {
+try {
+configStream.close();
+} catch (IOException e) {
+throw AxisFault.makeFault(e);
+}
+}
}
Parameter axis2repoPara = axisConfig.getParameter(DeploymentConstants.AXIS2_REPO);
if (axis2repoPara != null) {
@@ -124,6 +133,7 @@
} else {
loadFromClassPath();
}
+axisConfig.setConfigurator(this);
return axisConfig;
}
Index:
[Axis2][continuum] BUILD FAILURE
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2401 Build statistics: State: Failed Previous State: Ok Started at: Tue, 19 Jun 2007 15:07:14 + Finished at: Tue, 19 Jun 2007 15:57:14 + Total time: 50m 0s Build Trigger: Forced Exit code: 70 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes dims Fix typo /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisServer.java dims - Actually use the AxisServer somewhere relevent :) - No, i would not want to start as a side effect of a deployService - Make configContext protected so that folks can easily extend the class - Add a createDefaultConfigurationContext for easy extensibility as well - Don't use short cuts in method names. - getConfigurationContext creates one using createDefaultConfigurationContext if configContext is null. /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisServer.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/SimpleAxis2Server.java dims add a parameter in the constructor for the user to take a decision on whether deploying a service should start the server /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisServer.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/SimpleAxis2Server.java ajith 1. Adding the XML declaration support for the serialized schemas (AXIS2-2685). This depends on a newer change in the XMLSchema! /webservices/axis2/trunk/java/modules/codegen/src/org/apache/axis2/wsdl/codegen/writer/SchemaWriter.java dims back out all my changes as per -1 from deepal (http://marc.info/?l=axis-cvsm=118196353513373w=2) /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisServer.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/SimpleAxis2Server.java deepal Make the AxisServer more useful considering everyone's suggestions. /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisServer.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/SimpleAxis2Server.java gdaniels * First part of fix for https://issues.apache.org/jira/browse/AXIS2-2642 (still need to add getEngagedModules to AxisDescription) * Throw the real error in RPCInOnlyMessageReceiver * A little prep work for better fault handling flow in AxisEngine (still on the drawing board) * General cleanups, JavaDoc improvements /webservices/axis2/trunk/java/modules/adb/src/org/apache/axis2/rpc/receivers/RPCInOnlyMessageReceiver.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/Constants.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/addressing/AddressingHelper.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/context/MessageContext.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/context/OperationContext.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/AxisConfigBuilder.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/DeploymentEngine.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/DescriptionBuilder.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/AxisDescription.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/description/java2wsdl/DefaultSchemaGenerator.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisConfiguration.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisEngine.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/ListenerManager.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/http/CommonsHTTPTransportSender.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/http/HTTPWorker.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/http/server/AxisHttpService.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/util/MessageContextBuilder.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/util/Utils.java deepal fixing engage module for AxisMessage issue. -
[Axis2] Build failed.
Hi guys, My build is failing in the kernel. Any clues Thanks Chathura Testsuite: org.apache.axis2.deployment.AxisMessageTest Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.719 sec - Standard Error - Jun 19, 2007 11:53:46 AM org.apache.axis2.deployment.ModuleDeployer deploy INFO: Deploying module: module1 Jun 19, 2007 11:53:47 AM org.apache.axis2.deployment.ServiceDeployer deploy INFO: The MessagetestService service, which is not valid, caused java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:1036) at java.util.HashMap$ValueIterator.next(HashMap.java:1067) at org.apache.axis2.deployment.DeploymentEngine.fillServiceGroup(DeploymentEngine.java:499) at org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:442) at org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:83) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:146) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:540) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:133) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:300) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:210) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:113) at org.apache.axis2.deployment.FileSystemConfigurator.loadServices(FileSystemConfigurator.java:146) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:74) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:173) at org.apache.axis2.deployment.AxisMessageTest.testAxisMessage(AxisMessageTest.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:536) Jun 19, 2007 11:53:47 AM org.apache.axis2.deployment.DeploymentEngine doDeploy INFO: org.apache.axis2.deployment.DeploymentException - --- Testcase: testAxisMessage(org.apache.axis2.deployment.AxisMessageTest): FAILED null junit.framework.AssertionFailedError at org.apache.axis2.deployment.AxisMessageTest.testAxisMessage(AxisMessageTest.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) -- Chathura Herath http://people.apache.org/~chathura/ http://chathurah.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2821) when localname is null try set it to the tagname/nodename in the toSAAJNode method
when localname is null try set it to the tagname/nodename in the toSAAJNode method -- Key: AXIS2-2821 URL: https://issues.apache.org/jira/browse/AXIS2-2821 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: nightly Environment: win XP + Sun 1.5 SDK Reporter: Lin Sun Fix For: nightly I have seen ElementImpl that doesn't have a localname but has a tagname in my test, when the tagname doesn't contain a : inside. same issue with attrNode. The fix is to try to set it to tagname/nodename when it is null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2821) when localname is null try set it to the tagname/nodename in the toSAAJNode method
[ https://issues.apache.org/jira/browse/AXIS2-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun updated AXIS2-2821: --- Attachment: AXIS2-2821.patch Tested in geronimo env. when localname is null try set it to the tagname/nodename in the toSAAJNode method -- Key: AXIS2-2821 URL: https://issues.apache.org/jira/browse/AXIS2-2821 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: nightly Environment: win XP + Sun 1.5 SDK Reporter: Lin Sun Fix For: nightly Attachments: AXIS2-2821.patch I have seen ElementImpl that doesn't have a localname but has a tagname in my test, when the tagname doesn't contain a : inside. same issue with attrNode. The fix is to try to set it to tagname/nodename when it is null. -- 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-2702) Codegen issues for operation with multiple faults of same type
[ https://issues.apache.org/jira/browse/AXIS2-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506249 ] Peter Danielsen commented on AXIS2-2702: Amila, Running the committed version on http-faults.wsdl produces a Stub whose populateFaults method has three sets of Map put calls with the same key and different values. Each set is overwriting the results of the previous one, so only the last set matters -- won't every fault that occurs will look like a ServiceTemporarilyUnavailable? An application using the Stub will only ever see that fault even though the others may be occurring, too. I think this is because the AxisFault handling is looking only at the type of the data contained in the fault. I took a closer look at the generated MessageReceiver and found the problem there also. It's invokeBusinessLogic method has a catch for each fault, which is expected, but in each case it's setting the msgContext's FAULT_NAME property to the same value, which is the fault's type, rather than it's name. At run time, AxisServlet uses the FAULT_NAME to look up the fault in AxisBindingOperation and get the HTTP status code. If it does find one with that name, I think we'll still have lost the original fault identity. It looks like the cause of the MessageReceiver problem is AxisServiceBasedMultiLanguageEmitter's getUniqueListofFaultsofMep(Document, String) method in its setting of the variable exceptionName. If it's set to key, the problem goes away. Peter Codegen issues for operation with multiple faults of same type -- Key: AXIS2-2702 URL: https://issues.apache.org/jira/browse/AXIS2-2702 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Peter Danielsen Assignee: Keith Godwin Chapman Priority: Blocker Attachments: AxisServiceBasedMultiLanguageEmitter.2.patch.txt, AxisServiceBasedMultiLanguageEmitter.patch.txt, http-faults.wsdl I ran into several issues when examining the output of Axis2 codegen on the attached WSDL2 file. The WSDL uses the HTTP binding for one interface with one operation containing three faults. All faults have the same type. The issues are: 1. In the Skeleton, the operation's method has a throws list that includes the same exception three times. 2. In the Stub, a. the fromOM method has three identical if statements, b. the populateFaults method has three identical additions to the HashMaps. c. the class contains SOAP-related code even though the WSDL is using the HTTP binding. 3. In the CallbackHandler, a. there is a single receiveError(Exception e) method even though there are three different faults. It's unclear how sub-classes will be able to distinguish the three faults. b. It seems like it would be more flexible for the CallbackHandler to be an interface, rather than an abstract class. The decision to include a clientData member seems like it should be up to the application. Most of the issues stem from AxisServiceBasedMultiLanguageEmitter's use of the fullyQualifiedClassMap. It's currently mapping the fault's element attribute to a Java class name. When multiple faults have the same element value, they all end up with the same class name resulting in the duplication identified above. I'm attaching a patch that fixes issues 1, 2a, and 2b by 1. changing the purpose of fullyQualifiedClassMap to be a mapping from fault name to a Java class name. 2. adding a separate faultToTypeMap that maps fault name to element type name. 3. updating methods within the class to use these to generate code that preserves the individual faults. -- 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-2821) when localname is null try set it to the tagname/nodename in the toSAAJNode method
[ https://issues.apache.org/jira/browse/AXIS2-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sumedha rubasinghe reassigned AXIS2-2821: - Assignee: sumedha rubasinghe when localname is null try set it to the tagname/nodename in the toSAAJNode method -- Key: AXIS2-2821 URL: https://issues.apache.org/jira/browse/AXIS2-2821 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: nightly Environment: win XP + Sun 1.5 SDK Reporter: Lin Sun Assignee: sumedha rubasinghe Fix For: nightly Attachments: AXIS2-2821.patch I have seen ElementImpl that doesn't have a localname but has a tagname in my test, when the tagname doesn't contain a : inside. same issue with attrNode. The fix is to try to set it to tagname/nodename when it is null. -- 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-2821) when localname is null try set it to the tagname/nodename in the toSAAJNode method
[ https://issues.apache.org/jira/browse/AXIS2-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sumedha rubasinghe resolved AXIS2-2821. --- Resolution: Fixed Applied the patch to revision 548806. Thanks. sumedha when localname is null try set it to the tagname/nodename in the toSAAJNode method -- Key: AXIS2-2821 URL: https://issues.apache.org/jira/browse/AXIS2-2821 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: nightly Environment: win XP + Sun 1.5 SDK Reporter: Lin Sun Assignee: sumedha rubasinghe Fix For: nightly Attachments: AXIS2-2821.patch I have seen ElementImpl that doesn't have a localname but has a tagname in my test, when the tagname doesn't contain a : inside. same issue with attrNode. The fix is to try to set it to tagname/nodename when it is null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [axis2] SOAP 1.1 default?
Really? You want to default to SOAP 1.2? Really? Did you actually flip this switch? I thought you were going to work on stabilizing Axis2 for the 1.3 release. This is going to rock the boat in a serious way. Tom Jordahl -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 12:36 PM To: axis-dev@ws.apache.org Subject: Re: [axis2] SOAP 1.1 default? Definitely +1! Can't remember why we default to 1.1 .. Sanjiva. Glen Daniels wrote: Forgive me if this has been covered recently, but why are we defaulting to SOAP 1.1 everywhere? Shouldn't our default be SOAP 1.2? --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] SOAP 1.1 default?
Defaulting to SOAP 1.2 will have more negative effects than positive, in my opinion -:) have in mind that SOAP 1.2 interop with other WS frameworks is very volatile at the moment (i.e. DotNET, and JAX-WS, more specifically - the wsimport tool) - that's what our experiences with soap 1.2 interop testing have shown. In addition to that some Axis2 modules such as Rampart are always using / converting to SOAP 1.1 no matter which soap version is chosen by the client. Thanks. Regards, Angel On 6/19/07, Tom Jordahl [EMAIL PROTECTED] wrote: Really? You want to default to SOAP 1.2? Really? Did you actually flip this switch? I thought you were going to work on stabilizing Axis2 for the 1.3 release. This is going to rock the boat in a serious way. Tom Jordahl -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 12:36 PM To: axis-dev@ws.apache.org Subject: Re: [axis2] SOAP 1.1 default? Definitely +1! Can't remember why we default to 1.1 .. Sanjiva. Glen Daniels wrote: Forgive me if this has been covered recently, but why are we defaulting to SOAP 1.1 everywhere? Shouldn't our default be SOAP 1.2? --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][continuum] BUILD SUCCESSFUL
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2411 Build statistics: State: Ok Previous State: Failed Started at: Tue, 19 Jun 2007 17:06:41 + Finished at: Tue, 19 Jun 2007 17:51:59 + Total time: 45m 18s Build Trigger: Schedule Exit code: 0 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes dims Fix for OutOfMemory and cleanup of files etc. Please see http://marc.info/?t=118217698900011r=1w=2 for more information /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/context/ConfigurationContext.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/DeploymentEngine.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/FileSystemConfigurator.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/URLBasedAxisConfigurator.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/WarBasedAxisConfigurator.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/scheduler/Scheduler.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisConfiguration.java /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/engine/AxisConfigurator.java davidillsley Replacing out of date scm info. We really need to get down to one build system. /webservices/axis2/trunk/java/pom.xml Output: Snipped Output: lasses Running post goal: java:prepare-filesystem java:compile: [copy] Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF [echo] Compiling to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes [javac] Compiling 2 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes java:jar-resources: Copying 2 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF test:test: java:prepare-filesystem: Running post goal: java:prepare-filesystem java:compile: [echo] Compiling to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes java:jar-resources: test:prepare-filesystem: [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-reports test:test-resources: Copying 1 file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes test:compile: [javac] Compiling 1 source file to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes [junit] Running org.apache.axis2.policy.model.MTOMAssertionTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.697 sec jar:jar: [jar] Building jar: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/axis2-mtompolicy-SNAPSHOT.jar jar:install: [echo] Installing... Uploading to org.apache.axis2/jars/axis2-mtompolicy-SNAPSHOT.jar: (8K) Uploading to org.apache.axis2/poms/axis2-mtompolicy-SNAPSHOT.pom: (13K) + | Executing multiproject:install-callback Apache Axis 2.0 - ping | Memory: 21M/50M + DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml DEPRECATED: the default goal should be specified in the build section of project.xml instead of maven.xml build:end: build:start: multiproject:install-callback: [echo] Running jar:install for Apache Axis 2.0 - ping java:prepare-filesystem: [mkdir] Created dir: /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes Running post goal: java:prepare-filesystem java:compile: [echo] Compiling to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes [javac] Compiling 3 source files to
RE: [axis2] WSDL2Java / Java2WSDL and Faults (PLEASE CHIME IN?)
I have read the complete thread and I know I am chiming in a little
late.
One common exception type generated for each Schema element is clearly
the optimal mapping for Java.
If I declare method1 and method2 to throw the same exception in the
server side, I expect WSDL2Java (or whatever wrong name you guys picked
:-) to generate a single Exception on the client side for this service.
The exceptions should be named after the element types. Axis 1.x did it
this way, and Axis2 should too.
Tom Jordahl
Adobe Server Development
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]
Sent: Monday, June 11, 2007 5:54 PM
To: Axis-Dev
Subject: [axis2] WSDL2Java / Java2WSDL and Faults (PLEASE CHIME IN?)
Hi folks!
We're here at the hackathon, and these two issues came up:
https://issues.apache.org/jira/browse/AXIS2-2778
https://issues.apache.org/jira/browse/AXIS2-2792
They both revolve around how to map faults to/from WSDL, and we'd like
some input. Consider starting with the following class:
package ns;
class Service {
void method1(void) throws CustomException {};
void method2(void) throws CustomException {};
}
You'll end up with a WSDL that looks like (paraphrased):
schema targetNamespace=http://ns;
element name=CustomException
...
/element
/schema
...
message name={MSG}
element name=ns:CustomException/
/message
...
operation name=method1
input/
output
fault message={MSG}/
/operation
operation name=method2
input/
output
fault message={MSG}/
/operation
I've left MSG as a variable because that's the real question here. In
particular, should MSG be based on a) just the Exception type (i.e.
CustomException), or b) the method (i.e. method1Fault). If we go
with (a), then we would generate only ONE message for both of the above
operations' faults and share it. If we go with (b) we would generate
TWO separate messages in the WSDL, both referring to the same element.
Now the second part revolves around how to behave when running WSDL2Java
from WSDL. Should we generate:
1)
class {MSG} extends RemoteException {
}
(i.e. use the message name regardless, meaning we'd generate multiple
exception types for multiple messages sharing an element)
or
2)
class CustomException extends RemoteException {
}
(i.e. use the element type regardless of message name)
Currently, for Java2WSDL we use approach (b), generating message names
based on the method name. For WSDL2Java we use approach (1), generating
fault types based on the message name. If multiple messages share the
same element, we'll all have them use the same fault class (based on the
message name, not the element name).
The current approach is somewhat inconsistent and confusing. We should
EITHER have WSDL2Java generate one fault per message (if the faults are
named after message names), letting the Java classes be different even
though the elements are the same, OR have it dig in to the element and
name the faults after the element types, and sharing the fault type
among any operation that uses that element in a fault message.
Thoughts and comments appreciated.
Thanks,
--Glen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] SOAP 1.1 default?
Angel, always using / converting to SOAP 1.1 no matter which soap version is chosen by the client == is a Very serious bug!!! please log a JIRA and any help to recreate the issue would be wonderful. thanks, dims On 6/19/07, Angel Todorov [EMAIL PROTECTED] wrote: Defaulting to SOAP 1.2 will have more negative effects than positive, in my opinion -:) have in mind that SOAP 1.2 interop with other WS frameworks is very volatile at the moment (i.e. DotNET, and JAX-WS, more specifically - the wsimport tool) - that's what our experiences with soap 1.2 interop testing have shown. In addition to that some Axis2 modules such as Rampart are always using / converting to SOAP 1.1 no matter which soap version is chosen by the client. Thanks. Regards, Angel On 6/19/07, Tom Jordahl [EMAIL PROTECTED] wrote: Really? You want to default to SOAP 1.2? Really? Did you actually flip this switch? I thought you were going to work on stabilizing Axis2 for the 1.3 release. This is going to rock the boat in a serious way. Tom Jordahl -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 12:36 PM To: axis-dev@ws.apache.org Subject: Re: [axis2] SOAP 1.1 default? Definitely +1! Can't remember why we default to 1.1 .. Sanjiva. Glen Daniels wrote: Forgive me if this has been covered recently, but why are we defaulting to SOAP 1.1 everywhere? Shouldn't our default be SOAP 1.2? --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] SOAP 1.1 default?
Hi Dims, I already talked to Ruchith, the problem seems to be the DOM - LLOM conversion. In fact its fixing may turn out to be very easy, but i haven't taken a look yet. I will file a jira. Regards, Angel On 6/19/07, Davanum Srinivas [EMAIL PROTECTED] wrote: Angel, always using / converting to SOAP 1.1 no matter which soap version is chosen by the client == is a Very serious bug!!! please log a JIRA and any help to recreate the issue would be wonderful. thanks, dims On 6/19/07, Angel Todorov [EMAIL PROTECTED] wrote: Defaulting to SOAP 1.2 will have more negative effects than positive, in my opinion -:) have in mind that SOAP 1.2 interop with other WS frameworks is very volatile at the moment (i.e. DotNET, and JAX-WS, more specifically - the wsimport tool) - that's what our experiences with soap 1.2 interop testing have shown. In addition to that some Axis2 modules such as Rampart are always using / converting to SOAP 1.1 no matter which soap version is chosen by the client. Thanks. Regards, Angel On 6/19/07, Tom Jordahl [EMAIL PROTECTED] wrote: Really? You want to default to SOAP 1.2? Really? Did you actually flip this switch? I thought you were going to work on stabilizing Axis2 for the 1.3 release. This is going to rock the boat in a serious way. Tom Jordahl -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 12:36 PM To: axis-dev@ws.apache.org Subject: Re: [axis2] SOAP 1.1 default? Definitely +1! Can't remember why we default to 1.1 .. Sanjiva. Glen Daniels wrote: Forgive me if this has been covered recently, but why are we defaulting to SOAP 1.1 everywhere? Shouldn't our default be SOAP 1.2? --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] SOAP 1.1 default?
Also, JAX-WS requires a SOAP 1.1 default so there will be additional work there that will need to be addressed. I'm for keeping the SOAP 1.1 default for now. There still isn't a WS-I profile that includes SOAP 1.2 either, is there? I thought that was coming in BP 2.0. Regards, -Nick Angel Todorov [EMAIL PROTECTED] com To axis-dev@ws.apache.org 06/19/2007 12:50 cc PM Subject Re: [axis2] SOAP 1.1 default? Please respond to [EMAIL PROTECTED] e.org Defaulting to SOAP 1.2 will have more negative effects than positive, in my opinion -:) have in mind that SOAP 1.2 interop with other WS frameworks is very volatile at the moment (i.e. DotNET, and JAX-WS, more specifically - the wsimport tool) - that's what our experiences with soap 1.2 interop testing have shown. In addition to that some Axis2 modules such as Rampart are always using / converting to SOAP 1.1 no matter which soap version is chosen by the client. Thanks. Regards, Angel On 6/19/07, Tom Jordahl [EMAIL PROTECTED] wrote: Really? You want to default to SOAP 1.2? Really? Did you actually flip this switch? I thought you were going to work on stabilizing Axis2 for the 1.3 release. This is going to rock the boat in a serious way. Tom Jordahl -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 12:36 PM To: [EMAIL PROTECTED] Subject: Re: [axis2] SOAP 1.1 default? Definitely +1! Can't remember why we default to 1.1 .. Sanjiva. Glen Daniels wrote: Forgive me if this has been covered recently, but why are we defaulting to SOAP 1.1 everywhere? Shouldn't our default be SOAP 1.2? --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] inline: graycol.gifinline: pic21325.gifinline: ecblank.gif
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506293 ] Amila Chinthaka Suriarachchi commented on AXIS2-2814: - I fixed an issue with the ADBXMLStreamReaderImpl which must have caused your problme. Can you please check with a nightly build? XSI:TYPE not being generated for SOAP JMS client requests - Key: AXIS2-2814 URL: https://issues.apache.org/jira/browse/AXIS2-2814 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Win XP, AXIS2 (1.2) Reporter: balaji iyer Assignee: Amila Chinthaka Suriarachchi Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip I'm trying to run the SOAP JMS webservice which is hosted in businessworks. I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding. However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP. The issues is that the xsi type is not being generated for JMS requests. Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks. -- 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-2714) Unnecessary recording of directionality in MessageContext executed phases, general improvements to same
[ https://issues.apache.org/jira/browse/AXIS2-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glen Daniels resolved AXIS2-2714. - Resolution: Fixed Fixed for now, any further changes will be improvements, so resolving this issue. Unnecessary recording of directionality in MessageContext executed phases, general improvements to same - Key: AXIS2-2714 URL: https://issues.apache.org/jira/browse/AXIS2-2714 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Glen Daniels Assignee: Glen Daniels Priority: Blocker When we added the flowComplete() stuff, I think we might have gotten a little unnecessarily specific about direction in MessageContext and AxisEngine. In particular - a MessageContext will only ever have a single direction, and right now we have two separate LinkedLists for executed phases (sic - it's really Handlers, even though they're usually Phases at the top level). This bubbles through a lot of the code in AxisEngine too, and it doesn't seem to be necessary. I'd like to consider the following two-stage fix for this. 1) Remove all the directionality, and simply have MessageContext.addExecutedHandler()/resetExecutedHandlers()/getExecutedHandlers(). This removes a bunch of code from MC (simplify simplify) and cleans up AxisEngine nicely. 2) If AXIS2-2703 is fixed (and therefore a single ExecutionChain will accurately reflect the entire list of executed handlers), we won't even need a separate executedHandlers structure at all, and flowComplete() will then be able to just work backwards from currentHandlerIndex to 0. At that point I think we could remove it entirely. -- 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-2626) HotUpdate fails on custom deployers
[ https://issues.apache.org/jira/browse/AXIS2-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2626. -- Resolution: Fixed Revision: 548855 http://svn.apache.org/viewvc?view=revrev=548855 HotUpdate fails on custom deployers --- Key: AXIS2-2626 URL: https://issues.apache.org/jira/browse/AXIS2-2626 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Thilina Gunarathne Assignee: Deepal Jayasinghe Priority: Critical +public static final int TYPE_SERVICE = 0; +public static final int TYPE_MODULE = 1; + /** * To check whether the file is a module or a servise */ +private int type = TYPE_SERVICE; Above make the hot deploy logic to treat all the deployed services as .aar or equivalent (TYPE_SERVICE).. Hot update on custom deployers fails to undeploy service before deploying again, which gives rise to an Exception. -- 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-1510) Included schema filenames impact wsdl2java with xmlbeans binding
[ https://issues.apache.org/jira/browse/AXIS2-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-1510. - Resolution: Fixed I tested the both wsdl files and they work with the name unsubscribe.xsd xs:include schemaLocation=subscribe.xsd/ xs:include schemaLocation=unsubscribe.xsd/ Included schema filenames impact wsdl2java with xmlbeans binding Key: AXIS2-1510 URL: https://issues.apache.org/jira/browse/AXIS2-1510 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Mariusz Woloncewicz Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Attachments: subscribe.xsd, TestServices.wsdl, TestServicesFAIL.wsdl, unsubscribe.xsd Types declaration in wsdl: xs:include schemaLocation=subscribe.xsd/ xs:include schemaLocation=unsubscribe.xsd/ xs:element name=subscribe type=tns:SubscribeType/ xs:element name=unsubscribe type=tns:UnsubscribeType/ Output generated by wsdl2java.bat -uri TestServices.wsdl -d xmlbeans : Retrieving schema at 'subscribe.xsd', relative to 'file:/C:/JIRA/'. Retrieving schema at 'unsubscribe.xsd', relative to 'file:/C:/JIRA/'. 2006-10-26 10:35:52 org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityR esolver resolveEntity INFO: Resolving schema with publicId [null] and systemId [subscribe.xsd] 2006-10-26 10:35:52 org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityR esolver resolveEntity INFO: Resolving schema with publicId [null] and systemId [unsubscribe.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetExcepti on at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB eansExtension.java:92) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:177) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB eansExtension.java:82) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: src-resolve: type '[EMAIL PROTECTED]/request/beans' not found. at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe nerationUtility.java:241) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: src-resolve: type 'Subscribe [EMAIL PROTECTED]/request/beans' not found. at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(Sche maTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe nerationUtility.java:167) ... 8 more Current workaround is renaming unsubscribe.xsd file (for instance, to unsubscription.xsd). -- 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-1461) WSDL2Java should also generate dual channel client codes
[ https://issues.apache.org/jira/browse/AXIS2-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-1461. - Resolution: Fixed add a seperate costructor to set isUseSeperateListner WSDL2Java should also generate dual channel client codes Key: AXIS2-1461 URL: https://issues.apache.org/jira/browse/AXIS2-1461 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: Tools Affects Versions: 1.0 Environment: Windows XP, JRE1.5.0_08 Reporter: falom Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Currently WSDL2Java can generate client stubs for both sync and osync calls, but they are only for single connection communication. Since Axis2 supports also dual channel communication, the tool should also generate java codes for those, as BlockingDualClient stub and NonBlockingDualClient stub. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2822) Unable to implement methods generated with WSDL2Java: org.apache.axis2.databinding.ADBException: Unexpected subelement PromoteEmailToActivity
Unable to implement methods generated with WSDL2Java: org.apache.axis2.databinding.ADBException: Unexpected subelement PromoteEmailToActivity - Key: AXIS2-2822 URL: https://issues.apache.org/jira/browse/AXIS2-2822 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: nightly Environment: Windows XP Pro, Java SE/JDK 6.0 u1, AXIS 2 nightly snapshot, Ant 1.7 Reporter: Henrik Mohr Priority: Blocker Attachments: Services.aar I'm not able to implement method in skeleton-class made from WSDL. Step1: type the following command line: WSDL2Java -uri file:///E:/tmp/WebService.wsdl -p org.tempuri.webservice -d adb -s -wv 1.2 -ss -sd Step 2: Implement method SetCrmServicesURL to return new SetCrmServicesURLResponse() - this works. Implement method PromoteEmailToActivity to return new PromoteEmailToActivityResponse(); - this doesn't work Step 3: build .aar file Step 4: deploy Step 5: test methods. As mentioned earlier, method PromoteEmailToActivity doesn't work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2822) Unable to implement methods generated with WSDL2Java: org.apache.axis2.databinding.ADBException: Unexpected subelement PromoteEmailToActivity
[ https://issues.apache.org/jira/browse/AXIS2-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik Mohr updated AXIS2-2822: --- Description: I'm not able to implement method in skeleton-class made from WSDL. Step1: type the following command line: WSDL2Java -uri file:///E:/tmp/WebService.wsdl -p org.tempuri.webservice -d adb -s -wv 1.2 -ss -sd Step 2: Implement method SetCrmServicesURL to return new SetCrmServicesURLResponse() - this works. Implement method PromoteEmailToActivity to return new PromoteEmailToActivityResponse(); - this doesn't work Step 3: build .aar file Step 4: deploy Step 5: test methods. As mentioned earlier, method PromoteEmailToActivity doesn't work. By the way; I started trying with release version 1.2, givin the same error. was: I'm not able to implement method in skeleton-class made from WSDL. Step1: type the following command line: WSDL2Java -uri file:///E:/tmp/WebService.wsdl -p org.tempuri.webservice -d adb -s -wv 1.2 -ss -sd Step 2: Implement method SetCrmServicesURL to return new SetCrmServicesURLResponse() - this works. Implement method PromoteEmailToActivity to return new PromoteEmailToActivityResponse(); - this doesn't work Step 3: build .aar file Step 4: deploy Step 5: test methods. As mentioned earlier, method PromoteEmailToActivity doesn't work. Unable to implement methods generated with WSDL2Java: org.apache.axis2.databinding.ADBException: Unexpected subelement PromoteEmailToActivity - Key: AXIS2-2822 URL: https://issues.apache.org/jira/browse/AXIS2-2822 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: nightly Environment: Windows XP Pro, Java SE/JDK 6.0 u1, AXIS 2 nightly snapshot, Ant 1.7 Reporter: Henrik Mohr Priority: Blocker Attachments: Services.aar, soap-response.xml, WebService.wsdl I'm not able to implement method in skeleton-class made from WSDL. Step1: type the following command line: WSDL2Java -uri file:///E:/tmp/WebService.wsdl -p org.tempuri.webservice -d adb -s -wv 1.2 -ss -sd Step 2: Implement method SetCrmServicesURL to return new SetCrmServicesURLResponse() - this works. Implement method PromoteEmailToActivity to return new PromoteEmailToActivityResponse(); - this doesn't work Step 3: build .aar file Step 4: deploy Step 5: test methods. As mentioned earlier, method PromoteEmailToActivity doesn't work. By the way; I started trying with release version 1.2, givin the same error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2822) Unable to implement methods generated with WSDL2Java: org.apache.axis2.databinding.ADBException: Unexpected subelement PromoteEmailToActivity
[ https://issues.apache.org/jira/browse/AXIS2-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik Mohr updated AXIS2-2822: --- Description: I'm not able to implement method in skeleton-class made from WSDL. Step1: type the following command line: WSDL2Java -uri file:///E:/tmp/WebService.wsdl -p org.tempuri.webservice -d adb -s -wv 1.2 -ss -sd Step 2: Implement method SetCrmServicesURL to return new SetCrmServicesURLResponse() - this works. Implement method PromoteEmailToActivity to return new PromoteEmailToActivityResponse(); - this doesn't work Step 3: build .aar file Step 4: deploy Step 5: test methods. As mentioned earlier, method PromoteEmailToActivity doesn't work. By the way; I started trying with release version 1.2, raising the same error. was: I'm not able to implement method in skeleton-class made from WSDL. Step1: type the following command line: WSDL2Java -uri file:///E:/tmp/WebService.wsdl -p org.tempuri.webservice -d adb -s -wv 1.2 -ss -sd Step 2: Implement method SetCrmServicesURL to return new SetCrmServicesURLResponse() - this works. Implement method PromoteEmailToActivity to return new PromoteEmailToActivityResponse(); - this doesn't work Step 3: build .aar file Step 4: deploy Step 5: test methods. As mentioned earlier, method PromoteEmailToActivity doesn't work. By the way; I started trying with release version 1.2, givin the same error. Unable to implement methods generated with WSDL2Java: org.apache.axis2.databinding.ADBException: Unexpected subelement PromoteEmailToActivity - Key: AXIS2-2822 URL: https://issues.apache.org/jira/browse/AXIS2-2822 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: adb Affects Versions: nightly Environment: Windows XP Pro, Java SE/JDK 6.0 u1, AXIS 2 nightly snapshot, Ant 1.7 Reporter: Henrik Mohr Priority: Blocker Attachments: Services.aar, soap-response.xml, WebService.wsdl I'm not able to implement method in skeleton-class made from WSDL. Step1: type the following command line: WSDL2Java -uri file:///E:/tmp/WebService.wsdl -p org.tempuri.webservice -d adb -s -wv 1.2 -ss -sd Step 2: Implement method SetCrmServicesURL to return new SetCrmServicesURLResponse() - this works. Implement method PromoteEmailToActivity to return new PromoteEmailToActivityResponse(); - this doesn't work Step 3: build .aar file Step 4: deploy Step 5: test methods. As mentioned earlier, method PromoteEmailToActivity doesn't work. By the way; I started trying with release version 1.2, raising the same error. -- 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-2812) [Performance] set enableMTOM flag in autogenerated services.xml
[ https://issues.apache.org/jira/browse/AXIS2-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506328 ] Amila Chinthaka Suriarachchi commented on AXIS2-2812: - we can do this for adb but other can't. so shall we give a new option to the user to enable mtom or not. and set the default value as false. [Performance] set enableMTOM flag in autogenerated services.xml --- Key: AXIS2-2812 URL: https://issues.apache.org/jira/browse/AXIS2-2812 Project: Axis 2.0 (Axis2) Issue Type: Improvement Reporter: Davanum Srinivas Assignee: Amila Chinthaka Suriarachchi Please see AXIS2-2743 for additional info. If someone has a axis2.xml where enableMTOM is set to true, then all the services take a performance hit whether they use mtom or not since the soap response is written to a string first and then to the actual stream. So if we look at the wsdl/xsd and find that there is no base64 types, we should set enableMTOM to false explictly. This takes precedence over the setting in the repository's setting. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][continuum] BUILD FAILURE
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2420 Build statistics: State: Failed Previous State: Ok Started at: Tue, 19 Jun 2007 23:06:38 + Finished at: Tue, 19 Jun 2007 23:40:05 + Total time: 33m 27s Build Trigger: Schedule Exit code: 70 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes modules/metadata/src/org/apache/axis2/jaxws/description/impl/EndpointInterfaceDescriptionImpl.java modules/jaxws/test/org/apache/axis2/jaxws/provider/StringProviderTests.java modules/jaxws/test/org/apache/axis2/jaxws/provider/SOAPFaultProviderTests.java modules/jaxws/test/org/apache/axis2/jaxws/framework/JAXWSTest.java modules/jaxws/project.xml Output: Snipped Output: [echo] Generating java from stock2.xsd [echo] Generating java from samplemtom.xsd [echo] Generating java from ProxyDocLitWrapped.wsdl [echo] Generating java from ProxyDocLitnonWrapped.wsdl [echo] Generating java from samplemtomjpeg.wsdl [echo] Generating java from RPCLit.wsdl [echo] Generating java from gorilla_dlw.wsdl [echo] Generating java from SOAP12Echo.wsdl [echo] Generating java from AddNumbers.wsdl [echo] Generating java from AddNumbersHandler.wsdl [echo] Generating java from async_doclitwr.wsdl [echo] Generating java from FaultyWebService.wsdl [echo] Generating java from FaultsService.wsdl [echo] Generating java from jaxbsource [echo] Generating java from doclit_nonwrap.wsdl for javabean endpoint support [echo] Generating java from doclitwrap.wsdl for javabean endpoint support [echo] Generating java from doclitbare.wsdl for javabean endpoint support [echo] Generating java from greeterTypes.xsd [echo] Generating java from EchoMessage.wsdl for javabean endpoint support [echo] Generating java from resourceinjection.wsdl for javabean endpoint Resource Injection support [echo] Generating java from AnyType.wsdl for javabean endpoint AnyType support [echo] Generating java from WSDLMultiTests.wsdl [echo] Generating java from Polymorphic shapes.wsdl for javabean endpoint support [echo] Generating java from SOAPActionTest.wsdl [echo] Generating java from rpclitenum.wsdl [echo] Generating java from StringList.wsdl [echo] Compiling generated schema [javac] Compiling 230 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/schema/classes [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] Compiling 245 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. Running post goal: test:compile [copy] Copying 7 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/EchoService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/BasicAuthSecurityService [copy] Copying 26 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/StringProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/StringMessageProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/SourceProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/SourceMessageProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/SoapMessageProviderService [copy] Copying 32 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/JAXBProviderService [copy] Copying 31 files to
[jira] Updated: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] balaji iyer updated AXIS2-2814: --- In the nightly build axis2-SNAPSHOT I get the following Exception NoSuchMethodError. Below is its stack trace. Exception in thread main java.lang.NoSuchMethodError: org.w3c.dom.Document.getInputEncoding()Ljava/lang/String; at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:80) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:355) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:300) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1878) at org.apache.ws.commons.schema.SchemaBuilder.handleInclude(SchemaBuilder.java:1661) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:166) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:79) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:355) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:300) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1878) at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1614) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:172) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:79) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:355) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:300) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1878) at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1896) at org.apache.ws.commons.schema.SchemaBuilder.handleInclude(SchemaBuilder.java:1668) at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:166) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:343) at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxisServiceBuilder.java:137) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(WSDL11ToAxisServiceBuilder.java:1949) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:261) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:100) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:131) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) XSI:TYPE not being generated for SOAP JMS client requests - Key: AXIS2-2814 URL: https://issues.apache.org/jira/browse/AXIS2-2814 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.2 Environment: Win XP, AXIS2 (1.2) Reporter: balaji iyer Assignee: Amila Chinthaka Suriarachchi Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip I'm trying to run the SOAP JMS webservice which is hosted in businessworks. I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding. However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP. The issues is that the xsi type is not being generated for JMS requests. Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks. -- 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-1701) Axis2 incorrectly serialized (to xml) XBeans adds xmlns=
[ https://issues.apache.org/jira/browse/AXIS2-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506366 ] Amila Chinthaka Suriarachchi commented on AXIS2-1701: - can you please attach your wsdl as well? Axis2 incorrectly serialized (to xml) XBeans adds xmlns= -- Key: AXIS2-1701 URL: https://issues.apache.org/jira/browse/AXIS2-1701 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen, databinding Affects Versions: 1.2 Environment: Axis 2 1.1 RC2 FC3 java version 1.5.0_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode) Reporter: Nathan Lipke Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Attachments: wsrp-2.0-types.xsd When running this code snippet (below), axis2 adds a xmlns= to the importPortlets element. importPortlet xmlns= importID=foo However importRequest.toString() correctly serializes it. Code: final ImportPortletsDocument importRequest = ImportPortletsDocument.Factory.newInstance(xmlOptions); final ImportPortlets importPortlets = importRequest.addNewImportPortlets(); importPortlets.setImportContext(importContext); importPortlets.setNilLifetime(); RegistrationContext registrationContext = importPortlets.addNewRegistrationContext(); registrationContext.setNil(); importPortlets.setNilUserContext(); final ImportPortlet importPortlet = importPortlets.addNewImportPortlet(); importPortlet.setImportID(foo); importPortlet.setExportData(exportData); System.out.println(importRequest); final ImportPortletsResponseDocument importResponseDoc = stub.importPortlets(importRequest); Axis2 XML: ?xml version=1.0 encoding=UTF-8? [exec] soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:wsee=urn:wsee:Security [exec] soapenv:Header/ [exec] soapenv:Body [exec] importPortlets xmlns=urn:oasis:names:tc:wsrp:v2:types [exec] registrationContext [exec] registrationHandle2004/registrationHandle [exec] /registrationContext [exec] importContextQkVBOldMUDpFWFBPUlQ6MS4wOmVuLVVT/importContext [exec] importPortlet xmlns= importID=foo [exec] exportData xmlns=urn:oasis:names:tc:wsrp:v2:typesH4sIALVU207bQBClUp/6FStLbZ/stSkgkiZBtAKEFCTUhqrqC9p4J3jVvWl3TQKv/Zj+R/tjnbWDSQS0CBVLlq3xzDkzZ453Y+PFy8HeQklyCc4Lo4dJkeUJAV0aLvTFMDmbHKa7yd5oIE3JpLhmAbM+gTe1K8HfHyYcfOmEDQ3g+O2+tBWbQiAzx/TvH79+MuET0lTCMJm5hAQR4mtdVxWp6uZO6GPAvwEnTNZKaFGrW0zQ6dGHDvZjBeCEiYj0gTEep4E1LjDZd8YEghfWaN/XEGqxGCZVCLZP6Xw+z6bAstIo6sFFTNqm0IXntDQ6OCO7GFJFsg6tpXgsWptNfW3j2x2wKqh1qPm7zLgLWvR6PbqIX9MWLFU46kwAvwOx8OI+hM08L+jXk/HnsgLFUqF9YLqEttCLvm/iYxS73dPTxyFtMF0G0+I8P88zzE5Gg7a00UxCOF42QRRz32s7ubK4+9P2W+eFUwczcLhbQAvetD1Gd6JQk6083yy2ejtFsRMf27vbebGdkLgz0OHMoRQUuAgWQTxdgTrAoHGZvSEzTmDBcnaUk8OM1TKcoE2VuAaOrmfSw8oIHRbRTGGf1plgSiMTcon+xsDxyf5pQto9sWkcJbgaBVeIK77EHH4TWvtDdC1ldP5DRDXuoSPRLMBzkLS77mjUVcaNYkJHI6zztbqsEy5ja4wHWC5Ji0sY5w68/1sHFUh75m7lXBpyrRNaXoi0OSBoTN8rhxNjX2/mwVhRvmHKvjfDSPu0jv+lETdzLQ3jh0byFa2EnprFc+zkAT6Pxn0OuvhvdCS93n/YeoMYz/T7j4HRqwFdObBHfwDYui+f7AYAAA==/exportData [exec] /importPortlet [exec] userContext xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true/ [exec] lifetime xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true/ [exec] /importPortlets [exec] /soapenv:Body [exec] /soapenv:Envelope XmlBeans XML: importPortlets xmlns=urn:oasis:names:tc:wsrp:v2:types xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; registrationContext xsi:nil=true/ importContextQkVBOldMUDpFWFBPUlQ6MS4wOmVuLVVT/importContext importPortlet importID=foo
Re: Running SAAJ problem
It works now, Thanks for the help! The problem was with this; QName bodyName = new QName(http://ws.apache.org/axis2/xsd;, x, m); It works after coding exactly like that. I could not found any SAAJ example on Axis. So I started from Sun J2EE tutorial, get confused and wasted so much time. There are examples on soon-to-be deprecated methods, not on SAAJ. A simple example could make difference! By the way, I have another problem. How cannot I pass XML strings to POJO methods and get returns in XML as well? I mean without using attachments which will complicate things. I am primarily targeting calls from .NET and PHP. Regards, Joe. -- View this message in context: http://www.nabble.com/Running-SAAJ-problem-tf3937707.html#a11206864 Sent from the Axis - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-2290) improve unwrapping option to support non complex data types
[ https://issues.apache.org/jira/browse/AXIS2-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-2290. - Resolution: Fixed fixed the issue to support simple types as well improve unwrapping option to support non complex data types --- Key: AXIS2-2290 URL: https://issues.apache.org/jira/browse/AXIS2-2290 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: codegen Reporter: Keith Godwin Chapman Assignee: Amila Chinthaka Suriarachchi Priority: Blocker Attachments: servicetypes.xsd, SOAPservice.wsdl Currently -uw option workes for complex types only. But the schema that i have attached has to complex types. I guess it might b trivial to improve unwrapping to support this schema. -- 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-2202) NullPointerException invoking a stub method
[ https://issues.apache.org/jira/browse/AXIS2-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-2202. - Resolution: Invalid resolve the issue since it is an user setting problem. Please report the C issue in http://ws.apache.org/axis2/c/ NullPointerException invoking a stub method --- Key: AXIS2-2202 URL: https://issues.apache.org/jira/browse/AXIS2-2202 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Linux Fedora fc5, tomcat 6.0.7, java1.5.0_11, Axis2 1.1.1 Reporter: Federica Ciotti Assignee: Amila Chinthaka Suriarachchi Service skeleton generated from wsdl with axis2 1.1.1 Client stub generate with axis2 1.1 (getting generation problems with 1.1.1 ) Trying to invoke a stub method form a client class I get: java.lang.NullPointerException at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:467) at com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.java:229) at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeAttribute(MTOMXMLStreamWriter.java:134) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:387) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSerializerUtil.java:171) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:803) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:555) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:792) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:546) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.serialize(OMSourcedElementImpl.java:583) at uddi_org.publication_v2.PublishSoapServiceStub$Get_authToken20$1.serialize(PublishSoapServiceStub.java:29717) at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:574) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:819) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:819) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:180) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848) at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:419) at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:55) at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:85) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:547) at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:119) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:349) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:519) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:310) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:276) at uddi_org.publication_v2.PublishSoapServiceStub.get_authToken(PublishSoapServiceStub.java:1195) at uddi_client.PublishClient.getAuthToken(PublishClient.java:28) at uddi_client.PublishClient.main(PublishClient.java:11) Tomcat log exception is: Feb 16, 2007 11:45:54 AM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet AxisServlet threw exception
Re: Running SAAJ problem
Hi Joe,
Good to hear that you got it working!!!
Are you referring to passing a String (which is an XML) to a method in POJO
getting a return String (which is also a XML) ?
eg:
class MyService{
public String myMethod(String xml){
//do something
}
}
On 6/20/07, Joe Nathan [EMAIL PROTECTED] wrote:
It works now, Thanks for the help!
The problem was with this;
QName bodyName = new QName(http://ws.apache.org/axis2/xsd;,
x, m);
It works after coding exactly like that. I could not found any SAAJ
example
on Axis. So I started from Sun J2EE tutorial, get confused and wasted so
much time. There are examples on soon-to-be deprecated methods, not
on SAAJ. A simple example could make difference!
By the way, I have another problem. How cannot I pass XML strings to
POJO methods and get returns in XML as well? I mean without using
attachments which will complicate things. I am primarily targeting
calls from .NET and PHP.
Regards,
Joe.
--
View this message in context:
http://www.nabble.com/Running-SAAJ-problem-tf3937707.html#a11206864
Sent from the Axis - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running SAAJ problem
Exactly! I tried on Axis POJO this, but it ended up with fatal error! I think
Axis does not do proper marshalling for special characters inside xml codes.
Joe,
sumedha rubasinghe-2 wrote:
Hi Joe,
Good to hear that you got it working!!!
Are you referring to passing a String (which is an XML) to a method in
POJO
getting a return String (which is also a XML) ?
eg:
class MyService{
public String myMethod(String xml){
//do something
}
}
--
View this message in context:
http://www.nabble.com/Running-SAAJ-problem-tf3937707.html#a11207308
Sent from the Axis - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][continuum] BUILD FAILURE
Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2422 Build statistics: State: Failed Previous State: Failed Started at: Wed, 20 Jun 2007 04:36:05 + Finished at: Wed, 20 Jun 2007 05:25:42 + Total time: 49m 37s Build Trigger: Schedule Exit code: 70 Building machine hostname: ws.zones.apache.org Operating system : SunOS(unknown) Java version : 1.5.0_09(Sun Microsystems Inc.) Changes dims fix build break. deepal, please check if this is ok /webservices/axis2/trunk/java/modules/scripting/src/org/apache/axis2/scripting/ScriptRepositoryListener.java amilas handle exceptions properly /webservices/axis2/trunk/java/modules/adb-codegen/src/org/apache/axis2/schema/template/ADBDatabindingTemplate.xsl amilas added new constructor to set isUseSeperateListner /webservices/axis2/trunk/java/modules/codegen/src/org/apache/axis2/wsdl/template/java/InterfaceImplementationTemplate.xsl Output: Snipped Output: [echo] Generating java from stock2.xsd [echo] Generating java from samplemtom.xsd [echo] Generating java from ProxyDocLitWrapped.wsdl [echo] Generating java from ProxyDocLitnonWrapped.wsdl [echo] Generating java from samplemtomjpeg.wsdl [echo] Generating java from RPCLit.wsdl [echo] Generating java from gorilla_dlw.wsdl [echo] Generating java from SOAP12Echo.wsdl [echo] Generating java from AddNumbers.wsdl [echo] Generating java from AddNumbersHandler.wsdl [echo] Generating java from async_doclitwr.wsdl [echo] Generating java from FaultyWebService.wsdl [echo] Generating java from FaultsService.wsdl [echo] Generating java from jaxbsource [echo] Generating java from doclit_nonwrap.wsdl for javabean endpoint support [echo] Generating java from doclitwrap.wsdl for javabean endpoint support [echo] Generating java from doclitbare.wsdl for javabean endpoint support [echo] Generating java from greeterTypes.xsd [echo] Generating java from EchoMessage.wsdl for javabean endpoint support [echo] Generating java from resourceinjection.wsdl for javabean endpoint Resource Injection support [echo] Generating java from AnyType.wsdl for javabean endpoint AnyType support [echo] Generating java from WSDLMultiTests.wsdl [echo] Generating java from Polymorphic shapes.wsdl for javabean endpoint support [echo] Generating java from SOAPActionTest.wsdl [echo] Generating java from rpclitenum.wsdl [echo] Generating java from StringList.wsdl [echo] Compiling generated schema [javac] Compiling 230 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/schema/classes [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] Compiling 245 source files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. Running post goal: test:compile [copy] Copying 7 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/EchoService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/BasicAuthSecurityService [copy] Copying 26 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/StringProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/StringMessageProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/SourceProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/SourceMessageProviderService [copy] Copying 25 files to /export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/jaxws/target/test-classes/services/SoapMessageProviderService [copy] Copying 32 files to
