Hi,
Could somebody give me the steps to deploy a webservice developed using
Axis2 JaxWS in Tomcat server? There are two different ways given at
http://ws.apache.org/axis2/1_4_1/jaxws-guide.html#DeployService, but
both of them make the service tightly coupled with axis2 servlet. Is
there a way to
[
https://issues.apache.org/jira/browse/AXIS2-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663888#action_12663888
]
Andreas Veithen commented on AXIS2-4206:
Since you are using a domain specific prot
On Wed, Jan 14, 2009 at 12:37 PM, Glen Daniels wrote:
> Hi Asankha, all:
>
> Asankha C. Perera wrote:
>> Hi Jarek
>>> I agree with changing the transport dependencies to test scope but in
>>> general I'm a little concerned about the circular dependency between
>>> axis2 and axis2-transport modules
Hi Asankha, all:
Asankha C. Perera wrote:
> Hi Jarek
>> I agree with changing the transport dependencies to test scope but in
>> general I'm a little concerned about the circular dependency between
>> axis2 and axis2-transport modules. Because of that circular dependency
>> I think we have to rele
Hi Jarek
I agree with changing the transport dependencies to test scope but in
general I'm a little concerned about the circular dependency between
axis2 and axis2-transport modules. Because of that circular dependency
I think we have to release axis2 and axis2-transport at the same time
(at leas
Support for 2004/03 version of ws-addressing
-
Key: AXIS2-4211
URL: https://issues.apache.org/jira/browse/AXIS2-4211
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: Address
I agree with changing the transport dependencies to test scope but in
general I'm a little concerned about the circular dependency between
axis2 and axis2-transport modules. Because of that circular dependency
I think we have to release axis2 and axis2-transport at the same time
(at least the base,
[
https://issues.apache.org/jira/browse/AXIS2-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663775#action_12663775
]
Andreas Veithen commented on AXIS2-3613:
The release is imminent: see http://markma
[
https://issues.apache.org/jira/browse/AXIS2-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663771#action_12663771
]
Doug Guzek commented on AXIS2-4206:
---
Thank you for your response.
I know this is more of
[
https://issues.apache.org/jira/browse/AXIS2-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663773#action_12663773
]
Doug Guzek commented on AXIS2-3613:
---
You mentioned that the fix is in 1.2.8 but yet its n
Asankha,
I agree with your changes and I share your point of view that we
should reduce dependencies an the transports to a minimum. From what
I've seen, the problem is simply that some modules depending on
addressing, clustering and/or saaj (the ones you changed) implicitly
rely on the fact that
11 matches
Mail list logo