[jira] Resolved: (AXIS2-1379) Base64 data is not encoded correctly

2006-10-14 Thread Thilina Gunarathne (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1379?page=all ] Thilina Gunarathne resolved AXIS2-1379. --- Resolution: Fixed http://svn.apache.org/viewvc?view=rev&rev=464128 Jake, Please check whether this solves your issue... Thanks, ~Thilina > Base

[jira] Commented: (AXIS2-1380) Error calling a service thru proxy

2006-10-14 Thread Thilina Gunarathne (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1380?page=comments#action_12442366 ] Thilina Gunarathne commented on AXIS2-1380: --- try this http://people.apache.org/~thilina/axis2/1.1-RC1/eclipse_codegen_plugin_1.1-RC1/ thanks, ~Thilina >

Re: svn commit: r463755 - in /webservices/axis2/branches/java/1_1/modules: java2wsdl/src/org/apache/ws/java2wsdl/ kernel/src/org/apache/axis2/description/ kernel/src/org/apache/axis2/receivers/

2006-10-14 Thread Thilina Gunarathne
About the Async MR case.. I checked the code and things seem to have gone to the correct places... But we need more testing!!! ~Thilina On 10/15/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: Deepal did u update the AsyncMRs? Those need to change of course. Also, looks like you broke the

[jira] Updated: (AXIS-2570) If the operation name is defined similar to the request element name in the wsdl schema type then wsdl2java generates incorrect classes.

2006-10-14 Thread Saif Rizvi (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2570?page=all ] Saif Rizvi updated AXIS-2570: - Attachment: TestWithoutBug.jar Classes generated as correctly complying to the request and response of the wsdl where operation name is not same as the request elemen

[jira] Updated: (AXIS-2570) If the operation name is defined similar to the request element name in the wsdl schema type then wsdl2java generates incorrect classes.

2006-10-14 Thread Saif Rizvi (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2570?page=all ] Saif Rizvi updated AXIS-2570: - Attachment: TestWithoutBug.wsdl same wsdl with operation name made different with the request element. this wsdl will generate correct classes. corresponding classes a

[jira] Updated: (AXIS-2570) If the operation name is defined similar to the request element name in the wsdl schema type then wsdl2java generates incorrect classes.

2006-10-14 Thread Saif Rizvi (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2570?page=all ] Saif Rizvi updated AXIS-2570: - Attachment: Test.jar Jar of the classes generated by Axis WSDL2Java > If the operation name is defined similar to the request element name in the > wsdl schema type

[jira] Updated: (AXIS-2570) If the operation name is defined similar to the request element name in the wsdl schema type then wsdl2java generates incorrect classes.

2006-10-14 Thread Saif Rizvi (JIRA)
[ http://issues.apache.org/jira/browse/AXIS-2570?page=all ] Saif Rizvi updated AXIS-2570: - Attachment: Test.wsdl wsdl to replicate the problem. > If the operation name is defined similar to the request element name in the > wsdl schema type then wsdl2java

[jira] Commented: (AXIS2-1380) Error calling a service thru proxy

2006-10-14 Thread Robert Luo (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1380?page=comments#action_12442341 ] Robert Luo commented on AXIS2-1380: --- I can only find the 1.1 branch for the whole axis2 package not the plugin tool. The Eclipse plugin is only available for 1.

[jira] Created: (AXIS-2570) If the operation name is defined similar to the request element name in the wsdl schema type then wsdl2java generates incorrect classes.

2006-10-14 Thread Saif Rizvi (JIRA)
If the operation name is defined similar to the request element name in the wsdl schema type then wsdl2java generates incorrect classes. Key: A

Re: svn commit: r463755 - in /webservices/axis2/branches/java/1_1/modules: java2wsdl/src/org/apache/ws/java2wsdl/ kernel/src/org/apache/axis2/description/ kernel/src/org/apache/axis2/receivers/

2006-10-14 Thread Sanjiva Weerawarana
Deepal did u update the AsyncMRs? Those need to change of course. Also, looks like you broke the Spring stuff; see the mail from Robert. Sanjiva. On Sat, 2006-10-14 at 09:28 +0600, Thilina Gunarathne wrote: > A quick comment... > > Did you test the Async message receivers... My instincts say the

[jira] Updated: (AXIS2-1358) Increased functionality for issue Axis2-1195

2006-10-14 Thread Roy A. Wood Jr. (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1358?page=all ] Roy A. Wood Jr. updated AXIS2-1358: --- Attachment: MDQPatch1014.txt This latest patch (MDQPatch1014) is the one to apply. The original patch contains errors and should be discarded. > Increas

[jira] Resolved: (AXIS2-598) $CLASSPATH based module discovery does not work with LWS (linear white spaces)

2006-10-14 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-598?page=all ] Davanum Srinivas resolved AXIS2-598. Resolution: Fixed Michel, the following fix for AXIS2-1359 should have fixed this problem as well. Please test and let me know. http://svn.apache.org/v

[jira] Commented: (AXIS2-1224) setOperationContext() not thread-safe

2006-10-14 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1224?page=comments#action_12442327 ] Davanum Srinivas commented on AXIS2-1224: - Deepal, Just reviewed the code, MessageContext.getCurrentContext() should and will work whatever the ServiceTCC

[jira] Resolved: (AXIS2-1374) WSDL's with policy references cause the WSDL2Java to fail with an UnsupportedOperationException thrown by the PolicyReference class

2006-10-14 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1374?page=all ] Davanum Srinivas resolved AXIS2-1374. - Resolution: Fixed checked in a fix in neethi - svn revision 463986. Sanka, Please cross check. thanks, dims > WSDL's with policy references cause t

[jira] Commented: (AXIS2-1380) Error calling a service thru proxy

2006-10-14 Thread Davanum Srinivas (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1380?page=comments#action_12442315 ] Davanum Srinivas commented on AXIS2-1380: - Nope. We changed the way (API's) to specify the authentication information. So please check latest javadocs. th

Re: [Axis2] What to include in the Axis2 1.1 distributions??

2006-10-14 Thread Davanum Srinivas
Yep. -- dims On 10/14/06, robert lazarski <[EMAIL PROTECTED]> wrote: Just to clarify, what I believe Dims and I agreed to via +1 was to remove all the spring jars from the war , and place just one 4K jar inside the std-bin dist - axis2-spring*.jar - which has the axis2 code to tie together spri

[jira] Commented: (AXIS2-1380) Error calling a service thru proxy

2006-10-14 Thread Robert Luo (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-1380?page=comments#action_12442310 ] Robert Luo commented on AXIS2-1380: --- Can I just simply replace the jar files that come with the Eclipse plug-ins with those from the 1.1 branch? Thanks, Robert

Re: [Axis2] What to include in the Axis2 1.1 distributions??

2006-10-14 Thread robert lazarski
Just to clarify, what I believe Dims and I agreed to via +1 was to remove all the spring jars from the war , and place just one 4K jar inside the std-bin dist - axis2-spring*.jar - which has the axis2 code to tie together spring and axis2 . Robert On 10/14/06, Ajith Ranabahu <[EMAIL PROTECTED]>

Re: [Axis2] What to include in the Axis2 1.1 distributions??

2006-10-14 Thread Ajith Ranabahu
Hi, And provide all aditional dependacncies of Axis2 as a one zip file from the site. Or add a minmial standard and exteneded distribution. I agree with Srinath in this. My guess is there would be users who want everything and some would want most of it but not all. Right now we have standard

Re: [Axis2] What to include in the Axis2 1.1 distributions??

2006-10-14 Thread Srinath Perera
Just looked at the std distribution .. we have 3 axom jars 10 Axis2 jars !!! Lets bring them down to two jars .. Most of these axis2 jars are small. So no harm putting everything in the one jar I would say 1) Get rid of bcel-5.2.jar 2) jaxme-* 3) spring-* And provide all aditional dependacnc

Re: [Axis2] What to include in the Axis2 1.1 distributions??

2006-10-14 Thread Srinath Perera
Couple of comments 1) Do we need JMS jar on minimal distribution? Plus we do not need jms transport on the axis2.xml by default. users could uncomment and add a jar if they need. 2) Can we make everything belong to Axis2 a one jar. At the time of creating the distribution we could do that. Also

Re: Test fails org.apache.axis2.jibx.Test

2006-10-14 Thread Saminda Abeyruwan
Hi Dennis,Build pass on both jks. It's just, I didn't have the latest jibx-bind and jibx-run jars. Thank youSaminda On 10/14/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:I'm using JDK 1.5.0_07 on Mandriva Linux, so I very much doubt there areany JDK issues.  :-) Are you sure you've cleaned every

Re: Test fails org.apache.axis2.jibx.Test

2006-10-14 Thread Dennis Sosnoski
I'm using JDK 1.5.0_07 on Mandriva Linux, so I very much doubt there are any JDK issues. :-) Are you sure you've cleaned everything properly and have everything synced to the repository? I made the checkins for this test well a full day ago, and no one else appears to be having build problems.

Re: Test fails org.apache.axis2.jibx.Test

2006-10-14 Thread Saminda Abeyruwan
Hi,My bad.I did online build, and everything is fine now. Sorry for the confusion I've caused.Saminda On 10/14/06, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:Hi, I'm runing on java version "1.5.0_08"Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03), Ubuntu LinuxWill go to 1.4

Re: Test fails org.apache.axis2.jibx.Test

2006-10-14 Thread Saminda Abeyruwan
Hi,I'm runing on java version "1.5.0_08"Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03), Ubuntu LinuxWill go to 1.4 and run the tests.Saminda On 10/14/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote: I've just confirmed that this test is working on my system, with currentsvn co