Vlad Vinogradsky wrote:
Do they work together?
Thanks,
Vlad
They work very well together on my laptop, running Suse Linux 7.1,
Kernel 2.4.0.
-Steve
--
Stephen Davidson
Java Consultant
Delphi Consultants, LLC
http://www.delphis.com
Phone: 214-696-6224 x208
At 06.21 22/09/2001, Vlad Vinogradsky wrote:
Do they work together?
Yes, we work daily with Sun's JDK 1.3.1_01 and Orion 1.5.2 on Windows 2000
machines (the latter not my choice...). We haven't met any particular
problem yet.
Sebastiano Pilla
E-TREE S.p.a. Via Fonderia 43 - 31100 Treviso
Vlad,
Its tough to get linux to work on a laptop, but we get Orion an Sun jdk1.3.1
working together on a Windows 98 laptop all of the time. Works fine.
I would have to say Sun jdk1.3.1 is better than the previous release on
windows systems.
There have been issues with the client and server
Ismael,
I had the same problem. The reason it occurs is because there is a jaxp.jar
in the jre/lib/ext directory of the IBM VM, which means this will be used as
standard by the VM (before the jaxp.jar in the orion directory). There must
be some version incompatibility between Orion and the IBM
I have checked this out and it does not seem to be
the problem. The orion-ejb-jar.xml file remains intact.
If I remove the deployment directory and do an
initial deployment, all data created while the server is up is readable. Any
data that already existed in the database is unreadable.
Simon,
Take a look at bug 512. Your map is defined in the orion-ejb-jar.xml file.
We have found the 1.5.2 will redeploy an ejb, and overwrite the
orion-ejb-jar.xml on a restart. This could be what's happening. Take a look
at the orion-ejb-jar.xml in the deployment directory.
Regards,
the
I had some problems after upgrading to 1.5.2. The app told me it upgraded
but it didn't. I wiped out the directory, installed orion fresh again
(1.4.5), did the upgrade again and it all worked fine.
Perhaps I had some file locked when I did the update, who knows.
-Original Message-
