+1
Jarek
On Sun, May 17, 2009 at 12:46 PM, Glen Daniels wrote:
> Hi Axis Developers:
>
> The 1.5 release candidate has been stable for a couple of weeks now, and thus
> I'd like to kick off a VOTE to officially release 1.5. The usual 72 hour
> window applies.
>
> You can find the distribution f
On Wed, Apr 8, 2009 at 5:40 AM, Andreas Veithen
wrote:
> I noticed that there are no recent snapshot builds on
> people.apache.org (last trunk build is 03-Apr-2009, 1.5 branch is
> 06-Apr-2009). I think there is a problem with the profile that is
> triggered when building Axis2 together with the t
ic HTTP tests in the testkit. The purpose was to apply these
>> generic tests to the NIO HTTP transport. This allows to compare the
>> behavior of both transports. From that perspective we may leave the
>> tests in the transports project ... as tests for the testkit :-)
ric tests to the NIO HTTP transport. This allows to compare the
> behavior of both transports. From that perspective we may leave the
> tests in the transports project ... as tests for the testkit :-)
>
> Andreas
>
> On Thu, Apr 2, 2009 at 17:08, Jarek Gawor wrote:
>>
On Wed, Apr 1, 2009 at 5:50 PM, Glen Daniels wrote:
> Jarek Gawor wrote:
>>> Also, I'd really like to get 1.5 out the door ASAP, it's lingered way too
>>> long already. So whatever solution gets us there soonest with consensus is
>>> the one I'll be h
On Tue, Mar 31, 2009 at 4:02 PM, Glen Daniels wrote:
> Hi Jarek, all:
>
> Jarek Gawor wrote:
>> So sounds like we agree on moving the http module back to Axis2 and
>> leaving transport base where it is (after fixing the utility classes
>> dependency). What about tcp a
On Tue, Mar 31, 2009 at 1:53 AM, Asankha C. Perera wrote:
>
> No, only the following two classes are using a two utility classes, which
> can be fixed easily. Like I said, the base will remain in the transports
> module - whether it be under commons or back again in Synapse.
>
> ./src/org/apache/a
On Tue, Mar 31, 2009 at 12:22 AM, Asankha C. Perera wrote:
>
>>> 2) Move the base, local, tcp, and http transport modules back to Axis2
>>> and release them with Axis2. That way the transports project would
>>> only have the 'optional' transport modules and we wouldn't have to
>>> release the tran
I mentioned two additional ideas to deal with this problem a while ago
when this issue also came up:
1) Release transports and axis2 at the same time. Have one vote for
both libraries.
2) Move the base, local, tcp, and http transport modules back to Axis2
and release them with Axis2. That way the
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689596#action_12689596
]
Jarek Gawor commented on AXIS2-4279:
Detelin,
I don't. I think we should
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688862#action_12688862
]
Jarek Gawor commented on AXIS2-4279:
I committed a basic fix for this security pro
[
https://issues.apache.org/jira/browse/AXIS2-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688713#action_12688713
]
Jarek Gawor commented on AXIS2-4282:
WSDL parser resolves relative imports base
[
https://issues.apache.org/jira/browse/AXIS2-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688697#action_12688697
]
Jarek Gawor commented on AXIS2-4282:
Stoil,
No, it won't. It's t
[
https://issues.apache.org/jira/browse/AXIS2-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688340#action_12688340
]
Jarek Gawor commented on AXIS2-4282:
I'm not too worried about that. In 99.
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688205#action_12688205
]
Jarek Gawor commented on AXIS2-4279:
I fixed the problem in trunk and branches/
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688150#action_12688150
]
Jarek Gawor edited comment on AXIS2-4279 at 3/22/09 8:4
[
https://issues.apache.org/jira/browse/AXIS2-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688204#action_12688204
]
Jarek Gawor commented on AXIS2-4282:
Yep. It's fixed in Ger
[
https://issues.apache.org/jira/browse/AXIS2-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4282.
Resolution: Fixed
Committed fixes to trunk (revision 757306) and branches/java/1_5 (revision
://issues.apache.org/jira/browse/AXIS2-4282
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.5, nightly
Reporter: Jarek Gawor
Assignee: Jarek Gawor
Fix For: 1.5, nightly
If JarFileClassLoader
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688150#action_12688150
]
Jarek Gawor edited comment on AXIS2-4279 at 3/22/09 9:5
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688150#action_12688150
]
Jarek Gawor commented on AXIS2-4279:
Ok, thanks. I can replicate now with 1.4.1
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688100#action_12688100
]
Jarek Gawor commented on AXIS2-4279:
I see this problem in trunk and branches/1_5
[
https://issues.apache.org/jira/browse/AXIS2-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4266.
Resolution: Fixed
Fix Version/s: nightly
1.5
> Comment nodes are
[
https://issues.apache.org/jira/browse/AXIS2-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680360#action_12680360
]
Jarek Gawor commented on AXIS2-4266:
Committed fixes and tests to trunk (revi
Components: saaj
Affects Versions: 1.5, nightly
Reporter: Jarek Gawor
Assignee: Jarek Gawor
When using Transformer API to build a SOAP message from DOM with comment nodes
can create an invalid DOM document:
Input:
Final (invalid) doc
FYI, I just published the 1.5-SNAPSHOT artifacts. Let me know if there
are any problems.
Jarek
On Tue, Mar 3, 2009 at 12:30 AM, Asankha C. Perera wrote:
> Hi Jarek
>
> The version on the pom states "1.5-beta-2" and effectively even if we
> include this into a maven repo will prevent updates from
On Thu, Feb 26, 2009 at 9:24 PM, Asankha C. Perera wrote:
> Hi Glen
>>>
>>> Is there a nightly build off [1] or a Maven repo where nightly snapshots
>>> are published? If no, are there any plans to set this up?
>>>
>>
>> Nope, no nightly of the 1.5 branch, though such a thing could certainly
>> be
Folks,
Besides axis2-transport modules Woden is the last SNAPSHOT dependency
that we have and need to resolve before the 1.5 release. The Woden
version change was made about 7 months ago in the following revision:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/parent/pom.xml?r1
[
https://issues.apache.org/jira/browse/AXIS2-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4209.
Resolution: Fixed
Fix Version/s: nightly
1.5
Merged the fix to branches
That's to be expected. Since Axis2 1.5 isn't released just yet these
Maven artifacts are not published yet to Maven central repo and
therefore cannot be automatically downloaded. So for now you have to
build these locally but once Axis2 1.5 is released and its Maven
artifacts are published this wil
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
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-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663636#action_12663636
]
Jarek Gawor commented on AXIS2-4209:
Committed a fix for it to trunk (revision 73
Components: jaxws
Affects Versions: 1.5, nightly
Reporter: Jarek Gawor
Assignee: Jarek Gawor
OASIS catalog resolution does not work for schema references. I ran into the
following exception when wsdl had schema import to http://foo/foo.xsd and
jax-ws-catalog.xml
[
https://issues.apache.org/jira/browse/AXIS2-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4005.
Resolution: Fixed
Fix Version/s: nightly
1.5
This was a problem in the
[
https://issues.apache.org/jira/browse/AXIS2-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657665#action_12657665
]
Jarek Gawor commented on AXIS2-4154:
I believe the wildcard support is already t
[
https://issues.apache.org/jira/browse/AXIS2-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4178.
Resolution: Fixed
Fix Version/s: 1.5
Assignee: Jarek Gawor
Committed the null
Yes. I added the basic transport modules to the bin distribution
(local, tcp, and http).
Jarek
On Mon, Dec 15, 2008 at 2:57 AM, Irantha wrote:
> When I tried to run axis2server.bat from extracted axis2-SNAPSHOT-bin.zip
> (created with: mvn -Drelease install). I got ClassNotFoundException:
> org.
Andreas,
How is it failing? My guess is that your snapshot of axis2-transport-*
modules is slightly old. Remove it from you m2 repo or build the
transport modules locally.
Jarek
On Sun, Dec 14, 2008 at 7:54 AM, Andreas Veithen
wrote:
> I see a different build failure which is caused by
> Dispat
Are org.tempuri.complex.ComplexDataTypesTest,
org.tempuri.BaseDataTypesTest. and
org.apache.axis2.deployment.WSDL11ToAxisServiceBuilderTest failing for
you? If so, that seems to be caused by r724737 and I've mentioned this
to Keith a few days ago.
Jarek
On Fri, Dec 12, 2008 at 11:36 AM, Deepal ja
[
https://issues.apache.org/jira/browse/AXIS2-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-4173:
---
Affects Version/s: (was: 1.5)
> NullPointerException from ServiceClient.fireAndFor
[
https://issues.apache.org/jira/browse/AXIS2-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655705#action_12655705
]
Jarek Gawor commented on AXIS2-4173:
This issue is already fixed in t
Is there a new target date for 1.5? Were all the critical issues
identified/resolved for 1.5?
Jarek
On Fri, Oct 17, 2008 at 9:12 AM, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Team:
>
> What do people think about gearing up for a 1.5 release in the
> not-too-distant future? I figure the earlier w
[
https://issues.apache.org/jira/browse/AXIS2-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4145.
Resolution: Fixed
Fix Version/s: nightly
Committed fixes and a test case for this issue to
[
https://issues.apache.org/jira/browse/AXIS2-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned AXIS2-4145:
--
Assignee: Jarek Gawor
> A null value for a Dispatch invocation using the XML/HTTP bind
+1
Jarek
On Thu, Nov 20, 2008 at 10:33 AM, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Folks:
>
> Discussion seems to have died down about the TLP proposal, and I think we
> heard a lot of valuable viewpoints during the conversation. At this point,
> I think it's time to VOTE on the idea and see w
[
https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644397#action_12644397
]
Jarek Gawor commented on AXIS2-4101:
I committed a partial fix this problem (revi
[
https://issues.apache.org/jira/browse/AXIS2-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4103.
Resolution: Invalid
If replyTo is null the rest of the expression will not be evaluated so no NPE
es directory. For example:
Thoughts?
Jarek
On Tue, Oct 28, 2008 at 5:20 PM, Jarek Gawor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Does anyone have comments on
> https://issues.apache.org/jira/browse/AXIS2-4101? In general, I would
> like to know if we should allow fo
Deepal,
I think you misunderstood. The code assumes there is one deploeyer per
extension. See DeploymentEngine.getDeployerForExtension(). That should
either be:
Deployer getDeployerForExtension(String directory, String extension)
or
List getDeployerForExtension(String extension)
Jarek
On Tue,
[
https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reopened AXIS2-4101:
Deepal,
Please take a look at the code. The code assumes there is one deployer per
extension and
Hi,
Does anyone have comments on
https://issues.apache.org/jira/browse/AXIS2-4101? In general, I would
like to know if we should allow for multiple deployers to be
registered for the same file extension (for any directory). Right now,
only one is assumed and that causes problems.
Thanks,
Jarek
-
This does not fail on Java 5. Anyway, committed a simple/temporary fix
to the test.
Jarek
On Tue, Oct 28, 2008 at 3:20 PM, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
> I'm unable to build Axis2, after a fresh checkout from svn, using "mvn clean
> install". It consistently fails during the SAAJ mo
On Mon, Oct 27, 2008 at 11:02 PM, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Hey dims, all:
>
> Davanum Srinivas wrote:
>>
>> There was a WS PMC thread which has not yet shown up here
>>
>> So, WDYT? Could we spin off Axis2 and related projects into a separate
>> TLP? Pros / Cons / Thoughts welc
[
https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-4101:
---
Description:
The axis2.xml contains the following entries for two deployers for the same
extension
Components: kernel
Affects Versions: nightly
Reporter: Jarek Gawor
Priority: Critical
Fix For: 1.5
The axis2.xml contains the following entries for two deployers for the same
extension.
Once would think that any jar files found in the "servic
+1 from me too. I was about to suggest the same. It would be good to
get Axis2 1.5 officially JAX-WS 2.1 certified. It's something that we
will also need for Geronimo.
Jarek
On Fri, Oct 17, 2008 at 10:12 AM, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Team:
>
> What do people think about gearing up
[
https://issues.apache.org/jira/browse/AXIS2-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639166#action_12639166
]
Jarek Gawor commented on AXIS2-4072:
Forgot to mention: thanks Tim for the p
[
https://issues.apache.org/jira/browse/AXIS2-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4072.
Resolution: Fixed
Fix Version/s: nightly
Committed the patch to trunk (revision 704201
Hey all,
Looks like Axis2 requires the wsa:MessageID header to be set when
using the 2005/08 (final) addressing spec (see
AddressingValidationHandler.checkMessageIDHeader()). I'm looking at
the spec and the MessageID header is marked as optional (not sending
it might cause problems with message co
[
https://issues.apache.org/jira/browse/AXIS2-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637366#action_12637366
]
Jarek Gawor commented on AXIS2-4072:
Tim, please correct me if I'm wrong
[
https://issues.apache.org/jira/browse/AXIS2-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4062.
Resolution: Fixed
Fix Version/s: nightly
Assignee: Jarek Gawor
Modified
Type: Bug
Components: jaxws
Affects Versions: nightly
Reporter: Jarek Gawor
Here's the exception I got when I tried to deploy a web service without SEI
with 3 public and 2 private methods:
javax.xml.ws.WebServiceException: The ServiceDescription failed to validat
Reporter: Jarek Gawor
By default the JAX-WS web services are deployed with "request" scope. If the
scope was changed to "application" scope the following things break:
1) @Resource WebServiceContext injection is not performed. That's because the
service class instance is cr
[
https://issues.apache.org/jira/browse/AXIS2-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630084#action_12630084
]
Jarek Gawor commented on AXIS2-4027:
Btw, the specific exception I was seeing on
[
https://issues.apache.org/jira/browse/AXIS2-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-4027.
Resolution: Fixed
Fix Version/s: nightly
Committed fixes to trunk (revision 694104
)
Issue Type: Bug
Affects Versions: nightly
Reporter: Jarek Gawor
Assignee: Jarek Gawor
Some methods in SOAPPartImpl such as getFirstChild() or getLastChild() or
getChildNodes() return object instances of type org.w3c.dom.Node instead of
javax.xml.soap.Node
[
https://issues.apache.org/jira/browse/AXIS2-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-3854.
Resolution: Fixed
Fix Version/s: nightly
Committed the patch to trunk (revision 668384
Hi,
I'm trying to minimize the configuration steps one would have go
through to get full JAX-WS support from Axis2. There are two key steps
- I had to do these for TCK:
1) Add extra Sun jars. They are needed to generate wsdl at runtime.
The following jars were needed (with Java 5):
jaxws-rt-2.1.
[
https://issues.apache.org/jira/browse/AXIS2-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3854:
---
Attachment: AXIS2-3854.patch
Patch for this issue.
> Default namespace not set on JAXBCont
Versions: nightly
Reporter: Jarek Gawor
Assignee: Jarek Gawor
Axis2 should set the default namespace property on the JAXBContext when
creating JAXBContext from individual classes. The default namespace property
should be set to the SEI @WebService.targetNamespace value.
In
[
https://issues.apache.org/jira/browse/AXIS2-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-3808.
Resolution: Fixed
Fix Version/s: nightly
Added basic implementations of appendChild
2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.4
Reporter: Jarek Gawor
Assignee: Jarek Gawor
The SAAJ implementation classes do not override the
appendChild(org.w3c.dom.Node) method and instead rely on the default
implementation of appendChild() method from
[
https://issues.apache.org/jira/browse/AXIS2-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3777:
---
Affects Version/s: 1.4
Fix Version/s: (was: 1.4)
> SAAJ Implementation
[
https://issues.apache.org/jira/browse/AXIS2-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3793:
---
Fix Version/s: (was: 1.4)
> move image to the correct pl
[
https://issues.apache.org/jira/browse/AXIS2-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned AXIS2-3805:
--
Assignee: Rich Scheuerle
> Provider does not w
[
https://issues.apache.org/jira/browse/AXIS2-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598320#action_12598320
]
Jarek Gawor commented on AXIS2-3805:
I committed a small fix to allow for Provider
[
https://issues.apache.org/jira/browse/AXIS2-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3805:
---
Affects Version/s: 1.4
Summary: Provider does not work (was: Using
DataSource
as <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> sounds good!
>
> Jarek Gawor wrote:
> | Ok. I'll start working on it. For jws-api and saaj-api there isn't
> | much to do. I will remove these from Axis2 svn and update dep
Ok. I'll start working on it. For jws-api and saaj-api there isn't
much to do. I will remove these from Axis2 svn and update dependencies
to use the Geronimo versions (once I verify they are exactly the
same). For jaxws-api I will scp the Axis2 version to Geronimo and
publish a snapshot of it. Once
---BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jarek,
>
> +1 to move the spec jars, now that they are pretty stable and have gone
> thru the TCK's. One question there is Geronimo
> is still on JAXWS 2.0. So that may be a block.
>
> - -- dims
>
>
>
>
I don't see that as a good reason to move these API classes into
kernel. In fact, in my opinion that makes things more confusing. I
think keeping these things separate is cleaner, easier to understand,
and more reusable. Another thing to understand is that these are API
classes which are far more s
Jeff,
This change breaks ?xsd=foo.xsd lookups.
Jarek
On Thu, Apr 17, 2008 at 2:19 PM, <[EMAIL PROTECTED]> wrote:
> Author: barrettj
> Date: Thu Apr 17 11:19:35 2008
> New Revision: 649213
>
> URL: http://svn.apache.org/viewvc?rev=649213&view=rev
> Log:
> Add call to AxisService.releaseSche
Reporter: Jarek Gawor
xsd:hexBinary types are not serialized properly on the wire. On they wire they
are serialized the same as xsd:base64Binary. This causes interop issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
[
https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-3742.
Resolution: Fixed
Fix Version/s: nightly
1.4
Assignee: Jarek
[
https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3742:
---
Attachment: AXIS2-3742.3.patch
After talking to David Illsley, we decided to move the real operation
[
https://issues.apache.org/jira/browse/AXIS2-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-3668.
Resolution: Fixed
Fix Version/s: nightly
1.4
This is already fixed and
[
https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3742:
---
Attachment: AXIS2-3742.tests.patch
Updated patch with tests (works nicely now without any other
[
https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3742:
---
Attachment: (was: AXIS2-3742.tests.patch)
> Use actaul message to determine the outbound
[
https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3742:
---
Attachment: AXIS2-3742.tests.patch
Tests for this issue (right now one must copy
[
https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589118#action_12589118
]
Jarek Gawor commented on AXIS2-3742:
David, I'm really just getting the rig
[
https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3742:
---
Attachment: AXIS2-3742.patch
Proposed patch.
> Use actaul message to determine the outbound
Components: Addressing, jaxws
Affects Versions: 1.4, nightly
Reporter: Jarek Gawor
When an anonymous operation is used, the wsa action either has to be explicitly
set on the message context or the default wsa outbound of the anonymous
operation will be used. However, in certain
[
https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588485#action_12588485
]
Jarek Gawor commented on AXIS2-3712:
Created https://issues.apache.org/jira/br
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: jaxws
Affects Versions: nightly
Reporter: Jarek Gawor
Add a configuration option to control whether to throw or suppress exceptions
on one-way invocations in HandlerChainProcessor.
--
This message
[
https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-3712.
Resolution: Fixed
Fix Version/s: nightly
1.4
Assignee: Jarek
[
https://issues.apache.org/jira/browse/AXIS2-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-3734.
Resolution: Fixed
Assignee: Jarek Gawor
Committed the patch to trunk (revision 647371) and
[
https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588154#action_12588154
]
Jarek Gawor commented on AXIS2-3712:
Yes, I definitely agree. Will open a new bu
[
https://issues.apache.org/jira/browse/AXIS2-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-3734:
---
Attachment: AXIS2-3734.patch
Proposed patch. Includes new test case and updated some existing test
Type: Bug
Components: jaxws
Reporter: Jarek Gawor
Fix For: 1.4, nightly
Array of strings (or other simple types) are serialized as xsd:list even though
the method or parameter is not annotated with @XmlList.
--
This message is automatically generated by JIRA
1 - 100 of 240 matches
Mail list logo
