Otherwise looks OK to me, but I haven't had a chance to actually run it
through its paces. That said, here's my +1.
--Glen
On 8/9/11 10:14 PM, Daniel Kulp wrote:
On Tuesday, August 09, 2011 8:33:23 PM Glen Daniels wrote:
Hi guys,
I downloaded the binary release and didn't see
Took a quick look, built the source distro, everything seems to look good.
+1
--Glen
On 7/11/11 12:17 PM, Daniel Kulp wrote:
Here is a vote to release Neethi 3.0.1
We've fixed 4 bugs that were found in 3.0.0 and it would be good to get those
fixes out to users.
Tag:
Hi Andreas,
On 6/4/11 2:22 PM, Andreas Veithen wrote:
s/Moved to Axis, delete/To be moved to Axis/
Everything that has been moved to Axis has already been deleted.
However, there is still stuff that has not been moved yet.
Right - looking at that more closely now. I don't see anything in
:
So if this is true, Macromedia (my and Glen Daniels employer at the time) and
now Adobe owns a copyright on Apache Axis code? We just didn't ask the
team to put this copyright in the code/NOTICE file?
And Day (now Adobe) has copyrights on the JackRabbit code?
And Sun (now Oracle) has
On 10/25/2010 11:24 AM, Daniel Kulp wrote:
cp -a /www/ws.apache.org/axis /www/axis.apache.org
cp -a /www/ws.apache.org/axis2 /www/axis.apache.org
cp -a /www/ws.apache.org/axis2-c /www/axis.apache.org
FYI, this is now done. Once we see the content show up on the front-facing
servers, we
*waves to Doug!*
+1 - a history section is absolutely the right thing. IIRC the SVN pointers
do redirect... right?
--Glen
On 10/25/2010 10:59 AM, Doug Davis wrote:
Not really wanting to jump into the middle of this :-) but it seems to
me that not mentioning Axis *1* would be bad too.
On 10/25/2010 12:19 PM, jehanzeb.qay...@gmail.com wrote:
Please remove me from list.
Automatic unsub not working.
And what leads you to believe that? If you send mail to
dev-unsubscr...@ws.apache.org you will get a response. That response will
either tell you to reply to confirm
On 10/18/2010 7:05 AM, Benson Margulies wrote:
I guess I'm +0 for doing this now, assuming that we will continue to have a
WS project in some way shape or form, containing many/most of these
subprojects.
OK, but what's the scoop on deleting things that got atticed or
transfered to Axis?
Hi Benson,
On 10/17/2010 4:54 PM, Benson Margulies wrote:
I hope no one will be offended by offering this as a vote right off
the bat, but it seems sort of self-evidently a good idea to me.
I want to move the contents of 'commons' to be direct children of the
ws project in svn. I've already
Hi Jonas, all,
You guys had expressed some interest in possibly continuing to work on MUSE
back in August, and we haven't heard anything since then. An active project
requires an active community, and we need to finalize a decision on whether
to move MUSE to the Attic or not.
Can you please let
+1
--Glen
On 9/28/2010 12:22 PM, Colm O hEigeartaigh wrote:
To the Apache Web Services Community,
This is a call for votes for the wss4j-1.5.9 release. It's been well
over a year since 1.5.8 was released, and 32 bugs have been fixed in
1.5.9.
The distribution was built from the
Hi Colm, all,
Thanks for the push of this release - I'll take a look at the artifacts later
this afternoon. One question to you and to the Rampart devs, which is of
course has this been tested with Rampart?
Thanks,
--Glen
On 9/27/2010 11:57 AM, Colm O hEigeartaigh wrote:
To the Apache Web
+1 from me. Thanks for rolling this out and fixing the API change.
--Glen
On 9/22/2010 5:39 PM, Benson Margulies wrote:
I have prepared a proposed release of Apache XmlSchema 1.4.7.
https://repository.apache.org/content/repositories/orgapachews-008/
This is a formal vote for a release.
Congratulations to the jUDDI team, this resolution is passed!
There were 9 binding +1s, and 1 non-binding +1. There were no -1s.
VOTE thread at http://markmail.org/message/yboktfwa7fjloxyx
The resolution is in this month's board report.
Thanks,
--Glen
Both of these resolutions were passed by the PMC.
There were 6 +1 votes, and no -1 votes.
VOTE thread at http://markmail.org/message/z6tdwmdlwofzoxss
The WSIF resolution is in this month's board report, and we decided to hold
off on submitting the Muse resolution until a bit more conversation
Congratulations to the jUDDI team, this resolution is passed!
There were 9 binding +1s, and 1 non-binding +1. There were no -1s.
VOTE thread at http://markmail.org/message/yboktfwa7fjloxyx
The resolution is in this month's board report.
Thanks,
--Glen
Web Services PMC members:
Please VOTE on the following resolution, which promotes the jUDDI and Scout
subprojects into a new TLP. There is just enough time to let this vote run
for 72 hours and still get the resolution in to our board report on Monday.
*** PLEASE DIRECT ALL VOTES TO
Web Services PMC members:
Please VOTE on the following resolution, which promotes the jUDDI and Scout
subprojects into a new TLP. There is just enough time to let this vote run
for 72 hours and still get the resolution in to our board report on Monday.
*** PLEASE DIRECT ALL VOTES TO
Hm, no comments on this yet? jUDDI folks?
--Glen
On 8/3/2010 12:04 PM, Glen Daniels wrote:
jUDDI developers and PMC members,
Greetings. In an effort to continue the successful restructuring of the Web
Services PMC, I'd like to hereby propose that we split out the jUDDI and
Scout
Sure, but I wanted in particular to make sure that was indeed the right list
of initial members. Just those four then?
--G
On 8/5/2010 1:15 PM, Kurt T Stam wrote:
Now that some people replied I think we have enough consensus to start
the actual vote? -Kurt
Glen Daniels wrote:
Hm
jUDDI developers and PMC members,
Greetings. In an effort to continue the successful restructuring of the Web
Services PMC, I'd like to hereby propose that we split out the jUDDI and
Scout subprojects into a new Top-Level Project known as the Apache jUDDI
Project. These two projects are healthy
Hi all,
So, it's time to get the WS project cleanup moving a little. Toward that
end, I submit for your approval two resolutions that I would like to present
to the board at this month's meeting. These serve to retire the Muse and
WSIF projects (which as far as I am aware have zero active
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
Hi all!
Well, Axis is gone, and as the dust settles, we need to keep moving the WS
project in whatever direction it's going to go. Toward that end, this email
brings you two exciting topics -
1) We need to submit a board report this month. I've set up a template here:
[
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:
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:
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:
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:
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:
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:
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:
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:
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:
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
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
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
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
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
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:
Hi Rich!
This change apparently broke the Hudson build:
http://hudson.zones.apache.org/hudson/job/ws-axiom-trunk/72/
Could you look into this?
Thanks,
--Glen
sc...@apache.org wrote:
Author: scheu
Date: Tue Oct 13 21:17:42 2009
New Revision: 824930
URL:
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
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
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
we require some jars to be
endorsed to run tests). I wish I could help to figure out the timeout issue
but unfortunately I am working for an assignment deadline :(.
regards,
Nandana
On Thu, Oct 8, 2009 at 11:10 PM, Glen Daniels g...@thoughtcraft.com wrote:
Hi Nandana:
Ok, I continued
Hi folks:
Before voting on the 1.5 release, I checked out the branch and did a mvn
clean install... it hung hard at Testing WS-Sec: custom scenario 3 the
first time, and at custom scenario 4 the second time.
Is anyone else seeing the build hanging? I'd like to confirm this isn't a
problem with
at 6:57 PM, Glen Daniels g...@thoughtcraft.com wrote:
Hi folks:
Before voting on the 1.5 release, I checked out the branch and did a mvn
clean install... it hung hard at Testing WS-Sec: custom scenario 3 the
first time, and at custom scenario 4 the second time.
Is anyone else seeing
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
Hi folks:
Please note that although this first release will entail releasing all the
transports simultaneously, this is quite possibly the LAST time that will
happen barring any major API changes in Axis2.
We need to be able to release *each* transport individually, on their own
schedules, as
[
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
1 - 100 of 1150 matches
Mail list logo
