Re: [axis2] RE: [ANN] Apache Axis2 1.4 Released

Hi, Now that 1.4 is released, I still see so many issues logged on JIRA that have not even been close to resolved. I think we all have to agree we can not do a release with zero jiras. When we do a release what we do is we go though the JIRA list and see what are the issues we need to

Re: [axis2] RE: [ANN] Apache Axis2 1.4 Released

hmmm... the server is either overloaded with thousands of download requests or down due to some other reson that is why I m unable to download the latest release... -- View this message in context: http://www.nabble.com/Re%3A--axis2RE%3A--ANN--Apache-Axis2-1.4-Released-tp17077356p17080628.h

[jira] Created: (AXIS2-3783) SVN conflict entries appearing on site home page

SVN conflict entries appearing on site home page Key: AXIS2-3783 URL: https://issues.apache.org/jira/browse/AXIS2-3783 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: samples,

[jira] Updated: (AXIS2-1820) javax.xml.stream.XMLStreamException: problem accessing the parser when using NTLM and stubs generated by xmlbeans

[ https://issues.apache.org/jira/browse/AXIS2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuwei updated AXIS2-1820: -- Attachment: WebServiceLocator.java Hi I use the NTLM authentication. seems this bug exist. The invoking code I

[jira] Commented: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces

[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594556#action_12594556 ] Dietmar Gaertner commented on AXIS2-2990: - This issue is not resolved in Axis2 1.4.

[jira] Reopened: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces

[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reopened AXIS2-2990: -- > WSDL port address is not correctly generated for machines having multiple > network inte

[jira] Updated: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces

[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe updated AXIS2-2990: - Assignee: Sanka Samaranayake Hi Sanka, Seems like this is a problem arise due to your rec

[jira] Created: (AXIS2-3784) WSDL port address is not correctly generated for machines having multiple network interfaces

WSDL port address is not correctly generated for machines having multiple network interfaces Key: AXIS2-3784 URL: https://issues.apache.org/jira/browse/AXIS2-3784

[jira] Commented: (AXIS2-3784) WSDL port address is not correctly generated for machines having multiple network interfaces

[ https://issues.apache.org/jira/browse/AXIS2-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594562#action_12594562 ] Dietmar Gaertner commented on AXIS2-3784: - See also: AXIS2-2990, AXIS2-3719 > WSDL

[jira] Created: (AXIS2-3785) Axis2 1.4 ships servlet-api-2.3.jar which gives a conflict in Tomcat 6

Axis2 1.4 ships servlet-api-2.3.jar which gives a conflict in Tomcat 6 -- Key: AXIS2-3785 URL: https://issues.apache.org/jira/browse/AXIS2-3785 Project: Axis 2.0 (Axis2) Iss

[Axis2] Please restart Axis2 Continuum

http://ws.zones.apache.org:1/continuum/servlet/continuum/target/Summary.vm/fid/continuumProject Looks like it stopped on 4/30 thanks, Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PR

Using Webservice via SMTP: SOAP message in body

Hi, I am looking for a easy way to send the SOAP-Message via SMTP NOT as an email attachment, but in the mail-body itself. In my case the communication between client and server is routed through a firewall which does not allow any attachments. In all Axis2-Examples the SMTP communication was rea

RE: Using Webservice via SMTP: SOAP message in body

Christopher, I think the mail transport implementation in Apache Synapse has support for this. You can use this transport as a replacement for the mail transport distributed with Axis2. Andreas _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: mardi 6 mai 2008 14:14 To

Re: Using Webservice via SMTP: SOAP message in body

Hi, The current SMTP transport in Axis2 is written according to http://people.apache.org/~pzf/SMTPBase64Binding.html . As Andreas has said, Apache Synapse project SMTP transport has the provision for your requirement. I believe we have to update the current spec. Thank you! Saminda On Tue, May

[jira] Updated: (AXIS2-3786) WSDL2Java generates incorrect class for complex types with more then one same named elements

[ https://issues.apache.org/jira/browse/AXIS2-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krystian Szczesny updated AXIS2-3786: - Attachment: DemoService.wsdl Example wsdl file > WSDL2Java generates incorrect class for

[jira] Created: (AXIS2-3786) WSDL2Java generates incorrect class for complex types with more then one same named elements

WSDL2Java generates incorrect class for complex types with more then one same named elements Key: AXIS2-3786 URL: https://issues.apache.org/jira/browse/AXIS2-3786

Re: [axis2] RE: [ANN] Apache Axis2 1.4 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We have tons of mirrors...please check the site below: http://www.apache.org/dyn/closer.cgi/ws/axis2/1_4/ If you have trouble, try the backup sites. - -- dims learn_n_share wrote: | | hmmm... the server is either overloaded with thousands of down

Re: [Axis2] Merging Kernel and JWS-API

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Deepal, Only way to override the JDK classes is by the endorsed directory mechanism :( Give me a day or so to think about this. thanks, dims Deepal jayasinghe wrote: | Hi Dims, |> Deepal, |> |> If you are talking about jws-api maven module...Pleas

Re: [Axis2] Merging Kernel and JWS-API

I don't see that as a good reason to move these API classes into kernel. In fact, in my opinion that makes things more confusing. I think keeping these things separate is cleaner, easier to understand, and more reusable. Another thing to understand is that these are API classes which are far more s

WSDL / minOccurs (patch included)

Hi, I didn't understand why Axis2 generates WSDLs for POJO functions with minOccurs=0 set for each function parameter. Either my function has a parameter X, or it has not. In the latter case no element should be created at all (that differs from having an element with minOccurs=0). So I made this

Re: WSDL / minOccurs (patch included)

Sorry, I forgot the diff file :-( Felix axis2-1.4-MinOccurs.patch Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Merging Kernel and JWS-API

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jarek, +1 to move the spec jars, now that they are pretty stable and have gone thru the TCK's. One question there is Geronimo is still on JAXWS 2.0. So that may be a block. - -- dims Jarek Gawor wrote: | I don't see that as a good reason to move t

Re: [Axis2] Merging Kernel and JWS-API

Yeah, but that doesn't matter. The spec modules are separate from rest of the Geronimo code so we can still move the API modules but they wouldn't be used in the Geronimo server right away. Jarek On Tue, May 6, 2008 at 10:19 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED

WSDL / void POJO functions (patch included)

Hi, I had some issues with Axis2 1.4 and MS Visual Studio when using POJO functions without any parameters, eg.: public String getSomething() { ... } >From the WSDL, VS generated a prototype for getSomething() that returns an instance of getSomethingResponse instead of a String. getSomethingResp

Re: [Axis2] Merging Kernel and JWS-API

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jarek, So, can you please do a svn cp right now and get them going? and start putting out SNAPSHOT's? thanks, dims Jarek Gawor wrote: | Yeah, but that doesn't matter. The spec modules are separate from rest | of the Geronimo code so we can still m

Re: Using Webservice via SMTP: SOAP message in body

Andreas Veithen wrote: Christopher, I think the mail transport implementation in Apache Synapse has support for this. You can use this transport as a replacement for the mail transport distributed with Axis2. Yes, you just need to drop the JAR file found here

Re: [axis2] RE: [ANN] Apache Axis2 1.4 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vinh, Are u serious? http://tinyurl.com/5j5n3p Thanks, dims Vinh Nguyen (vinguye2) wrote: | Hi, | | What's very interesting to me is that I haven't seen any emails from the | Axis2 team notifying developers that 1.4 will be released, or even vote |

Re: WSDL / void POJO functions (patch included)

Hi Felix, Would be better if you can create a Jira and attach the patch. Jira makes it easier to keep track of changes. Thanks, Keith. On Tue, May 6, 2008 at 7:57 PM, Felix J. Ogris <[EMAIL PROTECTED]> wrote: > Hi, > > I had some issues with Axis2 1.4 and MS Visual Studio when using POJO > func

Re: WSDL / minOccurs (patch included)

Hi Felix, Same again :). Would be better if you can create a Jira and attach the patch. Jira makes it easier to keep track of changes. Thanks, Keith. On Tue, May 6, 2008 at 7:46 PM, Felix J. Ogris <[EMAIL PROTECTED]> wrote: > Sorry, I forgot the diff file :-( > > Felix > > > ---

[jira] Commented: (AXIS2-2990) WSDL port address is not correctly generated for machines having multiple network interfaces

[ https://issues.apache.org/jira/browse/AXIS2-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594757#action_12594757 ] Keith Godwin Chapman commented on AXIS2-2990: - No This was not introduces after

Estimated Complexity field in Jira

I find that we have a field called "Estimated Complexity" in our Jira. I propose that we use this field to mark issues to help people pick what to fix based on their expertise. Specially helps with new contributions. I find that the Harmony project is using this. The possible values are: * Unk

Re: Estimated Complexity field in Jira

+1 for the idea, This will help in defining the time lines as well. Thanks Sandakith On Wed, May 7, 2008 at 8:00 AM, Samisa Abeysinghe < [EMAIL PROTECTED]> wrote: > I find that we have a field called "Estimated Complexity" in our Jira. > I propose that we use this field to mark issues to help peo

Re: Estimated Complexity field in Jira

+1, Suran did bring this idea up some time ago too. If a Jira admin can add these fields I can volunteer to go through some Jiras and assign Estimated Complexities. Thanks, Keith. On Wed, May 7, 2008 at 8:00 AM, Samisa Abeysinghe < [EMAIL PROTECTED]> wrote: > I find that we have a field called "

Re: Estimated Complexity field in Jira

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 s/James Gosling/Deepal/g and we are all set :) +1 from me. - -- dims keith chapman wrote: | +1, Suran did bring this idea up some time ago too. If a Jira admin can add | these fields I can volunteer to go through some Jiras and assign Estimated | C

Re: Estimated Complexity field in Jira

s/James Gosling/Deepal/g and we are all set :) hehe :) +1 from me. -Deepal +1 from me. -- dims keith chapman wrote: | +1, Suran did bring this idea up some time ago too. If a Jira admin can add | these fields I can volunteer to go through some Jiras and assign Estimated | Complexities

Re: Estimated Complexity field in Jira

+1, will help more people to contribute to Axis2. thanks, nandana On Wed, May 7, 2008 at 9:29 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > s/James Gosling/Deepal/g and we are all set :) > > +1 from me. > > - -- dims > > keith chapman wrot

Re: WSDL / void POJO functions (patch included)

Felix J. Ogris wrote: Hi, I had some issues with Axis2 1.4 and MS Visual Studio when using POJO functions without any parameters, eg.: public String getSomething() { ... } >From the WSDL, VS generated a prototype for getSomething() that returns an instance of getSomethingResponse instead of a

Re: WSDL / minOccurs (patch included)

Thank you very much for the patch. -Deepal Sorry, I forgot the diff file :-( Felix - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Estimated Complexity field in Jira

Definitely +1. Thanks. Suran Samisa Abeysinghe wrote: I find that we have a field called "Estimated Complexity" in our Jira. I propose that we use this field to mark issues to help people pick what to fix based on their expertise. Specially helps with new contributions. I find that the Harmony

Re: [Axis2] Merging Kernel and JWS-API

I don't see that as a good reason to move these API classes into kernel. In fact, in my opinion that makes things more confusing. I think keeping these things separate is cleaner, easier to understand, and more reusable. I agreed , but the problem is we need to have multiple jar files to get a

Re: [Axis2] Merging Kernel and JWS-API

Davanum Srinivas wrote: Jarek, So, can you please do a svn cp right now and get them going? and start putting out SNAPSHOT's? +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4

[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated AXIS2-3778: --- Component/s: (was: kernel) wsdl Priority: Critical (was: Blocker) > For the case

[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4

[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated AXIS2-3778: --- Priority: Blocker (was: Critical) > For the case of multiple WSDLs and XSDs for one service, Axis2 1.3 can w

[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4

[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Dou updated AXIS2-3778: --- Description: It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs

[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4

[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Dou updated AXIS2-3778: --- Attachment: WSDLs.zip See the attached WSDLs.zip for wsdls > For the case of multiple WSDLs and XSDs

Re: WSDL / void POJO functions (patch included)

Deepal jayasinghe ([EMAIL PROTECTED]) wrote: > true Hi Deepal, thanks for your help. I didn't find that parameter neither in the docs nor the wiki, but in the source code :-). Is there somethink like http://ws.apache.org/axis/java/reference.html#GlobalAxisConfiguration for Axis2? BTW, doclitBare