[
https://jira.jboss.org/jira/browse/JBIDE-4608?page=com.atlassian.jira.plu...
]
Alexander Lengson commented on JBIDE-4608:
------------------------------------------
Rob,
For the case when project itself is deployed onto server, this really works well when
descriptors exist.
Making Full Publish causes server to redeploy new EJB.
Thank you for the clarification, I'm going to insert this solution into forum.
Hopefully it'll help somebody to google it.
It does seem that there's a runtime issue in the core App Server
where it's hard to restart a module without a descriptor. One would expect that since
there's no descriptor, simply touching the ear or ejb folder would restart the module,
but a simple test shows this is not the case.
Yep.
For the archives - I make absolutely the same until '- It publishes', because in
my environment it simply does not.
No archive appears in deploy folder, and unit test does not work.
However, on the neighbor's machine archives on the same project *works* pretty well,
so I am stuck here because I have all the fresh installations. No errors appear in Error
Log when I do publish. This may be either issue of my environment, or plugin's working
flow - don't know.
Since archives work on another machine, I would not insist on further investigations, just
in case you'are curios about it I may provide some additional info.
Thanks.
Hot deployment woks incorrectly with JBossAS Tools
--------------------------------------------------
Key: JBIDE-4608
URL:
https://jira.jboss.org/jira/browse/JBIDE-4608
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.1.GA
Environment: Windows XP SP3
Eclipse 3.5: eclipse-jee-galileo-win32.zip
JBossTools : 3.0.1.GA JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18.zip
JBoss AS: 5.0.1.GA
Reporter: Alexander Lengson
Assignee: Rob Stryker
Fix For: 3.0.2.GA
Attachments: clear-prj.zip
Original Estimate: 3 days
Remaining Estimate: 3 days
Hot deployment does not work as expected with the above configuration.
* Two eclipse projects are created: one EJB Project containing single EJB, and one EAR
project containing that EJB.
* EAR Project is deployed to JBoss thru JBoss Server View.
* JBoss started and recognized EJB:
clear-ear/EJB01/remote - EJB3.x Default Remote Business Interface
clear-ear/EJB01/remote-EJBRem - EJB3.x Remote Business Interface
* When source code of EJB is changed, it is recompiled and "Republish" note
appeared
* After pressing "Full publish" code is actually copied to the deploy folder on
the server (byte code is verified manually), but JBoss does not detect hot deployment and
does not redeploy EJB
When trying to make deployment thru Project Archives View on the same configuration, the
following happening:
* Archives are created within eclipse project folder.
* After pressing "Publish to Server" in Project Archives View, item appears in
JBoss Server View, but archive is not copied into JBoss deploy folder and JBoss does not
detect that new EJB is deployed.
JBoss' properties are:
Use the JBoss deploy folder
Tested on two separate machines. Results are the same.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira