The following comment has been added to this issue:

     Author: Florin Vancea
    Created: Fri, 28 Nov 2003 1:48 AM
       Body:
Sorry for being rather briefer than clearer :)

I mean that when starting, JBoss "deploys" that file. One can check for that file's 
deployment status using RMI or HTTP JMX methods (of course once _some_ of the services 
have started). 
When JBoss reports that jboss-service.xml is deployed, it means the server is fully 
operational (all services started, all existing EARs, WARs, SARs, RARs, ... are fully 
loaded).

In my scripts I fork-start the server, then wait blind for some seconds for the JMX 
services to start, then JMX-wait for the appropriate jboss-service.xml file, then I 
can do whatever needed on a fresh fully started server.

(OK, I lied a little, the above is valid for some Ant scripts I use. In Maven I take 
advantage of Cactus plugin, with some personal touch in the plugin.jelly and my own 
JMX-waiter, which is basically the same method).

Florin
---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBOSS-3


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPJBOSS-3
    Summary: jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in 
jboss plugin project.properties
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-jboss-plugin
   Fix Fors:
             1.4
   Versions:
             1.3

   Assignee: 
   Reporter: Dima Berastau

    Created: Tue, 1 Jul 2003 3:53 AM
    Updated: Fri, 28 Nov 2003 1:48 AM

Description:
default maven.jboss.jmx.url.deploy and maven.jboss.jmx.url.undeploy seem to be missing 
0 at the end (should read 'arg0=' rather than 'arg=', tested in jboss 3.2).


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to