[Axis2] Updated the INSTALL doc

Hi, The attached svn diff file contains some updates to the INSTALL doc. I have corrected some mistakes and improved the formatting. Thanks, Ishan. Index: INSTALL === --- INSTALL (revision 438755) +++ INSTALL (working

[jira] Created: (AXIS2C-238) Unexpected behavior when the value of an axiom_attribute is NULL

Unexpected behavior when the value of an axiom_attribute is NULL Key: AXIS2C-238 URL: http://issues.apache.org/jira/browse/AXIS2C-238 Project: Axis2-C Issue Type: Bug

Re: [Axis2] 0.93 Release - Code Freeze

I have tagged the svn, bundled and uploaded the release files. So would like to declare that the code freeze is over. Thanks, Samisa... Samisa Abeysinghe wrote: I would like to propose that we freeze the svn code by 1200 hours GMT for the release Once code is frozen, please refrain from

[jira] Updated: (AXIS2C-170) Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object.

[ http://issues.apache.org/jira/browse/AXIS2C-170?page=all ] Samisa Abeysinghe updated AXIS2C-170: - Fix Version/s: (was: 0.93) Could not complete for 0.93. Postponed Compact the if blocks into one if block in create_dll method so that the lib

[jira] Resolved: (AXIS2C-149) Add dynamic invocation methods to Service Client API

[ http://issues.apache.org/jira/browse/AXIS2C-149?page=all ] Samisa Abeysinghe resolved AXIS2C-149. -- Resolution: Fixed I thik we can call this done as the URL case is implemented and I do not see the need for the other function Add dynamic

[jira] Updated: (AXIS2C-169) Arrange the parameter list taken by string functions to be consistant

[ http://issues.apache.org/jira/browse/AXIS2C-169?page=all ] Samisa Abeysinghe updated AXIS2C-169: - Fix Version/s: 1.0.0 (was: 0.93) Could not complete this before 0.93 Would be done for 1.0 Arrange the parameter list taken

[jira] Closed: (AXIS2C-236) SVN checkout path on Axis2/c Home page

[ http://issues.apache.org/jira/browse/AXIS2C-236?page=all ] Samisa Abeysinghe closed AXIS2C-236. Fix Version/s: 0.93 Resolution: Fixed Assignee: Samisa Abeysinghe I added a svn.html page and updated the web site as well for 0.93

[jira] Commented: (AXIS2C-238) Unexpected behavior when the value of an axiom_attribute is NULL

[ http://issues.apache.org/jira/browse/AXIS2C-238?page=comments#action_12431941 ] Samisa Abeysinghe commented on AXIS2C-238: -- Please provide a small test case for this if possible. I assume you muct have the piece of code that caused

[jira] Commented: (AXIS2C-232) WODEN/C fails parsing some WSDLs

[ http://issues.apache.org/jira/browse/AXIS2C-232?page=comments#action_12431944 ] Samisa Abeysinghe commented on AXIS2C-232: -- If possible, please attach the WSDLs here. If those WSDL files are already in the svn, please mention the

[jira] Commented: (AXIS2-653) Handler method cleanup is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=comments#action_12431800 ] Deepal Jayasinghe commented on AXIS2-653: - I think we need to call cleanup method after each invocation , since lifetime of a handler is same as lifetime

[jira] Commented: (AXIS2-850) NullPointerException in AbstractHTTPSender

[ http://issues.apache.org/jira/browse/AXIS2-850?page=comments#action_12431812 ] Deepal Jayasinghe commented on AXIS2-850: - Well as I understand your scenario is something like below; Client --(async call) - Server A

Re: [Axis2] Re-setting of the Action

So there are 2 ways of reusing the Options object. 1. User re-use so that a user can sc.sendReceive() repeatedly and it works 2. Internal re-use of the Options object for the response per OutInAxisOperation line 349: // This is a hack - Needs to change

[jira] Created: (AXIS2-1096) org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null

org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null Key: AXIS2-1096 URL: http://issues.apache.org/jira/browse/AXIS2-1096 Project: Apache Axis 2.0 (Axis2) Issue

[jira] Assigned: (AXIS2-776) Make the AddressingBasedDispatcher a handler in the Addressing module

[ http://issues.apache.org/jira/browse/AXIS2-776?page=all ] Deepal Jayasinghe reassigned AXIS2-776: --- Assignee: Eran Chinthaka Make the AddressingBasedDispatcher a handler in the Addressing module

[jira] Assigned: (AXIS2-653) Handler method cleanup is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=all ] Deepal Jayasinghe reassigned AXIS2-653: --- Assignee: Deepal Jayasinghe Handler method cleanup is never called Key: AXIS2-653

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

[ http://issues.apache.org/jira/browse/AXIS2-598?page=all ] Deepal Jayasinghe reassigned AXIS2-598: --- Assignee: Deepal Jayasinghe $CLASSPATH based module discovery does not work with LWS (linear white spaces)

RE: Mtom Sample

Hi Robert, Tried adding this on weblogic.xml however does not work. Has Anyone tried running MTOM sample and was successfully able to transfer the images using it? Thanks, Rajesh Pawnikar Mail ID: [EMAIL PROTECTED] From: robert lazarski [mailto:[EMAIL

[jira] Assigned: (AXIS2-1083) WSDL2Java: SchemaLocation and circular imports / StackOverflowError

[ http://issues.apache.org/jira/browse/AXIS2-1083?page=all ] Deepal Jayasinghe reassigned AXIS2-1083: Assignee: Deepal Jayasinghe WSDL2Java: SchemaLocation and circular imports / StackOverflowError

[jira] Assigned: (AXIS2-935) Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open

[ http://issues.apache.org/jira/browse/AXIS2-935?page=all ] Deepal Jayasinghe reassigned AXIS2-935: --- Assignee: Deepal Jayasinghe Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open

[jira] Resolved: (AXIS2-1068) Axis2 deployment does not preserve the original WSDL from META-INF

[ http://issues.apache.org/jira/browse/AXIS2-1068?page=all ] Deepal Jayasinghe resolved AXIS2-1068. -- Resolution: Fixed fixed in current SVN Axis2 deployment does not preserve the original WSDL from META-INF

[jira] Commented: (AXIS2-850) NullPointerException in AbstractHTTPSender

[ http://issues.apache.org/jira/browse/AXIS2-850?page=comments#action_12431855 ] Michele Mazzucco commented on AXIS2-850: Deepal, now I've found out the reason (or at least I think I did it): the WS-Addressing specifications

Re: Axis2/Woden Integration Scenario Explanation (Request for User Documentation)

Hi, Is the integration available with Axis2 Version 1.0? (Axis2 documentation doesn't say anything about it :-( ) Am looking to generate Java code (using WSDL2Code) with WSDL 2.0 (HTTP Binding). Can you give me pointers to user documentation to use the feature? Thanks Venkat - Original

Re: Mtom Sample

You have a jar conflict ... if you look around on weblogic somewhere there will probably be a jar in a higher classloader that has the javax.xml.namespace.QName being loaded from there. What you're looking for is axis2 to load javax.xml.namespace.QName from the jar in the axis2 distro,

[jira] Closed: (AXIS2-1090) Dispatch InvokeAsync Hangs on Malformed URL.

[ http://issues.apache.org/jira/browse/AXIS2-1090?page=all ] Nick Gallardo closed AXIS2-1090. Resolution: Fixed Dispatch InvokeAsync Hangs on Malformed URL. Key: AXIS2-1090

Re: [Axis2] Re-setting of the Action

David, I've tracked it down to this change from Deepal. Not sure if he remembers it :) http://svn.apache.org/viewvc?view=revrevision=366507 -- dims On 8/31/06, David Illsley [EMAIL PROTECTED] wrote: So there are 2 ways of reusing the Options object. 1. User re-use so that a user can

Re: [Axis2] Re-setting of the Action

I think the general intent is to avoid cloning options at all costs. And if the internal classes do not change the options, then the user can reuse the options class. the change for the setAction() broke that unwritten contract is my guess. thanks, dims On 8/31/06, Davanum Srinivas [EMAIL

[AXIS2] error in generation of EPR of services

sorry, if this is already known. in the axis2 nightly build: 2006-08-31 the target EPR, displayed at the service listing page (usually http://localhost:8080/axis2/services/listServices;), is wrong. example: for the version default service is

WSS4J 2.0(?)

Team, - What do you think about moving from maven1/ant to maven2? - Is it time to move all the security stuff from Axis2 svn to wss4j? (secpolicy/rampart/rahas etc)? - How about we remove the sandbox code in wss4j? I was thinking basically about the following: the existing code under

[jira] Commented: (AXIS2-653) Handler method cleanup is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=comments#action_12431888 ] Bill Nagy commented on AXIS2-653: - Hi Deepal. I actually proposed this modification to the lifecycle sometime in April (

Re: Axis2/Woden Integration Scenario Explanation (Request for User Documentation)

[EMAIL PROTECTED] wrote: Hi, Is the integration available with Axis2 Version 1.0? (Axis2 documentation doesn't say anything about it :-( ) No its not available with Axis2 1.0. But its in the nightly builds. Am looking to generate Java code (using WSDL2Code) with WSDL 2.0 (HTTP

[jira] Created: (AXIS2-1097) Add metadata support for WebServiceProvider and related annotations on provider-based service implementation class

Add metadata support for WebServiceProvider and related annotations on provider-based service implementation class -- Key: AXIS2-1097 URL:

[jira] Resolved: (AXIS2-861) cache setting is not working in Nightly build Jun 22,06

[ http://issues.apache.org/jira/browse/AXIS2-861?page=all ] Thilina Gunarathne resolved AXIS2-861. -- Resolution: Fixed resolved in the latest SVN Head... http://svn.apache.org/viewvc?rev=438087view=rev cache setting is not working in Nightly build

Re: FW: Creating or setting header options

Hello Joe, Have you engaged the addressing module in your client? If you haven't then follow the details here, http://ws.apache.org/axis2/1_0/userguide3.html#EchoNonBlockingDualClient Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319

RE: FW: Creating or setting header options

Thanks so much. I have actually done that and my addressing headers are working just fine. For those following the thread and searchingfor a similar problem, Iput theaddressing-1.0.mar into the classpath and the following lines of code into my client where I was getting the Stub. stub =

RE: FW: Creating or setting header options

As a side note, the documentation, http://ws.apache.org/axis2/1_0/userguide3.html#Engaging_Addressing_in_Client_Side,to needs to be updated. In the section, "Engaging Addressing in Client Side" it only instructs the user to add the addressing-version.mar file to your classpath or create tthe

[jira] Updated: (AXIS2-1097) Add metadata support for WebServiceProvider and related annotations on provider-based service implementation class

[ http://issues.apache.org/jira/browse/AXIS2-1097?page=all ] Jeff Barrett updated AXIS2-1097: Attachment: 1097_patch.txt Fixed per Description. Added testcase also. Add metadata support for WebServiceProvider and related annotations on

[jira] Created: (AXIS2-1098) JAXWSTest not running ProxyNonWrappedTests

JAXWSTest not running ProxyNonWrappedTests -- Key: AXIS2-1098 URL: http://issues.apache.org/jira/browse/AXIS2-1098 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws

Re: WSS4J 2.0(?)

All, - Is it time to move all the security stuff from Axis2 svn to wss4j? (secpolicy/rampart/rahas etc)? I see an issue here : Rampart had its own release as Rampart 1.0 and I'd prefer if we can have this separate. The same goes for Rahas (WS-Trust impl). Basically how about pushing these

Re: WSS4J 2.0(?)

On Thu, 2006-08-31 at 20:28 +0530, Ruchith Fernando wrote: Basically how about pushing these up to be two new sub projects or the Apache Web services project : Ramaprt - WS-Security and WS-SecureConversation implementation Rahas - WS-Trust implementation This is similar to the way we

[jira] Commented: (AXIS2-1098) JAXWSTest not running ProxyNonWrappedTests

[ http://issues.apache.org/jira/browse/AXIS2-1098?page=comments#action_12431915 ] Jeff Barrett commented on AXIS2-1098: - This file should have been added as part of https://issues.apache.org/jira/browse/AXIS2-1072. I checked the patch file

[jira] Created: (AXIS2-1099) Asyc Feature for JAXWS proxy Doc/Lit non Wrap.

Asyc Feature for JAXWS proxy Doc/Lit non Wrap. -- Key: AXIS2-1099 URL: http://issues.apache.org/jira/browse/AXIS2-1099 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature

[jira] Updated: (AXIS2-1099) Asyc Feature for JAXWS proxy Doc/Lit non Wrap.

[ http://issues.apache.org/jira/browse/AXIS2-1099?page=all ] Nikhil Thaker updated AXIS2-1099: - Attachment: JIRA_1099_DocLitNONWrapAsyncSupport.txt Here's patch that will add support for DOC/LIT non Wrap Async support and I have also included a test

Re: WSS4J 2.0(?)

Another big +1 from me too. I was really worried about the increasing number of modules within Axis2 project, but didn't take this up as people were busy with other important issues. I'd like to add two more things to Ruchith's proposal. 1. Move Savan also to a sub-project out of Axis2 2. Write

[jira] Updated: (AXIS2-1098) JAXWSTest not running ProxyNonWrappedTests

[ http://issues.apache.org/jira/browse/AXIS2-1098?page=all ] Jeff Barrett updated AXIS2-1098: Attachment: 1098_patch.txt Fixed per Description. JAXWSTest not running ProxyNonWrappedTests --

[jira] Updated: (AXIS2-937) WSDL2Java not generating parameters for stub methods

[ http://issues.apache.org/jira/browse/AXIS2-937?page=all ] Ajith Harshana Ranabahu updated AXIS2-937: -- Summary: WSDL2Java not generating parameters for stub methods (was: WSDL2Java not generating parameters for stib methods) Its supposed to

Re: WSS4J 2.0(?)

Hi, I'm also +1 on this move - it makes things modular and easy to handle. BTW I don't think you need to move the integration tests - they are *Axis2* integration tests and they should not go to any other project! Of course the rampart module will be external after the change but that does not

[Axis2] Jar Files ...

In which Jar file can I find the org.apache.rahas package? The only one I have available is axis2-rahas-SNAPSHOT.jar, and I have a suspicion that the classes within were compiled against a different version of Axis2 than what I am trying to deploy against. Background: I've used

Re: [Axis2] Jar Files ...

Hi Joe, I guess that it is possible to the rampart module to be a 'mix and match' so the best thing to do would be to build them from source :) Ajith On 8/31/06, Joe Wyrembelski [EMAIL PROTECTED] wrote: In which Jar file can I find the org.apache.rahas package? The only one I have available

[jira] Commented: (AXIS2-1076) Catchall documentation improvements

[ http://issues.apache.org/jira/browse/AXIS2-1076?page=comments#action_12432027 ] robert lazarski commented on AXIS2-1076: Joe Wyrembelski had this to say: [EMAIL PROTECTED] to axis-dev As a side note, the documentation,

Re: WSS4J 2.0(?)

Ajith, If we implement this, it is going to be exactly similar to the WS-FX project ... which we got rid of, some time back ! It is much more clearer to have the different WS-* implementations at direct children of the WS project. Also its important to note that these sub-projects (Rampart,

[jira] Updated: (AXIS2-1087) CLONE -Problem with resolving imported schemas from WSDL11ToAxisServiceBuilder

[ http://issues.apache.org/jira/browse/AXIS2-1087?page=all ] Lori VanGulick updated AXIS2-1087: -- Attachment: patch.txt I have attached a patch that fixes this problem for my testcases. It is the same fix I described above - a one line change in

Re: WSS4J 2.0(?)

Hi, Ok, the fact that they are the home for their C counterparts is valid to some extent to make it to the top level ( I mean as direct children of WS project - subsequent uses of top level would mean the same stated otherwise). But why did we place XMLSchema, Axiom, neethi, tcpmon and such

[jira] Resolved: (AXIS2-932) axis2 doesn't receive null values correctly

[ http://issues.apache.org/jira/browse/AXIS2-932?page=all ] Deepal Jayasinghe resolved AXIS2-932. - Resolution: Fixed fixed in current SVN axis2 doesn't receive null values correctly ---

[jira] Assigned: (AXIS2-1087) CLONE -Problem with resolving imported schemas from WSDL11ToAxisServiceBuilder

[ http://issues.apache.org/jira/browse/AXIS2-1087?page=all ] Eran Chinthaka reassigned AXIS2-1087: - Assignee: Deepal Jayasinghe (was: Ajith Harshana Ranabahu) CLONE -Problem with resolving imported schemas from WSDL11ToAxisServiceBuilder

[jira] Assigned: (AXIS2-957) AxisServlet does not generate WSDL containing a wsdl:fault

[ http://issues.apache.org/jira/browse/AXIS2-957?page=all ] Eran Chinthaka reassigned AXIS2-957: Assignee: Deepal Jayasinghe AxisServlet does not generate WSDL containing a wsdl:fault --

[jira] Assigned: (AXIS2-931) WSDL2Java generated fault exceptions don't provide a way to specify an exception message or cause.

[ http://issues.apache.org/jira/browse/AXIS2-931?page=all ] Eran Chinthaka reassigned AXIS2-931: Assignee: Eran Chinthaka WSDL2Java generated fault exceptions don't provide a way to specify an exception message or cause.

[jira] Assigned: (AXIS2-850) NullPointerException in AbstractHTTPSender

[ http://issues.apache.org/jira/browse/AXIS2-850?page=all ] Eran Chinthaka reassigned AXIS2-850: Assignee: Deepal Jayasinghe NullPointerException in AbstractHTTPSender -- Key: AXIS2-850

[jira] Assigned: (AXIS2-814) unwrapping support in codegen

[ http://issues.apache.org/jira/browse/AXIS2-814?page=all ] Eran Chinthaka reassigned AXIS2-814: Assignee: Eran Chinthaka unwrapping support in codegen - Key: AXIS2-814 URL:

[jira] Created: (AXIS2-1100) Inconsistence in handler API

Inconsistence in handler API Key: AXIS2-1100 URL: http://issues.apache.org/jira/browse/AXIS2-1100 Project: Apache Axis 2.0 (Axis2) Issue Type: Wish Components: core Reporter: Deepal

[jira] Created: (AXIS2-1101) Bug in handler getName

Bug in handler getName -- Key: AXIS2-1101 URL: http://issues.apache.org/jira/browse/AXIS2-1101 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: core Reporter: Deepal Jayasinghe In

[jira] Resolved: (AXIS2-776) Make the AddressingBasedDispatcher a handler in the Addressing module

[ http://issues.apache.org/jira/browse/AXIS2-776?page=all ] Eran Chinthaka resolved AXIS2-776. -- Resolution: Won't Fix Moving AddressingBasedDispatcher completely in to the addressing module is not a good idea. I agree this can be true for the client

[jira] Assigned: (AXIS2-1101) Bug in handler getName

[ http://issues.apache.org/jira/browse/AXIS2-1101?page=all ] Deepal Jayasinghe reassigned AXIS2-1101: Assignee: Deepal Jayasinghe Bug in handler getName -- Key: AXIS2-1101 URL:

[jira] Resolved: (AXIS2-1016) EndpointReference serialization/deserialization should be consolidated in the EndpointReference class

[ http://issues.apache.org/jira/browse/AXIS2-1016?page=all ] Eran Chinthaka resolved AXIS2-1016. --- Resolution: Fixed Making this inside endpoint reference class is not a good idea. Lets please do this using a helper. EndpointReference