Because until now, Axis2 trunk worked fine with Axiom 1.2.8. I'm
working on an issue in Axis2 that seems to be solved by some of the
OMStAXWrapper fixes in Axiom and I was actually going to change the
dependency to Axiom 1.2.9-SNAPSHOT.
Andreas
On Sun, Jun 21, 2009 at 04:32, Davanum Srinivas wrot
[
https://issues.apache.org/jira/browse/AXIS2-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-4383.
Resolution: Fixed
Fix Version/s: 1.6
Assignee: Andreas Veithen
I tested you
+1 for switching to snapshots of Neethi/XmlSchema/Axiom/woden at the very
least. Not sure about transports.
thanks,
dims
On 06/21/2009 03:57 AM, Andreas Veithen wrote:
Because until now, Axis2 trunk worked fine with Axiom 1.2.8. I'm
working on an issue in Axis2 that seems to be solved by some
Note that the drawback is that before doing a release of Axis2, we
would need to make sure that all dependencies have been released.
Maybe it's better to switch to snapshots only when there is a precise
reason? I don't know.
Andreas
On Sun, Jun 21, 2009 at 12:27, Davanum Srinivas wrote:
> +1 for
[
https://issues.apache.org/jira/browse/AXIS2-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722405#action_12722405
]
Andreas Veithen commented on AXIS2-4374:
Can you try to validate the response using
Andreas,
Please see
http://marc.info/?l=axis-dev&m=117734349010193&w=2
* The trunk should always be "cutting edge" and as such should usually
be pointing at SNAPSHOT versions of all dependencies. This allows for
continuous integration with our partner projects.
Also see,
http://marc.info/?t=1
InputStream left open in AxisService
Key: AXIS2-4400
URL: https://issues.apache.org/jira/browse/AXIS2-4400
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Reporter: Mike
