[
https://issues.apache.org/jira/browse/AXIS2-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Malinga updated AXIS2-4953:
-
Summary: axis2 codegen related Issues (was: axis2 codegen related bugs)
> axis2 codegen related
[
https://issues.apache.org/jira/browse/AXIS2-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Malinga updated AXIS2-4953:
-
Issue Type: Improvement (was: Bug)
> axis2 codegen related Issues
>
[
https://issues.apache.org/jira/browse/AXIS2-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Malinga updated AXIS2-4953:
-
Attachment: sample4.zip
sample3.zip
sample2.zip
sa
[
https://issues.apache.org/jira/browse/AXIS2-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991812#comment-12991812
]
Supun Malinga commented on AXIS2-4953:
--
Following are the list of Issue that came acr
axis2 codegen related bugs
--
Key: AXIS2-4953
URL: https://issues.apache.org/jira/browse/AXIS2-4953
Project: Axis2
Issue Type: Bug
Components: codegen, kernel
Reporter: Supun Malinga
Hello Krishantha and Vijitha,
I am no longer facing this issue.
Thank you very much for your reply.
Thanks
AmilaJ
On Tue, Feb 8, 2011 at 8:39 AM, Krishantha Manjula Rathnayaka
wrote:
> Dear Amila,
> If you remove all signatures and extensions from the HTTP Filter settings,
> and if you configu
Dear Amila,
If you remove all signatures and extensions from the HTTP Filter settings,
and if you configure the HTTP Filter component to allow all signatures and
extensions, you no longer experience this problem.
Kindly Regards,
Krishantha Manjula
krishantha.rathnay...@ifsworld.com
On Fri, Feb
+1
On Feb 7, 2011 12:28 PM, "Ruwan Linton" wrote:
> What I would suggest is to do the 1.6 release without the JAX-WS TCK
> compatibility, if there are lot to be fixed. This is because we have
enough
> fixes on the trunk to do a release. May be we can target a major release
> like 2.0 with the JAX-
The Axis Project Management Committee (PMC, see [1]) is pleased to
announce that Thilina Mahesh Buddhika has accepted the invitation to
become a committer and PMC member.
Thilina is a keen contributor for Apache Axis2 and Rampart projects
and has provided more than 20 patches. Among those patches,
JAX-WS dynamic ports should be scoped to the service instance the created them
--
Key: AXIS2-4952
URL: https://issues.apache.org/jira/browse/AXIS2-4952
Project: Axis2
The trunk seems to build just fine with Neethi 2.0.4. This confirms
Dan's (and also my own) finding that there have been no significant
changes on the Neethi trunk since the last release.
On the other hand, Dan's recent changes broke integration with the
Axis2 trunk. Probably nobody noticed that b
I agree with Ruwan. Instead of further increasing the scope of Axis2
1.6, just get this thing out and make sure that we can easily do
maintenance releases. I think that with the 1.5.x releases, I've
proven that it is perfectly possible to have a release every 2-3
months.
Andreas
On Mon, Feb 7, 20
[
https://issues.apache.org/jira/browse/AXIS2-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Krecan updated AXIS2-4951:
Attachment: axis2-test.zip
Test project. If you remove axis2-jaxws from pom.xml the test passes
>
Incomplete document transformation into SOAP body
-
Key: AXIS2-4951
URL: https://issues.apache.org/jira/browse/AXIS2-4951
Project: Axis2
Issue Type: Bug
Components: saaj
Affects V
[
https://issues.apache.org/jira/browse/AXIS2-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Katherine Sanders updated AXIS2-4948:
-
Attachment: AXIS2-4948.patch
This issue also affects WebServiceContextImpl.getEndpointRef
On Feb 3, 2011, at 11:21 PM, Sanjiva Weerawarana wrote:
> What's the verdict on this? I don't see the point of rushing out 1.6 without
> passing the TCK .. having full JAX-WS support would (finally) be a major
> milestone!
From the perspective of an Axis2 consumer (i.e. Geornimo), I'd agree...
On Mon, Feb 7, 2011 at 6:33 PM, Sagara Gunathunga <
sagara.gunathu...@gmail.com> wrote:
> Hi Isuru,
>
> I will add more documentation about exact versions and steps I followed .
>
> BTW can you post steps you followed to the jaxws-tck list ?
>
Sure, will do..
Thanks
~Isuru
>
> Thanks !
>
>
Hi Isuru,
I will add more documentation about exact versions and steps I followed .
BTW can you post steps you followed to the jaxws-tck list ?
Thanks !
On Mon, Feb 7, 2011 at 6:14 PM, Isuru Suriarachchi wrote:
> Hi Sagara,
>
> I tried to run the TCK on Axis2. But I'm getting lot of build
Hi Sagara,
I tried to run the TCK on Axis2. But I'm getting lot of build errors in the
"ant build.tck" step. In the README.txt, it says "You need a JDK 1.5.0_06
JVM available. Versions newer than that WON'T work". Is this statement
outdated or still valid?
Can you please add a simple document wh
[
https://issues.apache.org/jira/browse/AXIS2-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahmoud Ibrahim updated AXIS2-4950:
---
Attachment: Jboss and webshpere .txt
> WCF issue with Websphere and Jboss
> -
WCF issue with Websphere and Jboss
--
Key: AXIS2-4950
URL: https://issues.apache.org/jira/browse/AXIS2-4950
Project: Axis2
Issue Type: Bug
Components: wsdl
Affects Versions: 1.5.1
Enviro
21 matches
Mail list logo
