JSON support for Axis2C (GSoC2007)

Hi, I have been working on the implementation of StAX parser for JSON support for Axis2C project and I went through the StAX wrapper that is used in Axis2C. I basically had look at *axiom_xml_reader.h* and *axiom_xml_writer.h *and I do have few doubts on the regarding the implementation of the

[jira] Created: (AXIS2C-608) Axis2/C transport sender unable to handle multiple transports.

Axis2/C transport sender unable to handle multiple transports. -- Key: AXIS2C-608 URL: https://issues.apache.org/jira/browse/AXIS2C-608 Project: Axis2-C Issue Type: Bug

Re: JSON support for Axis2C (GSoC2007)

Kasun Indrasiri wrote: Hi, I have been working on the implementation of StAX parser for JSON support for Axis2C project and I went through the StAX wrapper that is used in Axis2C. I basically had look at /axiom_xml_reader.h/ and / axiom_xml_writer.h /and I do have few doubts on the

Re: JSON support for Axis2C (GSoC2007)

Hi, I think it's better to look at guththila api and implement it to support JSON. Then we can easily write guththlia reader/writer wrapper like wrapper to plug JSON parser to Axiom. I think Java people did the same thing. The real problem is how to handle both XML JSON at the same time?. :(

XML stax parser with improved performance

Hi, In the past few weeks I was going through the code in Guththila and I was trying to identify the weaknesses in the parser. I was playing around with the code and introduced quite a lot of changes. At the end I realized that I have a completely different parser from the original one. In fact

Re: XML stax parser with improved performance

Hi Supun, Supun Kamburugamuva [EMAIL PROTECTED] writes: Hi, In the past few weeks I was going through the code in Guththila and I was trying to identify the weaknesses in the parser. I was playing around with the code and introduced quite a lot of changes. At the end I realized that I have

Re: XML stax parser with improved performance

Hi, I would really like to contribute this code to Apache Axis2/C. But there are few difficulties in doing that. First one is that I have written it without any dependency to Axis2/C. The next major concern is that I couldn't test it rigorously (I have tested it with few XML files) but I

Re: XML stax parser with improved performance

Supun Kamburugamuva [EMAIL PROTECTED] writes: Hi, I would really like to contribute this code to Apache Axis2/C. But there are few difficulties in doing that. First one is that I have written it without any dependency to Axis2/C. The next major concern is that I couldn't test it

Re: XML stax parser with improved performance

Supun Kamburugamuva wrote: Hi, I would really like to contribute this code to Apache Axis2/C. But there are few difficulties in doing that. First one is that I have written it without any dependency to Axis2/C. The next major concern is that I couldn't test it rigorously (I have tested it

[jira] Commented: (AXIS2C-480) improve support for XSD constructs

[ https://issues.apache.org/jira/browse/AXIS2C-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500080 ] Franz Fehringer commented on AXIS2C-480: For real world use respective as a touchstone for AXIS2C you could

Re: XML stax parser with improved performance

On 5/30/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Given that new code is similar to old code and is better, why not replace current code in Guththila with new code? That helps in terms of maintenance I suppose - rather than to maintain two code bases, maintain one. What advantage would we

[jira] Created: (AXIS2C-609) NullPointerException generating WSDL with anonymous simple types

NullPointerException generating WSDL with anonymous simple types Key: AXIS2C-609 URL: https://issues.apache.org/jira/browse/AXIS2C-609 Project: Axis2-C Issue Type: Bug

Re: XML stax parser with improved performance

Supun Kamburugamuva wrote: On 5/30/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Given that new code is similar to old code and is better, why not replace current code in Guththila with new code? That helps in terms of maintenance I suppose - rather than to maintain two code bases, maintain

Building Axiom/C using axutil_string

Hi, At the moment Axiom has the interface required to build using axutil_string instead of char *. AFAIK there is a problem with this approach. When a XML comes to the parser sometimes it doesn't know the length of the buffer containing the XML i.e. XML is in a file. So at the beginning parser

[jira] Created: (AXIS2-2730) Classloader getResourceAsStream error, returns null.

Classloader getResourceAsStream error, returns null. Key: AXIS2-2730 URL: https://issues.apache.org/jira/browse/AXIS2-2730 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions:

[jira] Commented: (AXIS2-48) SOAP Encoding support

[ https://issues.apache.org/jira/browse/AXIS2-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500060 ] Ralf Hauser commented on AXIS2-48: -- Hi Davanum, In AXIS2-2242 , you write that there is no plan to support

Axis2 Stack Comparison

Hi I have seen http://wiki.apache.org/ws/StackComparison that Axis2 http://wiki.apache.org/ws/StackComparison%20that%20Axis2 is supporting WS-Eventing and no modules is mentioned there. Does that mean axis2 supports WS-Eventing by itself? Thanks And Regards Smitha Aldrin

[jira] Created: (AXIS2-2731) Add progress bar to IDEA AXIS2 WSDL2Java plugin

Add progress bar to IDEA AXIS2 WSDL2Java plugin --- Key: AXIS2-2731 URL: https://issues.apache.org/jira/browse/AXIS2-2731 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components:

[jira] Resolved: (AXIS2-2724) java.net.BindException: Address already in use: connect when sending ~10000 requests to a service

[ https://issues.apache.org/jira/browse/AXIS2-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2724. -- Resolution: Fixed To have the feature you can do two things

Classpath

Hi Can anybody pls explain what classpath meant in axis2? My Problem is I am putting savan-config.xml in the WEB-INF directory. Still it's complaining cannot find savan-config.xml in the classpath. Pls do respond Thanks And Regards Smitha Aldrin The information contained in

[jira] Resolved: (AXIS2-2630) webapp ?wsdl fails validation from Eclipse WTP 2.0 wsdl validation

[ https://issues.apache.org/jira/browse/AXIS2-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2630. -- Resolution: Fixed issue is fixed in the current SVN webapp ?wsdl fails validation

[jira] Commented: (AXIS2-2553) When using custom protocol (eg myhttps) AxisFault caused by MalformedURLException is thrown during web sevice invocation

[ https://issues.apache.org/jira/browse/AXIS2-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500088 ] Deepal Jayasinghe commented on AXIS2-2553: -- Hi Sergio; could you please attach SVN dif not the source

[jira] Resolved: (AXIS2-2531) Make the outgoing SOAPEnvelope available to the service

[ https://issues.apache.org/jira/browse/AXIS2-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2531. -- Resolution: Won't Fix Hi Thilina, I can not understand how do we make out going SOAP

[jira] Resolved: (AXIS2-1473) org.apache.axis2.AxisFault: Connection reset - connections are not closing for long time

[ https://issues.apache.org/jira/browse/AXIS2-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1473. -- Resolution: Fixed Issues is fixed , please have a look at

[jira] Assigned: (AXIS2-2589) com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.

[ https://issues.apache.org/jira/browse/AXIS2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-2589: Assignee: Amila Chinthaka Suriarachchi (was: Deepal Jayasinghe)

Re: Axis2 Stack Comparison

Savan module [1] supports WS-Eventing. Thanks, Ruchith [1] https://svn.apache.org/repos/asf/webservices/savan/trunk/java/ On 5/30/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi I have seen http://wiki.apache.org/ws/StackComparison that Axis2 is supporting WS-Eventing and no

[jira] Resolved: (AXIS2-1916) jars, mars and aars are locked in the file system even after undeployment of the axis2 webapp

[ https://issues.apache.org/jira/browse/AXIS2-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1916. -- Resolution: Fixed Issue is fixed in both 1.2 release and the trunk Thanks Deepal

[Axis2][continuum] BUILD FAILURE

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2182 Build statistics: State: Failed Previous State: Failed Started at: Wed, 30 May 2007 10:36:08 + Finished at: Wed, 30 May 2007 10:59:40 + Total

[jira] Reopened: (AXIS2-2531) Make the outgoing SOAPEnvelope available to the service

[ https://issues.apache.org/jira/browse/AXIS2-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Gunarathne reopened AXIS2-2531: --- Hi Deepal, This not about the client side... This request is to change the InOut message

[jira] Updated: (AXIS2-2451) WS Policy Attachments for services.xml

[ https://issues.apache.org/jira/browse/AXIS2-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nencho Lupanov updated AXIS2-2451: -- Attachment: PolicyReference.diff Functionality added: public OMElement

[jira] Updated: (AXIS2-2451) WS Policy Attachments for services.xml

[ https://issues.apache.org/jira/browse/AXIS2-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nencho Lupanov updated AXIS2-2451: -- Attachment: PolicyEngine.diff basic changes: 1) The policy content is extracted in a thread

[jira] Updated: (AXIS2-2451) WS Policy Attachments for services.xml

[ https://issues.apache.org/jira/browse/AXIS2-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nencho Lupanov updated AXIS2-2451: -- Attachment: PolicyReaderThread.java Thread for reading remote policy reference content.We need

[axis2]Policy references

hi all, I supplied some diffs for https://issues.apache.org/jira/browse/AXIS2-2451 it is described in the jira issue what changes are required, The jira issue is about handling policy references like this: wsp:PolicyReference

[AXIS2] : multidimensional arrays

Hi all, Could it be that axis2 does not handle properly multidimensional arrays. This was an old problem, and I think it was fixed in the 1.1 or 1.1.1release and I haven't tested it ever since. Now it does not work again (even with two dimensional arrays). I am using the axis2-SNAPSHOT war

[jira] Resolved: (AXIS2-2634) When several requests are processed simultaneously, parent nodes are mixed

[ https://issues.apache.org/jira/browse/AXIS2-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-2634. -- Resolution: Fixed issue is fixed in current svn When several requests are processed

[jira] Created: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

java.lang.ArrayStoreException if you have methods that return same object type in array and single type --- Key: AXIS-2669 URL:

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same Object both in array and as

[Axis2][continuum] BUILD FAILURE

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2189 Build statistics: State: Failed Previous State: Failed Started at: Wed, 30 May 2007 12:03:00 + Finished at: Wed, 30 May 2007 12:38:18 + Total

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same Object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same Object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same Object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[axis2] Quick ClassLoader questions

Hi folks! So deployment.util.Utils.getClassLoader() sets up a classloader with a classpath consisting of: - The passed root dir (i.e. modules/ or services/) - The lib and Lib subdirs - Any jar files found in lib/Lib 1) Who uses Lib/ with a capital L? Do we need this? 2) Should the

[Axis2] Clustering: No need for ContextManager contextAdded contextRemoved methods

I think there is no need for the contextAdded contextRemoved methods in the ContextManager interface. contextUpdated should suffice. The reason is, when a contextUpdated message is received, if it does not exist on a particular node, it can be created. Similary, the context cleanup mechanism

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

Re: Accessing WSDL2 styles in Axis2 codegen emitter templates

Keith, Thanks for the quick response on this, however, I still have some concerns. I thought that WSDL2's style was intended to be a more general replacement for WSDL1's? If that's correct, why is a WSDL2 style attribute an AxisOperation Parameter while a WSDL1 style attribute is a first class

Re: Accessing WSDL2 styles in Axis2 codegen emitter templates

We do support all WSDL 2.0 MEPS at the moment. The WSDL 2.0 style has no relationship to the WSDL 1.1 Styles (rpc, document), they just enforce restrictions on how the element itself will look like. WSDL 2 has defined three styles IRI, rpc and multipart. If you look at the spec [1] you will see

[Axis2][continuum] BUILD SUCCESSFUL

Online report : http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2191 Build statistics: State: Ok Previous State: Failed Started at: Wed, 30 May 2007 13:05:38 + Finished at: Wed, 30 May 2007 13:52:28 + Total time:

[jira] Updated: (AXIS-2669) java.lang.ArrayStoreException if you have methods that return same object type in array and single type

[ https://issues.apache.org/jira/browse/AXIS-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vesa Luomala updated AXIS-2669: --- Description: I have noticed the following problem: If I return the same object both in array and as

[jira] Created: (AXIS2-2732) Too much introspection in MessageReceivers

Too much introspection in MessageReceivers -- Key: AXIS2-2732 URL: https://issues.apache.org/jira/browse/AXIS2-2732 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Glen Daniels

[jira] Created: (AXIS2-2733) java.lang.RuntimeException thrown from parsing incorrect XML causes the entire Axis thread to hang

java.lang.RuntimeException thrown from parsing incorrect XML causes the entire Axis thread to hang -- Key: AXIS2-2733 URL:

[jira] Updated: (AXIS2-2733) java.lang.RuntimeException thrown from parsing incorrect XML causes the entire Axis thread to hang

[ https://issues.apache.org/jira/browse/AXIS2-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Gibbs updated AXIS2-2733: --- Description: I'm using the Betfair API and Axis 2 in ADB mode, and have discovered that

Re: Accessing WSDL2 styles in Axis2 codegen emitter templates

Keith, I agree that the adjuncts spec reference you provided identifies the pre-defined styles, but I was thinking more about this section in the core spec: http://www.w3.org/TR/2007/PR-wsdl20-20070523/#InterfaceOperationStyle There isn't anything in this section that limits the styles to those

[jira] Created: (AXIS2-2734) Disabling REST should should make the http binding generation in WSDL stop too..

Disabling REST should should make the http binding generation in WSDL stop too.. Key: AXIS2-2734 URL: https://issues.apache.org/jira/browse/AXIS2-2734 Project: Axis 2.0

[jira] Assigned: (AXIS2-2734) Disabling REST should should make the http binding generation in WSDL stop too..

[ https://issues.apache.org/jira/browse/AXIS2-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas reassigned AXIS2-2734: --- Assignee: Keith Godwin Chapman Disabling REST should should make the http binding

Re: [Axis2] Switch either to maven or maven2

+1 for a M2 build asankha Afkham Azeez wrote: +1 for moving to Maven2. If there are problems with the Maven2 build, lets fix those, and after some time, lets scrap the Maven1 build. -- Azeez On 5/29/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi all, As you all know in

[jira] Created: (AXIS2-2735) CLONE -NullPointerException generating WSDL with anonymous simple types

CLONE -NullPointerException generating WSDL with anonymous simple types --- Key: AXIS2-2735 URL: https://issues.apache.org/jira/browse/AXIS2-2735 Project: Axis 2.0 (Axis2)

[jira] Closed: (AXIS2-2735) CLONE -NullPointerException generating WSDL with anonymous simple types

[ https://issues.apache.org/jira/browse/AXIS2-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Voelkle closed AXIS2-2735. - Resolution: Invalid Sorry, I was misusing JIRA. I have the same issue using the same test case

[jira] Created: (AXIS2-2736) Allow to address own xsd from own wsdl

Allow to address own xsd from own wsdl -- Key: AXIS2-2736 URL: https://issues.apache.org/jira/browse/AXIS2-2736 Project: Axis 2.0 (Axis2) Issue Type: Wish Components: kernel Affects

[jira] Updated: (AXIS2-2736) Allow to address own xsd from own wsdl

[ https://issues.apache.org/jira/browse/AXIS2-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Seng updated AXIS2-2736: --- Attachment: my.aar import like xsd:import namespace=urn:myxsd schemaLocation=myxsd.xsd / Allow to

[jira] Updated: (AXIS2-2736) Allow to address own xsd from own wsdl

[ https://issues.apache.org/jira/browse/AXIS2-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Seng updated AXIS2-2736: --- Attachment: my2.aar import like xsd:import namespace=urn:myxsd schemaLocation=my2?xsd=myxsd.xsd /

Re: Axis2 Architecture problems.

hi deepl, I agree with you that we have already release the 1.2 and there is no way to do any changes (even every one agrees as well). this is a solution came to my mind which would adreess the two issues you have raise. public void next(MessageContext messageContext) throws AxisFault {

Re: [Axis2] Clustering: No need for ContextManager contextAdded contextRemoved methods

Hi Azeez, On 5/30/07, Afkham Azeez [EMAIL PROTECTED] wrote: I think there is no need for the contextAdded contextRemoved methods in the ContextManager interface. contextUpdated should suffice. The reason is, when a contextUpdated message is received, if it does not exist on a particular

[jira] Updated: (AXIS2-2726) The service cannot be found for the endpoint reference (EPR)

[ https://issues.apache.org/jira/browse/AXIS2-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhagya Kitty updated AXIS2-2726: Priority: Critical (was: Major) The service cannot be found for the endpoint reference (EPR)

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

[ https://issues.apache.org/jira/browse/AXIS2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500213 ] Michael Krumpus commented on AXIS2-565: --- I know that the root problem here was closed, but I do think that the

[jira] Created: (AXIS-2670) Nested sequences with multiple constraints aren't generating correctly

Nested sequences with multiple constraints aren't generating correctly -- Key: AXIS-2670 URL: https://issues.apache.org/jira/browse/AXIS-2670 Project: Axis Issue Type: Bug

[jira] Created: (AXIS2-2737) XSD2Java generates bad code

XSD2Java generates bad code --- Key: AXIS2-2737 URL: https://issues.apache.org/jira/browse/AXIS2-2737 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1, 1.2 Environment: Tested on Windows

[jira] Updated: (AXIS2-2737) XSD2Java generates bad code

[ https://issues.apache.org/jira/browse/AXIS2-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Adili updated AXIS2-2737: -- Attachment: XSD2JavaBug.zip XSD2Java generates bad code ---

[axis2] More Modules and classpaths

I'd like to be able to deploy a Module by just putting it on the classpath... CLASSPATH=...; addressing.mar; ... This is pretty easy to implement, seems highly convenient, and goes along with some other deployment-related stuff I'm thinking about, but I wanted to run it past folks first. It

Re: [axis2] More Modules and classpaths

Glen, I thought this is already implemented (However I stand to be corrected) --Rajith On 5/30/07, Glen Daniels [EMAIL PROTECTED] wrote: I'd like to be able to deploy a Module by just putting it on the classpath... CLASSPATH=...; addressing.mar; ... This is pretty easy to implement, seems

WS-Notification

Hi All Can anybody explain me what's the difference between WS-Notification and WS-Eventing? Thanks And Regards Smitha Aldrin The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and

[jira] Updated: (AXIS-1603) org.xml.sax.SAXException: Invalid element in com.test.sample._CurveResponse - Status

[ https://issues.apache.org/jira/browse/AXIS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna R Seelam updated AXIS-1603: --- Description: Hi , we are using axis-1_2beta2 wsdl2java compiler to generate Stub Classes. we

[jira] Commented: (AXIS-1603) org.xml.sax.SAXException: Invalid element in com.test.sample._CurveResponse - Status

[ https://issues.apache.org/jira/browse/AXIS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500279 ] Krishna R Seelam commented on AXIS-1603: Sorry I did not mean to edit org.xml.sax.SAXException: Invalid

[jira] Updated: (AXIS-1603) org.xml.sax.SAXException: Invalid element in com.test.sample._CurveResponse - Status

[ https://issues.apache.org/jira/browse/AXIS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna R Seelam updated AXIS-1603: --- Description: Hi , we are using axis-1_2beta2 wsdl2java compiler to generate Stub Classes. we

[jira] Commented: (AXIS-1603) org.xml.sax.SAXException: Invalid element in com.test.sample._CurveResponse - Status

[ https://issues.apache.org/jira/browse/AXIS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500282 ] Krishna R Seelam commented on AXIS-1603: Hi We (the Webservice client) generates the same problem when the

[jira] Commented: (AXIS2-2721) axis 2.0 parent jar missing on ibiblio.org for maven 2

[ https://issues.apache.org/jira/browse/AXIS2-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500284 ] Larry Hamel commented on AXIS2-2721: Maybe it will be more clear to describe the 'use-case' of how axis-parent

[jira] Commented: (AXIS-2613) faultString: org.xml.sax.SAXException: Invalid element in com.icl.content.contentReq -providers error accurs frequently

[ https://issues.apache.org/jira/browse/AXIS-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500286 ] Krishna R Seelam commented on AXIS-2613: Chethan We got the same problem at client end when the wsdl

Sequence/choice minOccurs and maxOccurs support attribute Group / Group support with ADB

I recently added the following new features to the ADB. 1. Sequence and choice level minOccurs and maxOccurs i.e now ADB can support following type schemas. xsd:element name=TestParticalSequenceMaxOccurs1 type=tns:TestParticalSequenceMaxOccursType1/ xsd:complexType