In the RPCProvider, the piece of code that handles the output params
(starting line 265) it puts the Holder objects into the argValues array
starting at an index based on the number of parameters passed in the
request. The problems is if some of the input parameters are optional and
not sent in
Steve,
This should be fixed now.
Jarek
-Original Message-
From: Steve Green [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 05, 2005 11:30 AM
To: axis-dev@ws.apache.org
Subject: Deserializing Booleans (and maybe other primitives)
Developers,
I did a CVS up yesterday.
Yes, I added that test case to demonstrate a problem in JavaBeanWriter.
Please see: http://marc.theaimsgroup.com/?l=axis-devm=114248722321343w=2
I'll poke Dims for comments on that change again.
Jarek
-Original Message-
From: Changshin Lee [mailto:[EMAIL PROTECTED]
Sent: Monday,
This test currently fails in trunk because the dependent samples/wsa/* files
are missing in trunk. Can you merge these files into trunk or disable this
test?
I also fixed up the test a bit to run ok on unix/linux machines.
Jarek
Hi,
Looking at axis2-saaj-api and axis2-jaxws-api module dependencies they
both contain dependencies on Sun's JavaMail and Activation API. I was
wondering if these dependencies could be changed to Apache Geronimo's
JavaMail and Activation API. That way Axis2 and the rest of the
community could
no objections for this move.
Jarek Gawor wrote:
Hi,
Looking at axis2-saaj-api and axis2-jaxws-api module dependencies they
both contain dependencies on Sun's JavaMail and Activation API. I was
wondering if these dependencies could be changed to Apache Geronimo's
JavaMail and Activation API
Bite :)
I do have some SAAJ 1.3 related changes (that I've put into a branch
right now) for Axis 1 but I'm a bit hesitant to commit them since I
have reasons to believe it might break the TCK. So I would like to get
my SAAJ changes tested first before merging then into trunk (if all
looks good).
Thanks everybody. I appreciate it very much!
Jarek
On 6/8/07, Glen Daniels [EMAIL PROTECTED] wrote:
Davanum Srinivas wrote:
Jarek is a long time Axis committer and now a Geronimo committer too.
He is working hard on the jaxws integration using Axis2 in Geronimo
and already has karma in all
IMHO, if you have some HashMap and it is accessed concurrently, it
should be synchronized (or use ConcurrentHashMap instead). Concurrent
access on unsynchronized HashMap caused the following bug:
http://blogs.opensymphony.com/plightbo/2005/07/hashmapget_can_cause_an_infini.html.
This was a while
Hi,
Currently, in Geronimo we are using Sun's JAX-WS API definitions and
we would like to replace it with Axis2's JAX-WS API definitions.
However, the jaxws-api module in Axis2 contains class definitions from
three different specs: JAX-WS, JSR 181 (JWS), and some from common
annotations spec. In
for that particular module, since that would provide the
complete set. I believe we only have the subset required for JAX-WS right now.
Thanks!
-Nick
Jarek Gawor [EMAIL PROTECTED]
Jarek Gawor [EMAIL PROTECTED]
06/13/2007 10:11 AM
Please respond to
axis-dev@ws.apache.org
Michael,
The recent commit from you removed one of the changes I've made to
this code before:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/jaxws/src/org/apache/axis2/jaxws/server/EndpointController.java?r1=549217r2=549216pathrev=549217
More specifically this change:
-
Ok, thanks!
Jarek
On 6/21/07, Michael Rheinheimer [EMAIL PROTECTED] wrote:
Jarek,
My mistake. I'll fix it right away. Thanks!
mike
Mike Rheinheimer
(512) 838-0086 t/l 678-0086
WebSphere WebService Core Engine Team
Jarek Gawor [EMAIL PROTECTED]
Jarek Gawor [EMAIL
FYI, I removed the javax.annotation.* classes from the jws-api module
and added dependencies on the geronimo-annotation-spec library. So the
jaxws-api and jws-api modules should now only contain classes relevant
to the given spec.
Jarek
On 6/15/07, Jarek Gawor [EMAIL PROTECTED] wrote:
Ok
)
Nicholas L Gallardo/Austin/[EMAIL PROTECTED] wrote on 06/25/2007 01:01:04 PM:
Jarek,
+1 Thanks for cleaning that up...
-Nick
[image removed] Jarek Gawor [EMAIL PROTECTED]
Jarek Gawor [EMAIL PROTECTED]
06/25/2007 12:18 PM
Please respond to
axis-dev@ws.apache.org
[image
I'm sorry, I have to object to this commit. This is removing some of
the changes I've made before (and one change just got removed for the
second time!). For example I've added support for
HandlerLifecycleManager that works just like EndpointLifecycleManager
and can do injection/call
Would it be possible to delay the branching to Friday? Those of us
working on JAX-WS still have a few fixes to check in.
Jarek
On 7/18/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi all,
We are planing to do our next RC , Axis2 1.3-RC2 on this Friday (20th
July). So far we have not found
Deepal,
Is it ok to commit the patch in
https://issues.apache.org/jira/browse/AXIS2-3022 to trunk branch?
Thanks,
Jarek
On 7/20/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Devs,
I created a branch [1] for Axis2 1.3 release since we are too close to
the release. So please do not do
Deepal,
We also would like to commit the patch in AXIS2-3053 to the branch.
Thanks,
Jarek
On 8/1/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
oops! forgot the change in WSDL11Writer.
thanks,
dims
On 8/1/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
Deepal,
Here's the diff i'd like
Thanks Dims!
Jarek
On 8/2/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
I've taken care of AXIS2-3053
-- dims
On 8/2/07, Deepal jayasinghe [EMAIL PROTECTED] wrote:
:
Deepal,
We also would like to commit the patch in AXIS2-3053 to the branch.
Sure , go ahead.
Thanks
First, I think you should use the users mailing list to send questions
like this. Second, I don't know if this will fix anything but the
following looks wrong:
@WebResult(name=RetrieveCustomerIdentifyByCFRequest,targetNamespace=http://my.it/data;)
I think that should be:
Deepal,
What's the svn revision number associated with RC3? Also, would it be
possible to publish RC3 to
http://people.apache.org/repo/m2-snapshot-repository? Becuase of
timing issues, in Geronimo we might not be able to use the final
version of Axis2 1.3 but we would like to use something as
On 8/6/07, Deepal jayasinghe [EMAIL PROTECTED] wrote:
I can upload RC3 into m2-snapshot-repository , and I will do that today,
however if you can wait three more days you will be able to go with final.
Please upload it. I know and our goal is to use an officially released
version of Axis2 but
+1
Jarek
On 8/10/07, Deepal jayasinghe [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I have uploaded Axis2 1.3 (take3) into my Apache home location [1]
again . As a result of we found a few issues in 1.3 take2 I had to
upload the artifacts again and call
+1
Jarek
On 8/15/07, R J Scheuerle Jr [EMAIL PROTECTED] wrote:
I would like to nominate Dustin Amrhein and Roy Wood to committer status.
Dustin is an active contributor to the metadata module.
Dustin proposed the MetaDataQuery functionality in June 2006 (AXIS2-872).
He has provided
In Geronimo, we don't have our own version of these classes (saaj-api
and jaxws-api) but we definitely use that code from Axis2. I think it
is and would be important to keep the API separate from the
implementation. We actaully use these Axis2 API classes with two
different implementations without
+1
Jarek
On Nov 14, 2007 11:32 AM, Glen Daniels [EMAIL PROTECTED] wrote:
Hi folks!
As mentioned I'd like us to invite Bjorn Townsend, who's been helping
out on the fringes of Axis for a while now, to become a committer so he
can help us out with the Axis1 1.5 release. He's kindly
You're probably using Java 6 to compile. Switch back to Java 5.
Jarek
On 3/5/08, Paula Wells [EMAIL PROTECTED] wrote:
All;
I have down loaded the new axis2 1.3 and was trying to build it with the
maven 2.0.8 in a Fedore Core 6 environment.I have not changed any code, yet.
I was wondering
Hi,
I was hoping to help in debugging TCK problems but since there is no
test harness extensions for Axis2 I will try take a look at it
(although I'm not promising anything here). Also, I don't think you
should wait for me to get this done before the 1.4 release.
Jarek
On Thu, Mar 27, 2008 at
I think there is a problem with the XMLFaultCode class with handling
custom fault codes. The way it handles custom fault codes by modifying
CUSTOM_SOAP11_ONLY enum value is just not thread safe (if I understand
enums right). I think the XMLFaultCode should be turned into a class
and each custom
Sure. I created https://issues.apache.org/jira/browse/AXIS2-3703 with a patch.
Jarek
On Thu, Apr 3, 2008 at 11:00 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jarek,
Could you please post the patch?
thanks,
dims
Jarek Gawor wrote
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=649213view=rev
Log:
Add call to AxisService.releaseSchemaList in
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
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
Jarek Gawor wrote:
| I don't see that as a good reason to move these API
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.
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 dependencies
| to use the Geronimo versions (once I verify
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):
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
+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 for
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 welcome.
I'm +1
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 module
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
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
ListDeployer getDeployerForExtension(String extension)
Jarek
.deployment.deployers.CustomDeployer/
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 for multiple deployers to be
registered for the same
+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 where
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 we
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
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
andreas.veit...@gmail.com wrote:
I see a different build failure
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 iran...@wso2.com wrote:
When I tried to run axis2server.bat from extracted axis2-SNAPSHOT-bin.zip
(created with: mvn -Drelease install). I got
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
On Wed, Jan 14, 2009 at 12:37 PM, Glen Daniels g...@thoughtcraft.com 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
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
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:
On Thu, Feb 26, 2009 at 9:24 PM, Asankha C. Perera asan...@apache.org 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
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 asan...@apache.org 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
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
On Tue, Mar 31, 2009 at 12:22 AM, Asankha C. Perera asan...@apache.org 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
On Tue, Mar 31, 2009 at 1:53 AM, Asankha C. Perera asan...@apache.org 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.
On Tue, Mar 31, 2009 at 4:02 PM, Glen Daniels g...@thoughtcraft.com 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 and local? Should
On Wed, Apr 1, 2009 at 5:50 PM, Glen Daniels g...@thoughtcraft.com 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 happy with.
Yes, I agree. Sounds
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 jga...@gmail.com wrote:
On Wed, Apr 1, 2009 at 5:50 PM, Glen Daniels g...@thoughtcraft.com wrote:
Jarek Gawor wrote
On Wed, Apr 8, 2009 at 5:40 AM, Andreas Veithen
andreas.veit...@gmail.com 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
[
http://issues.apache.org/jira/browse/AXIS-1754?page=comments#action_58202 ]
Jarek Gawor commented on AXIS-1754:
---
I added the clearCall() becuase ThreadLocal was used. If ThreadLocal can be
dropped then clearCall() can also be removed.
Service
The built-in WS-A handler cannot be disabled
Key: AXIS-2440
URL: http://issues.apache.org/jira/browse/AXIS-2440
Project: Apache Axis
Type: Bug
Reporter: Jarek Gawor
Currently, the built-in WS-A handler cannot
[ http://issues.apache.org/jira/browse/AXIS-2438?page=all ]
Jarek Gawor resolved AXIS-2438:
---
Fix Version: current (nightly)
Resolution: Fixed
Committed a fix for this in trunk.
WSDL2Java: Extra \n in generated stub files prevents these files
[ http://issues.apache.org/jira/browse/AXIS-2361?page=all ]
Jarek Gawor resolved AXIS-2361:
---
Fix Version: current (nightly)
Resolution: Fixed
STATUS_CODE and STATUS_MESSAGE will now be set by the CommonsHTTPSender.
Visibility of error code
[ http://issues.apache.org/jira/browse/AXIS-2242?page=all ]
Jarek Gawor closed AXIS-2242:
-
Resolution: Invalid
I'm going to close this bug as it seems it is a server issue. The server does
not understand how to deal with HTTP/1.1 and chunked encoding
[ http://issues.apache.org/jira/browse/AXIS-2310?page=all ]
Jarek Gawor resolved AXIS-2310:
---
Fix Version: current (nightly)
Resolution: Fixed
Fix committed to trunk.
Incorrect catching of java.lang.Error subclasses
[ http://issues.apache.org/jira/browse/AXIS-1877?page=all ]
Jarek Gawor resolved AXIS-1877:
---
Resolution: Invalid
This was caused by having different version of axis.jar at runtime then at
compile time.
weird apache axis (?) run-time problem
[ http://issues.apache.org/jira/browse/AXIS-2162?page=all ]
Jarek Gawor resolved AXIS-2162:
---
Resolution: Fixed
Preliminary MTOM support has been added in July 2005.
MTOM Support in Axis 1.X
Key: AXIS-2162
[ http://issues.apache.org/jira/browse/AXIS-2258?page=all ]
Jarek Gawor resolved AXIS-2258:
---
Resolution: Fixed
Pretty printing is now (as of Jan 2006) disabled by default (disablePrettyXML =
true).
Make pretty printing disabled by default
[ http://issues.apache.org/jira/browse/AXIS-2435?page=all ]
Jarek Gawor resolved AXIS-2435:
---
Fix Version: current (nightly)
Resolution: Fixed
Fixed in trunk.
Bad envelope tag: html on 503 response code with CommonsHttpSender
[ http://issues.apache.org/jira/browse/AXIS-2362?page=all ]
Jarek Gawor resolved AXIS-2362:
---
Resolution: Fixed
The CommonsHTTPSender was updated to reuse the MultiThreadedConnectionManager.
Re-use of MultiThreadedConnectionManager
[ http://issues.apache.org/jira/browse/AXIS-2030?page=all ]
Jarek Gawor resolved AXIS-2030:
---
Resolution: Fixed
The CommonsHTTPSender was updated to reuse the MultiThreadedConnectionManager.
Singleton getInstance returns new instances each time
[ http://issues.apache.org/jira/browse/AXIS-2220?page=all ]
Jarek Gawor resolved AXIS-2220:
---
Resolution: Fixed
The CommonsHTTPSender was updated to check for an empty response, and if so it
releases the connection immediately and returns without
[ http://issues.apache.org/jira/browse/AXIS-2394?page=all ]
Jarek Gawor resolved AXIS-2394:
---
Resolution: Fixed
Patch committed.
SOAPFaultBuilder throws DOMException WRONG_DOCUMENT_ERR
[ http://issues.apache.org/jira/browse/AXIS-2455?page=all ]
Jarek Gawor resolved AXIS-2455:
---
Resolution: Fixed
Patch applied.
LogHandler writeToConsole broken
Key: AXIS-2455
URL: http
[ http://issues.apache.org/jira/browse/AXIS-2200?page=all ]
Jarek Gawor resolved AXIS-2200:
---
Resolution: Fixed
Added 'axis.addHostnameFaultDetail' property (set by AxisProperties) that can
be used to suppress the hostname and the exception name
[ http://issues.apache.org/jira/browse/AXIS-2469?page=all ]
Jarek Gawor resolved AXIS-2469:
---
Resolution: Fixed
Java process hang due to Thread race condition in
org.apache.axis.utils.JavaUtils::isEnumClass
[ http://issues.apache.org/jira/browse/AXIS-2327?page=all ]
Jarek Gawor resolved AXIS-2327:
---
Fix Version: current (nightly)
Resolution: Fixed
Committed a fix for this issue and added tests.
ClassCastException in UnsignedInt and UnsignedLong
: jaxws
Reporter: Jarek Gawor
It looks like axis2-jaxws-api has a dependency on
org/apache/axis2/java/security/AccessController which is in the axis2 kernel
module. That prevents the api to be used with different jaxws implementations.
--
This message is automatically generated by JIRA
(Axis2)
Issue Type: Bug
Reporter: Jarek Gawor
I was trying to use Axis2 SAAJ API with Sun's SAAJ implementation. So I created
the appropriate META-INF/services/ files accessible from the classloader (with
bogus classnames for testing). However, during factory lookup I
SAAJ API issue
--
Key: AXIS2-2331
URL: https://issues.apache.org/jira/browse/AXIS2-2331
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Jarek Gawor
One of the SAAJResult constructor has the following code
(Axis2)
Issue Type: Improvement
Components: jaxws
Reporter: Jarek Gawor
Attachments: AXIS2-2745.patch
--
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-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-2745:
---
Attachment: AXIS2-2745.patch
Allow for a different EndpointDispatcherFactory implementation
: Jarek Gawor
Attachments: AXIS2-2767.patch
Factored out some calls into separate methods in certain classes to make it
easier to extend them and change behavior.
--
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-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-2767:
---
Attachment: AXIS2-2767.patch
Minor extensibility improvements
/AXIS2-2783
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Jarek Gawor
--
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-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-2783:
---
Attachment: AXIS2-2783.patch
This patch fixes some of the The endpoint reference (EPR
[
https://issues.apache.org/jira/browse/AXIS2-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502465
]
Jarek Gawor commented on AXIS2-2783:
Yes, I think so.
Better checking for overloaded operations
[
https://issues.apache.org/jira/browse/AXIS2-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502503
]
Jarek Gawor commented on AXIS2-2783:
Actually, there is a small problem with this change. The null value here
[
https://issues.apache.org/jira/browse/AXIS2-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-2783:
---
Attachment: AXIS2-2783.patch
Better checking for overloaded operations in AxisService
[
https://issues.apache.org/jira/browse/AXIS2-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-2783:
---
Attachment: AXIS2-2783.patch
Better checking for overloaded operations in AxisService
[
https://issues.apache.org/jira/browse/AXIS2-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-2783:
---
Attachment: (was: AXIS2-2783.patch)
Better checking for overloaded operations in AxisService
: Jarek Gawor
The attached patch enables for the HandlerChain annotation to be overridden.
That's needed by app servers where the handlers can be specified in a
deployment descriptor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
[
https://issues.apache.org/jira/browse/AXIS2-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated AXIS2-2787:
---
Attachment: AXIS2-2787.patch
Override HandlerChain annotation
[
https://issues.apache.org/jira/browse/AXIS2-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-2787.
Resolution: Fixed
Fix Version/s: 1.3
Patch committed (Committed revision 545829
[
https://issues.apache.org/jira/browse/AXIS2-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved AXIS2-2804.
Resolution: Fixed
Patch applied with some changes and simplifications
[
https://issues.apache.org/jira/browse/AXIS2-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504779
]
Jarek Gawor commented on AXIS2-2804:
Committed revision 547278.
DescriptionBuilderComposite needs
[
https://issues.apache.org/jira/browse/AXIS2-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned AXIS2-2859:
--
Assignee: Jarek Gawor (was: sumedha rubasinghe)
SAAJ - set default fault code and faul
1 - 100 of 221 matches
Mail list logo
