Jeff -
I have had to go in and change the ejb-jar file in the atm app as I am looking at
using SapDB for
our database choice. Since SapDB requires object names to be 32 or less in length, I
had to make
these changes to ejb names in the atm ejb-jar file and re-deploy. I removed the
application from
the applications-deployments directory as well. I am using Orion 1.4.5 on Windows 2000
Server and
Professional and SapDB (most recent version). It picked up my changes with no problem.
I did not
however, change the class files themselves. Maybe there is an issue with that
aspect
Cheers
Ray
--- Jeff Schnitzer [EMAIL PROTECTED] wrote:
Has anyone else noticed that 1.4.5 seems to neglect changes made to the
ejb-jar? It unpacks the ear and deploys changed war files just fine,
and if I change the ejb-jar.xml, it will unpack the ejb jar. But if I
change only the ejb class files, Orion just upacks the ear and sits.
Even restarting the server doesn't help.
Since nobody else has mentioned it yet, I'm wondering if it's just me.
I can get 1.4.4 to work just fine, though, so I suspect not.
I am deploying by copying the new ear over the old one.
Jeff
__
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/
