[
https://issues.apache.org/jira/browse/AXIS2-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863662#action_12863662
]
Tharindu Mathew commented on AXIS2-4593:
I tried downloading from:
http://download
[
https://issues.apache.org/jira/browse/AXIS2-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tharindu Mathew updated AXIS2-3820:
---
Attachment: import-wsdl.zip
Hi Krystian,
I tried to import your wsdl to make a .aar using ws
Daniel Kulp wrote:
On Monday 03 May 2010 6:57:54 am Dennis Sosnoski wrote:
...
From what I've seen CXF always builds the DOM representation of the
entire message and passes it to WSS4J anytime WS-Security is configured,
just as Axis2 does (though Dan did add a check to disable response
me
[
https://issues.apache.org/jira/browse/AXIS2-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4701.
---
Resolution: Fixed
> JAX-WS: Error when processing a JAXB enum that lacks certain methods
> --
[
https://issues.apache.org/jira/browse/AXIS2-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4700.
---
Resolution: Fixed
> JAX-WS: Wrapper defaulting is wrong
> ---
JAX-WS: Error when processing a JAXB enum that lacks certain methods
Key: AXIS2-4701
URL: https://issues.apache.org/jira/browse/AXIS2-4701
Project: Axis2
Issue Type: Bug
JAX-WS: Wrapper defaulting is wrong
---
Key: AXIS2-4700
URL: https://issues.apache.org/jira/browse/AXIS2-4700
Project: Axis2
Issue Type: Bug
Components: jaxws
Reporter: Rich Scheuerle
On Sun, May 2, 2010 at 11:37 PM, Andreas Veithen
wrote:
> On Sat, May 1, 2010 at 09:12, Dennis Sosnoski wrote:
>> Yes, I think it'd make much more sense to base a build-on-demand document
>> model on the DOM API than to try to modify all the WSS4J and related code to
>> use Axiom. Especially sinc
[
https://issues.apache.org/jira/browse/AXIS-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863365#action_12863365
]
Kim Neunert commented on AXIS-1050:
---
Hi,
i'm not sure if someone will still read this. I'
[
https://issues.apache.org/jira/browse/AXIS-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863365#action_12863365
]
Kim Neunert commented on AXIS-1050:
---
Hi,
i'm not sure if someone will still read this. I'
Just a note on Axiom based implementation of Rampart. As Ruchith have
pointed out the implementation is fairly supports the majority of use cases.
Obviously, it may need refinements, but a working implementation of XML-C14N
to SOAP security is there in this. An earlier version of Axiom based C14N i
Andreas Veithen wrote:
On Mon, May 3, 2010 at 07:02, Dennis Sosnoski wrote:
...
So rather than an incremental build-on-demand model, I think an approach
which just flipped DOM on or off at the message level would work just as
well for web services. On the inbound side, if a SOAP Header is p
On Mon, May 3, 2010 at 10:19, Amila Suriarachchi
wrote:
> Is (or was) there any reason to Axiom to come up with an new API rather than
> using DOM API?
I guess that one of the goals was also to provide an API that is more
convenient than DOM.
> I was thinking that Dom does not support differed b
On Mon, May 3, 2010 at 07:02, Dennis Sosnoski wrote:
> Andreas Veithen wrote:
>>
>> On Sat, May 1, 2010 at 09:12, Dennis Sosnoski wrote:
>>
>>>
>>> ...
>>>
>>
>> Each of the two approaches (porting WSS4J to Axiom / building a new
>> optimized Axiom+DOM implementation) have their pros and cons and
[
https://issues.apache.org/jira/browse/AXIS2-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863267#action_12863267
]
Tharindu Mathew commented on AXIS2-3201:
This issue does not exist any more. Please
Is (or was) there any reason to Axiom to come up with an new API rather than
using DOM API?
I was thinking that Dom does not support differed building and that seems to
be wrong.
There are some axis2 specific methods to get under line xml stream etc...
But they would have added by
extending the DO
Whoops, meant to have this in my first response...
Andreas Veithen wrote:
Each of the two approaches (porting WSS4J to Axiom / building a new
optimized Axiom+DOM implementation) have their pros and cons and I
think there is enough room for the two. They could even be
complementary provided that
17 matches
Mail list logo
