Re: [Axis2] making minOccurs=1 by default for wsdl generated with POJO

On Tue, Jan 5, 2010 at 8:26 PM, Mauro Molinari wrote: > Mauro Molinari ha scritto: > > Please note that all my trials and researches were carried out on .NET 1.1 >> and .NET 2.0 interoperability. I don't have details on the behaviours of 3.x >> .NET client generation tools. Maybe in the later ver

[jira] Resolved: (AXIS2-4200) ConverterUtil.compare fails for BigInteger values

[ https://issues.apache.org/jira/browse/AXIS2-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4200. - Resolution: Fixed fixed the issue with revision 896320 > Convert

[jira] Commented: (AXIS2-3156) OMElement.declareDefaultNamespace() declares empty namespace for child element.

[ https://issues.apache.org/jira/browse/AXIS2-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796853#action_12796853 ] chris snow commented on AXIS2-3156: --- I have the same issue with Axis2 1.5.1 > OMElement.

[jira] Updated: (AXIS2-4353) ServiceClient can not resolve WSDL with imported schemas

[ https://issues.apache.org/jira/browse/AXIS2-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4353: --- Assignee: Amila Chinthaka Suriarachchi (was: Andreas Veithen) > ServiceClient can not resolv

Re: [Axis2] making minOccurs=1 by default for wsdl generated with POJO

Mauro Molinari ha scritto: Please note that all my trials and researches were carried out on .NET 1.1 and .NET 2.0 interoperability. I don't have details on the behaviours of 3.x .NET client generation tools. Maybe in the later versions all the issues have been solved (so that minOccurs=0 could

[jira] Commented: (AXIS2-4353) ServiceClient can not resolve WSDL with imported schemas

[ https://issues.apache.org/jira/browse/AXIS2-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796681#action_12796681 ] Ben Reif commented on AXIS2-4353: - That's correct, they are stored in a jar and do not chan

Re: [Axis2] making minOccurs=1 by default for wsdl generated with POJO

On Tue, Jan 5, 2010 at 12:06 PM, Dennis Sosnoski wrote: It's definitely best to use minOccurs=1 for primitives. nillable=true is *not* a good choice in general, and I'd recommend you instead go with minOccurs=0 for object types. Why is nillable=true bad? 1. It requires the element to still be

[jira] Updated: (AXIS2-4596) Client unable to turn on addressing with UsingAddressing in the WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Katherine Sanders updated AXIS2-4596: - Attachment: 632660.patch Here's a patch that fixes the problem. I've modified BindingPro

[jira] Commented: (AXIS2-4200) ConverterUtil.compare fails for BigInteger values

[ https://issues.apache.org/jira/browse/AXIS2-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796643#action_12796643 ] David Übelacker commented on AXIS2-4200: Have the same problem with version 1.5.1

[jira] Updated: (AXIS2-4596) Client unable to turn on addressing with UsingAddressing in the WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4596: --- Component/s: (was: Addressing) jaxws > Client unable to turn on addressi

[jira] Created: (AXIS2-4596) Client unable to turn on addressing with UsingAddressing in the WSDL

Client unable to turn on addressing with UsingAddressing in the WSDL Key: AXIS2-4596 URL: https://issues.apache.org/jira/browse/AXIS2-4596 Project: Axis2 Issue Type: Bug

[jira] Commented: (AXIS2-3300) minOccurs="0" always generated by Java2WSDL - problems with .NET client generation

[ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796621#action_12796621 ] Amila Chinthaka Suriarachchi commented on AXIS2-3300: - I have started a

[jira] Commented: (AXIS2-3300) minOccurs="0" always generated by Java2WSDL - problems with .NET client generation

[ https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796616#action_12796616 ] Mauro Molinari commented on AXIS2-3300: --- This is acceptable and is ok for .NET >=2.0

Re: [Axis2] making minOccurs=1 by default for wsdl generated with POJO

Amila Suriarachchi wrote: On Tue, Jan 5, 2010 at 12:06 PM, Dennis Sosnoski > wrote: Hi Amila, It's definitely best to use minOccurs=1 for primitives. nillable=true is *not* a good choice in general, and I'd recommend you instead go with minOccurs=0 f

Re: [Axis2] making minOccurs=1 by default for wsdl generated with POJO

On Tue, Jan 5, 2010 at 12:06 PM, Dennis Sosnoski wrote: > Hi Amila, > > It's definitely best to use minOccurs=1 for primitives. nillable=true is > *not* a good choice in general, and I'd recommend you instead go with > minOccurs=0 for object types. > > Why is nillable=true bad? 1. It requires the