Anyone using axis 1.2.1 (latest) with BES 6.01?
Currently, BES 6.01 is using axis 1.1 and we are facing some performance
problem with axis servlet. We wanted to upgrade to the latest and wanted to
know if the latest axis will work on BES 6.01
Appreciate your comments.
Rgds,
S.Srinivas
> Anyone using axis 1.2.1 (latest) with BES 6.01?
>
> Currently, BES 6.01 is using axis 1.1 and we are facing some
> performance problem with axis servlet. We wanted to upgrade to the
> latest and wanted to know if the latest axis will work on BES 6.01
There should be no problem using any version of Axis in your
application as long as it's packaged in your WAR file (I use that model
myself quite successfully with Axis 1.2).
I would also recommend that you upgrade to BES 6.5 if possible as it
includes a number of performance enhancements and bug fixes over
version 6.0.
--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/
NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html
Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html
Rgds,
S.Srinivas
"Kevin Dean [TeamB]" <NkOdS...@datadevelopment.com> wrote in message
news:xn0e66e324k...@www.teamb.com...
We tried Axis 1.2.1 and Xerces 2.7.1 on Borland Enterprise Server 6.0 and
6.5.
I could not even start the parition with the latest xercesImpl.jar file. But
I can start the partition with Axis 1.2.1 and the original xercesImpl.jar
file that borland provides.
Below is the error:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/w3c/dom/DOMError
at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
at
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown
Source)
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:656)
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616)
at
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:602)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.
java:460)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
at
org.apache.log4j.xml.XMLWatchdog.doOnChange(DOMConfigurator.java:815)
at
org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:80
)
at
org.apache.log4j.helpers.FileWatchdog.<init>(FileWatchdog.java:49)
at org.apache.log4j.xml.XMLWatchdog.<init>(DOMConfigurator.java:807)
at
org.apache.log4j.xml.DOMConfigurator.configureAndWatch(DOMConfigurator.java:
574)
at
com.borland.enterprise.server.Partition.initializeLog4j(Partition.java:609)
at com.borland.enterprise.server.Partition.main(Partition.java:141)
Any idea?
Rgds,
S.Srinivas
"Srinivas Sampathkumar" <srin...@ibatech.com> wrote in message
news:11245408...@unicorn.iba.com.sg...
> We tried Axis 1.2.1 and Xerces 2.7.1 on Borland Enterprise Server 6.0
> and 6.5.
> I could not even start the parition with the latest xercesImpl.jar
> file. But I can start the partition with Axis 1.2.1 and the original
> xercesImpl.jar file that borland provides.
I personally stick with the xercesImpl provided with the Application
Server; I've never had a compelling reason to upgrade it. Is the
DOMError class in your version of xercesImpl.jar?