Re: [Axis2] Moving Axis2 code base into JDK 1.5

Are there critical things that you see in Axis2 1.4 which would be necessary for JDK 1.4 users? If so I can agree with you otherwise I think its time to move on from JDK 1.4 .. Sanjiva. David Illsley wrote: Um, right now I'd be tempted to push out an Axis2 1.4 with JDK 1.4 support soon for ex

[jira] Updated: (AXIS2-3464) A patch for the CORBA module to support types declared insides interfaces.

[ https://issues.apache.org/jira/browse/AXIS2-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eranga Jayasundera updated AXIS2-3464: -- Attachment: corba_new_2.patch use corba_new_2.patch. It includes the missing exception.

Re: [Axis2] Moving Axis2 code base into JDK 1.5

From my experiences working with companies moving to Axis2 I'd say about half are still using JDK 1.4. If they can't count on that support being maintained I think they're likely to reconsider adopting Axis2. Just having an archived 1.3 version of Axis2 won't be enough to convince them, unless

Re: [Axis2] Build breaks from axiom changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Amila, Please try MAVEN_OPTS=-Xms256m -Xmx512m thanks, dims Amila Suriarachchi wrote: | hi, | | does OSGI module builds correctly? I got this exception while building | (without tests) the OSGI module with jdk 1.5 in ubuntu linux. | | ~/projects/a

Re: [Axis2] Build breaks from axiom changes

hi, does OSGI module builds correctly? I got this exception while building (without tests) the OSGI module with jdk 1.5 in ubuntu linux. ~/projects/axis2_trunk/java/modules/osgi$ mvn clean install - Dmaven.test.skip=true -U [INFO]

Re: [Axis2] Re: XML Catalog test case failure in Axis2 on Linux

Brian, fixed the breaking test with the hack for now... Great:) -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Build breaks from axiom changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rich, I see a couple of new build breaks. Looks like the AXIOM changes are catching up.. Failed tests: ~ testFault(org.apache.axis2.jaxws.provider.SOAPFaultProviderTests) Tests in error: ~ testGetPayloadFromSoap12(org.apache.axis2.jaxws.message.

[Axis2] Re: XML Catalog test case failure in Axis2 on Linux

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian, fixed the breaking test with the hack for now... - -- dims Brian Murray wrote: | Hi all, | | The test cases introduced in the jaxws module as part of XML Catalog support | fail on Linux. One problem I have found is that the Catalog API's ar

Axis2 1.4

Hi group, Does axis2 1.3 implements jax-rpc or jax-ws? Does Jax-ws requires jdk 1.5? Which version of jax-ws is used in axis2 1.3? Axis 1.4 implements jax-rpc. Can anybody confirm? Thanks, Ajit DISCLAIMER: This message contains privileged and confidential information and is int

Re: [Axis2] Moving Axis2 code base into JDK 1.5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am torn!...so +0 for the proposal. thanks, dims David Illsley wrote: | Um, right now I'd be tempted to push out an Axis2 1.4 with JDK 1.4 | support soon for existing JDK 1.4 users, then move to 5 for Axis2 1.5. | David | | On Tue, Feb 26, 2008 at

Re: Java2WSDL's choice of namespaces

I recently used the Eclipse WebTools WSDL validator. It doesn't like the way that Axis2 creates Schemas. If you look at the AddressBook WSDL that gives you a good example. http://service.addressbook.sample"; attributeFormDefault="qualified" elementFormDefault="qualified" targetName

Re: [Axis2] Moving Axis2 code base into JDK 1.5

Um, right now I'd be tempted to push out an Axis2 1.4 with JDK 1.4 support soon for existing JDK 1.4 users, then move to 5 for Axis2 1.5. David On Tue, Feb 26, 2008 at 10:35 PM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > +1to move to jdk 1.5. > > thanks, > Amila. > > > > On Wed, Feb

Re: [Axis2] Axis2-CORBA IDL parsing problem

Hello Marcin, Currently, the CORBA module does not support pre-processor directives. Therefore you have to manually include the contents of tmp.idl to the main IDL file. Best Regards, Eranga On Mon, Feb 25, 2008 at 6:07 PM, Marcin Malinowski <[EMAIL PROTECTED]> wrote: > Hello, > > I'm going to

Re: Topics for discussion at Microsoft re: Axis interop with .NET, Windows

Hi Folks, During the last WCF plugfest [1] at MSFT we were able to fix all issues related to WS-Security 1.0, WS-Security 1.1 and WS-SecureConversation. All these fixes are available in the Rampart/Java trunk at the moment. You can try the latest Rampart snapshots here: [2] Thanks, Ruchith 1. h

Re: [Axis2] Moving Axis2 code base into JDK 1.5

+1 from me... -Nick Deepal Jayasinghe <[EMAIL PROTECTED] e.lk>

Re: [Axis2] Moving Axis2 code base into JDK 1.5

+1 Woden has also discussed a move to Java 5 and the dev team was in favour of this move. As Axis2 depends on Woden we cannot consider this move unless Axis2 also moves. Lawrence Deepal Jayasinghe <[EMAIL PROTECTED]> 02/26/2008 11:15 PM Please respond to axis-dev@ws.apache.org To "axis-

A wsdl2java problem -- node code generated for message soapHeader

Hi, All, I am encountering a problem when generating java stub from a wsdl using wsdl2java. Basically, I have a binding in WSDL like this: http://schemas.xmlsoap.org/soap/http"/> And the operation is deinfe

[Axis2] Moving Axis2 code base into JDK 1.5

Hi all , As you might remember few months back Glen asked the list about moving to JDK 1.5 and I think we got very positive feedback. So I thought of asking again and change the code to work with JDK 1.5 . The main reason behind sending this mail is due the dependency we have for annogen. As I

XML Catalog test case failure in Axis2 on Linux

Hi all, The test cases introduced in the jaxws module as part of XML Catalog support fail on Linux. One problem I have found is that the Catalog API's are returning "file://" (two slashes) on Linux when they (correctly) return "file:/" (one slash) on Windows. If I add the following just before t

[jira] Resolved: (AXIS2-1053) ConcurrentModificationException when concurrent threads try to engage the Addressing module

[ https://issues.apache.org/jira/browse/AXIS2-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-1053. - Resolution: Fixed Assignee: Davanum Srinivas (was: Deepal Jayasinghe) > Concurrent

[jira] Commented: (AXIS2-1053) ConcurrentModificationException when concurrent threads try to engage the Addressing module

[ https://issues.apache.org/jira/browse/AXIS2-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572687#action_12572687 ] Davanum Srinivas commented on AXIS2-1053: - Fixed in svn revision 631403 thanks, di

Re: Topics for discussion at Microsoft re: Axis interop with .NET, Windows

Thanks Plamena, I'll see what I can do with this. On Feb 26, 2008, at 7:58 AM February 26, Plamena Chongova wrote: Hi Bjorn, Unfortunately I could find only the wsdl, app.config and main program for the AsymmetricBinding (which worked on MS VS OrcasBeta). I'm not sure whether this will he

[jira] Assigned: (AXIS2-3550) Improve structure of JAXWS end-to-end tetss

[ https://issues.apache.org/jira/browse/AXIS2-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roy A. Wood Jr. reassigned AXIS2-3550: -- Assignee: Roy A. Wood Jr. > Improve structure of JAXWS end-to-end tetss > -

[jira] Created: (AXIS2-3550) Improve structure of JAXWS end-to-end tetss

Improve structure of JAXWS end-to-end tetss --- Key: AXIS2-3550 URL: https://issues.apache.org/jira/browse/AXIS2-3550 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws

[jira] Commented: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style

[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572682#action_12572682 ] Davanum Srinivas commented on AXIS2-2389: - lowering priority a bit. > Dispatching

[jira] Updated: (AXIS2-3215) Strange behavior: org.apache.axis2.AxisFault: For input string: ""

[ https://issues.apache.org/jira/browse/AXIS2-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3215: Priority: Critical (was: Blocker) > Strange behavior: org.apache.axis2.AxisFault: For inpu

[jira] Commented: (AXIS2-3215) Strange behavior: org.apache.axis2.AxisFault: For input string: ""

[ https://issues.apache.org/jira/browse/AXIS2-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572678#action_12572678 ] Davanum Srinivas commented on AXIS2-3215: - lowering priority a bit. > Strange beha

[jira] Commented: (AXIS2-3189) Axis2 incomplete cached files should be deleted BUT they aren't; how can I delete them

[ https://issues.apache.org/jira/browse/AXIS2-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572680#action_12572680 ] Davanum Srinivas commented on AXIS2-3189: - lowering priority a bit. > Axis2 incomp

[jira] Updated: (AXIS2-3189) Axis2 incomplete cached files should be deleted BUT they aren't; how can I delete them

[ https://issues.apache.org/jira/browse/AXIS2-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3189: Priority: Critical (was: Blocker) > Axis2 incomplete cached files should be deleted BUT th

[jira] Updated: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style

[ https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-2389: Priority: Critical (was: Blocker) > Dispatching based on the SOAP message body does not wo

[jira] Commented: (AXIS2-3239) Custom fault handling issue in code-first approach

[ https://issues.apache.org/jira/browse/AXIS2-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572677#action_12572677 ] Davanum Srinivas commented on AXIS2-3239: - lowering priority a bit. > Custom fault

[jira] Updated: (AXIS2-3336) Remove /services from the webservices endpoint URL

[ https://issues.apache.org/jira/browse/AXIS2-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3336: Priority: Critical (was: Blocker) > Remove /services from the webservices endpoint URL > -

[jira] Updated: (AXIS2-3239) Custom fault handling issue in code-first approach

[ https://issues.apache.org/jira/browse/AXIS2-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3239: Priority: Critical (was: Blocker) > Custom fault handling issue in code-first approach > -

[jira] Commented: (AXIS2-3336) Remove /services from the webservices endpoint URL

[ https://issues.apache.org/jira/browse/AXIS2-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572676#action_12572676 ] Davanum Srinivas commented on AXIS2-3336: - lowering priority a bit. > Remove /serv

[jira] Commented: (AXIS2-3497) NPE Accesing Service During Bringup

[ https://issues.apache.org/jira/browse/AXIS2-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572674#action_12572674 ] Davanum Srinivas commented on AXIS2-3497: - lowering priority a bit. > NPE Accesing

[jira] Updated: (AXIS2-3497) NPE Accesing Service During Bringup

[ https://issues.apache.org/jira/browse/AXIS2-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3497: Priority: Critical (was: Blocker) > NPE Accesing Service During Bringup >

[jira] Updated: (AXIS2-3538) RPCServiceClient response handling incorrect when there are multi byte[] object in the return bean

[ https://issues.apache.org/jira/browse/AXIS2-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3538: Priority: Critical (was: Blocker) > RPCServiceClient response handling incorrect when ther

[jira] Commented: (AXIS2-3538) RPCServiceClient response handling incorrect when there are multi byte[] object in the return bean

[ https://issues.apache.org/jira/browse/AXIS2-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572671#action_12572671 ] Davanum Srinivas commented on AXIS2-3538: - lowering priority a bit. > RPCServiceCl

[jira] Commented: (AXIS2-3515) restore previously commented JAXWS tests

[ https://issues.apache.org/jira/browse/AXIS2-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572643#action_12572643 ] Mike Rheinheimer commented on AXIS2-3515: - I'll restore these tests Wednesday. Dim

[jira] Assigned: (AXIS2-3515) restore previously commented JAXWS tests

[ https://issues.apache.org/jira/browse/AXIS2-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer reassigned AXIS2-3515: --- Assignee: Mike Rheinheimer (was: Davanum Srinivas) > restore previously commented JA

[jira] Commented: (AXIS2-3149) org.apache.axis2.saaj.SOAPConnectionImpl(line # 181) Null checking is required

[ https://issues.apache.org/jira/browse/AXIS2-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572613#action_12572613 ] Davanum Srinivas commented on AXIS2-3149: - Looks like this is fixed already. i can

[jira] Resolved: (AXIS2-3149) org.apache.axis2.saaj.SOAPConnectionImpl(line # 181) Null checking is required

[ https://issues.apache.org/jira/browse/AXIS2-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3149. - Resolution: Fixed > org.apache.axis2.saaj.SOAPConnectionImpl(line # 181) Null checking is

[jira] Commented: (AXIS2-3134) javax.xml.stream.XMLStreamException: problem accessing the parser. Parser already accessed! - Authenticated WS Client

[ https://issues.apache.org/jira/browse/AXIS2-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572609#action_12572609 ] Davanum Srinivas commented on AXIS2-3134: - Looks like the workaround works. > java

[jira] Created: (AXIS2-3549) Refactor the ThreadContextMigratorUtil class to use parameters instead of properties.

Refactor the ThreadContextMigratorUtil class to use parameters instead of properties. - Key: AXIS2-3549 URL: https://issues.apache.org/jira/browse/AXIS2-3549 Project:

[jira] Resolved: (AXIS2-3134) javax.xml.stream.XMLStreamException: problem accessing the parser. Parser already accessed! - Authenticated WS Client

[ https://issues.apache.org/jira/browse/AXIS2-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3134. - Resolution: Fixed > javax.xml.stream.XMLStreamException: problem accessing the parser. Pa

Java2WSDL's choice of namespaces

I recently used the Eclipse WebTools WSDL validator. It doesn't like the way that Axis2 creates Schemas. If you look at the AddressBook WSDL that gives you a good example. http://service.addressbook.sample"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespa

[jira] Created: (AXIS2-3548) getter for configuration on CodeGenerationEngine to access generated info

getter for configuration on CodeGenerationEngine to access generated info - Key: AXIS2-3548 URL: https://issues.apache.org/jira/browse/AXIS2-3548 Project: Axis 2.0 (Axis2)