[ANN] updated XWSDLC 2.0.3 (WSDL 2 JavaJnterface Ant task that uses XMLBeans)

hi, this is last update sent to [EMAIL PROTECTED] and axis-dev - all future announcements will be sent to xgws-user AT cs.indiana.edu XWSDLC code is now updated to use .xsdconfig for mapping (wsdlpkg is no longer supported) and additionally .wsdlconfig that has the same format as .xsdconfig but

[Axis2]code is moving to head freeze the code till it is done

Hi All; I am working on the new build to Axis2 based on the modules please do not commit any changes in in the mean time Thanks Srinath

Re: [axis2]move the code to trunk/java/src

1) for the original question about the scratch I purpose to move dev to trunk/archive/java/dev/scratch. 2) +1 for the Davids suggestion I purpose following modules axis/java/modules/core - engine and the basic stuff axis/java/modules/om axis/java/modules/deployment axis/java.mldules/wsdl depe

Re: [Axis2][M1]do we need shift a war with aixs2-M1-bin.zip

yap glen it is "ship" :), Sorry Other developers .. I need the answer bit quicker (if we are to ship this next monday). I like to freeze the code for few days Thanks Srinath On Thu, 17 Feb 2005 19:14:21 -0500, Glen Daniels <[EMAIL PROTECTED]> wrote: > Hi Srinath: > > I assume you meant "ship"? :)

[jira] Commented: (AXIS-1547) Document/Literal wrapped response creates wrong SOAP envelope root element in response message.

[ http://issues.apache.org/jira/browse/AXIS-1547?page=comments#action_59365 ] Bill Keese commented on AXIS-1547: -- FYI, I think there are 2 or 3 problems that this bug addresses. (This list below is partly quoted from axis-user messages) 1) array wr

Re: [Axis2][M1]do we need shift a war with aixs2-M1-bin.zip

Hi Srinath: I assume you meant "ship"? :) And I guess I would also vote for choice #2. --Glen Srinath Perera wrote: At the yesterdays chat we decide to VOTE on the follwoing choices for aixs2-M1-bin.zip 1) Shift the aixs2-M1-bin.zip with a war e.g. aixs2/samples/*.jar axis2/docs axis2/webapps/axis

[jira] Updated: (AXIS-1821) ?wsdl handler causes StackOverflowError in certain circumstances

[ http://issues.apache.org/jira/browse/AXIS-1821?page=history ] Michael Thome updated AXIS-1821: Attachment: bogus.wsdl To reproduce the problem: 1. wsdl2java -s -B bogus.wsdl 2. ant jar 3. deploy the service in the usual way. 4. invoke http://.../Bogus?

[jira] Created: (AXIS-1821) ?wsdl handler causes StackOverflowError in certain circumstances

?wsdl handler causes StackOverflowError in certain circumstances Key: AXIS-1821 URL: http://issues.apache.org/jira/browse/AXIS-1821 Project: Axis Type: Bug Components: WSDL processing Versions:

[jira] Commented: (AXIS-1455) WSDL2Java --server-side doesn't produce wrapped stubs

[ http://issues.apache.org/jira/browse/AXIS-1455?page=comments#action_59336 ] Simon Fell commented on AXIS-1455: -- Isn't an element declaration ? > WSDL2Java --server-side doesn't produce wrapped stubs > ---

[jira] Commented: (AXIS-1455) WSDL2Java --server-side doesn't produce wrapped stubs

[ http://issues.apache.org/jira/browse/AXIS-1455?page=comments#action_59335 ] Davanum Srinivas commented on AXIS-1455: Simon, Please take a quick look at org.apache.axis.wsdl.symbolTable.SchemaUtils.isWrappedType method. It enforces the rules

[jira] Commented: (AXIS-1818) MessageElement [] for doesn't include all elements

[ http://issues.apache.org/jira/browse/AXIS-1818?page=comments#action_59330 ] Simon Fell commented on AXIS-1818: -- No, the any clearly indicates that any element from the targetnamespace is valid to appear after the Id element. The XSD validator in Xer

RE: [jira] Commented: (AXIS-1818) MessageElement [] for doesn't include all elements

Title: RE: [jira] Commented: (AXIS-1818) MessageElement [] for doesn't include all elements No, the any clearly indicates that any element from the targetnamespace is valid to appear after the Id element. The XSD validator in Xerces agrees with me. Cheers Simon -Original Message-

RE: Committers: 3 patches to commit

Can we applied them now? -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Monday, January 10, 2005 3:43 PM To: axis-dev@ws.apache.org Subject: Re: Committers: 3 patches to commit Sebastien, Please hang on. we are trying to get the TCK's to work with Axis. -- di

[jira] Assigned: (AXIS-1547) Document/Literal wrapped response creates wrong SOAP envelope root element in response message.

[ http://issues.apache.org/jira/browse/AXIS-1547?page=history ] Davanum Srinivas reassigned AXIS-1547: -- Assign To: Glen Daniels Glen, Can you please take a look at this one? (for RC3) Thanks, dims > Document/Literal wrapped response creates wrong

Re: [axis2]move the code to trunk/java/src

+1 to enforce as per Alek's (and david's) suggestion. -- dims On Wed, 16 Feb 2005 23:23:43 -0500, Aleksander Slominski <[EMAIL PROTECTED]> wrote: > +1 to modules > > only be carefult odecode about right granularity of modules. one could > say that AXIS1 is modular it has just one module with hu

[jira] Resolved: (AXIS-1815) tcpmon don't support mulit-byte encording

[ http://issues.apache.org/jira/browse/AXIS-1815?page=history ] Toshiyuki Kimura resolved AXIS-1815: Resolution: Fixed It should be fixed on the nightly build. Thanks, Toshi > tc

[jira] Created: (AXIS2-8) XSD choice not handled properly.

XSD choice not handled properly. - Key: AXIS2-8 URL: http://issues.apache.org/jira/browse/AXIS2-8 Project: Axis2 Type: Bug Components: wsdl Environment: Windows/Tomcat Reporter: kfir Bloch Assigned to: Davanum Srinivas We