[
https://issues.apache.org/jira/browse/AXIS2-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12835315#action_12835315
]
Glen Daniels commented on AXIS2-4337:
-
Hi Norbert - you can go to
http
Hi all:
I've put a template board report in place for January [1]. Both the new Axis
PMC and the Web Services PMC will be reporting. I'll write up the Axis PMC
report directly, describing the split and that we're still in the midst of
infra discussions for project setup.
The WS report will
Hi all:
Just wanted to officially (and a bit belatedly) announce that as of the
December board meeting, we've agreed to create a new Top Level Project for
Axis1, Axis2, all the modules (i.e. Rampart, Sandesha, Kandua, Savan), and
the commons transports. In other words, everything that has to do
[
https://issues.apache.org/jira/browse/AXIS2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784044#action_12784044
]
Glen Daniels commented on AXIS2-2883:
-
Hi Brecht:
I did not actually test
to:
axis-dev
11/12/2009 03:30 PM
Cc:
Glen
Daniels
Please respond to
axis-dev
__
That is not correct. The entire Javadoc of the cleanupTransport method
was written before the introduction
Hi folks:
The VOTE on the Axis2 TLP proposal has passed with many +1s and no -1s.
I'll hold off for a few days before submitting it to the board, to give
others a chance to sign themselves up for the new PMC.
After the resolution passes, we'll need to figure out the logistics of the
mailing
Hey y'all:
Those of us here at ApacheCon, let's grab a table in the main ballroom in
order to do some JIRA bashing (prioritizing, targeting, assigning) at 5:30PM
today, after Nandana's talk ending the WS track.
For those not physically here, we'll hop on #apache-axis. I should think
we'll spend
Uh.. that's PACIFIC time... sorry for the confusion!
Glen Daniels wrote:
Hey y'all:
Those of us here at ApacheCon, let's grab a table in the main ballroom in
order to do some JIRA bashing (prioritizing, targeting, assigning) at 5:30PM
today, after Nandana's talk ending the WS track
[
https://issues.apache.org/jira/browse/AXIS2-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4337:
Priority: Major (was: Blocker)
1) This isn't really a blocker, so downgrading.
2) Here's my
[
https://issues.apache.org/jira/browse/AXIS2-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4404.
-
Resolution: Invalid
Closing this for now, since we've had no test case or stack trace since
a track day for the project on Thursday. We hope to
see you there.
Sign up today at http://us.apachecon.com/c/acus2009/
Thanks for your interest in Apache Axis2!
--Glen Daniels
Jordahl
-Original Message-
From: Glen Daniels [mailto:g...@thoughtcraft.com]
Sent: Tuesday, October 20, 2009 10:49 AM
To: Axis-Dev
Subject: [VOTE] Axis2 1.5.1 - final vote (I hope :) )
OK, after adding the default 30-second timeout for connection starvation
issues, and confirming
OK, after adding the default 30-second timeout for connection starvation
issues, and confirming that Rampart now works fine with 1.5.1, let's try this
one more time. Please VOTE on releasing 1.5.1 - then we can get moving on 1.6!
You can find the distribution files in here:
Hey folks!
So who is going to be at ApacheCon? I'm hoping once again that we can get
some good work done on Axis2 and other WS projects while we're there.
What we work on will depend on who's there, so in the interest of planning
ahead, who's going to be around when?
I'm arriving on Tuesday,
Hi folks!
OK, so here are the results of my weekend investigations. The lockup when
running the Rampart 1.5 tests with Axis2 1.5.1 was due to http connection
starvation. I've fixed two issues and everything works now, but I'd like to
respin both Axis2 1.5.1 and Rampart 1.5 as a result. Details
)
Issue Type: New Feature
Components: modules
Reporter: Glen Daniels
I don't think this is already there, but correct me if I'm wrong.
We could use the capability to express Axis2 version compatibility in the
module.xml file. Something like:
module name=WS-Foo class
From: Glen Daniels [g...@thoughtcraft.com]
Sent: Wednesday, October 07, 2009 13:36
To: axis-dev@ws.apache.org
Subject: Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Ping! Please VOTE... or comment?
--G
Glen Daniels wrote:
Hi Axis Developers,
After fixing the documentation
Ping! Please VOTE... or comment?
--G
Glen Daniels wrote:
Hi Axis Developers,
After fixing the documentation and a few other small issues since the last
attempt at 1.5.1, I think we're ready to try again. I've also addressed the
forced build of Axiom issue with the CLOSE_WAIT fix - we now
[
https://issues.apache.org/jira/browse/AXIS2-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4163.
-
Resolution: Fixed
Fix Version/s: 1.5.1
1.6
Fixed on 1.5 branch
Hi Axis Developers,
After fixing the documentation and a few other small issues since the last
attempt at 1.5.1, I think we're ready to try again. I've also addressed the
forced build of Axiom issue with the CLOSE_WAIT fix - we now by default
clean up the last operation context each time we
[
https://issues.apache.org/jira/browse/AXIS2-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4501.
-
Resolution: Fixed
Documentation links on Axis2 1.4.1 page, left pane, are broken - Related
[
https://issues.apache.org/jira/browse/AXIS2-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4497.
-
Resolution: Fixed
Fixed, changes should be up shortly.
axis2 1.4.1 download link is incorrect
[
https://issues.apache.org/jira/browse/AXIS2-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756892#action_12756892
]
Glen Daniels commented on AXIS2-4434:
-
This was caused by the JAXWS metadata module
[
https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-3919:
Fix Version/s: 1.6
We've replaced the referenced code with a TempFileManager class that does two
One of the main reasons we designed service groups was precisely to allow
people to deploy related web services in a convenient package. The
services.xml format works fine with this IIRC - can't Zooz just merge the
files manually and put both service elements under a single serviceGroup?
Hi Dobri!
Sorry for the delay on responding to this. Comments inline.
Dobri Kitipov wrote:
We now share an instance of HTTPClient across each ConfigurationContext
(i.e.
each Axis2 server or ServiceClient) - connection reuse is now automatic.
This
means the REUSE_HTTP_CLIENT flag is no
release until at least preliminary builds of transports
and Rampart are available to work with 1.5.1. Otherwise, the Axis2 download
page should warn users that the release has limited functionality until
these other projects are available.
- Dennis
Glen Daniels wrote:
(resend
[
https://issues.apache.org/jira/browse/AXIS2-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4408:
Fix Version/s: 1.6
Targeting this for 1.6
the problem of In-only method with throw exception
[
https://issues.apache.org/jira/browse/AXIS2-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4376.
-
Resolution: Invalid
Resolving this, and I promise to update the main page with the new JDK
[
https://issues.apache.org/jira/browse/AXIS2-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4404:
Fix Version/s: 1.6
Targeting this for 1.6.
Also, reminder to Ramya - please update
[
https://issues.apache.org/jira/browse/AXIS2-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4353:
Fix Version/s: 1.6
Targeting for 1.6
ServiceClient can not resolve WSDL with imported schemas
[
https://issues.apache.org/jira/browse/AXIS2-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reassigned AXIS2-4337:
---
Assignee: Glen Daniels
Missing org.apache.axis2.transport.tcp.TCPTransportSender into Axis2
[
https://issues.apache.org/jira/browse/AXIS2-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744093#action_12744093
]
Glen Daniels commented on AXIS2-4337:
-
I don't agree with adding the extra transports
[
https://issues.apache.org/jira/browse/AXIS2-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4319:
Fix Version/s: 1.6
Targeting this at 1.6
CLONE -WSDL2Java: minOccurs and maxOccurs in sequence
[
https://issues.apache.org/jira/browse/AXIS2-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744096#action_12744096
]
Glen Daniels commented on AXIS2-4279:
-
Isn't this already resolved in 1.5? I don't
[
https://issues.apache.org/jira/browse/AXIS2-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4197:
Fix Version/s: 1.6
Targeting for 1.6
Issue with toEnvelope(..) and toOm(..) in Axis 2 generated
[
https://issues.apache.org/jira/browse/AXIS2-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4050:
Fix Version/s: (was: nightly)
1.6
Targeting 1.6 for a final fix
[
https://issues.apache.org/jira/browse/AXIS2-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-3947:
Fix Version/s: 1.6
Targeting 1.6.
EJB provider run only once
[
https://issues.apache.org/jira/browse/AXIS2-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-3723:
Fix Version/s: (was: nightly)
1.6
Targeting this at 1.6.
AXIS2
[
https://issues.apache.org/jira/browse/AXIS2-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-3781.
-
Resolution: Fixed
Fix Version/s: 1.5.1
This appears to work fine now, so am uncommenting
[
https://issues.apache.org/jira/browse/AXIS2-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-1556:
Fix Version/s: 1.6
Targeting for 1.6.
DeploymentException with segmented wsdl files
Hi Axis Developers,
I've put up what will hopefully be our 1.5.1 release, with a few key fixes as
follows:
* Fix for the dreaded CLOSE_WAIT problem (JIRA issues 935, 2883, etc).
We now share an instance of HTTPClient across each ConfigurationContext (i.e.
each Axis2 server or ServiceClient)
(resend with corrected URL)
Hi Axis Developers,
I've put up what will hopefully be our 1.5.1 release, with a few key fixes as
follows:
* Fix for the dreaded CLOSE_WAIT problem (JIRA issues 935, 2883, etc).
We now share an instance of HTTPClient across each ConfigurationContext (i.e.
each
Hi Deepal:
Deepal Jayasinghe wrote:
So, there are currently no JIRAs left targeted for 1.5.1, and there were at
least a few major fixes (in particular the CLOSE_WAIT issues, transport
deployer fix, and the module versioning stuff) since 1.5 that I for one would
really like to get out into the
Hi Sebastian:
Sebastian Just - RÖPERWEISE Systems wrote:
On Thu, 06 Aug 2009 09:44:16 -0400, Glen Daniels g...@thoughtcraft.com
Would you mind merging this fix over to the 1.5 branch so it can get into
1.5.1?
So will it be in 1.5.1 release?
Or will it be in some other release (can you say
Thanks, dims!
Would you mind merging this fix over to the 1.5 branch so it can get into 1.5.1?
--Glen
Davanum Srinivas wrote:
Checked in svn revision 801630.
thanks,
dims
On 08/06/2009 08:45 AM, Sebastian Just - RÖPERWEISE Systems wrote:
Hi !
On Thu, 6 Aug 2009 06:58:22 -0400, Davanum
[
https://issues.apache.org/jira/browse/AXIS2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-2883.
-
Resolution: Fixed
Fix Version/s: 1.5.1
Hi all.
This long-standing problem is now fixed
[
https://issues.apache.org/jira/browse/AXIS2-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4330.
-
Resolution: Fixed
Fix Version/s: 1.5.1
This has been fixed (see http://svn.apache.org
[
https://issues.apache.org/jira/browse/AXIS2-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-2945.
-
Resolution: Fixed
Fix Version/s: 1.5.1
Marking this as resolved for now, based on testing
Hi folks:
So, there are currently no JIRAs left targeted for 1.5.1, and there were at
least a few major fixes (in particular the CLOSE_WAIT issues, transport
deployer fix, and the module versioning stuff) since 1.5 that I for one would
really like to get out into the world ASAP.
What needs to
[
https://issues.apache.org/jira/browse/AXIS2-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4426:
Fix Version/s: (was: 1.5.1)
1.6
Retargeting this at 1.6, since it's
[
https://issues.apache.org/jira/browse/AXIS2-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4185:
Fix Version/s: (was: 1.4.1)
(was: 1.4)
(was: 1.3
[
https://issues.apache.org/jira/browse/AXIS2-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-3967:
Fix Version/s: (was: 1.4)
1.6
Re-targeting for 1.6 - we'll evaluate again
[
https://issues.apache.org/jira/browse/AXIS2-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels updated AXIS2-4348:
Fix Version/s: (was: 1.4.1)
1.6
Re-targeting to 1.6.
Service
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12738176#action_12738176
]
Glen Daniels commented on AXIS2-4114:
-
Hi all - I just checked in NPE protection code
[
https://issues.apache.org/jira/browse/AXIS2-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4377.
-
Resolution: Fixed
Just fixed this on the branch. Still needs a test case, but leaving 4114 open
Hi Dennis:
Dennis Sosnoski wrote:
Whether officially led by WSO2 or not, certainly most of the direction
of the project has come from people associated with WSO2 and/or the Sri
Lanka university. Glen is, I believe, the current chair of the PMC, and
was also the release manager for the 1.5
Hi Dennis:
Dennis Sosnoski wrote:
I'm going to try and get 1.5.1 out the door ASAP, and will commit to
at least
the transports happening along with that.
Sounds great, Glen! But Axis2 really requires compatible Rampart and
probably Sandesha releases since these implement functionally which
Hi everyone:
Once again, I'm cc'ing all the -dev lists to make absolutely sure everyone
sees this note. Future mails will just go to gene...@.
It's time to get this discussion going, and hopefully bring it to some kind
of a place from which we can affect change as a community. We're going to
[
https://issues.apache.org/jira/browse/AXIS2-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12726945#action_12726945
]
Glen Daniels commented on AXIS2-2945:
-
Michele, I just checked in what I think is a fix
[
https://issues.apache.org/jira/browse/AXIS2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reassigned AXIS2-2883:
---
Assignee: Glen Daniels (was: Deepal Jayasinghe)
CLOSE_WAIT slowly building up over
[
https://issues.apache.org/jira/browse/AXIS2-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AXIS2-2883 started by Glen Daniels.
CLOSE_WAIT slowly building up over the period of time
[
https://issues.apache.org/jira/browse/AXIS2-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-3084.
-
Resolution: Fixed
Fixed in rev 784574. Please check it out and Andreas, if you feel strongly
[
https://issues.apache.org/jira/browse/AXIS2-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-2856:
-
This has certainly not been fixed, and should remain open until it's actually
resolved.
Module
[
https://issues.apache.org/jira/browse/AXIS2-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-4040:
-
fixed was an inappropriate resolution.
Web Service with Java generic type
[
https://issues.apache.org/jira/browse/AXIS2-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4040.
-
Resolution: Invalid
Web Service with Java generic type
[
https://issues.apache.org/jira/browse/AXIS2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-3274.
-
Resolution: Cannot Reproduce
Correct resolution.
Axis2 kernel logging on WAS 6.1
[
https://issues.apache.org/jira/browse/AXIS2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-3274:
-
Not fixed
Axis2 kernel logging on WAS 6.1
---
Key
[
https://issues.apache.org/jira/browse/AXIS2-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-2790:
-
Not fixed
Having a problem with the JavaScript call (of Google Analytics) on axis2 html
after
[
https://issues.apache.org/jira/browse/AXIS2-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-2790.
-
Resolution: Won't Fix
If this is still an issue, please feel free to reopen.
Having a problem
[
https://issues.apache.org/jira/browse/AXIS2-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-3195.
-
Resolution: Invalid
If this is actually still a problem with Axiom or Rampart, please let's
[
https://issues.apache.org/jira/browse/AXIS2-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-3195:
-
Not fixed
AXIOM parser's throwing NullPointerException if OMElement.getParent() is
instance
[
https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-2819.
-
Resolution: Incomplete
Need a test case, if this is indeed still a problem (in which case please
[
https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-2819:
-
We don't know this is fixed
Faulty handling of JMS asynchronous calls
[
https://issues.apache.org/jira/browse/AXIS2-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-3084:
-
Not fixed.
Should make inflow/outflow (at least) case insensitive in module.xml
[
https://issues.apache.org/jira/browse/AXIS2-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719142#action_12719142
]
Glen Daniels commented on AXIS2-3084:
-
We just need to iterate over the child elements
[
https://issues.apache.org/jira/browse/AXIS2-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-2969:
-
This wasn't fixed - it should be either invalid, won't fix, or we should
continue discussing
[
https://issues.apache.org/jira/browse/AXIS2-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719151#action_12719151
]
Glen Daniels commented on AXIS2-3084:
-
I can relate to your way of thinking, Andreas
If you'd like to discuss the PMC reorganization issue, please keep that
thread on gene...@ws instead of any of the project-specific lists.
Thanks!
--Glen
, usage, etc.
Thanks for your interest in Apache Axis2!
--Glen Daniels
[
https://issues.apache.org/jira/browse/AXIS2-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718171#action_12718171
]
Glen Daniels commented on AXIS2-4371:
-
I agree re: considering a quick 1.5.1, Deepal
[
https://issues.apache.org/jira/browse/AXIS2-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718205#action_12718205
]
Glen Daniels commented on AXIS2-4371:
-
+1, Andreas. Can you merge your fixes over
.
Thanks for your interest in Apache Axis2!
--Glen Daniels
Hi folks.
Just FYI - I haven't officially announced the 1.5 release yet because I'm
doing a few changes to the site (and hopefully the process around the site as
well). The artifacts are in Maven already, however, and the dist is where
you'd expect. :)
I'll do the actual announcement tonight or
Andreas Veithen wrote:
Amila,
Can you fix the typo in the value of the
ENABLE_CHILD_FIRST_CLASS_LOADING constant? (there is an i missing)
While we're at it, what do you think of changing it to simply
ChildFirstClassLoading? The Enable part seems redundant and only leads
to more typing
Hey folks!
Axis2 1.5 release vote passes with 8 +1's (7 binding) and no -1's.
I'll be doing the actual release tomorrow after I get home from my current
biz trip.
Thanks,
--Glen
Hi Deepal:
Deepal jayasinghe wrote:
Yes, there is a difference. One method is for management other method is
for dispatching.
So at the runtime when a message receive we call getService, and if we
want to activate, inactivate we call other method.
Throwing an exception to do this is (IMHO)
Hi Andreas:
Andreas Veithen wrote:
What do you mean by JDK 1.5 can't compile @Override annotations???
In JDK 1.5, @Override is supported only for superclass methods, and using it
on an interface method produces a compiler error. :( This sucks, but until
we move off 1.5 that's what we seem
Hi y'all:
So I'm cleaning up a little code and javadoc, and happened to come across
AxisConfiguration.getService()... which *throws an Exception* if you ask for
an inactive service.
...which is why we have a second method called getServiceForActivation()
that simply avoids the check and the
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 files in here:
[PLEASE KEEP REPLIES TO THIS THREAD ON gene...@ws. If you're not on it and
interested, please subscribe.]
Hi all:
June approaches, and with it another WS PMC board report. After the March
report, we were again asked by the board what's up with our project's
organization. As such, I'd like to
Amila Suriarachchi wrote:
Hm - it seems like you didn't actually get my point. We CAN'T
return the
actual allServices map because that would be breaking the abstraction
boundary provided by the class.
As I remember this change was done to avoid concurrent modifications to
Hi Keith!
keith chapman wrote:
Due to a design issue in the Axis2 API we have implemented the
getServices() method as follows,
public HashMapString, AxisService getServices() {
HashMapString, AxisService hashMap = new HashMapString,
AxisService(this.allServices.size());
keith chapman wrote:
In my view this is highly inefficient, especially if you have
plenty of
services in the system. Wouldn't it be better to fix the API and
return
a Map instead of a HashMap? If we did that we could simple return
allServices instead of returning
Hi all!
New version of Axis2 1.5 Release Candidate is ready, including a)
NOTICE/LICENSE files in the jars, b) some JiBX fixes from Dennis, c) some
fixes from Amila, d) a README which is more clear about building from
scratch. Please check it out if you get a chance, and let me know if there
are
Hi Nandana!
Turns out there were a few other issues with the 1.5 RC, so we're going to do
another one anyway. As such, please do go ahead and apply your fixes to the
branch if you're confident they're solid. I was hoping to roll out another
RC today but it looks like it might be Monday.
Just read your note more carefully, and noticed the patch. I'll go apply it!
--Glen
Glen Daniels wrote:
Hi Nandana!
Turns out there were a few other issues with the 1.5 RC, so we're going to do
another one anyway. As such, please do go ahead and apply your fixes to the
branch if you're
[
https://issues.apache.org/jira/browse/AXIS2-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-4313.
-
Resolution: Fixed
Patch applied and tested. Thanks Nandana.
Some MTOMPolicy module
Thanks, Andreas. Martin, the test you refer to doesn't fail for me when I
build... are you seeing this error when doing a mvn clean install?
Incidentally, I'm in the midst of fixing the poms to include NOTICE and
LICENSE files in all the jars (thanks to Dan Kulp for pointing this out on
IM).
Hi all!
After a failed set of attempts to use the Maven release plugin, I've built
and uploaded a Release Candidate for Axis2 1.5. Please check it out, kick
the tires, etc. If I don't hear anything back in the next day or so I'll
start a VOTE to release these bits as 1.5.
You can find the
1 - 100 of 829 matches
Mail list logo
