[
http://jira.jboss.com/jira/browse/JBAS-5643?page=comments#action_12417750 ]
Ales Justin commented on JBAS-5643:
-----------------------------------
If you can open a new forum post on "Design of POJO Server" describing what
exactly you miss, and I'll look into it.
Just make sure you link that forum post to this issue.
MainDeployer MBean methods don't work in JBoss 5.0 Beta4
--------------------------------------------------------
Key: JBAS-5643
URL:
http://jira.jboss.com/jira/browse/JBAS-5643
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.0.Beta4
Environment: JDK 1.6.0_05, Windows XP64
Reporter: Wolfgang Knauf
Assigned To: Ales Justin
I know that the deployment was reworked, but I don't know which impacts this had on
the MainDeployer MBean. At least it seems to be quite non-functional
This is the state of the MainDeployer:
-operation "listDeployed" and others just return nothing
-"isDeployed (string)" works for a URL
"file:/C:/temp/jboss-5.0.0.Beta4/server/default/deploy/KuchenZutatNM.ear", but
not for
"vfs:/C:/temp/jboss-5.0.0.Beta4/server/default/deploy/KuchenZutatNM.ear"
-"undeploy" and others don't work for any of the above URLs, both result in
a console output "21:11:45,890 WARN [MainDeployer] undeploy
'file:/C:/temp/jboss-5.0.0.Beta4/server/default/deploy/KuchenZutatNM.ear' :
package not deployed"
I created a small plugin for Eclipse WTP which tries to undeploy a module and waits for
successful deployment of new modules, and this plugin does not work at all with JBoss 5.
Probably I need to change it to use the new deployers, but I didn't find a hint to
them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira