[jira] Assigned: (GERONIMO-4289) [saaj] javax.xml.soap.MessageFactory property is not optional
[ https://issues.apache.org/jira/browse/GERONIMO-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas reassigned GERONIMO-4289: -- Assignee: Jarek Gawor > [saaj] javax.xml.soap.MessageFactory property is not optional > - > > Key: GERONIMO-4289 > URL: https://issues.apache.org/jira/browse/GERONIMO-4289 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Davanum Srinivas >Assignee: Jarek Gawor > Attachments: saaj.diff > > > According to the SAAJ 1.3 specification, javax.xml.soap.MessageFactory is > optional and when it is not specified, we should fall back to the > SAAJMetaFactory basically use > "newMessageFactory(SOAPConstants.SOAP_1_1_PROTOCOL)" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4289) [saaj] javax.xml.soap.MessageFactory property is not optional
[ https://issues.apache.org/jira/browse/GERONIMO-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated GERONIMO-4289: --- Attachment: saaj.diff > [saaj] javax.xml.soap.MessageFactory property is not optional > - > > Key: GERONIMO-4289 > URL: https://issues.apache.org/jira/browse/GERONIMO-4289 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Davanum Srinivas > Attachments: saaj.diff > > > According to the SAAJ 1.3 specification, javax.xml.soap.MessageFactory is > optional and when it is not specified, we should fall back to the > SAAJMetaFactory basically use > "newMessageFactory(SOAPConstants.SOAP_1_1_PROTOCOL)" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4289) [saaj] javax.xml.soap.MessageFactory property is not optional
[saaj] javax.xml.soap.MessageFactory property is not optional - Key: GERONIMO-4289 URL: https://issues.apache.org/jira/browse/GERONIMO-4289 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: specs Reporter: Davanum Srinivas Attachments: saaj.diff According to the SAAJ 1.3 specification, javax.xml.soap.MessageFactory is optional and when it is not specified, we should fall back to the SAAJMetaFactory basically use "newMessageFactory(SOAPConstants.SOAP_1_1_PROTOCOL)" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3980) Replace maven-maven-plugin usage with shitty-maven-plugin
[ https://issues.apache.org/jira/browse/GERONIMO-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591072#action_12591072 ] Davanum Srinivas commented on GERONIMO-3980: reading the subject/title...for a micro second, i thought you were joking :) > Replace maven-maven-plugin usage with shitty-maven-plugin > - > > Key: GERONIMO-3980 > URL: https://issues.apache.org/jira/browse/GERONIMO-3980 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Reporter: Jason Dillon >Assignee: Jason Dillon > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3953) ArrayIndexOutOfBoundsException reading MimeMultipart from a file with multiple attachments.
[
https://issues.apache.org/jira/browse/GERONIMO-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated GERONIMO-3953:
---
Description:
Here's the stack trace :
==
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
at java.util.Vector.get(Vector.java:710)
at javax.mail.Multipart.getBodyPart(Multipart.java:93)
at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:110)
at
javax.mail.internet.MimeMultipartTest.testMIMEWriting(MimeMultipartTest.java:107)
==
Please see the uploaded diff to existing test case to demonstrate the issue.
was:
Here's the stack trace :
==
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
at java.util.Vector.get(Vector.java:710)
at javax.mail.Multipart.getBodyPart(Multipart.java:93)
at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:110)
at
javax.mail.internet.MimeMultipartTest.testMIMEWriting(MimeMultipartTest.java:107)
==
Here's the code snippet to recreate the issue :
==
C:\Apache\geronimo-javamail_1.4_spec>svn diff
Index: src/test/java/javax/mail/internet/MimeMultipartTest.java
===
--- src/test/java/javax/mail/internet/MimeMultipartTest.java(revision
645758)
+++ src/test/java/javax/mail/internet/MimeMultipartTest.java(working copy)
@@ -26,6 +26,7 @@
import java.io.ByteArrayInputStream;
import java.io.ByteArrayOutputStream;
import java.io.File;
+import java.io.FileInputStream;
import java.util.Properties;
import javax.mail.BodyPart;
import javax.mail.MessagingException;
@@ -95,6 +96,23 @@
assertEquals("This is a preamble\r\n",
((MimeMultipart)newMessage.getContent()).getPreamble());
}
+public void testMIMEWriting() throws IOException, MessagingException {
+FileInputStream inStream = new
FileInputStream("src/test/resources/wmtom.bin");
+Properties props = new Properties();
+javax.mail.Session session = javax.mail.Session
+.getInstance(props, null);
+MimeMessage mimeMessage = new MimeMessage(session, inStream);
+DataHandler dh = mimeMessage.getDataHandler();
+MimeMultipart multiPart = new MimeMultipart(dh.getDataSource());
+MimeBodyPart mimeBodyPart0 = (MimeBodyPart) multiPart.getBodyPart(0);
+Object object0 = mimeBodyPart0.getContent();
+assertNotNull(object0);
+MimeBodyPart mimeBodyPart1 = (MimeBodyPart) multiPart.getBodyPart(1);
+Object object1 = mimeBodyPart1.getContent();
+assertNotNull(object1);
+assertEquals(multiPart.getCount(), 2);
+}
+
protected void writeToSetUp() throws Exception {
defaultMap = CommandMap.getDefaultCommandMap();
MailcapCommandMap myMap = new MailcapCommandMap();
i'll upload wmtom.bin as an attachment
> ArrayIndexOutOfBoundsException reading MimeMultipart from a file with
> multiple attachments.
> ---
>
> Key: GERONIMO-3953
> URL: https://issues.apache.org/jira/browse/GERONIMO-3953
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: mail
>Reporter: Davanum Srinivas
> Attachments: test.diff, wmtom.bin
>
>
> Here's the stack trace :
> ==
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
> at java.util.Vector.get(Vector.java:710)
> at javax.mail.Multipart.getBodyPart(Multipart.java:93)
> at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:110)
> at
> javax.mail.internet.MimeMultipartTest.testMIMEWriting(MimeMultipartTest.java:107)
> ==
> Please see the uploaded diff to existing test case to demonstrate the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3953) ArrayIndexOutOfBoundsException reading MimeMultipart from a file with multiple attachments.
[
https://issues.apache.org/jira/browse/GERONIMO-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated GERONIMO-3953:
---
Attachment: test.diff
diff with the test case.
> ArrayIndexOutOfBoundsException reading MimeMultipart from a file with
> multiple attachments.
> ---
>
> Key: GERONIMO-3953
> URL: https://issues.apache.org/jira/browse/GERONIMO-3953
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: mail
>Reporter: Davanum Srinivas
> Attachments: test.diff, wmtom.bin
>
>
> Here's the stack trace :
> ==
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
> at java.util.Vector.get(Vector.java:710)
> at javax.mail.Multipart.getBodyPart(Multipart.java:93)
> at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:110)
> at
> javax.mail.internet.MimeMultipartTest.testMIMEWriting(MimeMultipartTest.java:107)
> ==
> Here's the code snippet to recreate the issue :
> ==
> C:\Apache\geronimo-javamail_1.4_spec>svn diff
> Index: src/test/java/javax/mail/internet/MimeMultipartTest.java
> ===
> --- src/test/java/javax/mail/internet/MimeMultipartTest.java(revision
> 645758)
> +++ src/test/java/javax/mail/internet/MimeMultipartTest.java(working copy)
> @@ -26,6 +26,7 @@
> import java.io.ByteArrayInputStream;
> import java.io.ByteArrayOutputStream;
> import java.io.File;
> +import java.io.FileInputStream;
> import java.util.Properties;
> import javax.mail.BodyPart;
> import javax.mail.MessagingException;
> @@ -95,6 +96,23 @@
> assertEquals("This is a preamble\r\n",
> ((MimeMultipart)newMessage.getContent()).getPreamble());
> }
> +public void testMIMEWriting() throws IOException, MessagingException {
> +FileInputStream inStream = new
> FileInputStream("src/test/resources/wmtom.bin");
> +Properties props = new Properties();
> +javax.mail.Session session = javax.mail.Session
> +.getInstance(props, null);
> +MimeMessage mimeMessage = new MimeMessage(session, inStream);
> +DataHandler dh = mimeMessage.getDataHandler();
> +MimeMultipart multiPart = new MimeMultipart(dh.getDataSource());
> +MimeBodyPart mimeBodyPart0 = (MimeBodyPart) multiPart.getBodyPart(0);
> +Object object0 = mimeBodyPart0.getContent();
> +assertNotNull(object0);
> +MimeBodyPart mimeBodyPart1 = (MimeBodyPart) multiPart.getBodyPart(1);
> +Object object1 = mimeBodyPart1.getContent();
> +assertNotNull(object1);
> +assertEquals(multiPart.getCount(), 2);
> +}
> +
> protected void writeToSetUp() throws Exception {
> defaultMap = CommandMap.getDefaultCommandMap();
> MailcapCommandMap myMap = new MailcapCommandMap();
> i'll upload wmtom.bin as an attachment
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3953) ArrayIndexOutOfBoundsException reading MimeMultipart from a file with multiple attachments.
[
https://issues.apache.org/jira/browse/GERONIMO-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated GERONIMO-3953:
---
Attachment: wmtom.bin
Here's the file as promised.
-- dims
> ArrayIndexOutOfBoundsException reading MimeMultipart from a file with
> multiple attachments.
> ---
>
> Key: GERONIMO-3953
> URL: https://issues.apache.org/jira/browse/GERONIMO-3953
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: mail
>Reporter: Davanum Srinivas
> Attachments: wmtom.bin
>
>
> Here's the stack trace :
> ==
> java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
> at java.util.Vector.get(Vector.java:710)
> at javax.mail.Multipart.getBodyPart(Multipart.java:93)
> at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:110)
> at
> javax.mail.internet.MimeMultipartTest.testMIMEWriting(MimeMultipartTest.java:107)
> ==
> Here's the code snippet to recreate the issue :
> ==
> C:\Apache\geronimo-javamail_1.4_spec>svn diff
> Index: src/test/java/javax/mail/internet/MimeMultipartTest.java
> ===
> --- src/test/java/javax/mail/internet/MimeMultipartTest.java(revision
> 645758)
> +++ src/test/java/javax/mail/internet/MimeMultipartTest.java(working copy)
> @@ -26,6 +26,7 @@
> import java.io.ByteArrayInputStream;
> import java.io.ByteArrayOutputStream;
> import java.io.File;
> +import java.io.FileInputStream;
> import java.util.Properties;
> import javax.mail.BodyPart;
> import javax.mail.MessagingException;
> @@ -95,6 +96,23 @@
> assertEquals("This is a preamble\r\n",
> ((MimeMultipart)newMessage.getContent()).getPreamble());
> }
> +public void testMIMEWriting() throws IOException, MessagingException {
> +FileInputStream inStream = new
> FileInputStream("src/test/resources/wmtom.bin");
> +Properties props = new Properties();
> +javax.mail.Session session = javax.mail.Session
> +.getInstance(props, null);
> +MimeMessage mimeMessage = new MimeMessage(session, inStream);
> +DataHandler dh = mimeMessage.getDataHandler();
> +MimeMultipart multiPart = new MimeMultipart(dh.getDataSource());
> +MimeBodyPart mimeBodyPart0 = (MimeBodyPart) multiPart.getBodyPart(0);
> +Object object0 = mimeBodyPart0.getContent();
> +assertNotNull(object0);
> +MimeBodyPart mimeBodyPart1 = (MimeBodyPart) multiPart.getBodyPart(1);
> +Object object1 = mimeBodyPart1.getContent();
> +assertNotNull(object1);
> +assertEquals(multiPart.getCount(), 2);
> +}
> +
> protected void writeToSetUp() throws Exception {
> defaultMap = CommandMap.getDefaultCommandMap();
> MailcapCommandMap myMap = new MailcapCommandMap();
> i'll upload wmtom.bin as an attachment
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3953) ArrayIndexOutOfBoundsException reading MimeMultipart from a file with multiple attachments.
ArrayIndexOutOfBoundsException reading MimeMultipart from a file with multiple
attachments.
---
Key: GERONIMO-3953
URL: https://issues.apache.org/jira/browse/GERONIMO-3953
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: mail
Reporter: Davanum Srinivas
Here's the stack trace :
==
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
at java.util.Vector.get(Vector.java:710)
at javax.mail.Multipart.getBodyPart(Multipart.java:93)
at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:110)
at
javax.mail.internet.MimeMultipartTest.testMIMEWriting(MimeMultipartTest.java:107)
==
Here's the code snippet to recreate the issue :
==
C:\Apache\geronimo-javamail_1.4_spec>svn diff
Index: src/test/java/javax/mail/internet/MimeMultipartTest.java
===
--- src/test/java/javax/mail/internet/MimeMultipartTest.java(revision
645758)
+++ src/test/java/javax/mail/internet/MimeMultipartTest.java(working copy)
@@ -26,6 +26,7 @@
import java.io.ByteArrayInputStream;
import java.io.ByteArrayOutputStream;
import java.io.File;
+import java.io.FileInputStream;
import java.util.Properties;
import javax.mail.BodyPart;
import javax.mail.MessagingException;
@@ -95,6 +96,23 @@
assertEquals("This is a preamble\r\n",
((MimeMultipart)newMessage.getContent()).getPreamble());
}
+public void testMIMEWriting() throws IOException, MessagingException {
+FileInputStream inStream = new
FileInputStream("src/test/resources/wmtom.bin");
+Properties props = new Properties();
+javax.mail.Session session = javax.mail.Session
+.getInstance(props, null);
+MimeMessage mimeMessage = new MimeMessage(session, inStream);
+DataHandler dh = mimeMessage.getDataHandler();
+MimeMultipart multiPart = new MimeMultipart(dh.getDataSource());
+MimeBodyPart mimeBodyPart0 = (MimeBodyPart) multiPart.getBodyPart(0);
+Object object0 = mimeBodyPart0.getContent();
+assertNotNull(object0);
+MimeBodyPart mimeBodyPart1 = (MimeBodyPart) multiPart.getBodyPart(1);
+Object object1 = mimeBodyPart1.getContent();
+assertNotNull(object1);
+assertEquals(multiPart.getCount(), 2);
+}
+
protected void writeToSetUp() throws Exception {
defaultMap = CommandMap.getDefaultCommandMap();
MailcapCommandMap myMap = new MailcapCommandMap();
i'll upload wmtom.bin as an attachment
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3102) Axis2: servicename and portname overwrite (from wsdl to annotation)
[ https://issues.apache.org/jira/browse/GERONIMO-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489207 ] Davanum Srinivas commented on GERONIMO-3102: i checked in a possible fix for the failure in Axis2 - http://svn.apache.org/viewvc?view=rev&revision=529374 Applied this patch - 529376 thanks, dims > Axis2: servicename and portname overwrite (from wsdl to annotation) > --- > > Key: GERONIMO-3102 > URL: https://issues.apache.org/jira/browse/GERONIMO-3102 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: G3102.patch > > > Hi Dims, > per our discussion on IRC today: > seems using JavaClassToDBCConverter.produceDBC() requires the consistency > (servicename and portname) between wsdl and annotation. i am getting this > error - http://rafb.net/p/dJGbk884.html > The patch will add some overwrite code in AxisServiceGenerator to overwrite > the WebServiceAnnot or WebServiceProviderAnnot that is generated by > JavaClassToDBCConverter.produceDBC(). > With the patch, able to get 2 of 3 jax-ws war test succeed. (am running an a > bit older version of axis2 snapshots (earlier last week), as the latest ones > didn't pass the maven test.). The error (http://rafb.net/p/F3Jpfk47.html) > caused the 1 fail out of the 3 tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3100) Axis2: remove hardcoded 12 jars in Axis2BuilderUtil
[ https://issues.apache.org/jira/browse/GERONIMO-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3100. Resolution: Fixed thanks. fixed in svn revision 529257 -- dims > Axis2: remove hardcoded 12 jars in Axis2BuilderUtil > --- > > Key: GERONIMO-3100 > URL: https://issues.apache.org/jira/browse/GERONIMO-3100 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: G3100.patch > > > as titled. per discussion on dev list: > Lin, > I think we can use ListableRepository interface somehow then we can > get rid of the version information. But i think we may have to fix > Maven2Repository to work even we don't pass in the version field in > Artifact. Can you please take a look at that? > thanks, > dims -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3019) Remove JAXB dependencies from Axis2 JAXWS
[ https://issues.apache.org/jira/browse/GERONIMO-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488862 ] Davanum Srinivas commented on GERONIMO-3019: here's what i get after applying this.. --- T E S T S --- Running org.apache.geronimo.axis2.Axis2HandlerResolverTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.078 sec Running org.apache.geronimo.axis2.Axis2WebServiceContainerTest java.lang.NoClassDefFoundError: org/apache/axis2/AxisFault at org.apache.geronimo.axis2.Axis2WebServiceContainerTest.invokeWithWSDL(Axis2WebServiceContainerTest.java:144) at org.apache.geronimo.axis2.Axis2WebServiceContainerTest.testInvokeWithWSDL(Axis2WebServiceContainerTest.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122) at org.apache.maven.surefire.Surefire.run(Surefire.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747) Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.406 sec <<< FAILURE! > Remove JAXB dependencies from Axis2 JAXWS > - > > Key: GERONIMO-3019 > URL: https://issues.apache.org/jira/browse/GERONIMO-3019 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices > Environment: Linux >Reporter: Lasantha Ranaweera > Attachments: G3019-2.patch, GERONIMO-3019.patch > > > As Axis2 moves with XBeans it is unnecessary to keep dependencies with JAXB > related stuff. Also JAXB related code generation has been removed from the > test cases too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3092) Axis2: after wsgen tool, need to scan the directory for the generated wsdl file
[ https://issues.apache.org/jira/browse/GERONIMO-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3092. Resolution: Fixed Fixed in svn revision 528250 thanks, dims > Axis2: after wsgen tool, need to scan the directory for the generated wsdl > file > --- > > Key: GERONIMO-3092 > URL: https://issues.apache.org/jira/browse/GERONIMO-3092 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: G3092.patch > > > Currently it is looking for SOAPService.wsdl. Later on I found out the tool > is generating wsdl file's name based on the serviceName specified in the > webservice annotation of the SEIC. For example, for jaxws-war we have: > @WebService(serviceName = "SOAPService", > A solution could be to scan any wsdl file in the output directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3094) Axis2: need to build the classpath and pass it onto wsgen
[ https://issues.apache.org/jira/browse/GERONIMO-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3094. Resolution: Fixed Applied in svn revision 528061 -- dims > Axis2: need to build the classpath and pass it onto wsgen > - > > Key: GERONIMO-3094 > URL: https://issues.apache.org/jira/browse/GERONIMO-3094 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: G3094.patch > > > First I tried to pass the module path as the classpath onto wsgen but that > didn't work. Seems I have to pass all the 12 jars plus the module path as > the classpath onto wsgen to make it happy, otherwise, I kept getting "unable > to find sei org.apache.greeter_control.GreetImpl" error. > With the patch, you can see .wsdl and .xsd files are generated upon > deployment but you'll soon hit a NPE due to G3033. I'll work on G3092 in a > bit. Thanks dims for your help! > Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2998) Geronimo Axis2 Adding Fault Handling for WSDL Provided
[ https://issues.apache.org/jira/browse/GERONIMO-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2998. Resolution: Fixed Thanks Lasantha. Applied. svn revision 527912 -- dims > Geronimo Axis2 Adding Fault Handling for WSDL Provided > -- > > Key: GERONIMO-2998 > URL: https://issues.apache.org/jira/browse/GERONIMO-2998 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices > Environment: Linux >Reporter: Lasantha Ranaweera > Attachments: G2898-2.patch, GERONIMO-2898.patch > > > This will add the fault handling capability to the WSDL provided scenario of > Geronimo Axis2 integration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2846) modified jax-ws calculator sample to work with CXF and Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487983 ] Davanum Srinivas commented on GERONIMO-2846: woohoo!! > modified jax-ws calculator sample to work with CXF and Axis2 > > > Key: GERONIMO-2846 > URL: https://issues.apache.org/jira/browse/GERONIMO-2846 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: sample apps >Affects Versions: 2.0-M2 > Environment: winxp + sun jsk 1.5 >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: calculator_axis2.zip, jax-ws-calculator.zip, > jax-ws-calculator.zip > > > Hi Dims, > Per your request, here's the modified version of the sample. > Current issues: > 1) I haven't been able to run the webservice client outside of my eclipse > env. Getting CNF error if I ran the client as "java -jar > jaxws-calculator-1.0.jar". This could be fixed by providing an ant script > or build the java execution into maven's pom.xml. > 2) Running the Axis2 CalculatorClient client caused > Caused by: java.lang.ClassNotFoundException: com.sun.xml.ws.spi.ProviderImpl > at java.net.URLClassLoader$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:34) > ... 6 more > I just added this client back in this morning so I probably have missed the > dependency for this one. There are so many Axis2 dependencies so if you > know which one I need let me know.:) > Running the Axis2 CalculatorClientAxiom client works fine. > Thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3086) Axis2: wsgen tool needs axis2-jaxws-api-SNAPSHOT.jar at runtime
[ https://issues.apache.org/jira/browse/GERONIMO-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3086. Resolution: Fixed Fixed in svn revision 527381 -- dims > Axis2: wsgen tool needs axis2-jaxws-api-SNAPSHOT.jar at runtime > --- > > Key: GERONIMO-3086 > URL: https://issues.apache.org/jira/browse/GERONIMO-3086 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: winxp + sun 1.5 SDK >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: 3086.patch > > > If this jar file isn't there, we'll get > Exception in thread "main" java.lang.NoClassDefFoundError: > javax/xml/ws/WebServi > ceException > when wsgen runs. > will submit a patch later on to specify it as a dependency for > geronimo-axis2-builder. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3085) Axis2: Response Wrapper class isn't set correctly which caused a NPE in Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3085. Resolution: Fixed Fix in svn revision 527272 thanks, dims > Axis2: Response Wrapper class isn't set correctly which caused a NPE in Axis2 > - > > Key: GERONIMO-3085 > URL: https://issues.apache.org/jira/browse/GERONIMO-3085 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: winxp + sun 1.5 SDK >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: 3085.patch > > > In AxisServiceGenerator, we are not setting the name of the Response Wrapper > class incorrectly, which caused a NPE in Axis2. Here's the exerpt from > geronimo.log: > 9938 40:10:21:48,687 DEBUG [ArtifactProcessor] The following class is > missing: samples.geronimo.apache.org.jws.AddResponse Processing continues. > ... > Request Wrapper class: null; Response Wrapper class: > samples.geronimo.apache.org.jws.AddResponse > It should be set as org.apache.geronimo.samples.jws.AddResponse here. > Modified the logic in getWrapperClassName method as the current code assumes > there is only one dot in host. With the fix, got passed by this NPE error > which I encountered yesterday but still not able to get end to end flow > working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3080) Axis2: Improve AxisServiceGenerator to handle more than 1 parameter of a service method (doclitwrapped case)
[ https://issues.apache.org/jira/browse/GERONIMO-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3080. Resolution: Fixed checked in svn revision 526904 thanks, dims > Axis2: Improve AxisServiceGenerator to handle more than 1 parameter of a > service method (doclitwrapped case) > > > Key: GERONIMO-3080 > URL: https://issues.apache.org/jira/browse/GERONIMO-3080 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: sun 1.5 SDK + Win XP >Reporter: Lin Sun > Fix For: 2.0-M5 > > Attachments: G3080.patch > > > The AxisServiceGenerator can only handle one parameter of the service method. > For example, from the calculatorservice.wsdl: > > > > > > > > > This add method contains 2 params however the AxisServiceGenerator would only > create 1 ParameterDescriptionComposite, which is the one for value1. The > fix is to build the ParameterDescriptionComposite inside of the while loop > for doclitwrapped case. > With the fix, I am able to get the calculatorservice.add invoked and see > value1 and value2 printed on the server. However, end to end flow still > doesn't work (due to a NPE from Axis2) and currently look into that to see if > it is an Axis2 issue or not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3074) Axis2: portname isn't set correctly
[ https://issues.apache.org/jira/browse/GERONIMO-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3074. Resolution: Fixed Checked in (svn revision 526756) thanks, dims > Axis2: portname isn't set correctly > --- > > Key: GERONIMO-3074 > URL: https://issues.apache.org/jira/browse/GERONIMO-3074 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: WInXP + Sun 1.5 SDK >Reporter: Lin Sun > Assigned To: Donald Woods > Fix For: 2.0-M5 > > Attachments: 3074.patch > > > In Axis2WebServiceContainer.java line 475, it is setting the portname using > portInfo.getPortName(). This isn't correct, as this will return the value of > the tag instead of the value of the tag. > The fix is to use portInfo.getWsdlPort().getLocalPart() instead in the patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3063) Axis2 Build Failure on Trunk
[ https://issues.apache.org/jira/browse/GERONIMO-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3063. Resolution: Fixed Fixed in svn revision 525554 thanks, dims > Axis2 Build Failure on Trunk > > > Key: GERONIMO-3063 > URL: https://issues.apache.org/jira/browse/GERONIMO-3063 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M5 > Environment: Trunk Rev525398, Sun 1.5.0_11, SLES10 >Reporter: Donald Woods > Assigned To: Davanum Srinivas >Priority: Blocker > Fix For: 2.0-M5 > > > Just started seeing this build failure on Trunk in the last hour after > starting with a clean .m2 repo, due to a new Axis2 SNAPSHOT being released > this morning - > [INFO] [compiler:compile] > [INFO] Compiling 11 source files to > /home/g20/working/server/modules/geronimo-axis2/target/classes > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Compilation failure > /home/g20/working/server/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[348,4] > > org.apache.geronimo.axis2.Axis2WebServiceContainer.Axis2RequestResponseTransport > is not abstract and does not override abstract method > signalFaultReady(org.apache.axis2.AxisFault) in > org.apache.axis2.transport.RequestResponseTransport > /home/g20/working/server/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[348,4] > > org.apache.geronimo.axis2.Axis2WebServiceContainer.Axis2RequestResponseTransport > is not abstract and does not override abstract method > signalFaultReady(org.apache.axis2.AxisFault) in > org.apache.axis2.transport.RequestResponseTransport > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 12 minutes 7 seconds > [INFO] Finished at: Wed Apr 04 12:12:58 EDT 2007 > [INFO] Final Memory: 95M/570M > [INFO] > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3055) Fix build break on axis2 (Revision: 524748)
[ https://issues.apache.org/jira/browse/GERONIMO-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-3055. Resolution: Fixed Applied. thanks. My bad. -- dims > Fix build break on axis2 (Revision: 524748) > --- > > Key: GERONIMO-3055 > URL: https://issues.apache.org/jira/browse/GERONIMO-3055 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices > Environment: Win XP + 1.5 SDK >Reporter: Lin Sun > Attachments: G3055.patch > > > as titled, here is a patch to add back the axis2 runtime dependencies as > we'll need them for the axis2webcontainertest. > You'll see an NPE from Axis2 due to recent changes in Axis2 (this will be > investigated seperately) but you'll get a build successful and pass the test. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2977) Axis2: process wsdlLocation annotation when wsdl-file property isn't used in webservices.xml or there isn't webservices.xml
[ https://issues.apache.org/jira/browse/GERONIMO-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485053 ] Davanum Srinivas commented on GERONIMO-2977: Sorry. in svn revision 523542 -- dims > Axis2: process wsdlLocation annotation when wsdl-file property isn't used in > webservices.xml or there isn't webservices.xml > --- > > Key: GERONIMO-2977 > URL: https://issues.apache.org/jira/browse/GERONIMO-2977 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Environment: sun 1.5 + winxp >Reporter: Lin Sun > Attachments: G2977-latest.patch, G2977.patch > > > Per discussion on dev list titled "Questions for Axis2 folks re: JAXWS", this > patch will do the following: > if wsdl-file property isn't specified in webservices.xml or there isn't a > webservices.xml but a user did supply a .wsdl file and specified the > wsdlLocation annotation, we will grab the value of the wsdlLocation from > annotation and set it in portInfo. > Has tried to test it by supplying wsdlLocation in jaxws-war file and worked > okay. Patched will be supplied in a bit after a successful build.:) > Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2977) Axis2: process wsdlLocation annotation when wsdl-file property isn't used in webservices.xml or there isn't webservices.xml
[ https://issues.apache.org/jira/browse/GERONIMO-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2977. Resolution: Fixed Applied. thanks, dims > Axis2: process wsdlLocation annotation when wsdl-file property isn't used in > webservices.xml or there isn't webservices.xml > --- > > Key: GERONIMO-2977 > URL: https://issues.apache.org/jira/browse/GERONIMO-2977 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Environment: sun 1.5 + winxp >Reporter: Lin Sun > Attachments: G2977-latest.patch, G2977.patch > > > Per discussion on dev list titled "Questions for Axis2 folks re: JAXWS", this > patch will do the following: > if wsdl-file property isn't specified in webservices.xml or there isn't a > webservices.xml but a user did supply a .wsdl file and specified the > wsdlLocation annotation, we will grab the value of the wsdlLocation from > annotation and set it in portInfo. > Has tried to test it by supplying wsdlLocation in jaxws-war file and worked > okay. Patched will be supplied in a bit after a successful build.:) > Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2977) Axis2: process wsdlLocation annotation when wsdl-file property isn't used in webservices.xml or there isn't webservices.xml
[ https://issues.apache.org/jira/browse/GERONIMO-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484949 ] Davanum Srinivas commented on GERONIMO-2977: looks good lin! -- dims > Axis2: process wsdlLocation annotation when wsdl-file property isn't used in > webservices.xml or there isn't webservices.xml > --- > > Key: GERONIMO-2977 > URL: https://issues.apache.org/jira/browse/GERONIMO-2977 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Environment: sun 1.5 + winxp >Reporter: Lin Sun > Attachments: G2977-latest.patch, G2977.patch > > > Per discussion on dev list titled "Questions for Axis2 folks re: JAXWS", this > patch will do the following: > if wsdl-file property isn't specified in webservices.xml or there isn't a > webservices.xml but a user did supply a .wsdl file and specified the > wsdlLocation annotation, we will grab the value of the wsdlLocation from > annotation and set it in portInfo. > Has tried to test it by supplying wsdlLocation in jaxws-war file and worked > okay. Patched will be supplied in a bit after a successful build.:) > Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2999) when issuing .wsdl request, the content-type isn't set
[ https://issues.apache.org/jira/browse/GERONIMO-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482436 ] Davanum Srinivas commented on GERONIMO-2999: Fixed for tomcat only in svn revision 520467 -- dims > when issuing .wsdl request, the content-type isn't set > -- > > Key: GERONIMO-2999 > URL: https://issues.apache.org/jira/browse/GERONIMO-2999 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.0 >Reporter: Lin Sun > Fix For: 2.0 > > > When running the calculator sample, we found out the response of the URL > request http://localhost:8081/jaxws-calculator-1.0/CalculatorService.wsdl > didn't have the proper content-type set which caused an exception from Axis2. > The content-type should be set to "Content-Type: text/xml". > This is with tomcat and there should be some default mime mapping for jetty > as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2979) More improvements to the Geronimo Axis2 Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2979. Resolution: Fixed > More improvements to the Geronimo Axis2 Integration > --- > > Key: GERONIMO-2979 > URL: https://issues.apache.org/jira/browse/GERONIMO-2979 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2979.patch > > > This patch will improve the existing coding of the Geronimo Axis2 integration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1680) MDB without activation-config in openejb-jar.xml silently fails
[ https://issues.apache.org/jira/browse/GERONIMO-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated GERONIMO-1680: --- Attachment: (was: rapesex.html) > MDB without activation-config in openejb-jar.xml silently fails > --- > > Key: GERONIMO-1680 > URL: https://issues.apache.org/jira/browse/GERONIMO-1680 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ, OpenEJB >Affects Versions: 1.0 >Reporter: Aaron Mulder >Priority: Critical > Fix For: 1.1.x > > > I created a queue and sent a couple messages to it. > Then I created an MDB with a message-destination-type of javax.jms.Queue and > a message-destination-link pointing to a message-destination with the name of > the Queue. It seems like this is enough information to point the MDB to that > queue, assuming that openejb-jar.xml lists the resource adapter for the MDB. > This deployed successfully, but no messages were received by the MDB. > Adding an activation-config section to openejb-jar.xml fixed the problem -- > the pending messages were received during deployment. > One of these two issues strikes me as a bug: > 1) Why wasn't the MDB hooked up to the queue without needing an > activation-config block in openejb-jar.xml? > 2) If that's an error, why is activation-config optional for an MDB in > openejb-jar.xml and why didn't it cause a deployment error? > In any case, I think deployment should always fail if an MDB is not actually > hooked up to a destination. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2914) Axis2: a few changes to set the servicepath, contextroot correctly in EJB to allow getWSDL() test working correctly
[ https://issues.apache.org/jira/browse/GERONIMO-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2914. Resolution: Fixed thanks. fix is in 513612. - dims > Axis2: a few changes to set the servicepath, contextroot correctly in EJB to > allow getWSDL() test working correctly > --- > > Key: GERONIMO-2914 > URL: https://issues.apache.org/jira/browse/GERONIMO-2914 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: winxp + sun 1.5 SDK >Reporter: Lin Sun > Fix For: 2.0 > > Attachments: G2914-new.patch, G2914.patch > > > This patch builds on top of GERONIMO-2894 since there are changes impacting > the same files (i.e. committing this patch will also commit the patch > submmitted in G2894). I could not find a better way to create patches for > easier review as G2894 isn't committed yet. > 1) The patch will change the initContextRoot() method to be an abstract > method and provide different implementation of it in POJO and EJB. > 2) The patch will also setServicePath of the axis2 configurationcontext > differently for POJO and EJB. > After applying the patch, please delete the 3 0KB files in > (Axis2WebServiceContext.java > , EJBWebServiceGBean.java > , Axis2WebServiceContainerFactoryGBean.java) in the > src\main\java\org\apache\geronimo\axis2 dir. > I have applied this patch and G2913 into an updated checkout dir and able to > run a full build with it. With this patch, jaxws-ejb getWSDL() test works > for both Jetty and Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2913) minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2913. Resolution: Fixed thanks. fix is in 513612. -- dims > minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for > Axis2 > --- > > Key: GERONIMO-2913 > URL: https://issues.apache.org/jira/browse/GERONIMO-2913 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: winxp + sun 1.5 SDK >Reporter: Lin Sun > Fix For: 2.0 > > Attachments: G2913.patch > > > This patch contains the following change: > 1) In Axis2 integration code, we use request.getURI().getQuery(), however > null is returned when running jaxws-ejb test as the queryString wasn't set. > The patch will pass the queryString as the parameter when constructing URI. > 2) In our Axis2 integration code, we call request.getContextPath() and it > returns null from JettyEJBWebServiceContext and > /JAXWS-EJB-2.0-snapshot/JAXWSBEAN from TomcatEJBWebServiceContext when > running the jaxws-ejb test case. To me, the tomcat behavior is right. (See > dev list on some discussion of this prob.) There seems to be a bug in Jetty > in request.getContextPath() so I propose to use request.getRequestURI() > instead to temply work around the prob. > Patch has been tested and able to do a full build with it. > Thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2894) Restructure geronimo-axis2 code to split between EJB and POJO containers
[ https://issues.apache.org/jira/browse/GERONIMO-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2894. Resolution: Fixed thanks. fix is in 513612. -- dims > Restructure geronimo-axis2 code to split between EJB and POJO containers > > > Key: GERONIMO-2894 > URL: https://issues.apache.org/jira/browse/GERONIMO-2894 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices > Environment: winxp + sun 1.5 >Reporter: Lin Sun > Attachments: G2894-latest.patch, G2894-new.zip, G2894.patch > > > This is needed as certain methods are POJO container specific, per Jarek's > comment in G2876. > Also attempted to fix the ?wsdl call in EJB mode by stripping the extra > forward slash. ?wsdl still not working yet. current exception is a > Nullpointerexception returned from uri.getQuery(). This is with jetty. > Need to track this one down next. > Checked the POJO mode and jetty was able to return wsdl as the result of > uri.getQuery(). > Tested the above change with all the tests (handlertest, > axis2webservicecontainertest, jax-ws-war and jax-ws-ejb) and also able to do > a full build with the patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2919) use axis2 saaj 1.3 spec jar
[ https://issues.apache.org/jira/browse/GERONIMO-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477174 ] Davanum Srinivas commented on GERONIMO-2919: The last vestige of axis2 dependency in saaj-api was removed with this commit (this morning) http://svn.apache.org/viewvc?view=rev&revision=513354 thanks, dims > use axis2 saaj 1.3 spec jar > --- > > Key: GERONIMO-2919 > URL: https://issues.apache.org/jira/browse/GERONIMO-2919 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0-M3 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 2.0-beta2 > > Attachments: GERONIMO-2919.patch > > > we're using the saaj 1.1 or 1.2 jar from axis1. We need saaj 1.3 support, > lets use the axis2 spec jar for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2915) Disable the call to processHTTPGetRequest to fix the build error
[ https://issues.apache.org/jira/browse/GERONIMO-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477054 ] Davanum Srinivas commented on GERONIMO-2915: Joe, Please hang on. a "mvn deploy" of Axis2 is underway -- dims > Disable the call to processHTTPGetRequest to fix the build error > > > Key: GERONIMO-2915 > URL: https://issues.apache.org/jira/browse/GERONIMO-2915 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: winzp + sun 1.5 >Reporter: Lin Sun > Assigned To: Joe Bohn > Fix For: 2.0 > > > Axis2 team commented out this processHTTPGetRequest method this AM and it > caused a build error! > The quick workaround is to disable the call. I was able to run a full build > with the workaround below and a clean Axis2 repo. > // deal with GET request > /*boolean processed = HTTPTransportUtils.processHTTPGetRequest( > msgContext, > response.getOutputStream(), > soapAction, > path, > configurationContext, > HTTPTransportReceiver.getGetRequestParameters(path));*/ > > boolean processed = false; > Thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2876. Resolution: Fixed Thanks Lin. svn revision 511987 -- dims > Initial web service EJB support for Axis2 > - > > Key: GERONIMO-2876 > URL: https://issues.apache.org/jira/browse/GERONIMO-2876 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Environment: winxp + sun 1.5 >Reporter: Lin Sun > Attachments: G2876-2.patch, G2876.patch > > > This work-in-progress patch tried to port the initial web service ejb support > from CXF to Axis2 (G2850) and here are a few details: > 1) I had a hard time with classexception while working through the two > portinfo classes (org.apache.geronimo.jaxws.PortInfo and > org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of > org.apache.geronimo.axis2.PortInfo for simplicities. > 2) I decided to keep the old Axis structure instead of the new CXF structure > for EJB support, as I envision that all the requests will be handled in one > Axis2WebServiceContainer. > Able to do a full build with the patch.Tested the patch with jax-ws-ejb > test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was > able to see the ejb module loaded and started. However, get the jaxb error: > 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory & package-info not found in > pa > ckage hierachy > 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying > to > invoke service method doService() > org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException > - with linked exception: > [javax.xml.bind.UnmarshalException: unexpected element > (uri:"http://apache.org/g > reeter_control/types", local:"greetMe"). Expected elements are (none)]; > nested e > xception is: > javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException > - with linked exception: > [javax.xml.bind.UnmarshalException: unexpected element > (uri:"http://apache.org/g > reeter_control/types", local:"greetMe"). Expected elements are (none)] > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) > at > org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa > geReceiver.java:147) > Will attempt to fix this tomorrow by supplying the generated ObjectFactory & > package-info classes for jax-ws-ejb test. > Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475874 ] Davanum Srinivas commented on GERONIMO-2876: Looks like i have to wait for a new patch :) thanks, dims > Initial web service EJB support for Axis2 > - > > Key: GERONIMO-2876 > URL: https://issues.apache.org/jira/browse/GERONIMO-2876 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Environment: winxp + sun 1.5 >Reporter: Lin Sun > Attachments: G2876.patch > > > This work-in-progress patch tried to port the initial web service ejb support > from CXF to Axis2 (G2850) and here are a few details: > 1) I had a hard time with classexception while working through the two > portinfo classes (org.apache.geronimo.jaxws.PortInfo and > org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of > org.apache.geronimo.axis2.PortInfo for simplicities. > 2) I decided to keep the old Axis structure instead of the new CXF structure > for EJB support, as I envision that all the requests will be handled in one > Axis2WebServiceContainer. > Able to do a full build with the patch.Tested the patch with jax-ws-ejb > test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was > able to see the ejb module loaded and started. However, get the jaxb error: > 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory & package-info not found in > pa > ckage hierachy > 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying > to > invoke service method doService() > org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException > - with linked exception: > [javax.xml.bind.UnmarshalException: unexpected element > (uri:"http://apache.org/g > reeter_control/types", local:"greetMe"). Expected elements are (none)]; > nested e > xception is: > javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException > - with linked exception: > [javax.xml.bind.UnmarshalException: unexpected element > (uri:"http://apache.org/g > reeter_control/types", local:"greetMe"). Expected elements are (none)] > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) > at > org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa > geReceiver.java:147) > Will attempt to fix this tomorrow by supplying the generated ObjectFactory & > package-info classes for jax-ws-ejb test. > Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2888) Axis2WebServiceContainerTest getting failed due to missing libraries in the classpath
[ https://issues.apache.org/jira/browse/GERONIMO-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475873 ] Davanum Srinivas commented on GERONIMO-2888: Fixed in svn revision 511793. thanks, dims > Axis2WebServiceContainerTest getting failed due to missing libraries in the > classpath > - > > Key: GERONIMO-2888 > URL: https://issues.apache.org/jira/browse/GERONIMO-2888 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2888.patch > > > Geronimo Axis2 related Axis2WebServiceContainerTest getting failed due to the > missing libraries in the classpath when it get invokes. The given patch will > add to libraries to the pom.xml. > Additionally includes the changes which were submitted under GERONIMO-2877 > too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2888) Axis2WebServiceContainerTest getting failed due to missing libraries in the classpath
[ https://issues.apache.org/jira/browse/GERONIMO-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2888. Resolution: Fixed > Axis2WebServiceContainerTest getting failed due to missing libraries in the > classpath > - > > Key: GERONIMO-2888 > URL: https://issues.apache.org/jira/browse/GERONIMO-2888 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2888.patch > > > Geronimo Axis2 related Axis2WebServiceContainerTest getting failed due to the > missing libraries in the classpath when it get invokes. The given patch will > add to libraries to the pom.xml. > Additionally includes the changes which were submitted under GERONIMO-2877 > too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2877) Minor improvement to Axis2 Jaxws Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2877. Resolution: Fixed > Minor improvement to Axis2 Jaxws Integration > > > Key: GERONIMO-2877 > URL: https://issues.apache.org/jira/browse/GERONIMO-2877 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera >Priority: Minor > Attachments: GERONIMO-2877-2.patch, GERONIMO-2877.patch > > > This patch will improve the source code of the Axis2 JAXWS integration in > following areas. > 1. Remove unnecessary Definition object used in the Axis2ServiceGenerator > class. > 2. Source code formatting ( I am totally not sure this source code formatting > getting messing up. If somebody please point me out if this is due to a > problem of patches I have been submitting or not). > Thanks, > Lasantha -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2877) Minor improvement to Axis2 Jaxws Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475872 ] Davanum Srinivas commented on GERONIMO-2877: Applied as part of svn revision 511793 for GERONIMO-2888 thanks, dims > Minor improvement to Axis2 Jaxws Integration > > > Key: GERONIMO-2877 > URL: https://issues.apache.org/jira/browse/GERONIMO-2877 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera >Priority: Minor > Attachments: GERONIMO-2877-2.patch, GERONIMO-2877.patch > > > This patch will improve the source code of the Axis2 JAXWS integration in > following areas. > 1. Remove unnecessary Definition object used in the Axis2ServiceGenerator > class. > 2. Source code formatting ( I am totally not sure this source code formatting > getting messing up. If somebody please point me out if this is due to a > problem of patches I have been submitting or not). > Thanks, > Lasantha -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2790) Remove Depricated addOperation from GBeans
[ https://issues.apache.org/jira/browse/GERONIMO-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475870 ] Davanum Srinivas commented on GERONIMO-2790: Close as per submitter's comment. -- dims > Remove Depricated addOperation from GBeans > -- > > Key: GERONIMO-2790 > URL: https://issues.apache.org/jira/browse/GERONIMO-2790 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2790.patch > > > I saw lot of deprecated methods in every GBean. So following is a patch to > remove it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2790) Remove Depricated addOperation from GBeans
[ https://issues.apache.org/jira/browse/GERONIMO-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2790. -- Resolution: Fixed > Remove Depricated addOperation from GBeans > -- > > Key: GERONIMO-2790 > URL: https://issues.apache.org/jira/browse/GERONIMO-2790 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2790.patch > > > I saw lot of deprecated methods in every GBean. So following is a patch to > remove it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2852) Test Case to Axis2WebServiceContainer
[ https://issues.apache.org/jira/browse/GERONIMO-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474609 ] Davanum Srinivas commented on GERONIMO-2852: Fixed in SVN revision 509806 thanks, dims > Test Case to Axis2WebServiceContainer > - > > Key: GERONIMO-2852 > URL: https://issues.apache.org/jira/browse/GERONIMO-2852 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2852-2.patch, GERONIMO-2852.patch > > > This is initial implementation of the test coverage of the > Axis2WebServiceContainer. It will add the test implementation to the Doc Lit > WSDL provided situation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2852) Test Case to Axis2WebServiceContainer
[ https://issues.apache.org/jira/browse/GERONIMO-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2852. Resolution: Fixed > Test Case to Axis2WebServiceContainer > - > > Key: GERONIMO-2852 > URL: https://issues.apache.org/jira/browse/GERONIMO-2852 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2852-2.patch, GERONIMO-2852.patch > > > This is initial implementation of the test coverage of the > Axis2WebServiceContainer. It will add the test implementation to the Doc Lit > WSDL provided situation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2850) CXF: initial web service support for EJBs
[ https://issues.apache.org/jira/browse/GERONIMO-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474576 ] Davanum Srinivas commented on GERONIMO-2850: Fixed in svn revision 509765 thanks, dims > CXF: initial web service support for EJBs > - > > Key: GERONIMO-2850 > URL: https://issues.apache.org/jira/browse/GERONIMO-2850 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Assigned To: Davanum Srinivas > Attachments: GERONIMO-2850.patch > > > The attached patch adds basic web services support for EJBs. The patch > contains refactored CXF code. Please note that CXFWebServiceContext.java and > CXFWebServiceContainerFactoryGBean.java files in geronimo-cxf module have > been removed. Also because I still couldn't properly figure out the > dependency issues, the cxf/car module will have an automatic dependency on > openejb/car module. Hopefully that will get resolved in the future. Also, the > patch updates the config.xml file of the assemblies to turn off loading of > axis2-deployer module (to prevent conflicts between axis2 and cxf deployers). > Again, this is just a temporary measure. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2850) CXF: initial web service support for EJBs
[ https://issues.apache.org/jira/browse/GERONIMO-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2850. Resolution: Fixed > CXF: initial web service support for EJBs > - > > Key: GERONIMO-2850 > URL: https://issues.apache.org/jira/browse/GERONIMO-2850 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Assigned To: Davanum Srinivas > Attachments: GERONIMO-2850.patch > > > The attached patch adds basic web services support for EJBs. The patch > contains refactored CXF code. Please note that CXFWebServiceContext.java and > CXFWebServiceContainerFactoryGBean.java files in geronimo-cxf module have > been removed. Also because I still couldn't properly figure out the > dependency issues, the cxf/car module will have an automatic dependency on > openejb/car module. Hopefully that will get resolved in the future. Also, the > patch updates the config.xml file of the assemblies to turn off loading of > axis2-deployer module (to prevent conflicts between axis2 and cxf deployers). > Again, this is just a temporary measure. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2849) service-ref app client test
[ https://issues.apache.org/jira/browse/GERONIMO-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474575 ] Davanum Srinivas commented on GERONIMO-2849: Fixed in svn revision 509765 thanks, dims > service-ref app client test > --- > > Key: GERONIMO-2849 > URL: https://issues.apache.org/jira/browse/GERONIMO-2849 > Project: Geronimo > Issue Type: Test > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Assigned To: Davanum Srinivas > Attachments: GERONIMO-2849.patch, GERONIMO-2849.patch > > > The attached patch contains service-ref test for app client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2849) service-ref app client test
[ https://issues.apache.org/jira/browse/GERONIMO-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2849. Resolution: Fixed > service-ref app client test > --- > > Key: GERONIMO-2849 > URL: https://issues.apache.org/jira/browse/GERONIMO-2849 > Project: Geronimo > Issue Type: Test > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Assigned To: Davanum Srinivas > Attachments: GERONIMO-2849.patch, GERONIMO-2849.patch > > > The attached patch contains service-ref test for app client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2850) CXF: initial web service support for EJBs
[ https://issues.apache.org/jira/browse/GERONIMO-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated GERONIMO-2850: --- Assignee: Davanum Srinivas > CXF: initial web service support for EJBs > - > > Key: GERONIMO-2850 > URL: https://issues.apache.org/jira/browse/GERONIMO-2850 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Assigned To: Davanum Srinivas > Attachments: GERONIMO-2850.patch > > > The attached patch adds basic web services support for EJBs. The patch > contains refactored CXF code. Please note that CXFWebServiceContext.java and > CXFWebServiceContainerFactoryGBean.java files in geronimo-cxf module have > been removed. Also because I still couldn't properly figure out the > dependency issues, the cxf/car module will have an automatic dependency on > openejb/car module. Hopefully that will get resolved in the future. Also, the > patch updates the config.xml file of the assemblies to turn off loading of > axis2-deployer module (to prevent conflicts between axis2 and cxf deployers). > Again, this is just a temporary measure. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2849) service-ref app client test
[ https://issues.apache.org/jira/browse/GERONIMO-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated GERONIMO-2849: --- Assignee: Davanum Srinivas > service-ref app client test > --- > > Key: GERONIMO-2849 > URL: https://issues.apache.org/jira/browse/GERONIMO-2849 > Project: Geronimo > Issue Type: Test > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Assigned To: Davanum Srinivas > Attachments: GERONIMO-2849.patch, GERONIMO-2849.patch > > > The attached patch contains service-ref test for app client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2850) CXF: initial web service support for EJBs
[ https://issues.apache.org/jira/browse/GERONIMO-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474565 ] Davanum Srinivas commented on GERONIMO-2850: Jarek, Just saw the "24 hour branch notice (or thereabouts)" notice from Matt. I don't think this is a fair check-in to make since it means that the branch will have Axis2 disabled by default for the release. We need to find a better alternative ASAP if we have to make the deadline. thanks, dims > CXF: initial web service support for EJBs > - > > Key: GERONIMO-2850 > URL: https://issues.apache.org/jira/browse/GERONIMO-2850 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2850.patch > > > The attached patch adds basic web services support for EJBs. The patch > contains refactored CXF code. Please note that CXFWebServiceContext.java and > CXFWebServiceContainerFactoryGBean.java files in geronimo-cxf module have > been removed. Also because I still couldn't properly figure out the > dependency issues, the cxf/car module will have an automatic dependency on > openejb/car module. Hopefully that will get resolved in the future. Also, the > patch updates the config.xml file of the assemblies to turn off loading of > axis2-deployer module (to prevent conflicts between axis2 and cxf deployers). > Again, this is just a temporary measure. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2852) Test Case to Axis2WebServiceContainer
[ https://issues.apache.org/jira/browse/GERONIMO-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474564 ] Davanum Srinivas commented on GERONIMO-2852: Lasantha, Patch is incomplete...missing a wsdl at the least. thanks, dims > Test Case to Axis2WebServiceContainer > - > > Key: GERONIMO-2852 > URL: https://issues.apache.org/jira/browse/GERONIMO-2852 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2852.patch > > > This is initial implementation of the test coverage of the > Axis2WebServiceContainer. It will add the test implementation to the Doc Lit > WSDL provided situation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2824) port the handler tests from CXF to Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473960 ] Davanum Srinivas commented on GERONIMO-2824: Already checked in. Forgot to close the issue. thanks, dims > port the handler tests from CXF to Axis2 > > > Key: GERONIMO-2824 > URL: https://issues.apache.org/jira/browse/GERONIMO-2824 > Project: Geronimo > Issue Type: Test > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: winxp + sun 1.5 >Reporter: Lin Sun > Fix For: 2.0 > > Attachments: geronimo-axis2-test.zip > > > Port the handler tests from CXF to Axis2. > Patch is tested with Axis2 and all handler tests pass! > To apply patch just unzip it to modules\geronimo-axis2\src directory. > thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2824) port the handler tests from CXF to Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2824. Resolution: Fixed > port the handler tests from CXF to Axis2 > > > Key: GERONIMO-2824 > URL: https://issues.apache.org/jira/browse/GERONIMO-2824 > Project: Geronimo > Issue Type: Test > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: winxp + sun 1.5 >Reporter: Lin Sun > Fix For: 2.0 > > Attachments: geronimo-axis2-test.zip > > > Port the handler tests from CXF to Axis2. > Patch is tested with Axis2 and all handler tests pass! > To apply patch just unzip it to modules\geronimo-axis2\src directory. > thanks, Lin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2842) Geronimo Axis2 - JAXWS Web Services are not working for WSDL provided situation
[ https://issues.apache.org/jira/browse/GERONIMO-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473958 ] Davanum Srinivas commented on GERONIMO-2842: Fixed in 508812 thanks, dims > Geronimo Axis2 - JAXWS Web Services are not working for WSDL provided > situation > --- > > Key: GERONIMO-2842 > URL: https://issues.apache.org/jira/browse/GERONIMO-2842 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2842-2.patch, GERONIMO-2842.patch > > > JAXWS webservices are not working in WSDL provided situation. This has been > working for a previous release & missing right now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2842) Geronimo Axis2 - JAXWS Web Services are not working for WSDL provided situation
[ https://issues.apache.org/jira/browse/GERONIMO-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2842. Resolution: Fixed > Geronimo Axis2 - JAXWS Web Services are not working for WSDL provided > situation > --- > > Key: GERONIMO-2842 > URL: https://issues.apache.org/jira/browse/GERONIMO-2842 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2842-2.patch, GERONIMO-2842.patch > > > JAXWS webservices are not working in WSDL provided situation. This has been > working for a previous release & missing right now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2845) Axis2 JAXWS handle document style WSDLs
[ https://issues.apache.org/jira/browse/GERONIMO-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473957 ] Davanum Srinivas commented on GERONIMO-2845: Fixed in 508812 thanks, dims > Axis2 JAXWS handle document style WSDLs > --- > > Key: GERONIMO-2845 > URL: https://issues.apache.org/jira/browse/GERONIMO-2845 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2845.patch > > > Following are the some highlights of the patch. > 1. This will handle more generic way of Document style WSDLs for the when it > is not given as annotations. > 2. Remove some deprecated code. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2845) Axis2 JAXWS handle document style WSDLs
[ https://issues.apache.org/jira/browse/GERONIMO-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2845. Resolution: Fixed > Axis2 JAXWS handle document style WSDLs > --- > > Key: GERONIMO-2845 > URL: https://issues.apache.org/jira/browse/GERONIMO-2845 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2845.patch > > > Following are the some highlights of the patch. > 1. This will handle more generic way of Document style WSDLs for the when it > is not given as annotations. > 2. Remove some deprecated code. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2840) Minor fixes
[ https://issues.apache.org/jira/browse/GERONIMO-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2840. Resolution: Fixed Fixed in 508298 > Minor fixes > --- > > Key: GERONIMO-2840 > URL: https://issues.apache.org/jira/browse/GERONIMO-2840 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Jarek Gawor > Attachments: GERONIMO-2840.patch > > > The attached patch contains the following minor fixes: > 1) Fix for JettyEJBWebServiceContext.Request.getURI(). It was returning > client's host/port information instead of server's. Also, ?wsdl request would > result in an exception thrown without jettyRequest.setHandled(true); call. > 2) Fix in EjbModuleBuilder.java. It was passing invalid environment to module > builder extensions. > 3) Added empty constructor to EjbDeployment.java. It is required when a type > is used as a reference for a gbean. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2836) Improvements for CXF integration
[ https://issues.apache.org/jira/browse/GERONIMO-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2836. Resolution: Fixed Fixed in 508298 > Improvements for CXF integration > > > Key: GERONIMO-2836 > URL: https://issues.apache.org/jira/browse/GERONIMO-2836 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2836.patch > > > The following patch includes a number of small improvements to CXF > integration: > 1) SOAP bindings are now show up in the dynamically generated WSDL. > 2) The soap:address location URL of the service is now properly returned > (without ?wsdl) > 3) Improved HandlerChains support to handle protocol bindings specified > either as an URI or a token. > 4) HandlerChains should be properly filtered (based on service qname, port > qname, and protocol binding) now on the server-side (namespace checking is > not done) > 5) HTTP GET on a service now returns 'Hi, I'm a web service' type of thing > instead of an error. > 6) Basic app client support (service-ref) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2830) Updated dependencies for ejb-based tests
[ https://issues.apache.org/jira/browse/GERONIMO-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2830. Resolution: Fixed Fixed in 508298 > Updated dependencies for ejb-based tests > > > Key: GERONIMO-2830 > URL: https://issues.apache.org/jira/browse/GERONIMO-2830 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Reporter: Jarek Gawor > Attachments: GERONIMO-2830.patch > > > Standalone test clients require a new openejb-client dependency after the > openejb2 to openejb3 switch. The patch adds these dependencies. These tests > still fail because of some JNDI lookup issues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2826) Test case to test invocations using service-ref
[ https://issues.apache.org/jira/browse/GERONIMO-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2826. Resolution: Fixed Fixed in 508298 > Test case to test invocations using service-ref > --- > > Key: GERONIMO-2826 > URL: https://issues.apache.org/jira/browse/GERONIMO-2826 > Project: Geronimo > Issue Type: Test > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2826.patch > > > The attached patch includes a new test case that invokes a web services from > within a JSP page. The JSP page obtains the looks up the service-ref in JNDI. > Currently, the test case will pass with CXF even though the service > invocation returns incorrect value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2825) CXF and spring version update
[ https://issues.apache.org/jira/browse/GERONIMO-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2825. Resolution: Fixed Fixed in 508298 thanks, dims > CXF and spring version update > - > > Key: GERONIMO-2825 > URL: https://issues.apache.org/jira/browse/GERONIMO-2825 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2825.patch > > > Geronimo currently uses outdated versions of CXF and Spring. The attached > patch upgrades the version of CXF and Spring and fixes minor package name > change in CXF code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2822) Axis2 Integration - Get invoke() method working for WSDL provided scenario
[ https://issues.apache.org/jira/browse/GERONIMO-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472376 ] Davanum Srinivas commented on GERONIMO-2822: fixed in svn revision 506561 > Axis2 Integration - Get invoke() method working for WSDL provided scenario > -- > > Key: GERONIMO-2822 > URL: https://issues.apache.org/jira/browse/GERONIMO-2822 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2822.patch > > > This patch will get the invoke() method working for WSDL provided scenario. > Make sure to generation JAXB related files & add them in to you archive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2822) Axis2 Integration - Get invoke() method working for WSDL provided scenario
[ https://issues.apache.org/jira/browse/GERONIMO-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2822. -- Resolution: Fixed > Axis2 Integration - Get invoke() method working for WSDL provided scenario > -- > > Key: GERONIMO-2822 > URL: https://issues.apache.org/jira/browse/GERONIMO-2822 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2822.patch > > > This patch will get the invoke() method working for WSDL provided scenario. > Make sure to generation JAXB related files & add them in to you archive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2813) SwitchingServiceRefBuilder environment fix
[ https://issues.apache.org/jira/browse/GERONIMO-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472375 ] Davanum Srinivas commented on GERONIMO-2813: Fixed in svn revision 505359 > SwitchingServiceRefBuilder environment fix > -- > > Key: GERONIMO-2813 > URL: https://issues.apache.org/jira/browse/GERONIMO-2813 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2813.patch > > > The SwitchingServiceRefBuilder was merging the environment dependency > incorrectly (at a wrong time) and therefore the dependency was not always > added to the classloader. The attached patch fixes that issue. The solution > is not perfect as access to the classloader is required at the > buildEnvironment() stage to load the classes to determine what type of > reference it is (JAX-RPC or JAX-WS). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2813) SwitchingServiceRefBuilder environment fix
[ https://issues.apache.org/jira/browse/GERONIMO-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2813. -- Resolution: Fixed > SwitchingServiceRefBuilder environment fix > -- > > Key: GERONIMO-2813 > URL: https://issues.apache.org/jira/browse/GERONIMO-2813 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2813.patch > > > The SwitchingServiceRefBuilder was merging the environment dependency > incorrectly (at a wrong time) and therefore the dependency was not always > added to the classloader. The attached patch fixes that issue. The solution > is not perfect as access to the classloader is required at the > buildEnvironment() stage to load the classes to determine what type of > reference it is (JAX-RPC or JAX-WS). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2821) SwitchingServiceRefBuilder environment fix (take 2)
[ https://issues.apache.org/jira/browse/GERONIMO-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2821. Resolution: Fixed Applied in svn revision 506311. thanks, dims > SwitchingServiceRefBuilder environment fix (take 2) > --- > > Key: GERONIMO-2821 > URL: https://issues.apache.org/jira/browse/GERONIMO-2821 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: naming >Reporter: Jarek Gawor > Attachments: GERONIMO-2821.patch > > > Always merge both environments since we don't have the full deployment > descriptor at the buildEnvironment() point. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2812) Axis2 integration - getWSDL with new Axis2 Version
[ https://issues.apache.org/jira/browse/GERONIMO-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2812. -- Resolution: Fixed Lasantha, Since i already applied GERONIMO-2811, am not checking in this one. ok? thanks, dims > Axis2 integration - getWSDL with new Axis2 Version > -- > > Key: GERONIMO-2812 > URL: https://issues.apache.org/jira/browse/GERONIMO-2812 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2812.patch > > > Both getWSDL & invoke methods of Axis2WebServiceContainer fails with new > Axis2 snapshot. This simple patch will address the issue as given way. > 1. Change the way of serviceName created using more generalize way. > 2. Remove the HTTPConstants.MC_HTTP_SERVLETREQUEST property from > MessageContext since it gives CCE problem in the Axis2 side. > Still we have to find solution to the invoke() method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2807) CXF: initial service-ref support
[ https://issues.apache.org/jira/browse/GERONIMO-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2807. -- Resolution: Fixed Fixed in svn revision 505171. thanks, dims > CXF: initial service-ref support > > > Key: GERONIMO-2807 > URL: https://issues.apache.org/jira/browse/GERONIMO-2807 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2807.2.patch, GERONIMO-2807.patch > > > The attached patch contains initial support for service-ref entries for web > services. Even though the actual invocations will not currently work with CXF > (upgrade needed) this patch has most of the necessary bits to make that work. > The code is not fully complete yet and therefore some bits remain the cxf > package but could be factored out later into the jaxws* modules. > The patch also contains some minor dependency updates. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2811) got runtimeexception when processing soap request in doservice2
[
https://issues.apache.org/jira/browse/GERONIMO-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved GERONIMO-2811.
Resolution: Fixed
Nice! fixed in 504879.
thanks,
dims
> got runtimeexception when processing soap request in doservice2
> ---
>
> Key: GERONIMO-2811
> URL: https://issues.apache.org/jira/browse/GERONIMO-2811
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
> Environment: winxp + sun 1.5
>Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2811.patch
>
>
> Some code change (from Axis2) recently caused the code below to add 2
> services to axis configurationcontext.
> configurationContext.getAxisConfiguration().addService(service);
> AxisConfiguration.addService(service) calls
> AxisConfiguration.addServiceGroup(...) method and inside the
> addServiceGroup method:
>if (endpoints.isEmpty()) {
> allServices.put(serviceName, axisService);
> } else if (endpoints.size() == 1) {
> // if we have one endpoint, just process it. This is special
> case as this will be the case
> // most of the time
> allServices.put(serviceName, axisService);
> allServices.put(serviceName + "." +
> axisService.getEndpointName(), axisService);
> It is putting 2 axisServices there which results services.size() = 2 in in
> doservice2() call, thus runtimeexception is thrown.
> I haven't been able to identify where the change came from. It can be they
> changed the way how wsdlBuilder.populateService() works
> so that endpoints is set to something with the new code while it was empty
> before.
> The fix is to determine axisservice based on the endpointclassname which
> seems a more robust way. I have tested the fix and was able to run .wsdl
> test with jax-ws test.
> Also was able to run a full build with the latest trunk successfully.:)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2810) Fix build error at getting incubator-woden
[ https://issues.apache.org/jira/browse/GERONIMO-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2810. Resolution: Fixed switch versions (svn revision 504599). Need it for runtime :) -- dims > Fix build error at getting incubator-woden > --- > > Key: GERONIMO-2810 > URL: https://issues.apache.org/jira/browse/GERONIMO-2810 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Environment: winxp + sun 1.5 >Reporter: Lin Sun >Priority: Critical > > My build run fine with a clean repo at the end. :-) > Hi, I am seeing a build error at getting incubator-woden (see below). I > removed the reference to the jar in root pom.xml and configs\axis2\pom.xml > and my build is still running. I don't see a need why we need them. :-) > Lin > -- > 1) incubator-woden:woden:jar:1.0.0M6 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=incubator-woden -DartifactId=woden \ > -Dversion=1.0.0M6 -Dpackaging=jar -Dfile=/path/to/file > Path to dependency: > 1) org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT > 2) incubator-woden:woden:jar:1.0.0M6 > -- > 1 required artifact is missing. > for artifact: > org.apache.geronimo.configs:axis2:car:2.0-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > codehaus (http://repository.codehaus.org), > apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), > codehaus-snapshots (http://snapshots.repository.codehaus.org), > apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), > axis2-m2-repo (http://ws.zones.apache.org/repository2/), > tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2798) Axis2 Integration - User JAXWS common module to implementation
[ https://issues.apache.org/jira/browse/GERONIMO-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470644 ] Davanum Srinivas commented on GERONIMO-2798: Lasantha, If you specify just the axis2-jaxws ,does it not pick up all the dependent jars? If not, then you can leave them in there. thanks, dims > Axis2 Integration - User JAXWS common module to implementation > --- > > Key: GERONIMO-2798 > URL: https://issues.apache.org/jira/browse/GERONIMO-2798 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2798.patch > > > Currently there is a JAXWS common module in the Geronimo. We will use it to > the Axis2 integration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2802) Axis2 integration - allow users to deploy jax-ws test, log the exceptions, set a few more messagecontext properties
[ https://issues.apache.org/jira/browse/GERONIMO-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2802. -- Resolution: Fixed Thanks Lin. Fixed in svn revision 504138. -- dims > Axis2 integration - allow users to deploy jax-ws test, log the exceptions, > set a few more messagecontext properties > --- > > Key: GERONIMO-2802 > URL: https://issues.apache.org/jira/browse/GERONIMO-2802 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices > Environment: winxp + sun 1.5 jdk >Reporter: Lin Sun > Fix For: 2.0 > > Attachments: G2802.patch > > > This patch contains the following updates to current axis2 integration code: > 1) removed a few unnecessary imports > 2) had to comment out a line where we setEndInterface to webserviceAnnot, as > this is causing an axis2 validation error upon the war deployment. With this > change, I was able to run .wsdl request. > 3) the code didn't set setAxisService on the messagecontext inside of > doservice2(). This caused a "The requested service could not be found" error > from axis2 when processing post request . > 4) also set a few other messagecontext properties and added the > Axis2RequestResponseTransport inner class that can allow for an > acknowledgement to be transmitted before processing has completed and also > allow for processing to be paused and resumed on a separate thread without > having a response be sent back. > 5) also tried to log the exceptions when statuscode=500 during doservice > calls. > The most recent error is: > org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException > - with linked exception: > [javax.xml.bind.UnmarshalException: unexpected element > (uri:"http://hello_world_ > soap_http.apache.org", local:"greetMe"). Expected elements are (none)]; > nested e > xception is: > javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException > - with linked exception: > Which i posted to axis2-dev list and awaiting for help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2798) Axis2 Integration - User JAXWS common module to implementation
[ https://issues.apache.org/jira/browse/GERONIMO-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470574 ] Davanum Srinivas commented on GERONIMO-2798: Yes, please. Also, please don't all the unnecessary entries in pom.xml. specifying axis2-jaxws should pick up the rest. thanks, dims > Axis2 Integration - User JAXWS common module to implementation > --- > > Key: GERONIMO-2798 > URL: https://issues.apache.org/jira/browse/GERONIMO-2798 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2798.patch > > > Currently there is a JAXWS common module in the Geronimo. We will use it to > the Axis2 integration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2797) Remove CXF Factory Name from JAXWSServiceBuilder
[ https://issues.apache.org/jira/browse/GERONIMO-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470219 ] Davanum Srinivas commented on GERONIMO-2797: Fixed in svn revision 503689 thanks, dims > Remove CXF Factory Name from JAXWSServiceBuilder > > > Key: GERONIMO-2797 > URL: https://issues.apache.org/jira/browse/GERONIMO-2797 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2797.patch > > > JAXWSServiceBuilder for any SOAP engine. Remove cxf related hard coded name > from it. ;) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2797) Remove CXF Factory Name from JAXWSServiceBuilder
[ https://issues.apache.org/jira/browse/GERONIMO-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2797. -- Resolution: Fixed > Remove CXF Factory Name from JAXWSServiceBuilder > > > Key: GERONIMO-2797 > URL: https://issues.apache.org/jira/browse/GERONIMO-2797 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2797.patch > > > JAXWSServiceBuilder for any SOAP engine. Remove cxf related hard coded name > from it. ;) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2796) HandlerResolver for CXF web servies & other improvements
[ https://issues.apache.org/jira/browse/GERONIMO-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470217 ] Davanum Srinivas commented on GERONIMO-2796: Fixed in SVN revision 503682. thanks, dims > HandlerResolver for CXF web servies & other improvements > > > Key: GERONIMO-2796 > URL: https://issues.apache.org/jira/browse/GERONIMO-2796 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2796.patch > > > The attached patch contains HandlerResolver implementation and tests used by > clients and on server-side. Also, the CXFServiceRefBuilder code was factored > out - key parts moved into geronimo-jaxws-builder module. Code in the > geronimo-jaxws module was also factored out a bit and improved. > Btw, please run dos2unix conversion on all files in the > geronimo-jaxws-builder and geronimo-jaxws modules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2796) HandlerResolver for CXF web servies & other improvements
[ https://issues.apache.org/jira/browse/GERONIMO-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2796. -- Resolution: Fixed > HandlerResolver for CXF web servies & other improvements > > > Key: GERONIMO-2796 > URL: https://issues.apache.org/jira/browse/GERONIMO-2796 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2796.patch > > > The attached patch contains HandlerResolver implementation and tests used by > clients and on server-side. Also, the CXFServiceRefBuilder code was factored > out - key parts moved into geronimo-jaxws-builder module. Code in the > geronimo-jaxws module was also factored out a bit and improved. > Btw, please run dos2unix conversion on all files in the > geronimo-jaxws-builder and geronimo-jaxws modules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2791) Switching ServiceRef naming builder
[ https://issues.apache.org/jira/browse/GERONIMO-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2791. -- Resolution: Fixed Applied in 502626. thanks, dims > Switching ServiceRef naming builder > --- > > Key: GERONIMO-2791 > URL: https://issues.apache.org/jira/browse/GERONIMO-2791 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-beta1 >Reporter: Jarek Gawor > Attachments: GERONIMO-2791.patch > > > Since NamingBuilderCollection/AbstractBuilderCollection does not allow two > naming builders to be registered for the same element in the deployment > descriptor (and even if this was allowed, one naming builder might accept > some values that the other rejects), a SwitchingServiceRefBuilder naming > builder was added to handle service-ref elements. The service-ref elements > can specify both JAX-RPC and JAX-WS endpoints. JAX-RCP endpoints are handled > by Axis1 while JAX-WS endpoints can either be handled by CXF or Axis2. So the > SwitchingServiceRefBuilder forwards the requests to the appropriate builder > by figuring out what sort of endpoint is specified in the service-ref > element. > The attached patch contains the SwitchingServiceRefBuilder code, as well as > updates to the Axis1ServiceRefBuilder, and a skeleton code for > CXFServiceRefBuilder (and appropriate plan updates to use the > SwitchingServiceRefBuilder). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2791) Switching ServiceRef naming builder
[ https://issues.apache.org/jira/browse/GERONIMO-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469683 ] Davanum Srinivas commented on GERONIMO-2791: Jarek, CXFServiceRefBuilder is not at all dependent on CXF. Could you please move it to geronimo-jaxws module and cut a fresh patch? thanks, dims > Switching ServiceRef naming builder > --- > > Key: GERONIMO-2791 > URL: https://issues.apache.org/jira/browse/GERONIMO-2791 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-beta1 >Reporter: Jarek Gawor > Attachments: GERONIMO-2791.patch > > > Since NamingBuilderCollection/AbstractBuilderCollection does not allow two > naming builders to be registered for the same element in the deployment > descriptor (and even if this was allowed, one naming builder might accept > some values that the other rejects), a SwitchingServiceRefBuilder naming > builder was added to handle service-ref elements. The service-ref elements > can specify both JAX-RPC and JAX-WS endpoints. JAX-RCP endpoints are handled > by Axis1 while JAX-WS endpoints can either be handled by CXF or Axis2. So the > SwitchingServiceRefBuilder forwards the requests to the appropriate builder > by figuring out what sort of endpoint is specified in the service-ref > element. > The attached patch contains the SwitchingServiceRefBuilder code, as well as > updates to the Axis1ServiceRefBuilder, and a skeleton code for > CXFServiceRefBuilder (and appropriate plan updates to use the > SwitchingServiceRefBuilder). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2786) Unable to deploy a web app to current trunk build of geronimo (rev 501640)
[ https://issues.apache.org/jira/browse/GERONIMO-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2786. Resolution: Fixed fixed in svn revision 502517. thanks, dims > Unable to deploy a web app to current trunk build of geronimo (rev 501640) > -- > > Key: GERONIMO-2786 > URL: https://issues.apache.org/jira/browse/GERONIMO-2786 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.0 > Environment: Linux > Java 1.5.0_8 >Reporter: Jay D. McHugh > Attachments: GERONIMO-2786.patch, simple.war > > > I tried to deploy a war file that I have been able to deploy previously. > But now, the deploy fails (both from the command line and from the console) > with the following stacktrace: > Failed to expand the module archive > org.apache.geronimo.common.DeploymentException: Failed to expand the module > archive > at > org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.discoverWebServices(JAXWSServiceBuilder.java:123) > at > org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder.findWebServices(JAXWSServiceBuilder.java:79) > at > org.apache.geronimo.jaxws.builder.JAXWSServiceBuilder$$FastClassByCGLIB$$5b2252ff.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.j2ee.deployment.WebServiceBuilder$$EnhancerByCGLIB$$230eff72.findWebServices() > at > org.apache.geronimo.tomcat.deployment.TomcatModuleBuilder.createModule(TomcatModuleBuilder.java:193) > at > org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createModule(AbstractWebModuleBuilder.java:154) > at > org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder$$FastClassByCGLIB$$8523248f.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$267bf04f.createModule() > at > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder.createModule(SwitchingModuleBuilder.java:94) > at > org.apache.geronimo.j2ee.deployment.SwitchingModuleBuilder$$FastClassByCGLIB$$d0c31844.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.j2ee.deployment.ModuleBuilder$$EnhancerByCGLIB$$267bf04f.createModule() > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.java:269) > at > org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) > at > org.apache.geronimo.gb
[jira] Commented: (GERONIMO-2493) Integrate Axis2 webservices
[ https://issues.apache.org/jira/browse/GERONIMO-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469220 ] Davanum Srinivas commented on GERONIMO-2493: Closing catch-all items. Since we are using specific jiras for bugs/features now. > Integrate Axis2 webservices > --- > > Key: GERONIMO-2493 > URL: https://issues.apache.org/jira/browse/GERONIMO-2493 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 1.2 >Reporter: David Jencks > Fix For: 2.0 > > > Integrate axis 2 for webservices. Probably at least 3 steps > - pojo ws > - ejb ws > - ws client -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2493) Integrate Axis2 webservices
[ https://issues.apache.org/jira/browse/GERONIMO-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2493. -- Resolution: Fixed > Integrate Axis2 webservices > --- > > Key: GERONIMO-2493 > URL: https://issues.apache.org/jira/browse/GERONIMO-2493 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 1.2 >Reporter: David Jencks > Fix For: 2.0 > > > Integrate axis 2 for webservices. Probably at least 3 steps > - pojo ws > - ejb ws > - ws client -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2492) Integrate CXF webservices
[ https://issues.apache.org/jira/browse/GERONIMO-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2492. -- Resolution: Fixed > Integrate CXF webservices > - > > Key: GERONIMO-2492 > URL: https://issues.apache.org/jira/browse/GERONIMO-2492 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 1.2 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 2.0-M2 > > > Integrate CXF for webservices. Probably at least 3 steps > - pojo ws > - ejb ws > - ws client > There's a early version of a celtix-geronimo deployer we can try updating. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2492) Integrate CXF webservices
[ https://issues.apache.org/jira/browse/GERONIMO-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469219 ] Davanum Srinivas commented on GERONIMO-2492: Closing catch-all items. Since we are using specific jiras for bugs/features now. > Integrate CXF webservices > - > > Key: GERONIMO-2492 > URL: https://issues.apache.org/jira/browse/GERONIMO-2492 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 1.2 >Reporter: David Jencks > Assigned To: David Jencks > Fix For: 2.0-M2 > > > Integrate CXF for webservices. Probably at least 3 steps > - pojo ws > - ejb ws > - ws client > There's a early version of a celtix-geronimo deployer we can try updating. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2724) create axis2 config and axis2-deployer config folders
[ https://issues.apache.org/jira/browse/GERONIMO-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469218 ] Davanum Srinivas commented on GERONIMO-2724: Already fixed. > create axis2 config and axis2-deployer config folders > - > > Key: GERONIMO-2724 > URL: https://issues.apache.org/jira/browse/GERONIMO-2724 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: Winxp + sun 1.5 JDK >Reporter: Lin Sun > Attachments: g2724.zip > > > This is a patch on top of G2717 to create axis2 config and axis2-deployer > config based on the two cxf config modules. I also enabled the > modules\pom.xml + configs\pom.xml to include the two axis2 modules and two > axis2 configs. I tried to remove some unnecessary dependencies in > modules\geronimo-axis2\pom.xml to keep it as simple as possible. > This built fine on my machine (patch created against revision 494904). > After a successful build, I tried to turn on the axis2-deployer module in > config.xml in jetty-jee5 assembly, but the axis2-deployer module failed to > start. Here's the stack trace: > [*- ] 60% 24s Startup failed > org.apache.geronimo.kernel.config.LifecycleException: load of > org.apache.geronim > o.configs/axis2-deployer/2.0-SNAPSHOT/car failed > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > iguration(SimpleConfigurationManager.java:271) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > iguration(SimpleConfigurationManager.java:250) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConf > iguration(KernelConfigurationManager.java:112) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastCla > ssByCGLIB$$b117102f.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod > Invoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio > n.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. > java:820) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5 > 7) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat > ionInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro > xyMethodInterceptor.java:96) > at > org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan > cerByCGLIB$$854c5ac.loadConfiguration() > at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:283) > at org.apache.geronimo.system.main.Daemon.(Daemon.java:74) > at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366) > Caused by: org.apache.geronimo.kernel.config.NoSuchConfigException: > org.apache.g > eronimo.configs/axis2-deployer/2.0-SNAPSHOT/car > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > igurationData(SimpleConfigurationManager.java:454) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > iguration(SimpleConfigurationManager.java:268) > ... 14 more > Will look into that. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2724) create axis2 config and axis2-deployer config folders
[ https://issues.apache.org/jira/browse/GERONIMO-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2724. -- Resolution: Fixed > create axis2 config and axis2-deployer config folders > - > > Key: GERONIMO-2724 > URL: https://issues.apache.org/jira/browse/GERONIMO-2724 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: Winxp + sun 1.5 JDK >Reporter: Lin Sun > Attachments: g2724.zip > > > This is a patch on top of G2717 to create axis2 config and axis2-deployer > config based on the two cxf config modules. I also enabled the > modules\pom.xml + configs\pom.xml to include the two axis2 modules and two > axis2 configs. I tried to remove some unnecessary dependencies in > modules\geronimo-axis2\pom.xml to keep it as simple as possible. > This built fine on my machine (patch created against revision 494904). > After a successful build, I tried to turn on the axis2-deployer module in > config.xml in jetty-jee5 assembly, but the axis2-deployer module failed to > start. Here's the stack trace: > [*- ] 60% 24s Startup failed > org.apache.geronimo.kernel.config.LifecycleException: load of > org.apache.geronim > o.configs/axis2-deployer/2.0-SNAPSHOT/car failed > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > iguration(SimpleConfigurationManager.java:271) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > iguration(SimpleConfigurationManager.java:250) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager.loadConf > iguration(KernelConfigurationManager.java:112) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager$$FastCla > ssByCGLIB$$b117102f.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod > Invoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio > n.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance. > java:820) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5 > 7) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat > ionInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro > xyMethodInterceptor.java:96) > at > org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan > cerByCGLIB$$854c5ac.loadConfiguration() > at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:283) > at org.apache.geronimo.system.main.Daemon.(Daemon.java:74) > at org.apache.geronimo.system.main.Daemon.main(Daemon.java:366) > Caused by: org.apache.geronimo.kernel.config.NoSuchConfigException: > org.apache.g > eronimo.configs/axis2-deployer/2.0-SNAPSHOT/car > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > igurationData(SimpleConfigurationManager.java:454) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConf > iguration(SimpleConfigurationManager.java:268) > ... 14 more > Will look into that. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2776) Axis2 Integration - Replace RPCMessageReciever with JAXWSMessageReciever
[ https://issues.apache.org/jira/browse/GERONIMO-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469216 ] Davanum Srinivas commented on GERONIMO-2776: Fixed in svn revision 501827 thanks, dims > Axis2 Integration - Replace RPCMessageReciever with JAXWSMessageReciever > > > Key: GERONIMO-2776 > URL: https://issues.apache.org/jira/browse/GERONIMO-2776 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2776-2.patch, GERONIMO-2776.patch > > > This will replace the RPCMessageReciever with JAXWSMessageReciever. Had to > changed to change the way of handling ?wsdl request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2776) Axis2 Integration - Replace RPCMessageReciever with JAXWSMessageReciever
[ https://issues.apache.org/jira/browse/GERONIMO-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2776. -- Resolution: Fixed > Axis2 Integration - Replace RPCMessageReciever with JAXWSMessageReciever > > > Key: GERONIMO-2776 > URL: https://issues.apache.org/jira/browse/GERONIMO-2776 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2776-2.patch, GERONIMO-2776.patch > > > This will replace the RPCMessageReciever with JAXWSMessageReciever. Had to > changed to change the way of handling ?wsdl request. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2789) allow users to specify something other than services in url-pattern in axis2 jax-ws wars
[ https://issues.apache.org/jira/browse/GERONIMO-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2789. -- Resolution: Fixed Fix Version/s: (was: 2.0-M2) Applied patch in revision 502017 thanks, dims > allow users to specify something other than services in url-pattern in axis2 > jax-ws wars > > > Key: GERONIMO-2789 > URL: https://issues.apache.org/jira/browse/GERONIMO-2789 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M2 > Environment: winxp + sun jdk 1.5 >Reporter: Lin Sun > Attachments: G2789.patch > > > In jax-ws test for axis2, we had to specify /services/* as the url-pattern > for the servlet: > > cxfPojoServlet > /services/* > > This is because the axis2 configurationcontext default the servicePath to > "services". However, that is not good for our user, which means they have > to put services inside of their url-pattern. The fix is to use the > configurationContext.setServicePath method to override the default 'services' > value. This looks okay to me as we are building one configurationcontext and > one axisservice per endpointClass. > To do this, I grab the url-pattern from servlet-mapping specified in web.xml > and set url-pattern for the user when none is specified for the > servlet/Implclass. I've tested the cases where a user specified /servlet/* > or /servlet/lin/* as the url-pattern and it both works fine when running the > jax-ws test with the RPCMessageReceiver code (before 2776 is checked in). > I've commented code where it will throws exception when the url-pattern > contains a star as that issue hasn't been resolved yet. > The code built fine with the latest change in trunk but I haven't been able > to get the jax-ws war file deployed yet (issues not related to this patch). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2783) CXF-based WebServices support: webservices.xml file is no longer required
[ https://issues.apache.org/jira/browse/GERONIMO-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2783. -- Resolution: Fixed Comitted (svn revision 500959) thanks, dims > CXF-based WebServices support: webservices.xml file is no longer required > - > > Key: GERONIMO-2783 > URL: https://issues.apache.org/jira/browse/GERONIMO-2783 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-beta1 >Reporter: Jarek Gawor > Attachments: GERONIMO-2783.patch > > > The attached patch allows for JAX-WS web services (CXF-based) to be deployed > without webservices.xml file. The patch also contains a minor update to the > handlers.xml file in jaxws-tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2752) Axis2 integration displays invalid information for URL requests
[ https://issues.apache.org/jira/browse/GERONIMO-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2752. Resolution: Fixed Lasantha, Closing bug as patch has been applied already. Please open one more bug when you have another patch. thanks, dims > Axis2 integration displays invalid information for URL requests > --- > > Key: GERONIMO-2752 > URL: https://issues.apache.org/jira/browse/GERONIMO-2752 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2752.patch1, GERONIMO-2752.patch2, > GERONIMO-2752.patch3 > > > Current integration of Axis2 gives wrong information to the wsdl, wsdl2, xsd= > .. etc URL requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2746) use dependencymanagement for some axis2 dependent modules
[ https://issues.apache.org/jira/browse/GERONIMO-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved GERONIMO-2746. Resolution: Fixed Fixed in svn revision 500906. thanks, dims > use dependencymanagement for some axis2 dependent modules > -- > > Key: GERONIMO-2746 > URL: https://issues.apache.org/jira/browse/GERONIMO-2746 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 > Environment: winxp + sun jdk 1.5 >Reporter: Lin Sun >Priority: Minor > Attachments: G2746-new.patch, G2746.patch > > > This patch is intended to use the dependencymanagement for the axis2 > dependencies that have the same version specified in root pom.xml file. > I removed the following dependency as I dont see a need of it: > - > -com.sun.xml.bind > -jaxb-xjc > -2.0.2 > - > Also, tried to correct the 202 typo. The logic doesn't look right so I went > back to the code where I think this portion of code was copied from > (HTTPWorker.service), and it has 200 there. > patch is created against rev 496844 and I was able to get jax-ws testing > running (both soap call + ?wsdl call), even tho I am not sure if the ?wsdl > call result looks completely correct. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2781) Improved CXF-based POJO WebService support
[ https://issues.apache.org/jira/browse/GERONIMO-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2781. -- Resolution: Fixed Applied. thanks, dims > Improved CXF-based POJO WebService support > -- > > Key: GERONIMO-2781 > URL: https://issues.apache.org/jira/browse/GERONIMO-2781 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-beta1 >Reporter: Jarek Gawor > Attachments: GERONIMO-2781.patch > > > The attached patch contains numerous improvements to JAX-WS support for POJOs > (via CXF): > 1) Annotation support for the service and handlers. The following annotation > are recognized: @Resource, @EJB, @WebServiceRef, @PreDestroy, @PostConstruct. > The values are injected if the given resource is defined in JNDI. The patch > includes a basic annotation processor. The processor itself is pretty basic > but is generic and pluggable and can be (re)used in other places. It was > necessary to add one because CXF annotation processor only handles @Resource > annotations and it was not very extensible. > 2) WebServicesContext.getUserPricipa() and .isUserInRole() are now properly > implemented by delegating the calls to the Servlet class > 3) Improved webservices.xml file parsing and information passing to the web > container. Information specified in the webservices.xml file can now > overwrite the information specified in the annotations. For example, > @HandlerChain can be overwritten by element. Same with > wsdl-port, wsdl-service, and wsdl-file. > 4) Switched to using Commons Logging API instead of Java Logging API -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2781) Improved CXF-based POJO WebService support
[ https://issues.apache.org/jira/browse/GERONIMO-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467918 ] Davanum Srinivas commented on GERONIMO-2781: Jarek, Please check the svn revision 500348. Specifically the webservices.xml (testsuite\webservices-testsuite\jaxws-tests\jaxws-war\src\main\webapp\WEB-INF\webservices.xml) I had to apply the diff by hand for that one. thanks, dims > Improved CXF-based POJO WebService support > -- > > Key: GERONIMO-2781 > URL: https://issues.apache.org/jira/browse/GERONIMO-2781 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-beta1 >Reporter: Jarek Gawor > Attachments: GERONIMO-2781.patch > > > The attached patch contains numerous improvements to JAX-WS support for POJOs > (via CXF): > 1) Annotation support for the service and handlers. The following annotation > are recognized: @Resource, @EJB, @WebServiceRef, @PreDestroy, @PostConstruct. > The values are injected if the given resource is defined in JNDI. The patch > includes a basic annotation processor. The processor itself is pretty basic > but is generic and pluggable and can be (re)used in other places. It was > necessary to add one because CXF annotation processor only handles @Resource > annotations and it was not very extensible. > 2) WebServicesContext.getUserPricipa() and .isUserInRole() are now properly > implemented by delegating the calls to the Servlet class > 3) Improved webservices.xml file parsing and information passing to the web > container. Information specified in the webservices.xml file can now > overwrite the information specified in the annotations. For example, > @HandlerChain can be overwritten by element. Same with > wsdl-port, wsdl-service, and wsdl-file. > 4) Switched to using Commons Logging API instead of Java Logging API -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2717) Geronimo Axis2 Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2717. -- Resolution: Fixed closing this issue. thanks, dims > Geronimo Axis2 Integration > -- > > Key: GERONIMO-2717 > URL: https://issues.apache.org/jira/browse/GERONIMO-2717 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: geronimo-axis2.zip > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2752) Axis2 integration displays invalid information for URL requests
[ https://issues.apache.org/jira/browse/GERONIMO-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465955 ] Davanum Srinivas commented on GERONIMO-2752: Lasantha, Please submit a new patch. thanks, dims > Axis2 integration displays invalid information for URL requests > --- > > Key: GERONIMO-2752 > URL: https://issues.apache.org/jira/browse/GERONIMO-2752 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2752.patch1, GERONIMO-2752.patch2 > > > Current integration of Axis2 gives wrong information to the wsdl, wsdl2, xsd= > .. etc URL requests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2750) Remove Depricated Code from Axis2 Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2750. -- Resolution: Fixed Looks like this is outdated now with GERONIMO-2752 -- dims > Remove Depricated Code from Axis2 Integration > - > > Key: GERONIMO-2750 > URL: https://issues.apache.org/jira/browse/GERONIMO-2750 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) >Affects Versions: 2.0-M1 >Reporter: Lasantha Ranaweera > Attachments: GERONIMO-2750.patch > > > This patch will do following stuff. > 1. Replaced deprecated source code > 2. Use java logger instead of Apache commons logger since it has been using > the Axis2Builder. > 3. Remove Unused variables. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2746) use dependencymanagement for some axis2 dependent modules
[ https://issues.apache.org/jira/browse/GERONIMO-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465953 ] Davanum Srinivas commented on GERONIMO-2746: Lin, Will you be submitting a new patch? thanks, dims > use dependencymanagement for some axis2 dependent modules > -- > > Key: GERONIMO-2746 > URL: https://issues.apache.org/jira/browse/GERONIMO-2746 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0-M1 > Environment: winxp + sun jdk 1.5 >Reporter: Lin Sun >Priority: Minor > Attachments: G2746.patch > > > This patch is intended to use the dependencymanagement for the axis2 > dependencies that have the same version specified in root pom.xml file. > I removed the following dependency as I dont see a need of it: > - > -com.sun.xml.bind > -jaxb-xjc > -2.0.2 > - > Also, tried to correct the 202 typo. The logic doesn't look right so I went > back to the code where I think this portion of code was copied from > (HTTPWorker.service), and it has 200 there. > patch is created against rev 496844 and I was able to get jax-ws testing > running (both soap call + ?wsdl call), even tho I am not sure if the ?wsdl > call result looks completely correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-2727) Enable axis2-deployer in jetty and tomcat jee5 assemblies
[ https://issues.apache.org/jira/browse/GERONIMO-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas closed GERONIMO-2727. -- Resolution: Fixed Checked into SVN (r49566). thanks, dims > Enable axis2-deployer in jetty and tomcat jee5 assemblies > - > > Key: GERONIMO-2727 > URL: https://issues.apache.org/jira/browse/GERONIMO-2727 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.0 > Environment: winxp + sun sdk >Reporter: Lin Sun > Fix For: 2.0 > > Attachments: G2727.patch > > > I have figured out why I got the exception descriped in G2724.This patch > would enable the axis2 config and axis2-deployer config in jetty and tomcat > javaee5 assemblies. > This built fine on my machine (patch created against revision 494904). After > a successful build, I can start both tomcat jee5 server and jetty jee5 server > successfully. Run a 'deploy.bat list-modules' command and the output > verified that configs\axis2-deployer is running, configs\axis2 is installed > but not running. The result is the same for the two cxf configs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2717) Geronimo Axis2 Integration
[ https://issues.apache.org/jira/browse/GERONIMO-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463551 ] Davanum Srinivas commented on GERONIMO-2717: Lasantha, checked in the contents of the zip (r494810). Will take a look at the TODO's to see if can help too. thanks, dims > Geronimo Axis2 Integration > -- > > Key: GERONIMO-2717 > URL: https://issues.apache.org/jira/browse/GERONIMO-2717 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: webservices >Reporter: Lasantha Ranaweera > Attachments: geronimo-axis2.zip > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
