|
I'd suggest something a little less radical
first... go into the orion-ejb-jar.xml file in your deployment directory and
make sure that your updates were reflected there. In particular, make sure
that Orion not only added what you did, but that it removed what you did.
Orion seems to, thankfully, be pretty conservative about changing the deployed
descriptors. If you don't have anything in there that you care about
(custom mappings, finders, whatever...), then you could just nuke that file,
touch the orion-application.xml to redeploy, and you should be
golden.
Rian
----- Original Message -----
Sent: Friday, March 30, 2001 6:46
AM
Subject: Re: Hot deployment not so
hot
When we had similar problems
we would remove the application from the application directory, the ear and
the files from the applications-deployment directory. Make sure you stop
the server before doing this.
Jonathan Bricker
Lilly Research Labs
Java ATG
|
| Dan North <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
03/30/2001 06:13 AM
Please respond to Orion-Interest
|
To:
Orion-Interest
<[EMAIL PROTECTED]>
cc:
Subject: Hot deployment not so
hot |
Hi
all.
I've been having a number of problems with hot deployment ever
since I
started using orion, and I wondered if anyone could shed any
light?
Typically it happens when I change an interface rather than just
internal
bean logic or code: orion says it is redeploying
whatever-xyz.jar, but will
complain that:
- A cmp-field is missing
(that I have removed from both the bean and the
ejb-jar.xml)
- A method
doesn't exist (that I have just added to both the bean and the
remote
i/f)
- etc.
All the messages I get seem to come down to a conflict
between some cached
version of the bean and the new version. If I
shut down and restart orion,
all the problems go away and it deploys the
new version fine.
This hasn't been a problem during development, but
I'm concerned that I
might be doing something wrong, and obviously once
the system goes live I
can't just stop and restart the server when I
deploy changes, so what's the
Right Way to redeploy a session or entity
bean into a running server and
tell orion to forget everything it knew
about the previous version?
(I'm running 1.4.7 on Sun's jdk1.3 on
Windows 2000 if it makes any
difference.)
Thanks,
Dan/tastapod
--
Dan North
VP
Development - Cadrion Software Ltd - +44 (0)20 7440
9550
CONFIDENTIALITY
This e-mail and any attachments are
confidential
and may also be privileged. If you are not the named
recipient,
please notify the sender immediately and do not disclose
the
contents to another person, use it for any purpose, or store
or copy
the information in any
medium
|
