]]Davanum
Srinivas [EMAIL PROTECTED]
*Davanum Srinivas [EMAIL PROTECTED]*
02/27/2008 08:33 AM Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2] Moving Axis2 code base into JDK 1.5
-BEGIN PGP SIGNED MESSAGE
Hi
On 28/02/2008, Andreas Veithen [EMAIL PROTECTED] wrote:
[...]
What we did was to use retrotranslator
(http://retrotranslator.sourceforge.net/
) to translate the library as well as its dependencies (including JAXB
2) back to Java 1.4.
retroweaver is another
Hi,
How can I edit the skeleton generated using JiBx or Axiom?
I dont want to do it manually.
Is there any way to edit it using some xsl templates and add it to the
.aar creation of ant task?
Regards,
Suresh B.
Tata Consultancy Services
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com
Hi all:
I'm essentially +0 on the move to 1.5 as well. I do think it's time,
and as one of our users stated back when we did the last poll, it can
actually help *them* to push the move to 1.5 inside their companies if
infrastructure like Axis makes the leap. However there is the very real
Does Axis2 use JDK 1.5 specific features e.g. generics?
Thanks/
Martin-
- Original Message -
From: Glen Daniels [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Monday, March 03, 2008 9:39 AM
Subject: Re: [Axis2] Moving Axis2 code base into JDK 1.5
Hi all:
I'm essentially +0
]
To: axis-dev@ws.apache.org
Sent: Monday, March 03, 2008 9:39 AM
Subject: Re: [Axis2] Moving Axis2 code base into JDK 1.5
Hi all:
I'm essentially +0 on the move to 1.5 as well. I do think it's time,
and as one of our users stated back when we did the last poll, it can
actually help *them
PROTECTED]
| 02/27/2008 05:15 AM
| Please respond to
| axis-dev@ws.apache.org
|
|
| To
| [EMAIL PROTECTED]
| cc
| axis-dev@ws.apache.org axis-dev@ws.apache.org
| Subject
| Re: [Axis2] Moving Axis2 code base into JDK 1.5
|
|
|
|
|
|
| +1 to moving to Java 5. I think maintenance releases could be key
Andreas Veithen wrote:
...
Moving to Java 1.5 doesn't necessarily mean to abandon support for
Java 1.4. I am currently working on a project for a company that still
uses Java 1.4 (and I think there are lots of them). We needed a
library to generate MS Project files, but the only one we could
Hi,
As far as the vote goes I would say 0-
From the suggestions we have the ones I can agree is to release 1.4
(the next one) with JDK 1.4 and focus on setting the new JDK version
for the next release (I have posted the XmlSchema release candidate
which complies to JDK 1.4 a few hours ago and had
I agree moving 1.5 is not merely a change of JDK but a change of APIs.
However, realistically, I imagine that'll be an incremental process- i.e.,
no one will sit and go thru and introduce generics wherever possible ..
rather we'll start using 1.5 features without restriction when the need
My concern is that I think there has been a lot of work done since the
last release and the JDK1.4 users will never get that benefit.
So - how about this for a plan.
Release 1.4 asap based on JDK 1.4.
Then do a 1.5 release *very soon after* based on JDK1.5.
That way even the names match :)
+1 to moving to Java 5. I think maintenance releases could be key in
keeping those users tied to Java 1.4, interested in Axis2 until
they're ready to move up to Java 5 themselves.
Jeremy
On 27/02/2008, Paul Fremantle [EMAIL PROTECTED] wrote:
Yes I guess that makes sense.
However, its most
Yes I guess that makes sense.
However, its most likely that we would roll up whatever is in the trunk.
I guess that there might be also end up being a 1.4.1 maintenance
release as well.
Paul
On Wed, Feb 27, 2008 at 10:36 AM, Michele Mazzucco
[EMAIL PROTECTED] wrote:
Paul,
if so, I think
Hi all ,
As you might remember few months back Glen asked the list about moving
to JDK 1.5 and I think we got very positive feedback. So I thought of
asking again and change the code to work with JDK 1.5 . The main
reason behind sending this mail is due the dependency we have for
annogen.
+1 to moving Axis2 to Java 5. With Woden currently at Java 1.4 (to support
Axis2) we provide a type-safe API using typed arrays. We would prefer to use
Java 5 generics.
+1 to previous suggestions about supporting existing Axis2 uses tied to Java
1.4 by rolling up trunk into an Axis2 1.4 release
PROTECTED]
cc
axis-dev@ws.apache.org axis-dev@ws.apache.org
Subject
Re: [Axis2] Moving Axis2 code base into JDK 1.5
+1 to moving to Java 5. I think maintenance releases could be key in
keeping those users tied to Java 1.4, interested in Axis2 until
they're ready to move up to Java 5 themselves
and Sametime ID: [EMAIL PROTECTED]
|
|
|
| Jeremy Hughes [EMAIL PROTECTED]
| Sent by: [EMAIL PROTECTED]
| 02/27/2008 05:15 AM
| Please respond to
| axis-dev@ws.apache.org
|
|
| To
| [EMAIL PROTECTED]
| cc
| axis-dev@ws.apache.org axis-dev@ws.apache.org
| Subject
| Re: [Axis2] Moving Axis2 code base
Hi all ,
As you might remember few months back Glen asked the list about moving
to JDK 1.5 and I think we got very positive feedback. So I thought of
asking again and change the code to work with JDK 1.5 . The main reason
behind sending this mail is due the dependency we have for annogen. As
-dev@ws.apache.org axis-dev@ws.apache.org,
[EMAIL PROTECTED] [EMAIL PROTECTED]
cc
Subject
[Axis2] Moving Axis2 code base into JDK 1.5
Hi all ,
As you might remember few months back Glen asked the list about moving
to JDK 1.5 and I think we got very positive feedback. So I thought of
asking
PROTECTED]
02/26/2008 11:15 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org axis-dev@ws.apache.org,
[EMAIL PROTECTED] [EMAIL PROTECTED]
cc
Subject
[Axis2] Moving Axis2 code base into JDK 1.5
Hi all ,
As you
]
cc
Please respond to
[EMAIL PROTECTED] Subject
e.org [Axis2] Moving Axis2 code base
@ws.apache.org axis-dev@ws.apache.org,
|[EMAIL PROTECTED] [EMAIL PROTECTED]
|cc
|
|Subject
|[Axis2] Moving Axis2 code base into JDK 1.5
|
|
|
|
|
|
|
|
|
|Hi all ,
|
|As you might remember few months back Glen asked the list about moving
|to JDK
To
axis-dev@ws.apache.org axis-dev@ws.apache.org,
[EMAIL PROTECTED] [EMAIL PROTECTED]
cc
Subject
[Axis2] Moving Axis2 code base into JDK 1.5
Hi all ,
As you might remember few months back Glen asked the list about moving
to JDK 1.5 and I
From my experiences working with companies moving to Axis2 I'd say
about half are still using JDK 1.4. If they can't count on that support
being maintained I think they're likely to reconsider adopting Axis2.
Just having an archived 1.3 version of Axis2 won't be enough to convince
them, unless
24 matches
Mail list logo
