[jira] Assigned: (AXIS2-547) wsdl2Java fails with StackOverflowError when creating Xmlbeans from recursive xml schema

[ http://issues.apache.org/jira/browse/AXIS2-547?page=all ] Deepal Jayasinghe reassigned AXIS2-547: --- Assign To: Ajith Harshana Ranabahu > wsdl2Java fails with StackOverflowError when creating Xmlbeans from recursive > xml schema >

[jira] Commented: (AXIS2-533) Axiom is heavy-weight and slow

[ http://issues.apache.org/jira/browse/AXIS2-533?page=comments#action_12375063 ] Sanjiva Weerawarana commented on AXIS2-533: --- I think we should close this: its impossible for one implementation to optimize both time and space .. that's the classic

[jira] Commented: (AXIS2-533) Axiom is heavy-weight and slow

[ http://issues.apache.org/jira/browse/AXIS2-533?page=comments#action_12375062 ] Dennis Sosnoski commented on AXIS2-533: --- Still heavy, no longer slow. ;-) > Axiom is heavy-weight and slow > -- > > Key: AXIS2-533 >

[Axis2]Re: WSDL2Java Server side code generation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Forwarded with [Axis2] prefix Saminda David Boyer wrote: > Hey all, > > I'd like to be able to control the generated products. > > Our wsdl's and schema are early in development and thus are subject to > frequent change. I would like to be able to

[jira] Assigned: (AXIS2-587) WSDL2Java generates duplicate fault classes, can't compile generated stub

[ http://issues.apache.org/jira/browse/AXIS2-587?page=all ] Deepal Jayasinghe reassigned AXIS2-587: --- Assign To: Ajith Harshana Ranabahu > WSDL2Java generates duplicate fault classes, can't compile generated stub > --

[jira] Assigned: (AXIS2-545) WSDL port address for JMS

[ http://issues.apache.org/jira/browse/AXIS2-545?page=all ] Deepal Jayasinghe reassigned AXIS2-545: --- Assign To: Davanum Srinivas Will we be able to fix this for 1.0 > WSDL port address for JMS > - > > Key: AXIS2-54

[jira] Resolved: (AXIS2-500) Service client sendRobust throw exception

[ http://issues.apache.org/jira/browse/AXIS2-500?page=all ] Deepal Jayasinghe resolved AXIS2-500: - Resolution: Fixed Fixed But dont have any test cases to test that :( > Service client sendRobust throw exception > -

[jira] Commented: (AXIS2-524) JMS Doesn't work

[ http://issues.apache.org/jira/browse/AXIS2-524?page=comments#action_12375040 ] Deepal Jayasinghe commented on AXIS2-524: - any sign of get it done for 1.0 ?:) > JMS Doesn't work > > > Key: AXIS2-524 > URL: htt

[jira] Commented: (AXIS2-533) Axiom is heavy-weight and slow

[ http://issues.apache.org/jira/browse/AXIS2-533?page=comments#action_12375039 ] Deepal Jayasinghe commented on AXIS2-533: - dont we in the good position to resolve this issue > Axiom is heavy-weight and slow > -- > >

Re: [Axis2] Dependancy problem with XMLBeans module

I don't know anything about IDEA (just say "no" to concealed source code :-) ), but it sounds like you want to either merge these two Axis2 modules into a single IDEA module (if IDEA's flexible enough to allow that approach) or switch to running your codegen from the xmlbeans module (which has

Re: [jira] Commented: (AXIS2-500) Service client sendRobust throw exception

I will fix that today :) Davanum Srinivas (JIRA) wrote: >[ > http://issues.apache.org/jira/browse/AXIS2-500?page=comments#action_12375023 > ] > >Davanum Srinivas commented on AXIS2-500: > > >Deepal, > >Do we need this for Axis2 1.0 Final? > >-- dims

Re: [Axis2] Dependancy problem with XMLBeans module

Hi, Sorry if I did not explain the problem properly. This is regarding running the codegen main class from the IDE (IntellijIDEA to be exact). I've set up the project as a multi module project (which I think is the right way to do so) and module dependancies can be put only in one direction. Since

[jira] Resolved: (AXIS2-585) WS-Addressing - Incorrect cardinality for RelatesTo in handler and on API

[ http://issues.apache.org/jira/browse/AXIS2-585?page=all ] Davanum Srinivas resolved AXIS2-585: Resolution: Fixed Fixed in latest SVN. thanks, dims > WS-Addressing - Incorrect cardinality for RelatesTo in handler and on API >

[jira] Resolved: (AXIS2-117) SOAP Fault information in SOAP Header

[ http://issues.apache.org/jira/browse/AXIS2-117?page=all ] Davanum Srinivas resolved AXIS2-117: Resolution: Fixed Eran, Isn't this fixed as well? thanks, dims > SOAP Fault information in SOAP Header > - >

[jira] Updated: (AXIS2-588) Support for streaming attachments without having to buffer first

[ http://issues.apache.org/jira/browse/AXIS2-588?page=all ] Deepak Bhole updated AXIS2-588: --- Attachment: axiom-attachmentstreaming.patch axiom-attachmentstreaming-new-files.tar.gz axiom-attachmentstreaming-sample-service.tar.

[jira] Commented: (AXIS2-500) Service client sendRobust throw exception

[ http://issues.apache.org/jira/browse/AXIS2-500?page=comments#action_12375023 ] Davanum Srinivas commented on AXIS2-500: Deepal, Do we need this for Axis2 1.0 Final? -- dims > Service client sendRobust throw exception > --

[jira] Resolved: (AXIS2-459) Remove unnecessary fields from WS-Addressing headers

[ http://issues.apache.org/jira/browse/AXIS2-459?page=all ] Davanum Srinivas resolved AXIS2-459: Resolution: Won't Fix Since Eran is silent on this one...marking as won't fix :) -- dims > Remove unnecessary fields from WS-Addressing headers >

[jira] Resolved: (AXIS2-451) Multiple attachments

[ http://issues.apache.org/jira/browse/AXIS2-451?page=all ] Davanum Srinivas resolved AXIS2-451: Resolution: Won't Fix we don't intend to implement SwA in Axis2. > Multiple attachments > > > Key: AXIS2-451 >

[jira] Resolved: (AXIS2-388) Proxy support requires all properties to be set

[ http://issues.apache.org/jira/browse/AXIS2-388?page=all ] Davanum Srinivas resolved AXIS2-388: Resolution: Fixed Looks like this is resolved. Please reopen if needed. thanks, dims > Proxy support requires all properties to be set > -

[jira] Created: (AXIS2-588) Support for streaming attachments without having to buffer first

Support for streaming attachments without having to buffer first Key: AXIS2-588 URL: http://issues.apache.org/jira/browse/AXIS2-588 Project: Apache Axis 2.0 (Axis2) Type: Improvement Components: om

[jira] Commented: (AXIS2-587) WSDL2Java generates duplicate fault classes, can't compile generated stub

[ http://issues.apache.org/jira/browse/AXIS2-587?page=comments#action_12375017 ] Simon Fell commented on AXIS2-587: -- That should be Axis 2.0 RC1 > WSDL2Java generates duplicate fault classes, can't compile generated stub > -

[jira] Updated: (AXIS2-587) WSDL2Java generates duplicate fault classes, can't compile generated stub

[ http://issues.apache.org/jira/browse/AXIS2-587?page=all ] Simon Fell updated AXIS2-587: - Attachment: enterprise.wsdl > WSDL2Java generates duplicate fault classes, can't compile generated stub > -

[jira] Created: (AXIS2-587) WSDL2Java generates duplicate fault classes, can't compile generated stub

WSDL2Java generates duplicate fault classes, can't compile generated stub - Key: AXIS2-587 URL: http://issues.apache.org/jira/browse/AXIS2-587 Project: Apache Axis 2.0 (Axis2) Type: Bug Compon

Re: [Axis2] Proposal: WS-Addressing RelatesTo API change

On Tue, 2006-04-18 at 14:46 -0400, Davanum Srinivas wrote: > Looks good to me. do we similarly keep the setRelatesTo? and what does > that mean? +1 to David's proposal .. but I wouldn't keep setRelatesTo(RelatesTo) because that's not needed .. at the point of setting you always have the relationsh

Re: [Axis2] Proposal: WS-Addressing RelatesTo API change

David, Eran, Please take a look at the latest methods in MessageContext and Options. The diff is here [1] Thanks, dims http://svn.apache.org/viewcvs.cgi?rev=395085&view=rev On 4/18/06, David Illsley <[EMAIL PROTECTED]> wrote: > Yep, looks like we had a hole in the test suite :-( not sure how to

Re: [Axis2] Axis2 1.0 release plan

+1 from me, too. I don't think it's ready for an official 1.0 yet, but the code is definitely getting more solid. - Dennis robert lazarski wrote: Looks great! An enthusiastic +1 from me for RC2 . Robert http://www.braziloutsource.com On 4/18/06, *Ruchith Fernando* < [EMAIL PROTECTED]

Re: [Axis2] Dependancy problem with XMLBeans module

Ajith Ranabahu wrote: After the XMLBeans module has been moved out, I'm facing a problem with running WSDL2Java in the IDE. What happens is that the XMLBeans module depends on the codegen module for compilation (since org.apache.axis2.xmlbeans.CodeGenerationUtility included in the xmlbeans modul

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374981 ] Ant Grinyer commented on AXIS2-565: --- Great stuff! Thanks :-) Ant > Namespace vanishes using StAXOMBuilder > -- > > Key: AXIS2-5

Re: [Axis2] Proposal: WS-Addressing RelatesTo API change

Looks good to me. do we similarly keep the setRelatesTo? and what does that mean? thanks, dims On 4/18/06, David Illsley <[EMAIL PROTECTED]> wrote: > Yep, looks like we had a hole in the test suite :-( not sure how to test > it in an interoperable way though... > > It's the end of the day here an

[jira] Commented: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

[ http://issues.apache.org/jira/browse/AXIS2-586?page=comments#action_12374971 ] Justin Schoeman commented on AXIS2-586: --- This does not seem to be entirely resolved in Axis2 0.95. Using the same configuration as before (except for Axis2 0.95 instead

[jira] Created: (AXIS2-586) CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages

CLONE -Axis2 does not deserialise abstract types correctly when receiving WSA messages -- Key: AXIS2-586 URL: http://issues.apache.org/jira/browse/AXIS2-586 Project: Apache Axis 2.0 (Axis2)

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374968 ] Davanum Srinivas commented on AXIS2-565: look out for rc2 on friday thanks, dims > Namespace vanishes using StAXOMBuilder > -- > >

Re: [Axis2] Proposal: Extending the handler invocation pattern

+1 to defer it. thanks, dims On 4/18/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > Hi Glen, > > Let's do this but let's not rush it. Even Bill isn't asking for it to be > in 1.0 .. we can add it after. > > I'm hesistatnt because I don't want to add something at this stage > without impl ex

Re: [Axis2] Proposal: Extending the handler invocation pattern

Hi Glen, Let's do this but let's not rush it. Even Bill isn't asking for it to be in 1.0 .. we can add it after. I'm hesistatnt because I don't want to add something at this stage without impl experience and then have to end up supporting it (effectively) for ever. Also there are subtleties we

Re: [Axis2] Proposal: WS-Addressing RelatesTo API change

Yep, looks like we had a hole in the test suite :-( not sure how to test it in an interoperable way though... It's the end of the day here and I can't do anything tonight so I'll do it in the morning unless anyone beats me to it ;-) RelatesTo in the W3C version is a pair of URIs, (no QNames lef

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374963 ] Ruchith Udayanga Fernando commented on AXIS2-565: - This is working in the SVN head and I think it should be available in AXIOM-1.0-RC1[1], which you can use it

Re: [Axis2] Re: Axis 2.0 support for Kerberos and NTLM

On Tue, 2006-04-18 at 11:33 -0400, Davanum Srinivas wrote: > Krishna, > > Last time we tried this the guy did not end up giving us a patch :( > > http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=httpclient+spnego&q=b > > Basically, we use Commons HTTPClient, so there would be some pieces > tha

Re: [Axis2] Proposal: WS-Addressing RelatesTo API change

Ouch, this looks like a big missing hole. Hmmm the WS-Addr test suite is missing a serious test it seems! I don't like to introduce Set .. how about just remove get/setRelatesTo and replace it with: addRelatesTo (QName relationship, String messageID) String getRelatesTo (QName relationship) I'm

WSDL2Java Server side code generation

Hey all, I'd like to be able to control the generated products. Our wsdl's and schema are early in development and thus are subject to frequent change.  I would like to be able to control the generated Skeleton, the ant build file, and the services.xml file. I've tracked down the xsl files which

[Axis2] REMINDER : Axis IRC chat TOMORROW

Hi folks! This is an automatic reminder that the weekly Axis2 developer chat will be occurring tomorrow, April 19, at: 5AM PST, 8AM EST, 1PM GMT, 7PM SLT, midnight (next day) AEST The chat takes place on the freenode IRC network, (use server irc.freenode.net), on channel #apache-axis, and is sch

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374961 ] Ant Grinyer commented on AXIS2-565: --- I think adding an extra xmlns:col="urn:mycolor" in the col element is better than not having the namespace at all in the item element...t

[jira] Commented: (AXIS2-574) NullPointer in XMLBeans Factory.parse() after OMElement.toString()

[ http://issues.apache.org/jira/browse/AXIS2-574?page=comments#action_12374959 ] Sebastian Szczygiel commented on AXIS2-574: --- I get exactly the same exception like Jens (same project and same InOut class), but in fromOM-Methode in following line:

[Axis2] Dependancy problem with XMLBeans module

oops - forgot the prefix! -- Forwarded message -- From: Ajith Ranabahu <[EMAIL PROTECTED]> Date: Apr 18, 2006 6:47 PM Subject: Dependancy problem with XMLBeans module To: Axis developer list Hi all, After the XMLBeans module has been moved out, I'm facing a problem with running

Re: [Axis2] Re: Axis 2.0 support for Kerberos and NTLM

Krishna, Last time we tried this the guy did not end up giving us a patch :( http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=httpclient+spnego&q=b Basically, we use Commons HTTPClient, so there would be some pieces that will need to go in there and there will be some configuration that will b

[jira] Updated: (AXIS2-574) NullPointer in XMLBeans Factory.parse() after OMElement.toString()

[ http://issues.apache.org/jira/browse/AXIS2-574?page=all ] Jens Schumann updated AXIS2-574: Attachment: axis-574-RC1.tar.gz Attached the same example using RC1. Did not use nightly snapshot since I did not find a .war archive for it. See build.xml if

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374935 ] Davanum Srinivas commented on AXIS2-565: OOPS!!! looking at the wrong xml. AXIOM *ADDS* an extra xmlns:col="urn:mycolor" to the color element even though it is present

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374934 ] Davanum Srinivas commented on AXIS2-565: Ant, Here's the output from the latest AXIOM. As you can see we no longer "lose" the (xmlns:col="urn:mycolor") on the item ele

Re: Dependancy problem with XMLBeans module

why dont we move those dependent code into separate module ? Ajith Ranabahu wrote: >Hi all, >After the XMLBeans module has been moved out, I'm facing a problem >with running WSDL2Java in the IDE. What happens is that the XMLBeans >module depends on the codegen module for compilation (since >org.a

[jira] Resolved: (AXIS2-572) Callback timeout incorrectly reported as an AxisFault( null )

[ http://issues.apache.org/jira/browse/AXIS2-572?page=all ] Deepal Jayasinghe resolved AXIS2-572: - Resolution: Fixed Applied the patch , the problem was I had not understand the patch correctly , I am sorry for that and thx for the patch > Cal

Dependancy problem with XMLBeans module

Hi all, After the XMLBeans module has been moved out, I'm facing a problem with running WSDL2Java in the IDE. What happens is that the XMLBeans module depends on the codegen module for compilation (since org.apache.axis2.xmlbeans.CodeGenerationUtility included in the xmlbeans module) but if I'm run

Re: [Axis2] Axis2 1.0 release plan

Looks great! An enthusiastic +1 from me for RC2 . Robert http://www.braziloutsource.comOn 4/18/06, Ruchith Fernando < [EMAIL PROTECTED]> wrote:+1 for RC2 from me too !Thanks,Ruchith On 4/18/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:> +1 for RC2.>> -- dims>> On 4/18/06, Ajith Ranabahu < [EMAI

[jira] Commented: (AXIS2-574) NullPointer in XMLBeans Factory.parse() after OMElement.toString()

[ http://issues.apache.org/jira/browse/AXIS2-574?page=comments#action_12374928 ] Davanum Srinivas commented on AXIS2-574: Nightly is here: http://cvs.apache.org/dist/axis2/nightly/ RC1 Details are as follows: * binary and source distributions - http

Re: [Axis2] Axis2 1.0 release plan

+1 for RC2 from me too ! Thanks, Ruchith On 4/18/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > +1 for RC2. > > -- dims > > On 4/18/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > > Hi, > > This seems quite ok. Gives me a bit of time to look into the issues > > > > Ajith > > > > On 4/18/06, De

[jira] Commented: (AXIS2-574) NullPointer in XMLBeans Factory.parse() after OMElement.toString()

[ http://issues.apache.org/jira/browse/AXIS2-574?page=comments#action_12374927 ] Jens Schumann commented on AXIS2-574: - Where do I get RC1? > NullPointer in XMLBeans Factory.parse() after OMElement.toString() > --

[jira] Resolved: (AXIS2-582) Default async message receiver needed for inonly MEP

[ http://issues.apache.org/jira/browse/AXIS2-582?page=all ] Deepal Jayasinghe resolved AXIS2-582: - Resolution: Fixed I added two new Asyn message receivers. So if a service author knows that his operation take long time to process the request t

[jira] Commented: (AXIS2-574) NullPointer in XMLBeans Factory.parse() after OMElement.toString()

[ http://issues.apache.org/jira/browse/AXIS2-574?page=comments#action_12374921 ] Deepal Jayasinghe commented on AXIS2-574: - I tried to run ur service and test cases , but I could not since I have latest code. I tried to use the lib that u have given

Check out this cool free iPod nano website!

Hi there. I don't usually send these on but you're going to want to see this. This company is giving away ipods. http://yourgift123.com/?r=MREUJYMGghVCBGcJDiYI&i=gmail&z=1&[EMAIL PROTECTED]&tc=21 What do you think? Cheers

[jira] Commented: (AXIS2-572) Callback timeout incorrectly reported as an AxisFault( null )

[ http://issues.apache.org/jira/browse/AXIS2-572?page=comments#action_12374918 ] rnell commented on AXIS2-572: - It has been my experience is that the looping in the while-loop almost never happens, the wait() completes due to a notify() or timeout, and there is

[jira] Assigned: (AXIS2-572) Callback timeout incorrectly reported as an AxisFault( null )

[ http://issues.apache.org/jira/browse/AXIS2-572?page=all ] Deepal Jayasinghe reassigned AXIS2-572: --- Assign To: Deepal Jayasinghe > Callback timeout incorrectly reported as an AxisFault( null ) >

Re: [jira] Commented: (AXIS2-434) SOAPMonitor ported to axis2

Thanks Ajith . Robert http://www.braziloutsource.comOn 4/18/06, Ruchith Udayanga Fernando (JIRA) < [EMAIL PROTECTED]> wrote:[ http://issues.apache.org/jira/browse/AXIS2-434?page=comments#action_12374847 ]Ruchith Udayanga Fernando commented on AXIS2-434:---

[jira] Commented: (AXIS2-572) Callback timeout incorrectly reported as an AxisFault( null )

[ http://issues.apache.org/jira/browse/AXIS2-572?page=comments#action_12374912 ] Deepal Jayasinghe commented on AXIS2-572: - I just went though your patch and realized that the wile loop will kill the CPU power , we had the somewhat similar mechanism

[jira] Assigned: (AXIS2-561) codegen schema lookup bug

[ http://issues.apache.org/jira/browse/AXIS2-561?page=all ] Deepal Jayasinghe reassigned AXIS2-561: --- Assign To: Ajith Harshana Ranabahu > codegen schema lookup bug > - > > Key: AXIS2-561 > URL: http://issue

[jira] Commented: (AXIS2-584) JiBX data binding support broken

[ http://issues.apache.org/jira/browse/AXIS2-584?page=comments#action_12374909 ] Deepal Jayasinghe commented on AXIS2-584: - I can not see any test cases in JiBX module , it will be great if you can add few test cases , that no one will break agian.

[jira] Assigned: (AXIS2-585) WS-Addressing - Incorrect cardinality for RelatesTo in handler and on API

[ http://issues.apache.org/jira/browse/AXIS2-585?page=all ] Deepal Jayasinghe reassigned AXIS2-585: --- Assign To: Eran Chinthaka > WS-Addressing - Incorrect cardinality for RelatesTo in handler and on API > ---

Re: [Axis2] Axis2 1.0 release plan

+1 for RC2. -- dims On 4/18/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > Hi, > This seems quite ok. Gives me a bit of time to look into the issues > > Ajith > > On 4/18/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > > Hi all; > > > > Well I also went through the JIRA list and found that t

[jira] Resolved: (AXIS2-544) Java2WSDL generates invalid WSDL

[ http://issues.apache.org/jira/browse/AXIS2-544?page=all ] Deepal Jayasinghe resolved AXIS2-544: - Resolution: Fixed applied the patch. Thank you very much for the patch and we are looking for some more patches > Java2WSDL generates invalid WSD

[jira] Resolved: (AXIS2-349) Supporting multiple cookies

[ http://issues.apache.org/jira/browse/AXIS2-349?page=all ] Deepal Jayasinghe resolved AXIS2-349: - Fix Version: 0.96 Resolution: Fixed currently we have cookie support and the correct cookie will be override by next cookie id > Supporting

[jira] Commented: (AXIS2-565) Namespace vanishes using StAXOMBuilder

[ http://issues.apache.org/jira/browse/AXIS2-565?page=comments#action_12374896 ] Ant Grinyer commented on AXIS2-565: --- Thanks for looking at this issue so soon; however, I'm still confused as to the state of this issue? Myself and a few other programmers a

Re: [Axis2] Axis2 1.0 release plan

Hi, This seems quite ok. Gives me a bit of time to look into the issues Ajith On 4/18/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > Hi all; > > Well I also went through the JIRA list and found that there are a > number of JIRAs that we have to fix before 1.0. So as you suggested lets > go f

Re: [Axis2] Axis2 1.0 release plan

Hi all; Well I also went through the JIRA list and found that there are a number of JIRAs that we have to fix before 1.0. So as you suggested lets go for RC2 on this Friday and keep that for about a week for review. Since we have considerable code changes it is better to do another RC before decl

Re: [Axis2] Axis2 1.0 release plan

Hi All, It seems that a number of issues has been reported about the codegen utility (probably caused by the major surgery we did for removing WOM). So it seems to me that the code freeze tomorrow (19th Apr) is not realistic. Anyway it is better for us to do a RC2 release before 1.0 at this state.

Re: [jira] Commented: (AXIS2-580) Admin Console Security does not work at all

Hmmm , Well I dont think that what I have done is a hack for 1.0 , may be that I have not dont the bast thing :) So I will really appreciate that if you could suggest the correct way of handling this .You can either send us a patch or you can give us a constructive way of doing that. Jens Schuma

[Axis2] Proposal: WS-Addressing RelatesTo API change

Hi all, I've just opened a Jira [1] that says: The WS-Addressing spec defines the RelatesTo element as: /wsa:RelatesTo This OPTIONAL (repeating) element information item contributes one abstract [relationship] property value, in the form of an (IRI, IRI) pair. The content of this eleme

[jira] Created: (AXIS2-585) WS-Addressing - Incorrect cardinality for RelatesTo in handler and on API

WS-Addressing - Incorrect cardinality for RelatesTo in handler and on API - Key: AXIS2-585 URL: http://issues.apache.org/jira/browse/AXIS2-585 Project: Apache Axis 2.0 (Axis2) Type: Bug Vers

[jira] Commented: (AXIS2-580) Admin Console Security does not work at all

[ http://issues.apache.org/jira/browse/AXIS2-580?page=comments#action_12374876 ] Jens Schumann commented on AXIS2-580: - Looks like its being fixed. But don't get me wrong - this is just an Axis2 1.0 Release hack. Isn't it;) > Admin Console Security doe

Re: [Axis2] Axis2 1.0 release plan

Hi Jens; we will definitely fix the issue before 1.0 Jens Schumann wrote: >Resend because of broken web client. Hope this gets through this time. > > >Deepal, > >luckily you just closed AXIS2-580;). > >In my opinion (and short time usin

[jira] Created: (AXIS2-584) JiBX data binding support broken

JiBX data binding support broken Key: AXIS2-584 URL: http://issues.apache.org/jira/browse/AXIS2-584 Project: Apache Axis 2.0 (Axis2) Type: Bug Environment: n/a Reporter: Dennis Sosnoski Changes to Axiom and serialization techn

Re: [Axis2] Axis2 1.0 release plan

The recent Axiom changes broke JiBX data binding support, which I'd definitely like to have working for the 1.0 release. I'm currently investigating what changed and how I can make it work again (along with adding a unit test, to make sure the build won't succeed if other changes break this in

Re: [Axis2] Axis2 1.0 release plan

Hi, Am working on both the issues and hopefully will be able to fix them soon Ajith On 4/18/06, Jens Schumann <[EMAIL PROTECTED]> wrote: > Resend because of broken web client. Hope this gets through this time. > > > Deepal, > > luckily

[jira] Resolved: (AXIS2-562) ?wsdl gives empty types element

[ http://issues.apache.org/jira/browse/AXIS2-562?page=all ] Deepal Jayasinghe resolved AXIS2-562: - Resolution: Cannot Reproduce I tryied to regenerate the problem , but I could not able to do that. So if you still have the proble pls re-open th

Re: [Axis2] Axis2 1.0 release plan

Resend because of broken web client. Hope this gets through this time. Deepal, luckily you just closed AXIS2-580;). In my opinion (and short time using axis2) there are two criticial issues left which I would love to see fixed before a

[jira] Resolved: (AXIS2-575) Support exploded .aar deployment

[ http://issues.apache.org/jira/browse/AXIS2-575?page=all ] Deepal Jayasinghe resolved AXIS2-575: - Resolution: Fixed We do support directory based module and service deployment. What you have to do is create a directory under /services say foo

[jira] Resolved: (AXIS2-580) Admin Console Security does not work at all

[ http://issues.apache.org/jira/browse/AXIS2-580?page=all ] Deepal Jayasinghe resolved AXIS2-580: - Resolution: Fixed user will be validate before doing any admin operations > Admin Console Security does not work at all > ---

[Axis2] Axis2 1.0 release plan

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all; We released Axis2 1.0 RC1 on 9th April for user and developer review (and still there to review) . Since then we found a few bugs (not critical and wont cause any API or major code changes) and we fixed most of them and I am sure that we can