Hi All,
In the process of adding a new test, I discovered that all tests with the
name *Util*.java were being excluded in the kernel pom.xml. It turns out
there were two tests that were being excluded, one of which passed and one
of which failed.
I've added explicit excludes for these two
[
https://issues.apache.org/jira/browse/AXIS2-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reassigned AXIS2-4158:
---
Assignee: Jeff Barrett
Enhance URIResolverImpl to be able to use static XML catalog
[
https://issues.apache.org/jira/browse/AXIS2-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-4158.
-
Resolution: Fixed
Patch committed to revision 745925.
Thanks for submitting the patch Lori
:
Jeff Barrett/Austin/i...@ibmus
To:
axis-dev@ws.apache.org
Date:
01/15/2009 08:35 PM
Subject:
Axis2: Getting compile errors in 1.5 branch integration module
Hi Folks,
I'm trying to run the tests on the 1.5 branch and I'm getting compile
errors in the integration module:
[copy] Copying 1 file
[
https://issues.apache.org/jira/browse/AXIS2-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12664684#action_12664684
]
Jeff Barrett commented on AXIS2-4198:
-
Thanks for the patch submission Rick!
Fixed
[
https://issues.apache.org/jira/browse/AXIS2-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-4198.
-
Resolution: Fixed
Fix Version/s: 1.5
Fixed in trunk and 1.5 branch
Can not stop
Phone: (512) 286-5256 or TieLine: 363-5256
Internet e-mail and Sametime ID: barre...@us.ibm.com
- Forwarded by Jeff Barrett/Austin/IBM on 01/15/2009 07:52 AM -
From:
Nandana Mihindukulasooriya nandana@gmail.com
To:
axis-dev@ws.apache.org
Date:
12/17/2008 10:54 PM
Subject:
Re: [ANNOUNCE
Hi Folks,
I'm trying to run the tests on the 1.5 branch and I'm getting compile
errors in the integration module:
[copy] Copying 1 file to
C:\blddir\eclipse\axis2\axis2-apache-1_5\modules\integration\target\test-classes\modules
[mkdir] Created dir:
at 9:07 AM, Jeff Barrett barre...@us.ibm.com wrote:
Hi Folks,
I just did an svn checkout of the 1.5 branch onto a system that didn't
have a maven repository (.m2) from previous builds, and I'm getting two
build errors. I didn't see a Jira open for this. It seems to me this
should
[
https://issues.apache.org/jira/browse/AXIS2-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reassigned AXIS2-4198:
---
Assignee: Jeff Barrett
Can not stop the ListenerManager when transports are added
[
https://issues.apache.org/jira/browse/AXIS2-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625485#action_12625485
]
Jeff Barrett commented on AXIS2-3620:
-
I added a call to the Handler getHeaders
[
https://issues.apache.org/jira/browse/AXIS2-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608847#action_12608847
]
Jeff Barrett commented on AXIS2-3792:
-
I commited Tom's patch to Axis2 trunk, Committed
Hi,
I wanted to let you know that I commited the patch (with a few minor
modifications) that was submitted for
https://issues.apache.org/jira/browse/AXIS2-3792 . I didn't realize the
Jira was assigned to you until after I did the commit; I hope you don't
mind. I thought it needed to be
[
https://issues.apache.org/jira/browse/AXIS2-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608865#action_12608865
]
Jeff Barrett commented on AXIS2-3807:
-
Note that the patch for AXIS2-3792 has been
[
https://issues.apache.org/jira/browse/AXIS2-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-3812.
-
Resolution: Duplicate
This problem went away when I applied the patch
Eclipse codegen wizard
Hi All,
I've got a couple of questions about this approach.
1) Are there any semantic differences between an Axis2 handler plugged
into specific phases at specific points and a MAR? For example, the
current JAXWS dispatchers have to plug in so that all the operation
resolution has been
+1
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: [EMAIL PROTECTED]
Davanum Srinivas [EMAIL PROTECTED]
04/24/2008 11:39 AM
Please respond to
axis-dev@ws.apache.org
To
Axis developer list
Hi Dims,
Just to follow up on our chat, I think that comment is wrong. The
constructor under test is used on the client side when processing the SEI,
and the test is using an interface class to drive the tests, so I think it
should stay.
Thanks,
Jeff
IBM Software Group - WebSphere Web
+1 to ship all three.
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: [EMAIL PROTECTED]
Davanum Srinivas [EMAIL PROTECTED]
04/09/2008 11:47 PM
Please respond to
axis-dev@ws.apache.org
To
Axis
[
https://issues.apache.org/jira/browse/AXIS2-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12583689#action_12583689
]
Jeff Barrett commented on AXIS2-3654:
-
Dims, No, I don't think it is needed for the 1.4
[
https://issues.apache.org/jira/browse/AXIS2-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-3679.
-
Resolution: Fixed
Committed revision 642603
Validation failure on using sun JDK
Hi Dims,
Good catch! That was by oversight, not by design. Fixing it now.
Thanks again!
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: [EMAIL PROTECTED]
Davanum Srinivas [EMAIL PROTECTED]
Reporter: Jeff Barrett
Assignee: Jeff Barrett
Fix For: 1.4
Tests in error:
testService_isAlive(org.apache.axis2.jaxws.sample.ParallelAsyncTests)
testService_ExecutorShutdownNow(org.apache.axis2.jaxws.sample.ParallelAsyncTests)
testService_ExecutorShutdownNow_2
[
https://issues.apache.org/jira/browse/AXIS2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AXIS2-3621 started by Jeff Barrett.
@WebMethod(exclude=true) is not being honored
-
Key: AXIS2
[
https://issues.apache.org/jira/browse/AXIS2-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-3621.
-
Resolution: Fixed
Fixed. Committed revision 641875
@WebMethod(exclude=true) is not being
Reporter: Jeff Barrett
Priority: Blocker
Following the instructions in modules/samples/java_first_jaxws/README does not
get the sample running. I copied java_first_jaxws-1.1.jar and
java_first_jaxws-1.1.war from target to repository/services (note the README
had no detailed
[
https://issues.apache.org/jira/browse/AXIS2-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reopened AXIS2-3663:
-
The ?WSDL still works (it worked before the change). What didn't work was the
client URL. We need
)
Issue Type: Bug
Components: jaxws
Reporter: Jeff Barrett
Support for server-side role-based mustUnderstand checking for JAXWS
Application Handlers was added under
https://issues.apache.org/jira/browse/AXIS2-3567.
Similar function is needed for client-side JAXWS
[
https://issues.apache.org/jira/browse/AXIS2-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-3567.
-
Resolution: Fixed
Fixed in revision 639636
Support role/actor based mustUnderstand header
All,
A few of us have been discussing whether the deprecated method
org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescriptionFromServiceImpl(Class,
AxisService) can and/or should be removed.
I think that it can and should be removed. I has been deprecated for a
long,
cleaning it up. It's used to support the
older 1.3's case of the JAXWS MR specified inside a services.xml.
thanks,
dims
Jeff Barrett wrote:
| All,
|
| A few of us have been discussing whether the deprecated method
|
org.apache.axis2
MESSAGE-
Hash: SHA1
Jeff,
I'd prefer that we leave it in as deprecated for at least 1.4 release
before cleaning it up. It's used to support the
older 1.3's case of the JAXWS MR specified inside a services.xml.
thanks,
dims
Jeff Barrett wrote:
| All,
|
| A few of us have been discussing
[
https://issues.apache.org/jira/browse/AXIS2-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reassigned AXIS2-3626:
---
Assignee: Jeff Barrett (was: Nikhil Thaker)
Remove MustUnderstandValidationDispatcher
[
https://issues.apache.org/jira/browse/AXIS2-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12580404#action_12580404
]
Jeff Barrett commented on AXIS2-3626:
-
Dims and I just discussed this on the phone
[
https://issues.apache.org/jira/browse/AXIS2-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-3626.
-
Resolution: Won't Fix
Resolving per discussion with Dims and comment above
Remove
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett closed AXIS2-2853.
---
Resolution: Duplicate
This will be fixed by making an explicit check for the JAXWS Message Receiver
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575415#action_12575415
]
Jeff Barrett commented on AXIS2-2853:
-
I think the remaining work will be covered
Looks good to me!
+1
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: [EMAIL PROTECTED]
Glen Daniels [EMAIL PROTECTED]
03/05/2008 12:37 PM
Please respond to
axis-dev@ws.apache.org
To
Hi Folks,
If we choose to stay on 1.4, remember that JAXWS requires Java 1.5 (due to
the spec-required use of generics). I think there are a couple of modules
that require Java 1.5 to build. Also note that in order to run the JAXWS
2.1 TCK, that will also require Java 1.5 since the TCK will
ims,
My understanding of what the TCK permits is the same as yours. You can
remove the RI-specific DDs and can add your own vendor-specific DDs.
However, anything that exists in the TCK application archive (such as
classes, WSDL, etc) must remain as is. So, the classes couldn't be moved
+1 to moving the tests to a jaxws-integration module and to splitting out
the tests in JAXWSTest.
Note that spliting out the JAXWSTest may be trickier than it sounds. Dims
actually tried that some time back, making each test run independently.
With some JDKs (but not all) and/or on Windows
Hi All,
I agree with Nick's suggestion of certifying based on JAXWS 2.1 rather
than 2.0.
In any case, we need to get the JAXWS deployment hooked into the Axis2
deployment. There's already a JIRA for that:
https://issues.apache.org/jira/browse/AXIS2-3223
Thanks,
Jeff
IBM Software Group -
[
https://issues.apache.org/jira/browse/AXIS2-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett closed AXIS2-3439.
---
Code dropped to SVN as noted above.
Support JAX-WS and Metadata client-side sparse composite
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Components: jaxws
Reporter: Jeff Barrett
Assignee: Jeff Barrett
Add support for a JAX-WS client to use a sparse DescriptionBuilderComposite to
override certain annotation values specified
[
https://issues.apache.org/jira/browse/AXIS2-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-3439.
-
Resolution: Fixed
Changes committed in revision 611042
Support JAX-WS and Metadata client-side
[
https://issues.apache.org/jira/browse/AXIS2-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530478
]
Jeff Barrett commented on AXIS2-2525:
-
Working on this now; just about have it fixed. It is a problem
[
https://issues.apache.org/jira/browse/AXIS2-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2525.
-
Resolution: Fixed
Fixed in Committed revision 579726
AnnotationServiceImplDescriptionTests
Components: jaxws
Reporter: Jeff Barrett
Assignee: Roy A. Wood Jr.
Currently the metadata processing for JAXWS (i.e. the creation of the metadata
description hierachy based on annotations and WSDL) is not integrated into the
Axis2 deployment model. The JAXWS unit
service feature concept of JAX-WS 2.1.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will you
find the time to do it again?
Jeff Barrett [EMAIL PROTECTED] wrote on 17
(if it exists) could be
used by anyone wanting it with Axis2...
David
On 14/09/2007, Jeff Barrett [EMAIL PROTECTED] wrote:
Hi Dims,
I believe the deployment descriptor is defined by JSR-109, not by
JAX-WS.
I could be wrong, but I don't think anyone was planning on adding
JSR-109
support (and thus DDs
Hi Dims,
I believe the deployment descriptor is defined by JSR-109, not by JAX-WS.
I could be wrong, but I don't think anyone was planning on adding JSR-109
support (and thus DDs) into the JAXWS (and associated metadata) module.
Thanks,
Jeff
IBM Software Group - WebSphere Web Services
[
https://issues.apache.org/jira/browse/AXIS2-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reassigned AXIS2-3129:
---
Assignee: Jeff Barrett
ProviderDispatcher in JAX-WS does not allow for non-parameterized
[
https://issues.apache.org/jira/browse/AXIS2-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-3129.
-
Resolution: Fixed
Patch committed to revision 568722. Thanks, Dustin!
ProviderDispatcher
Hi Sanjiva,
I would say that Axis2 runninng in the context of a particular server
(e.g. Geronimo in this case) is JAX-WS compliant. And, I agree, that is
awesome!
Has the JAX-WS TCK been run against Axis2 outside the context of another
server? I don't think it has, and I think there is
for 35 JIRA issues.
Roy has been an active contributor to Axis2 since September 2006.
He contributed the initial code for collecting annotation and reflective
class information (AXIS2-1195, etc)
This was the foundation of the metadata module.
Roy works closely with Jeff Barrett to maintain
[
https://issues.apache.org/jira/browse/AXIS2-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516743
]
Jeff Barrett commented on AXIS2-3011:
-
Hi Jarek,
Here are a few things we need to consider regarding
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513636
]
Jeff Barrett commented on AXIS2-2853:
-
Added a JAXWS handler that will mark SOAP Headers which correspond to SEI
. I'll go finish my response on the other
thread right now, but until then, I apologize but -1 on this commit.
--Glen
Jeff Barrett wrote:
Hi All,
I've commited the changes for
https://issues.apache.org/jira/browse/AXIS2-2853 under revision 556761.
It is implemented as described below
bit more. I'll go finish my response on the other
thread right now, but until then, I apologize but -1 on this commit.
--Glen
Jeff Barrett wrote:
Hi All,
I've commited the changes for
https://issues.apache.org/jira/browse/AXIS2-2853 under revision 556761.
It is implemented as described
Hi Glen.
I don't think the mustUnderstand checkers have the same semantics as an
engine handler, so they shouldn't be implemented as one. A handler
processes the message. A mustUnderstand checker doesn't process the
message and so it shouldn't modify the message state; another component
the 1.3 release?
Alternatively, let's revoke this, cut the release branch and then commit
it. Then it'll be in 1.4 (or whatever release we want to do next .. maybe
1.3.1 if its just this) but its just wrong to slip in new features between
release candidates.
Sanjiva.
Jeff Barrett wrote:
Sorry
Hi All,
After a long chat with Glen and Dims on IRC, I am reverting the changes to
rev 556761. I am working on an iterim solution that will (hopefully) pass
compliance tests and is entirely contained within the jaxws module.
Basically I will add a JAXWS-specific handler that can be added to
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513332
]
Jeff Barrett commented on AXIS2-2853:
-
The changes commited to revision 556761 have been reverted in revision
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513407
]
Jeff Barrett commented on AXIS2-2853:
-
Per discussion on the list and via IRC chat (transcript also posted
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2853.
-
Resolution: Fixed
Implented pluggable mustUnderstand checker framework. The previous comment
).
Thanks again for the comments!
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: [EMAIL PROTECTED]
- Forwarded by Jeff Barrett/Austin/IBM on 07/16/2007 06:05 PM -
Jeff Barrett/Austin/IBM
07/11
application handler,
mySample.handler, understands header {http://mySample}Foo.
Thanks,
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
Jeff Barrett/Austin/[EMAIL PROTECTED] wrote on 07/11/2007 05:20:35 PM:
Hi All,
Here is my proposal for a mustUnderstand header
, the semantics of the engine
remain unchanged, and with plugins I think we can solve all the scenarios
brought up on the list.
--Glen
Jeff Barrett wrote:
Goals
=
1. Pluggable and extensible via configuration. Allow higher-level,
non-engine components to participate
Hi All,
Here is my proposal for a mustUnderstand header validation framework.
PLEASE NOTE the mustUnderstand processing is required for fixes we're
trying to get in by 7/20 and which Geronimo needs.
So, please take a look as soon as possible. If the overview seems OK,
then I'll start on the
the remaining JAXWS compliance-related issues fixed by 7/20.
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: [EMAIL PROTECTED]
- Forwarded by Jeff Barrett/Austin/IBM on 07/10/2007 03:06 PM -
Ann
[
https://issues.apache.org/jira/browse/AXIS2-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2888.
-
Resolution: Fixed
Commited to revision 552921. Thanks, Dustin!
RPCLitMethodMarshaller should
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509983
]
Jeff Barrett commented on AXIS2-2853:
-
Dims,
Thanks for the offer, but I'm working on backing out revision
[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509989
]
Jeff Barrett commented on AXIS2-2853:
-
I have backed out the changes made (under revision 549924) which
[
https://issues.apache.org/jira/browse/AXIS2-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reassigned AXIS2-2888:
---
Assignee: Jeff Barrett
RPCLitMethodMarshaller should take bindng namespace into account
later on.
Thanks,
Jeff
IBM Software Group - WebSphere Web Services Development
Phone: 512-838-4587 or Tie Line 678-4587
Internet e-mail and Sametime ID: [EMAIL PROTECTED]
- Forwarded by Jeff Barrett/Austin/IBM on 07/02/2007 01:14 PM -
Jeff Barrett/Austin/IBM
06/28/2007 01:05 PM
To
axis-dev
Hi All,
Thanks for all the feedback. I think we need to break this up into two
different threads of discussion:
- What to do in 1.3 (so there are no API changes)
- How to fix this correctly in post 1.3 for all the scenarios (which will
include API changes for headers and roles, plugability,
[
https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508201
]
Jeff Barrett commented on AXIS2-2851:
-
The patch was commited to revision 550753.
Move RESPONSE_WRITTEN flag
[
https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2851.
-
Resolution: Fixed
Patch was commited to SVN as noted above.
Move RESPONSE_WRITTEN flag from
Hi Dims and Sanjiva,
I've read the previous discussion of mustUnderstand processing which Dims
sent me via a chat http://marc.info/?t=11694997345r=1w=2 (Thanks,
Dims)
Given that discussion, I believe the suggested approach here is to add a
handler in the distpatch phase that will mark the
[
https://issues.apache.org/jira/browse/AXIS2-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2216.
-
Resolution: Fixed
The changes for this Jira were commited under Jira
https://issues.apache.org
[
https://issues.apache.org/jira/browse/AXIS2-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2597.
-
Resolution: Fixed
Commited patch to revision 550594. Thanks, Roy!
Support WS-A action
[
https://issues.apache.org/jira/browse/AXIS2-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2538.
-
Resolution: Fixed
Patch commited to revision 534196.
Fix NPE in getSyncOperation
[
https://issues.apache.org/jira/browse/AXIS2-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett closed AXIS2-2538.
---
Fix NPE in getSyncOperation()
-
Key: AXIS2-2538
Hi,
I just did a checkout from trunck and I'm getting an unsatisfied
dependency for jaxb-api-2.0.3.jar. I'm not running the build with -o.
I see that rev 533762 updated the jaxbri.version from 2.0.2 to 2.0.3. What
do I need to do in order to download that jar so I can build successfully?
Nice! +1 with one possible caveat
At one time on the list there was a discussion of doing a code reformat
prior to each release. I know that's not in the list below, and that's a
Very Good Thing. I don't think we should do a code format prior to a
release (or indeed, ever again); we
committing?
Thanks,
--Glen
Jeff Barrett wrote:
Nice! +1 with one possible caveat
At one time on the list there was a discussion of doing a code
reformat
prior to each release. I know that's not in the list below, and that's
a
Very Good Thing. I don't think we should do a code format
Reporter: Jeff Barrett
The SOAPBinding JAXWS API class role-related methods should use SetString not
SetURI
--
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-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490073
]
Jeff Barrett commented on AXIS2-2563:
-
I'm working on this now.
SOAPBinding JAX-WS API class is incorrect
[
https://issues.apache.org/jira/browse/AXIS2-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2563.
-
Resolution: Fixed
Fixed in commited revision 530529
SOAPBinding JAX-WS API class is incorrect
[
https://issues.apache.org/jira/browse/AXIS2-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett closed AXIS2-2563.
---
SOAPBinding JAX-WS API class is incorrect
[
https://issues.apache.org/jira/browse/AXIS2-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489802
]
Jeff Barrett commented on AXIS2-2550:
-
After fixing the tests to use the JUnit assert* methods and the service
[
https://issues.apache.org/jira/browse/AXIS2-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489406
]
Jeff Barrett commented on AXIS2-2525:
-
Dims, thanks for the info. I ran the test (and it passed) on the IBM JDK
[
https://issues.apache.org/jira/browse/AXIS2-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2536.
-
Resolution: Fixed
Fix contributed by Dustin Amrhein. Committed revision 529310.
Support
[
https://issues.apache.org/jira/browse/AXIS2-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett closed AXIS2-2536.
---
Support client side WSDL files within JARs on UNIX/LINUX platforms
[
https://issues.apache.org/jira/browse/AXIS2-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reassigned AXIS2-2536:
---
Assignee: Jeff Barrett
Support client side WSDL files within JARs on UNIX/LINUX platforms
: Bug
Components: jaxws
Reporter: Jeff Barrett
Priority: Minor
On *IX, the path is getting two leading /, causing it to treat the file as
remote. Dustin Amrhein found the problem and has contributed a fix which I
will apply shortly.
--
This message
[
https://issues.apache.org/jira/browse/AXIS2-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2445.
-
Resolution: Cannot Reproduce
The code in WSDL11ToAxisServiceBuilder has been refactored, and I
[
https://issues.apache.org/jira/browse/AXIS2-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett reassigned AXIS2-2542:
---
Assignee: Jeff Barrett
DescriptionFactoryImpl caching and updates need to be threadsafe
: Bug
Components: jaxws
Reporter: Jeff Barrett
The ServiceDescription cache and updating of the enpdoints needs to be
threadsafe.
--
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-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2542.
-
Resolution: Fixed
Fix contributed by Dustin Amrhein. Commited revision: 529355
1 - 100 of 288 matches
Mail list logo
