Hi,
Uthaiyashankar [EMAIL PROTECTED] writes:
Hi,
We fixed the error. Now it is working without crashing.
We have fixed all the major bugs that we had with Axis2/C 1.3.1
Release artifacts. Ill upload new Release artifacts soon.
thanks,
Dinesh
--
http://nethu.org
Hi Devs,
I have packaged and uploaded the Apache Axis2/C 1.3.1 release artifacts at
[1]. The key used to sign the release artifacts can be found at [2].
Please test, review and vote on the release artifacts for Apache Axis2/C
1.3.1 release.
I have tested and reviewed them, here is my +1
Hi,
I've tested in Ubuntu 7.04, both the source and binary works fine.
Here's my +1,
Regs
lahiru
On Wed, Apr 23, 2008 at 3:30 PM, Dinesh Premalal [EMAIL PROTECTED] wrote:
Hi Devs,
I have packaged and uploaded the Apache Axis2/C 1.3.1 release artifacts
at [1]. The key used to sign the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff,
Do we need this test case anymore? Here's the comment from the test case
~/*
~* This is a TEMPORARY test. It is testing the construction of a
~* ParameterDesc using a class (instead of a DBC). Using a class should
~* be
Glen Daniels wrote:
[ Please refer to this thread for context :
http://markmail.org/message/lg3giq5kj74gjnxb
]
OK, let me make a concrete proposal here.
I hereby propose that we kick off a ws-commons transports project.
As with the other ws-commons projects, this would have its own
+1 to this proposal
Paul
On Wed, Apr 23, 2008 at 5:11 AM, Sanjiva Weerawarana
[EMAIL PROTECTED] wrote:
Wow, miss this list for a few days and boom!
Here's my attempt at a summary position:
- First of all, Asankha, why synapse-transports.jar?? That makes no sense
to me- so if you have a
On 23 Apr 2008, at 05:11, Sanjiva Weerawarana wrote:
- First of all, Asankha, why synapse-transports.jar?? That makes
no sense to me- so if you have a bug in the VFS code you'll rev all
the stuff? Why? There should be one jar per transport.
Java provides packages for that. There's no need
Hey Sanjiva:
Sanjiva Weerawarana wrote:
- I agree with that Axis2 transports should NOT be in the kernel jar.
Can we finally agree (forget the history please) to that now and create
new maven modules for each transport and put each one into its own jar?
This is for the transports that are (or
+1
And while we're at it (separate conversation though), perhaps
transports should be deployable as easily as services/modules...
conf/
modules/
services/
transports/
nhttp.tsp
jms.tsp
...with transport.xml inside *.tsp/META-INF
This is just a matter of writing a new
Deepal Jayasinghe wrote:
And while we're at it (separate conversation though), perhaps
transports should be deployable as easily as services/modules...
conf/
modules/
services/
transports/
nhttp.tsp
jms.tsp
...with transport.xml inside *.tsp/META-INF
This is just a matter of
Hi Michele:
Michele Mazzucco wrote:
- First of all, Asankha, why synapse-transports.jar?? That makes no
sense to me- so if you have a bug in the VFS code you'll rev all the
stuff? Why? There should be one jar per transport.
Java provides packages for that. There's no need to have tons of
Glen,
I disagree, each transport is composed by just a few classes, not
megs of code.
I can't see really see where the problem is if you put JMS and SMTP
transports into the same jar file.
Michele
On 23 Apr 2008, at 13:09, Glen Daniels wrote:
Hi Michele:
Michele Mazzucco wrote:
- First
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
Michele, its about making it easy to maintain and use. We gain nothing by
putting them into the same jar file.
With respect to your comment earlier saying
So you end up increasing the limits for files/sockets on you linux box
HUH?? What are you talking about?? This has nothing to do with limits
On Tue, Apr 22, 2008 at 6:12 PM, Deepal jayasinghe [EMAIL PROTECTED]
wrote:
Davanum Srinivas wrote:
Folks,
First step, let's get rid of backport jar? thoughts?
+1 , after that I will start generic support in POJOs :)
+1 what about removing annogen??
-Deepal
Amila,
+1 to that too
thanks,
dims
PS: What a peaceful thread this one is :)
On Wed, Apr 23, 2008 at 11:17 AM, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
On Tue, Apr 22, 2008 at 6:12 PM, Deepal jayasinghe [EMAIL PROTECTED]
wrote:
Davanum Srinivas wrote:
Folks,
First step,
On 23 Apr 2008, at 14:24, Sanjiva Weerawarana wrote:
Michele, its about making it easy to maintain and use. We gain
nothing by putting them into the same jar file.
With respect to your comment earlier saying
So you end up increasing the limits for files/sockets on you linux
box
HUH?? What
I can't connect to
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/Summary.vm/fid/continuumProject
thanks,
Tom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Dims,
Yeah, with much peace :-) +1 from me too.
Thanks,
Ruwan
On Wed, Apr 23, 2008 at 9:36 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
Amila,
+1 to that too
thanks,
dims
PS: What a peaceful thread this one is :)
On Wed, Apr 23, 2008 at 11:17 AM, Amila Suriarachchi
[EMAIL
Problem with SimpleAxisServer
-
Key: AXIS2-3762
URL: https://issues.apache.org/jira/browse/AXIS2-3762
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Brian DePradine
Assignee: Davanum
Issues with loading the W3CEndpointReference class
--
Key: AXIS2-3763
URL: https://issues.apache.org/jira/browse/AXIS2-3763
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components:
Michele Mazzucco wrote:
Yes, since every jar file adds 1 to the number of files opened by a
process (your JVM is a process itself). The default limit for files +
socket that can be opened by a process is 1024.
Um in toy systems maybe .. but this a tunable kernel parameter and in any
real
[
https://issues.apache.org/jira/browse/AXIS2-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian DePradine updated AXIS2-3763:
---
Attachment: PATCH.TXT
A patch to address the issues mentioned previously.
Issues with
On 23 Apr 2008, at 18:20, Sanjiva Weerawarana wrote:
Michele Mazzucco wrote:
Yes, since every jar file adds 1 to the number of files opened by
a process (your JVM is a process itself). The default limit for
files + socket that can be opened by a process is 1024.
Um in toy systems maybe
+1 for this
Personally I would like to download all the transport as a single jar , but
I do not mind releasing them separately as long as you give single jar as
well.
I like this idea very much. I said more or less the same thing when we had a
similar disucssion a while back.
If my memory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
FYI, I still have 3 tests to fix and clustering module to work. But rest of the
build is fine with Harmony. Many thanks
to the Harmony team for quick turn arounds. Oh, maven2 builds/tests of Axiom,
Neethi, XmlSchema, Woden all work fine now
Sanjiva
Sanjiva Weerawarana wrote:
- First of all, Asankha, why synapse-transports.jar?? That makes no
sense to me- so if you have a bug in the VFS code you'll rev all the
stuff? Why? There should be one jar per transport. Yes, lots of jar
files but so what?
- Asankha, you seem to think
Who will run all the transports in a single server? I like the ability to pick
and choose what I want. May be you will ship one or two key transports as
part of Axis2 and that is sufficient for most of the users.
This way if there is a bug in a particular transport that can be fixed and
Glen, why ws/commons/transports? Why not ws/transports??
We've moved away from commons in Axiom etc. - that is, packages no longer
say that and IMO that's better.
Sanjiva.
Deepal jayasinghe wrote:
Glen Daniels wrote:
[ Please refer to this thread for context :
Glen, why ws/commons/transports? Why not ws/transports??
Even though we call ws/commons/transports or ws/transports those
components only valid for Axis2. Therefore I can not see the value of
having axis2 transport under WS [ I know I did +1 on the proposal.] :-\
We've moved away from
As we discussed in the mailing list I created a prototype deployer
(TransportDeployer) for transport deployment. With the deployer I wrote
we can deploy transport as we deploy service or module. The only thing
we need to do is to add a descriptor file called “transport.xml” into
the META-INF
31 matches
Mail list logo
