You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Glen Daniels <gl...@thoughtcraft.com> on 2007/08/15 06:25:51 UTC
[axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Hi Axis2 developers and users!
There has been a bunch of discussion lately revolving around the
question of JDK1.4 compatibility. It has been suggested that Axis2 move
to JDK 1.5, in order to gain the benefits of things like generics,
built-in concurrency (no backport lib), and annotations. Some folks
feel that there are enough people out there still in a 1.4 environment
that we should hold off, and others think we should bite the bullet and
move to 1.5.
HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
Are you using, or planning to use, Axis2 in an environment that is
locked to JDK 1.4? If so, please let us know by responding to this
thread and telling us (if you can) about the particulars of what's tying
you to 1.4 - is it your app server? Company policy? Something else?
We'd really like to take good care of our users, and doing that involves
figuring out whether we can jump into 1.5-land or if we need to keep
things working with 1.4.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
Posted by "Du, David (US SSA)" <da...@baesystems.com>.
I have log4j-1.2.14.jar in the axis2.war file. So it should not be that.
Thanks
David
-----Original Message-----
From: Michael.Davis@servicecanada.gc.ca
[mailto:Michael.Davis@servicecanada.gc.ca]
Sent: Thursday, August 16, 2007 3:11 PM
To: axis-user@ws.apache.org
Subject: RE: 'org.apache.commons.logging.impl.Log4JLogger' cannot be
found or is not useable.
Maybe you need the log4j*.jar file?
cheers,
md
> -----Original Message-----
> From: Du, David (US SSA) [mailto:david.du@baesystems.com]
> Sent: Thursday, August 16, 2007 2:32 PM
> To: axis-user@ws.apache.org
> Subject: 'org.apache.commons.logging.impl.Log4JLogger' cannot be found
> or is not useable.
>
>
> Hi, I tried the new axis2-1.3 release, I got the following error after
> copied axis2.war file into my tomcat4.1.36, the axis2-1.2
> worked before,
> but not the 1.3 release; it happened to tomcat5.5.23 as well.
> I checked
> the commons-logging-1.1.jar file, it exists under directory:
> C:\apache-tomcat-4.1.36\webapps\axis2\WEB-INF\lib.
>
> 2007-08-16 13:35:09 ContextConfig[/axis2] Parse error in
> default web.xml
> org.apache.commons.logging.LogConfigurationException:
> User-specified log
> class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or
> is not useable.
> at
> org.apache.commons.digester.Digester.createSAXException(Digest
> er.java:31
> 81)
> at
> org.apache.commons.digester.Digester.createSAXException(Digest
> er.java:32
> 07)
> at
> org.apache.commons.digester.Digester.endElement(Digester.java:1225)
> at
> org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
> at
> org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown
> Source)
> at
> org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown
> Source)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndE
> lement(Unk
> nown Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$Fragment
> ContentDis
> patcher.dispatch(Unknown Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocu
> ment(Unkno
> wn Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
> Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> Source)
> at
> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unkno
> wn Source)
> at
> org.apache.commons.digester.Digester.parse(Digester.java:1745)
> at
> org.apache.catalina.startup.ContextConfig.defaultConfig(Contex
> tConfig.ja
> va:488)
> at
> org.apache.catalina.startup.ContextConfig.start(ContextConfig.
> java:579)
> at
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(Conte
> xtConfig.j
> ava:182)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L
> ifecycleSu
> pport.java:120)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext
> .java:3644
> )
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(Contai
> nerBase.ja
> va:777)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.
> java:760)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
> at
> org.apache.catalina.core.StandardHostDeployer.install(Standard
> HostDeploy
> er.java:261)
> at
> org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:559)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:374)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:785)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConf
> ig.java:33
> 1)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L
> ifecycleSu
> pport.java:120)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1156)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
> at
> org.apache.catalina.core.StandardService.start(StandardService
> .java:450)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.j
> ava:2213)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:459)
> at
> org.apache.catalina.startup.Catalina.execute(Catalina.java:346)
> at
> org.apache.catalina.startup.Catalina.process(Catalina.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
>
> 2007-08-16 13:35:09 ContextConfig[/axis2]: Occurred at line 324 column
> 46
> 2007-08-16 13:35:09 ContextConfig[/axis2]: Marking this application
> unavailable due to previous error(s)
> 2007-08-16 13:35:09 StandardManager[/axis2]: Seeding random number
> generator class java.security.SecureRandom
> 2007-08-16 13:35:09 StandardManager[/axis2]: Seeding of random number
> generator has been completed
> 2007-08-16 13:35:09 StandardContext[/axis2]: Context startup
> failed due
> to previous errors
> 2007-08-16 13:35:09 StandardHost[localhost]: ContainerBase.addChild:
> start:
> LifecycleException: Context startup failed due to previous errors
> at
> org.apache.catalina.core.StandardContext.start(StandardContext
> .java:3701
> )
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(Contai
> nerBase.ja
> va:777)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.
> java:760)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
> at
> org.apache.catalina.core.StandardHostDeployer.install(Standard
> HostDeploy
> er.java:261)
> at
> org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:559)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:374)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:785)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConf
> ig.java:33
> 1)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L
> ifecycleSu
> pport.java:120)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1156)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
> at
> org.apache.catalina.core.StandardService.start(StandardService
> .java:450)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.j
> ava:2213)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:459)
> at
> org.apache.catalina.startup.Catalina.execute(Catalina.java:346)
> at
> org.apache.catalina.startup.Catalina.process(Catalina.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
> orImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable.
Posted by "Du, David (US SSA)" <da...@baesystems.com>.
Hi, I tried the new axis2-1.3 release, I got the following error after
copied axis2.war file into my tomcat4.1.36, the axis2-1.2 worked before,
but not the 1.3 release; it happened to tomcat5.5.23 as well. I checked
the commons-logging-1.1.jar file, it exists under directory:
C:\apache-tomcat-4.1.36\webapps\axis2\WEB-INF\lib.
2007-08-16 13:35:09 ContextConfig[/axis2] Parse error in default web.xml
org.apache.commons.logging.LogConfigurationException: User-specified log
class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or
is not useable.
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:31
81)
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:32
07)
at
org.apache.commons.digester.Digester.endElement(Digester.java:1225)
at
org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at
org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown
Source)
at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unk
nown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at
org.apache.commons.digester.Digester.parse(Digester.java:1745)
at
org.apache.catalina.startup.ContextConfig.defaultConfig(ContextConfig.ja
va:488)
at
org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:579)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.j
ava:182)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu
pport.java:120)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3644
)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja
va:777)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:760)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeploy
er.java:261)
at
org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:559)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:374)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:785)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:33
1)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu
pport.java:120)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1156)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
at
org.apache.catalina.core.StandardService.start(StandardService.java:450)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
at org.apache.catalina.startup.Catalina.start(Catalina.java:459)
at
org.apache.catalina.startup.Catalina.execute(Catalina.java:346)
at
org.apache.catalina.startup.Catalina.process(Catalina.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
2007-08-16 13:35:09 ContextConfig[/axis2]: Occurred at line 324 column
46
2007-08-16 13:35:09 ContextConfig[/axis2]: Marking this application
unavailable due to previous error(s)
2007-08-16 13:35:09 StandardManager[/axis2]: Seeding random number
generator class java.security.SecureRandom
2007-08-16 13:35:09 StandardManager[/axis2]: Seeding of random number
generator has been completed
2007-08-16 13:35:09 StandardContext[/axis2]: Context startup failed due
to previous errors
2007-08-16 13:35:09 StandardHost[localhost]: ContainerBase.addChild:
start:
LifecycleException: Context startup failed due to previous errors
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3701
)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja
va:777)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:760)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeploy
er.java:261)
at
org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:559)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:374)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:785)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:33
1)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu
pport.java:120)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1156)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
at
org.apache.catalina.core.StandardService.start(StandardService.java:450)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
at org.apache.catalina.startup.Catalina.start(Catalina.java:459)
at
org.apache.catalina.startup.Catalina.execute(Catalina.java:346)
at
org.apache.catalina.startup.Catalina.process(Catalina.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
[axis2] StandAlone consumer.
Posted by "Hernandez Morales V, Carlos Alberto" <ca...@intercall.com>.
Hello Guys,
First of all, thank you for your help.
I'm trying to create a WebStart application that can upload and download
files to an Axis 2 enabled WebApp. I thought that WebServices will be
great since it is going to be deployed over the internet.
I'm reading the wiki page about the SimpleAxisServer... does any of you
have any example code that I can use to help me in my research? Is the
SimpleAxisServer the correct way to do that?
Thank you again I really appreciate your help.
Carlos Alberto (Newbie :P)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by New AxisU <ne...@gmail.com>.
We are using jdk 1.5 & planning to move to 1.6
On 8/15/07, Pantvaidya, Vishwajit <vp...@selectica.com> wrote:
> I agree - adding support for 1.5 while retaining compatibility with 1.4
> (essentially not to use features of 1.5) is probably the best option.
>
>
> - Vish.
>
> >-----Original Message-----
> >From: Bjorn Townsend [mailto:bjorn@sourcelabs.com]
> >Sent: Wednesday, August 15, 2007 2:54 PM
> >To: axis-user@ws.apache.org
> >Cc: Axis-Dev
> >Subject: Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
> >
> >Hi Glen,
> >
> >I wanted to throw my two cents in on this as it's an important issue.
> >In short, I think Axis2 should continue to support both, especially
> >if it wants to encourage stragglers to migrate from 1.x. Most of
> >Sourcelabs' customers are inherently conservative Global 2000
> >companies, most of them use Axis 1.x in one form or another, and none
> >of them have completely migrated to 1.5. The reasons for this are
> >generally the result of company policy -- internal standards and the
> >desire to minimize upgrades being prominent reasons for said policy.
> >The process of moving to 1.5 for them will be a long and painful one,
> >and they are much more likely to be interested in or need to migrate
> >to Axis2 before upgrading to Java 1.5. Our customers would find
> >migrating to Axis2 much more palatable if they didn't need to upgrade
> >to Java 1.5 at the same time. I suspect the same is probably true of
> >many users of Axis in the enterprise.
> >
> >Thanks,
> >Bjorn
> >
> >On Aug 14, 2007, at 9:25 PM August 14, Glen Daniels wrote:
> >
> >> Hi Axis2 developers and users!
> >>
> >> There has been a bunch of discussion lately revolving around the
> >> question of JDK1.4 compatibility. It has been suggested that Axis2
> >> move to JDK 1.5, in order to gain the benefits of things like
> >> generics, built-in concurrency (no backport lib), and annotations.
> >> Some folks feel that there are enough people out there still in a
> >> 1.4 environment that we should hold off, and others think we should
> >> bite the bullet and move to 1.5.
> >>
> >> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
> >>
> >> Are you using, or planning to use, Axis2 in an environment that is
> >> locked to JDK 1.4? If so, please let us know by responding to this
> >> thread and telling us (if you can) about the particulars of what's
> >> tying you to 1.4 - is it your app server? Company policy?
> >> Something else?
> >>
> >> We'd really like to take good care of our users, and doing that
> >> involves figuring out whether we can jump into 1.5-land or if we
> >> need to keep things working with 1.4.
> >>
> >> Thanks,
> >> --Glen
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by "Pantvaidya, Vishwajit" <vp...@selectica.com>.
I agree - adding support for 1.5 while retaining compatibility with 1.4 (essentially not to use features of 1.5) is probably the best option.
- Vish.
>-----Original Message-----
>From: Bjorn Townsend [mailto:bjorn@sourcelabs.com]
>Sent: Wednesday, August 15, 2007 2:54 PM
>To: axis-user@ws.apache.org
>Cc: Axis-Dev
>Subject: Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
>
>Hi Glen,
>
>I wanted to throw my two cents in on this as it's an important issue.
>In short, I think Axis2 should continue to support both, especially
>if it wants to encourage stragglers to migrate from 1.x. Most of
>Sourcelabs' customers are inherently conservative Global 2000
>companies, most of them use Axis 1.x in one form or another, and none
>of them have completely migrated to 1.5. The reasons for this are
>generally the result of company policy -- internal standards and the
>desire to minimize upgrades being prominent reasons for said policy.
>The process of moving to 1.5 for them will be a long and painful one,
>and they are much more likely to be interested in or need to migrate
>to Axis2 before upgrading to Java 1.5. Our customers would find
>migrating to Axis2 much more palatable if they didn't need to upgrade
>to Java 1.5 at the same time. I suspect the same is probably true of
>many users of Axis in the enterprise.
>
>Thanks,
>Bjorn
>
>On Aug 14, 2007, at 9:25 PM August 14, Glen Daniels wrote:
>
>> Hi Axis2 developers and users!
>>
>> There has been a bunch of discussion lately revolving around the
>> question of JDK1.4 compatibility. It has been suggested that Axis2
>> move to JDK 1.5, in order to gain the benefits of things like
>> generics, built-in concurrency (no backport lib), and annotations.
>> Some folks feel that there are enough people out there still in a
>> 1.4 environment that we should hold off, and others think we should
>> bite the bullet and move to 1.5.
>>
>> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>>
>> Are you using, or planning to use, Axis2 in an environment that is
>> locked to JDK 1.4? If so, please let us know by responding to this
>> thread and telling us (if you can) about the particulars of what's
>> tying you to 1.4 - is it your app server? Company policy?
>> Something else?
>>
>> We'd really like to take good care of our users, and doing that
>> involves figuring out whether we can jump into 1.5-land or if we
>> need to keep things working with 1.4.
>>
>> Thanks,
>> --Glen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by Ciaran Dunn <ci...@gmail.com>.
Hello,
I'd like to throw my few cents(inflation) behind Bjorns email. My
Axis background is as an contracted architect and developer in the
European financial(mainly the UK) sector. As someone "in the
trenches" you find for many reasons it is impractical or impossible
to force organisations to haphazardly upgrade legacy systems to 1.5.
In fact I've worked in places where even older JREs still had a
presence :) I think forcing a 1.5 path would simply make many
dismiss Axis out of hand and that would be a great shame. For many
organisations the act of upgrading the JRE is often highly dependent
on competing upgrade choices such as the OS(ie the current version of
solaris ships with JRE whatever and we are required to use that as it
is company policy) or application servers being approved by security
etc. In my experience the lag of 1.4 has a lot to do with simple
business requirements(security is a big one... many enterprises go
thru long and costly security evaluations for things such as app
servers and dont like to do them terribly often) and budget concerns
(ie "Wed love to upgrade to 1.5 but we don't have the resources right
now")
Hope that helps.
Cheers,
Ciaran
On 15 Aug 2007, at 22:54, Bjorn Townsend wrote:
> Hi Glen,
>
> I wanted to throw my two cents in on this as it's an important
> issue. In short, I think Axis2 should continue to support both,
> especially if it wants to encourage stragglers to migrate from 1.x.
> Most of Sourcelabs' customers are inherently conservative Global
> 2000 companies, most of them use Axis 1.x in one form or another,
> and none of them have completely migrated to 1.5. The reasons for
> this are generally the result of company policy -- internal
> standards and the desire to minimize upgrades being prominent
> reasons for said policy. The process of moving to 1.5 for them
> will be a long and painful one, and they are much more likely to be
> interested in or need to migrate to Axis2 before upgrading to Java
> 1.5. Our customers would find migrating to Axis2 much more
> palatable if they didn't need to upgrade to Java 1.5 at the same
> time. I suspect the same is probably true of many users of Axis in
> the enterprise.
>
> Thanks,
> Bjorn
>
> On Aug 14, 2007, at 9:25 PM August 14, Glen Daniels wrote:
>
>> Hi Axis2 developers and users!
>>
>> There has been a bunch of discussion lately revolving around the
>> question of JDK1.4 compatibility. It has been suggested that
>> Axis2 move to JDK 1.5, in order to gain the benefits of things
>> like generics, built-in concurrency (no backport lib), and
>> annotations. Some folks feel that there are enough people out
>> there still in a 1.4 environment that we should hold off, and
>> others think we should bite the bullet and move to 1.5.
>>
>> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>>
>> Are you using, or planning to use, Axis2 in an environment that is
>> locked to JDK 1.4? If so, please let us know by responding to
>> this thread and telling us (if you can) about the particulars of
>> what's tying you to 1.4 - is it your app server? Company policy?
>> Something else?
>>
>> We'd really like to take good care of our users, and doing that
>> involves figuring out whether we can jump into 1.5-land or if we
>> need to keep things working with 1.4.
>>
>> Thanks,
>> --Glen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by Bjorn Townsend <bj...@sourcelabs.com>.
Hi Glen,
I wanted to throw my two cents in on this as it's an important issue.
In short, I think Axis2 should continue to support both, especially
if it wants to encourage stragglers to migrate from 1.x. Most of
Sourcelabs' customers are inherently conservative Global 2000
companies, most of them use Axis 1.x in one form or another, and none
of them have completely migrated to 1.5. The reasons for this are
generally the result of company policy -- internal standards and the
desire to minimize upgrades being prominent reasons for said policy.
The process of moving to 1.5 for them will be a long and painful one,
and they are much more likely to be interested in or need to migrate
to Axis2 before upgrading to Java 1.5. Our customers would find
migrating to Axis2 much more palatable if they didn't need to upgrade
to Java 1.5 at the same time. I suspect the same is probably true of
many users of Axis in the enterprise.
Thanks,
Bjorn
On Aug 14, 2007, at 9:25 PM August 14, Glen Daniels wrote:
> Hi Axis2 developers and users!
>
> There has been a bunch of discussion lately revolving around the
> question of JDK1.4 compatibility. It has been suggested that Axis2
> move to JDK 1.5, in order to gain the benefits of things like
> generics, built-in concurrency (no backport lib), and annotations.
> Some folks feel that there are enough people out there still in a
> 1.4 environment that we should hold off, and others think we should
> bite the bullet and move to 1.5.
>
> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>
> Are you using, or planning to use, Axis2 in an environment that is
> locked to JDK 1.4? If so, please let us know by responding to this
> thread and telling us (if you can) about the particulars of what's
> tying you to 1.4 - is it your app server? Company policy?
> Something else?
>
> We'd really like to take good care of our users, and doing that
> involves figuring out whether we can jump into 1.5-land or if we
> need to keep things working with 1.4.
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by david <da...@davidwbrown.name>.
Hello Alberto, I was working a gig at an insurance company when they upgraded from the WASD 6.1 to the Websphere so-called RAD7. This in my estimation was their best move because the Websphere RAD7 is 100% Eclipse based The only caveat is the Eclipse comes with every possible plugin including the Rational UML graphics plugin. HTH, David.
Alberto Patino wrote ..
> In our project, I strongly recommended the use of axis2, fortunately,
> this projects is totally new, the only concern I had was considering
> the use of WebSphere, corporative rules demand the use of WAS as our
> corporate Application Server, So I was very clear asting for the 6.1
> release but people is reluctant with websphere 6.1 because the main
> reason is that they don't have enough expertise with the newest
> release, if I were locked with websphere 6.0 or minor I might not use
> axis2 with java5 cause Webshere 6.0 depends on java 1.4.
>
> In the other hand if Axis2 were rewritten with java5 in mind, this
> would be an excellent excuse to adopt the use of WAS 6.1 or change it
> for another Application Server ;-)
>
>
>
> On 8/14/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> > Hi Axis2 developers and users!
> >
> > There has been a bunch of discussion lately revolving around the
> > question of JDK1.4 compatibility. It has been suggested that Axis2 move
> > to JDK 1.5, in order to gain the benefits of things like generics,
> > built-in concurrency (no backport lib), and annotations. Some folks
> > feel that there are enough people out there still in a 1.4 environment
> > that we should hold off, and others think we should bite the bullet and
> > move to 1.5.
> >
> > HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
> >
> > Are you using, or planning to use, Axis2 in an environment that is
> > locked to JDK 1.4? If so, please let us know by responding to this
> > thread and telling us (if you can) about the particulars of what's tying
> > you to 1.4 - is it your app server? Company policy? Something else?
> >
> > We'd really like to take good care of our users, and doing that involves
> > figuring out whether we can jump into 1.5-land or if we need to keep
> > things working with 1.4.
> >
> > Thanks,
> > --Glen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> Don't be evil!!!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by Alberto Patino <pa...@gmail.com>.
In our project, I strongly recommended the use of axis2, fortunately,
this projects is totally new, the only concern I had was considering
the use of WebSphere, corporative rules demand the use of WAS as our
corporate Application Server, So I was very clear asting for the 6.1
release but people is reluctant with websphere 6.1 because the main
reason is that they don't have enough expertise with the newest
release, if I were locked with websphere 6.0 or minor I might not use
axis2 with java5 cause Webshere 6.0 depends on java 1.4.
In the other hand if Axis2 were rewritten with java5 in mind, this
would be an excellent excuse to adopt the use of WAS 6.1 or change it
for another Application Server ;-)
On 8/14/07, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi Axis2 developers and users!
>
> There has been a bunch of discussion lately revolving around the
> question of JDK1.4 compatibility. It has been suggested that Axis2 move
> to JDK 1.5, in order to gain the benefits of things like generics,
> built-in concurrency (no backport lib), and annotations. Some folks
> feel that there are enough people out there still in a 1.4 environment
> that we should hold off, and others think we should bite the bullet and
> move to 1.5.
>
> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>
> Are you using, or planning to use, Axis2 in an environment that is
> locked to JDK 1.4? If so, please let us know by responding to this
> thread and telling us (if you can) about the particulars of what's tying
> you to 1.4 - is it your app server? Company policy? Something else?
>
> We'd really like to take good care of our users, and doing that involves
> figuring out whether we can jump into 1.5-land or if we need to keep
> things working with 1.4.
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Don't be evil!!!
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by Bjorn Townsend <bj...@sourcelabs.com>.
Hi Glen,
I wanted to throw my two cents in on this as it's an important issue.
In short, I think Axis2 should continue to support both, especially
if it wants to encourage stragglers to migrate from 1.x. Most of
Sourcelabs' customers are inherently conservative Global 2000
companies, most of them use Axis 1.x in one form or another, and none
of them have completely migrated to 1.5. The reasons for this are
generally the result of company policy -- internal standards and the
desire to minimize upgrades being prominent reasons for said policy.
The process of moving to 1.5 for them will be a long and painful one,
and they are much more likely to be interested in or need to migrate
to Axis2 before upgrading to Java 1.5. Our customers would find
migrating to Axis2 much more palatable if they didn't need to upgrade
to Java 1.5 at the same time. I suspect the same is probably true of
many users of Axis in the enterprise.
Thanks,
Bjorn
On Aug 14, 2007, at 9:25 PM August 14, Glen Daniels wrote:
> Hi Axis2 developers and users!
>
> There has been a bunch of discussion lately revolving around the
> question of JDK1.4 compatibility. It has been suggested that Axis2
> move to JDK 1.5, in order to gain the benefits of things like
> generics, built-in concurrency (no backport lib), and annotations.
> Some folks feel that there are enough people out there still in a
> 1.4 environment that we should hold off, and others think we should
> bite the bullet and move to 1.5.
>
> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>
> Are you using, or planning to use, Axis2 in an environment that is
> locked to JDK 1.4? If so, please let us know by responding to this
> thread and telling us (if you can) about the particulars of what's
> tying you to 1.4 - is it your app server? Company policy?
> Something else?
>
> We'd really like to take good care of our users, and doing that
> involves figuring out whether we can jump into 1.5-land or if we
> need to keep things working with 1.4.
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by George Stanchev <Gs...@serena.com>.
Hi Glen,
As as committer on another open source project that uses axis2 as a
dependency,
I second the vote to keep 1.4 compatibility. A lot of older, bigger
organizations keep
older JVMs for the reasons already stated by others. If you switch axis2
1.4 and above to JVM 1.5,
you will loose a lot of adopters, especially in the bigger enterprises
which will be
forced to stick to older releases for JVM compatibility issues. Give it
another year and
ask the same question again :-)
Best Regards,
George
-----Original Message-----
From: Glen Daniels [mailto:glen@thoughtcraft.com]
Sent: Tuesday, August 14, 2007 10:26 PM
To: Axis-Dev; axis-user@ws.apache.org
Subject: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Importance: High
Hi Axis2 developers and users!
There has been a bunch of discussion lately revolving around the
question of JDK1.4 compatibility. It has been suggested that Axis2 move
to JDK 1.5, in order to gain the benefits of things like generics,
built-in concurrency (no backport lib), and annotations. Some folks
feel that there are enough people out there still in a 1.4 environment
that we should hold off, and others think we should bite the bullet and
move to 1.5.
HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
Are you using, or planning to use, Axis2 in an environment that is
locked to JDK 1.4? If so, please let us know by responding to this
thread and telling us (if you can) about the particulars of what's tying
you to 1.4 - is it your app server? Company policy? Something else?
We'd really like to take good care of our users, and doing that involves
figuring out whether we can jump into 1.5-land or if we need to keep
things working with 1.4.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by Franz Fehringer <fe...@isogmbh.de>.
Hello all,
I vote for abandoning Java 1.4 support, i.e. go for Java 1.5
Cheers
Franz
david schrieb:
> Hello Glen, I am currently working a gig @ a financial outfit. We are running axis1.4 and axis2 WSs under JDK6, 5 and 1.4. Nobody said we couldn't. This mix of JDKs is strictly on the development machines. The production version of our work is running supposedly under JDK1.4. I have always upgraded the JDK when possible. Staying so-called stuck in one environment would remind me of using somethng like: .NET. I vote: go-for-it! HAG1, David.
>
> Glen Daniels wrote ..
>
>> Hi Axis2 developers and users!
>>
>> There has been a bunch of discussion lately revolving around the
>> question of JDK1.4 compatibility. It has been suggested that Axis2 move
>> to JDK 1.5, in order to gain the benefits of things like generics,
>> built-in concurrency (no backport lib), and annotations. Some folks
>> feel that there are enough people out there still in a 1.4 environment
>> that we should hold off, and others think we should bite the bullet and
>> move to 1.5.
>>
>> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>>
>> Are you using, or planning to use, Axis2 in an environment that is
>> locked to JDK 1.4? If so, please let us know by responding to this
>> thread and telling us (if you can) about the particulars of what's tying
>> you to 1.4 - is it your app server? Company policy? Something else?
>>
>> We'd really like to take good care of our users, and doing that involves
>> figuring out whether we can jump into 1.5-land or if we need to keep
>> things working with 1.4.
>>
>> Thanks,
>> --Glen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Dr. Franz Fehringer (Dipl. Math.)
Projektleiter Touristik-Systeme
____________________________________
ISO Software Systeme GmbH
Eichendorffstrasse 29
90491 Nürnberg
Germany
Tel.: +49/(911) - 99594-0
mailto:Franz.Fehringer@isogmbh.de
http://www.isogmbh.de
Amtsgericht Nürnberg HRB 18299
Geschäftsführer: Dipl.-Inform., Dipl.-Kaufm. Harald Goeb
Sitz: Nürnberg
Re: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by david <da...@davidwbrown.name>.
Hello Glen, I am currently working a gig @ a financial outfit. We are running axis1.4 and axis2 WSs under JDK6, 5 and 1.4. Nobody said we couldn't. This mix of JDKs is strictly on the development machines. The production version of our work is running supposedly under JDK1.4. I have always upgraded the JDK when possible. Staying so-called stuck in one environment would remind me of using somethng like: .NET. I vote: go-for-it! HAG1, David.
Glen Daniels wrote ..
> Hi Axis2 developers and users!
>
> There has been a bunch of discussion lately revolving around the
> question of JDK1.4 compatibility. It has been suggested that Axis2 move
> to JDK 1.5, in order to gain the benefits of things like generics,
> built-in concurrency (no backport lib), and annotations. Some folks
> feel that there are enough people out there still in a 1.4 environment
> that we should hold off, and others think we should bite the bullet and
> move to 1.5.
>
> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>
> Are you using, or planning to use, Axis2 in an environment that is
> locked to JDK 1.4? If so, please let us know by responding to this
> thread and telling us (if you can) about the particulars of what's tying
> you to 1.4 - is it your app server? Company policy? Something else?
>
> We'd really like to take good care of our users, and doing that involves
> figuring out whether we can jump into 1.5-land or if we need to keep
> things working with 1.4.
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by Mi...@servicecanada.gc.ca.
Hi all,
I'm working on contract for the Canadian government, developing web apps (and now web services) for their intranet. There is a different department that provides the hosting services. They're currently on WebSphere 5.1 and jdk 1.4. They do feel the pressure to upgrade to WS 6.1 and jdk 1.5, but they're slow as molasses to get anything done, so I fear we'll be stuck with 1.4 for perhaps a year.
However, I don't mind sticking with the current version of Axis2 for now. It works fine for me. If Axis2 1.4 abandons jdk1.4, it will give me another tool with which to prod and poke that other department.
So I'll abstain - I'd personally like to see it move to 1.5 but I understand others might be in a worse situation than mine.
cheers,
md
> -----Original Message-----
> From: Glen Daniels [mailto:glen@thoughtcraft.com]
> Sent: Wednesday, August 15, 2007 12:26 AM
> To: Axis-Dev; axis-user@ws.apache.org
> Subject: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback
> requested
> Importance: High
>
>
> Hi Axis2 developers and users!
>
> There has been a bunch of discussion lately revolving around the
> question of JDK1.4 compatibility. It has been suggested that
> Axis2 move
> to JDK 1.5, in order to gain the benefits of things like generics,
> built-in concurrency (no backport lib), and annotations. Some folks
> feel that there are enough people out there still in a 1.4
> environment
> that we should hold off, and others think we should bite the
> bullet and
> move to 1.5.
>
> HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
>
> Are you using, or planning to use, Axis2 in an environment that is
> locked to JDK 1.4? If so, please let us know by responding to this
> thread and telling us (if you can) about the particulars of
> what's tying
> you to 1.4 - is it your app server? Company policy? Something else?
>
> We'd really like to take good care of our users, and doing
> that involves
> figuring out whether we can jump into 1.5-land or if we need to keep
> things working with 1.4.
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Posted by George Stanchev <Gs...@serena.com>.
Hi Glen,
As as committer on another open source project that uses axis2 as a
dependency,
I second the vote to keep 1.4 compatibility. A lot of older, bigger
organizations keep
older JVMs for the reasons already stated by others. If you switch axis2
1.4 and above to JVM 1.5,
you will loose a lot of adopters, especially in the bigger enterprises
which will be
forced to stick to older releases for JVM compatibility issues. Give it
another year and
ask the same question again :-)
Best Regards,
George
-----Original Message-----
From: Glen Daniels [mailto:glen@thoughtcraft.com]
Sent: Tuesday, August 14, 2007 10:26 PM
To: Axis-Dev; axis-user@ws.apache.org
Subject: [axis2] [IMPORTANT] JDK 1.4 compatibility - feedback requested
Importance: High
Hi Axis2 developers and users!
There has been a bunch of discussion lately revolving around the
question of JDK1.4 compatibility. It has been suggested that Axis2 move
to JDK 1.5, in order to gain the benefits of things like generics,
built-in concurrency (no backport lib), and annotations. Some folks
feel that there are enough people out there still in a 1.4 environment
that we should hold off, and others think we should bite the bullet and
move to 1.5.
HERE'S YOUR CHANCE TO PROVIDE VALUABLE INPUT!
Are you using, or planning to use, Axis2 in an environment that is
locked to JDK 1.4? If so, please let us know by responding to this
thread and telling us (if you can) about the particulars of what's tying
you to 1.4 - is it your app server? Company policy? Something else?
We'd really like to take good care of our users, and doing that involves
figuring out whether we can jump into 1.5-land or if we need to keep
things working with 1.4.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org