Does Axis2 compatible with Java 1.4?

Hi, Just to confirm, does Axis2 1.3 works on JDK 1.4? Thx a lot! Regards, Mai Sun

Re: Does Axis2 compatible with Java 1.4?

On Tue, May 13, 2008 at 1:45 PM, <[EMAIL PROTECTED]> wrote: > Hi, > > Just to confirm, does Axis2 1.3 works on JDK 1.4? > yes, Even Axis2 1.4. >From Axis2 1.5 JDK 1.5 or higher. thanks, Amila. > Thx a lot! > > Regards, > Mai Sun > -- Amila Suriarachchi, WSO2 Inc.

[jira] Created: (AXIS2-3796) AxisCallback.onFault(..) not used with OutInAxisOperation

AxisCallback.onFault(..) not used with OutInAxisOperation - Key: AXIS2-3796 URL: https://issues.apache.org/jira/browse/AXIS2-3796 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects V

[jira] Updated: (AXIS2-3796) AxisCallback.onFault(..) not used with OutInAxisOperation

[ https://issues.apache.org/jira/browse/AXIS2-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans G Knudsen updated AXIS2-3796: -- Attachment: onfault_OutInAxisOperation.txt Hi! Fix to make OutInAxisOperation use AxisCallback

Re: [Axis2] Generating a wrong port address for POJO deployment

Dims, On May 12, 2008, at 11:59 PM, Davanum Srinivas wrote: I was talking about moving JAXWS services and clients across implementations. Not on the wire interop. Sorry it was not clearer. I'm not sure how that applies here. Axis2 is the only JAX-WS implementation that does this funky End

[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=12596423#action_12596423 ] Dietmar Gaertner commented on AXIS2-3784: - Hi Sanka, I saw the possibility to set

Problems with Axis2 1.4

Hi all I just downloaded and installed AXIS2-1.4 today. I tried wsdl2java and I was pleased that some bugs such as "unexpected token: staticabstract" have been fixed. Many thanks to the Axis2 development team. I experienced the following problems: == 1- wsdl2java errors == 1- When I

RE: [Axis2] Generating a wrong port address for POJO deployment

> The fact that Axis2 does this wacky thing actually made it HARDER for Just to chime in here - I agree with Dan that Axis2 *is* doing something wacky here by tacking on the port name to the endpoint. As far as the "we should throw an error if a SOAP 1.1 endpoint gets SOAP 1.2" argument is conce

Re: Accessing SOAP Header in Web Service implementation

Hi, Try the following inside your service implementation, if you just need to access the incoming headers. MessageContext messageContext = MessageContext .getCurrentMessageContext(); SOAPHeader header =messageContext.getEnvelope().get

[jira] Resolved: (AXIS2-3772) improve service-name-pattern and port-name-pattern checking for file referenced by @HandlerChain

[ https://issues.apache.org/jira/browse/AXIS2-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Rheinheimer resolved AXIS2-3772. - Resolution: Fixed Resolved in 655988. I used the equivalent Java regular expression and

[jira] Updated: (AXIS2-3765) BeanUtil.deserialize() tries to deserialize the wrong OMNode for byte[]

[ https://issues.apache.org/jira/browse/AXIS2-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sven Blösl updated AXIS2-3765: -- Description: BeanUtil decodes the wrong node for byte[] which are part of a complex type contained in

[jira] Updated: (AXIS2-3765) BeanUtil.deserialize() tries to deserialize the wrong OMNode for byte[]

[ https://issues.apache.org/jira/browse/AXIS2-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sven Blösl updated AXIS2-3765: -- Im not that familiar with axis2 internals (yet), but i could imagine that this is the same problem as in i

Re: [Axis2] Generating a wrong port address for POJO deployment

Hello Everyone, Please find my comments inlined. Tom Jordahl wrote: The fact that Axis2 does this wacky thing actually made it HARDER for Just to chime in here - I agree with Dan that Axis2 *is* doing something wacky here by tacking on the port name to the endpoint. As far as the "we s

Re: [Axis2] Generating a wrong port address for POJO deployment

Hello Everyone, Please find my comments inlined. [1] http://www.mail-archive.com/axis-dev@ws.apache.org/msg26438.html [2] http://www.mail-archive.com/axis-dev@ws.apache.org/msg40047.html Daniel Kulp wrote: Dims, On May 12, 2008, at 11:59 PM, Davanum Srinivas wrote: I was talking about mov