please document this one in bugzilla... it looks real enough
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Michael G. Drew
|Sent: Thursday, October 26, 2000 10:51 AM
|To: jBoss Mailing List
|Subject: [jBoss-User] Wierdness While Re-Deploying Beans
|
|
|Hi All,
|
| I ran into a weird one while re-depolying a set of beans. There was a
|problem in one of my deployment descriptors, so the original deploy
|failed. After I fixed my deployment descriptor (and some code), I
|tried to
|re-deploy the app by simply copying the jar over-top of the old one in the
|deploy directory. The AutoDeployer tried to deploy the beans, but it gave
|me the same error messages as before (which I knew could not be possible
|based on the changes I made). After shutting down jBoss and clearing out
|the tmp/deploy directory and restarting, everything was fine. Has anybody
|else seen this? Do I need to be sure to delete (undeploy) a broken jar
|before copying a newer version of the jar to the deploy?
|
|
|Michael G. Drew
|Kishwaukee College
|Interface Programmer
|[EMAIL PROTECTED]
|(815) 825-2086 ext. 595
|
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
