RE: [JBoss-dev] sar startup ordering

2002-06-03 Thread Per Nyfelt

I ended up creating my own Comparator since i want the non-numbered files to
deploy first using the rules of the DeploymentSorter and then deploy
according to their numbered prefix. In order to actually use is however, the
only way I found that worked was to add my class to jboss-system.jar,
otherwise i got a ClassNotFoundException (e.g. when jaring it up and putting
the jar in lib). Is this a bug or intended?

Best regards,
Per

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of
 lsanders
 Sent: Thursday, May 30, 2002 4:59 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] sar startup ordering


 This has been available since (I think) 3.0 RC2.  Take a look at
 the default
 jboss-service.xml file.   At the bottom in the Deployment
 Scanning section,
 look for an attribute named URLComparator.  The default comparator
 (DeploymentSorter) sorts by type in this order: *.sar, *service.xml, *rar,
 *jar, *war, *wsr, *ear, *zip, *.

 There is a second comparator (commented out) called
 PrefixDeploymentSorter.
 If you use this then all deployments that start with a numeric prefix will
 be deployed in order of those prefixes.  Non-prefixed deployments are
 deployed last.  Ties are broken using the sorting from DeploymentSorter
 above.

 If this is still not cutting it, then you are free to implement
 an instance
 of java.util.Comparator that is capable of comparing two URL objects.

 -Larry

 - Original Message -
 From: Per Nyfelt [EMAIL PROTECTED]
 To: Jboss-Development@Lists. Sourceforge. Net
 [EMAIL PROTECTED]
 Sent: Thursday, May 30, 2002 6:29 AM
 Subject: [JBoss-dev] sar startup ordering


  I've been trying to find what was decided for how to specify in
 what order
  sar archives should be loaded and started, but the mail discussions I've
  found points in many different directions. Could anyone please set me
  straight?
 
  I have a jxta.sar that i want to start before a ozone.sar
  From what i can see from testing the following works:
 
  1. Label them 10-jxta.sar and 20-ozone.sar
 
  2. keep the names but make sure the timestamp of the jxta.sar is earlier
  than the ozone.sar
 
  Is there any mechanism that allows this behaviour to be configured?
 
  Best regards,
  Per
 
 
  ___
 
  Don't miss the 2002 Sprint PCS Application Developer's Conference
  August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development




___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] sar startup ordering

2002-06-03 Thread Larry Sandereson

I set it up so non-numbered deployments deploy last.  It seemed that someone
who required that kind of control over ordering would only need it for the
first deployments.  Should I change it so that non-numbered deployments
deploy first?

-Larry

- Original Message -
From: marc fleury [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 03, 2002 5:49 AM
Subject: RE: [JBoss-dev] sar startup ordering


 This should be the default comparator, I have been saying it for about 4
 month,

 Main Deployer is part of the System,

 marcf

 PS: please patch HEAD with this,


 |-Original Message-
 |From: [EMAIL PROTECTED]
 |[mailto:[EMAIL PROTECTED]]On Behalf Of Per
 |Nyfelt
 |Sent: Monday, June 03, 2002 12:31 AM
 |To: [EMAIL PROTECTED]
 |Subject: RE: [JBoss-dev] sar startup ordering
 |
 |
 |I ended up creating my own Comparator since i want the
 |non-numbered files to
 |deploy first using the rules of the DeploymentSorter and then deploy
 |according to their numbered prefix. In order to actually use is
 |however, the
 |only way I found that worked was to add my class to jboss-system.jar,
 |otherwise i got a ClassNotFoundException (e.g. when jaring it up
 |and putting
 |the jar in lib). Is this a bug or intended?
 |
 |Best regards,
 |Per
 |
 | -Original Message-
 | From: [EMAIL PROTECTED]
 | [mailto:[EMAIL PROTECTED]]On Behalf Of
 | lsanders
 | Sent: Thursday, May 30, 2002 4:59 PM
 | To: [EMAIL PROTECTED]
 | Subject: Re: [JBoss-dev] sar startup ordering
 |
 |
 | This has been available since (I think) 3.0 RC2.  Take a look at
 | the default
 | jboss-service.xml file.   At the bottom in the Deployment
 | Scanning section,
 | look for an attribute named URLComparator.  The default comparator
 | (DeploymentSorter) sorts by type in this order: *.sar,
 |*service.xml, *rar,
 | *jar, *war, *wsr, *ear, *zip, *.
 |
 | There is a second comparator (commented out) called
 | PrefixDeploymentSorter.
 | If you use this then all deployments that start with a numeric
 |prefix will
 | be deployed in order of those prefixes.  Non-prefixed deployments are
 | deployed last.  Ties are broken using the sorting from DeploymentSorter
 | above.
 |
 | If this is still not cutting it, then you are free to implement
 | an instance
 | of java.util.Comparator that is capable of comparing two URL objects.
 |
 | -Larry
 |
 | - Original Message -
 | From: Per Nyfelt [EMAIL PROTECTED]
 | To: Jboss-Development@Lists. Sourceforge. Net
 | [EMAIL PROTECTED]
 | Sent: Thursday, May 30, 2002 6:29 AM
 | Subject: [JBoss-dev] sar startup ordering
 |
 |
 |  I've been trying to find what was decided for how to specify in
 | what order
 |  sar archives should be loaded and started, but the mail
 |discussions I've
 |  found points in many different directions. Could anyone please set me
 |  straight?
 | 
 |  I have a jxta.sar that i want to start before a ozone.sar
 |  From what i can see from testing the following works:
 | 
 |  1. Label them 10-jxta.sar and 20-ozone.sar
 | 
 |  2. keep the names but make sure the timestamp of the jxta.sar
 |is earlier
 |  than the ozone.sar
 | 
 |  Is there any mechanism that allows this behaviour to be configured?
 | 
 |  Best regards,
 |  Per
 | 
 | 
 |  ___
 | 
 |  Don't miss the 2002 Sprint PCS Application Developer's Conference
 |  August 25-28 in Las Vegas --
http://devcon.sprintpcs.com/adp/index.cfm
 | 
 |  ___
 |  Jboss-development mailing list
 |  [EMAIL PROTECTED]
 |  https://lists.sourceforge.net/lists/listinfo/jboss-development
 | 
 |
 |
 | ___
 |
 | Don't miss the 2002 Sprint PCS Application Developer's Conference
 | August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 |
 | ___
 | Jboss-development mailing list
 | [EMAIL PROTECTED]
 | https://lists.sourceforge.net/lists/listinfo/jboss-development
 |
 |
 |
 |
 |___
 |
 |Don't miss the 2002 Sprint PCS Application Developer's Conference
 |August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 |
 |___
 |Jboss-development mailing list
 |[EMAIL PROTECTED]
 |https://lists.sourceforge.net/lists/listinfo/jboss-development


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

Re: [JBoss-dev] sar startup ordering

2002-06-03 Thread Larry Sandereson

The best solution I have found is to use the classpath... / tag in your
default jboss-service.xml.  Certainly putting it in your jboss-system.jar
seems a bit extreme.

-Larry

- Original Message -
From: Per Nyfelt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 03, 2002 12:30 AM
Subject: RE: [JBoss-dev] sar startup ordering


 I ended up creating my own Comparator since i want the non-numbered files
to
 deploy first using the rules of the DeploymentSorter and then deploy
 according to their numbered prefix. In order to actually use is however,
the
 only way I found that worked was to add my class to jboss-system.jar,
 otherwise i got a ClassNotFoundException (e.g. when jaring it up and
putting
 the jar in lib). Is this a bug or intended?

 Best regards,
 Per

  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of
  lsanders
  Sent: Thursday, May 30, 2002 4:59 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] sar startup ordering
 
 
  This has been available since (I think) 3.0 RC2.  Take a look at
  the default
  jboss-service.xml file.   At the bottom in the Deployment
  Scanning section,
  look for an attribute named URLComparator.  The default comparator
  (DeploymentSorter) sorts by type in this order: *.sar, *service.xml,
*rar,
  *jar, *war, *wsr, *ear, *zip, *.
 
  There is a second comparator (commented out) called
  PrefixDeploymentSorter.
  If you use this then all deployments that start with a numeric prefix
will
  be deployed in order of those prefixes.  Non-prefixed deployments are
  deployed last.  Ties are broken using the sorting from DeploymentSorter
  above.
 
  If this is still not cutting it, then you are free to implement
  an instance
  of java.util.Comparator that is capable of comparing two URL objects.
 
  -Larry
 
  - Original Message -
  From: Per Nyfelt [EMAIL PROTECTED]
  To: Jboss-Development@Lists. Sourceforge. Net
  [EMAIL PROTECTED]
  Sent: Thursday, May 30, 2002 6:29 AM
  Subject: [JBoss-dev] sar startup ordering
 
 
   I've been trying to find what was decided for how to specify in
  what order
   sar archives should be loaded and started, but the mail discussions
I've
   found points in many different directions. Could anyone please set me
   straight?
  
   I have a jxta.sar that i want to start before a ozone.sar
   From what i can see from testing the following works:
  
   1. Label them 10-jxta.sar and 20-ozone.sar
  
   2. keep the names but make sure the timestamp of the jxta.sar is
earlier
   than the ozone.sar
  
   Is there any mechanism that allows this behaviour to be configured?
  
   Best regards,
   Per
  
  
   ___
  
   Don't miss the 2002 Sprint PCS Application Developer's Conference
   August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
  
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
  ___
 
  Don't miss the 2002 Sprint PCS Application Developer's Conference
  August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] sar startup ordering

2002-06-03 Thread marc fleury

Your applications depends on the system beind deployed so you better put
your numbered deployments at the end.

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Larry
|Sandereson
|Sent: Monday, June 03, 2002 8:25 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] sar startup ordering
|
|
|The best solution I have found is to use the classpath... / tag in your
|default jboss-service.xml.  Certainly putting it in your jboss-system.jar
|seems a bit extreme.
|
|-Larry
|
|- Original Message -
|From: Per Nyfelt [EMAIL PROTECTED]
|To: [EMAIL PROTECTED]
|Sent: Monday, June 03, 2002 12:30 AM
|Subject: RE: [JBoss-dev] sar startup ordering
|
|
| I ended up creating my own Comparator since i want the non-numbered files
|to
| deploy first using the rules of the DeploymentSorter and then deploy
| according to their numbered prefix. In order to actually use is however,
|the
| only way I found that worked was to add my class to jboss-system.jar,
| otherwise i got a ClassNotFoundException (e.g. when jaring it up and
|putting
| the jar in lib). Is this a bug or intended?
|
| Best regards,
| Per
|
|  -Original Message-
|  From: [EMAIL PROTECTED]
|  [mailto:[EMAIL PROTECTED]]On Behalf Of
|  lsanders
|  Sent: Thursday, May 30, 2002 4:59 PM
|  To: [EMAIL PROTECTED]
|  Subject: Re: [JBoss-dev] sar startup ordering
| 
| 
|  This has been available since (I think) 3.0 RC2.  Take a look at
|  the default
|  jboss-service.xml file.   At the bottom in the Deployment
|  Scanning section,
|  look for an attribute named URLComparator.  The default comparator
|  (DeploymentSorter) sorts by type in this order: *.sar, *service.xml,
|*rar,
|  *jar, *war, *wsr, *ear, *zip, *.
| 
|  There is a second comparator (commented out) called
|  PrefixDeploymentSorter.
|  If you use this then all deployments that start with a numeric prefix
|will
|  be deployed in order of those prefixes.  Non-prefixed deployments are
|  deployed last.  Ties are broken using the sorting from DeploymentSorter
|  above.
| 
|  If this is still not cutting it, then you are free to implement
|  an instance
|  of java.util.Comparator that is capable of comparing two URL objects.
| 
|  -Larry
| 
|  - Original Message -
|  From: Per Nyfelt [EMAIL PROTECTED]
|  To: Jboss-Development@Lists. Sourceforge. Net
|  [EMAIL PROTECTED]
|  Sent: Thursday, May 30, 2002 6:29 AM
|  Subject: [JBoss-dev] sar startup ordering
| 
| 
|   I've been trying to find what was decided for how to specify in
|  what order
|   sar archives should be loaded and started, but the mail discussions
|I've
|   found points in many different directions. Could anyone please set me
|   straight?
|  
|   I have a jxta.sar that i want to start before a ozone.sar
|   From what i can see from testing the following works:
|  
|   1. Label them 10-jxta.sar and 20-ozone.sar
|  
|   2. keep the names but make sure the timestamp of the jxta.sar is
|earlier
|   than the ozone.sar
|  
|   Is there any mechanism that allows this behaviour to be configured?
|  
|   Best regards,
|   Per
|  
|  
|   ___
|  
|   Don't miss the 2002 Sprint PCS Application Developer's Conference
|   August 25-28 in Las Vegas --
http://devcon.sprintpcs.com/adp/index.cfm
  
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
  ___
 
  Don't miss the 2002 Sprint PCS Application Developer's Conference
  August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] sar startup ordering

2002-06-03 Thread Per Nyfelt

Yes, that is the only way that makes sence for me at least.

I've submitted my sorter to patches...

Best regards,
Per

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of marc
 fleury
 Sent: Monday, June 03, 2002 7:30 PM
 To: [EMAIL PROTECTED]
 Subject: RE: [JBoss-dev] sar startup ordering


 Your applications depends on the system beind deployed so you better put
 your numbered deployments at the end.

 marcf

 |-Original Message-
 |From: [EMAIL PROTECTED]
 |[mailto:[EMAIL PROTECTED]]On Behalf Of Larry
 |Sandereson
 |Sent: Monday, June 03, 2002 8:25 AM
 |To: [EMAIL PROTECTED]
 |Subject: Re: [JBoss-dev] sar startup ordering
 |
 |
 |The best solution I have found is to use the classpath... / tag in your
 |default jboss-service.xml.  Certainly putting it in your jboss-system.jar
 |seems a bit extreme.
 |
 |-Larry
 |
 |- Original Message -
 |From: Per Nyfelt [EMAIL PROTECTED]
 |To: [EMAIL PROTECTED]
 |Sent: Monday, June 03, 2002 12:30 AM
 |Subject: RE: [JBoss-dev] sar startup ordering
 |
 |
 | I ended up creating my own Comparator since i want the
 non-numbered files
 |to
 | deploy first using the rules of the DeploymentSorter and then deploy
 | according to their numbered prefix. In order to actually use
 is however,
 |the
 | only way I found that worked was to add my class to jboss-system.jar,
 | otherwise i got a ClassNotFoundException (e.g. when jaring it up and
 |putting
 | the jar in lib). Is this a bug or intended?
 |
 | Best regards,
 | Per
 |
 |  -Original Message-
 |  From: [EMAIL PROTECTED]
 |  [mailto:[EMAIL PROTECTED]]On Behalf Of
 |  lsanders
 |  Sent: Thursday, May 30, 2002 4:59 PM
 |  To: [EMAIL PROTECTED]
 |  Subject: Re: [JBoss-dev] sar startup ordering
 | 
 | 
 |  This has been available since (I think) 3.0 RC2.  Take a look at
 |  the default
 |  jboss-service.xml file.   At the bottom in the Deployment
 |  Scanning section,
 |  look for an attribute named URLComparator.  The default comparator
 |  (DeploymentSorter) sorts by type in this order: *.sar, *service.xml,
 |*rar,
 |  *jar, *war, *wsr, *ear, *zip, *.
 | 
 |  There is a second comparator (commented out) called
 |  PrefixDeploymentSorter.
 |  If you use this then all deployments that start with a numeric prefix
 |will
 |  be deployed in order of those prefixes.  Non-prefixed deployments are
 |  deployed last.  Ties are broken using the sorting from
 DeploymentSorter
 |  above.
 | 
 |  If this is still not cutting it, then you are free to implement
 |  an instance
 |  of java.util.Comparator that is capable of comparing two URL objects.
 | 
 |  -Larry
 | 
 |  - Original Message -
 |  From: Per Nyfelt [EMAIL PROTECTED]
 |  To: Jboss-Development@Lists. Sourceforge. Net
 |  [EMAIL PROTECTED]
 |  Sent: Thursday, May 30, 2002 6:29 AM
 |  Subject: [JBoss-dev] sar startup ordering
 | 
 | 
 |   I've been trying to find what was decided for how to specify in
 |  what order
 |   sar archives should be loaded and started, but the mail discussions
 |I've
 |   found points in many different directions. Could anyone
 please set me
 |   straight?
 |  
 |   I have a jxta.sar that i want to start before a ozone.sar
 |   From what i can see from testing the following works:
 |  
 |   1. Label them 10-jxta.sar and 20-ozone.sar
 |  
 |   2. keep the names but make sure the timestamp of the jxta.sar is
 |earlier
 |   than the ozone.sar
 |  
 |   Is there any mechanism that allows this behaviour to be configured?
 |  
 |   Best regards,
 |   Per
 |  
 |  
 |   ___
 |  
 |   Don't miss the 2002 Sprint PCS Application Developer's Conference
 |   August 25-28 in Las Vegas --
 http://devcon.sprintpcs.com/adp/index.cfm
   
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
   
  
  
   ___
  
   Don't miss the 2002 Sprint PCS Application Developer's Conference
   August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
  
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
 
 
  ___
 
  Don't miss the 2002 Sprint PCS Application Developer's Conference
  August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

RE: [JBoss-dev] sar startup ordering

2002-06-03 Thread Per Nyfelt

Ahh, thanks!

/Per :)

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Larry
 Sandereson
 Sent: Monday, June 03, 2002 5:25 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] sar startup ordering


 The best solution I have found is to use the classpath... / tag in your
 default jboss-service.xml.  Certainly putting it in your jboss-system.jar
 seems a bit extreme.

 -Larry

 - Original Message -
 From: Per Nyfelt [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, June 03, 2002 12:30 AM
 Subject: RE: [JBoss-dev] sar startup ordering


  I ended up creating my own Comparator since i want the
 non-numbered files
 to
  deploy first using the rules of the DeploymentSorter and then deploy
  according to their numbered prefix. In order to actually use is however,
 the
  only way I found that worked was to add my class to jboss-system.jar,
  otherwise i got a ClassNotFoundException (e.g. when jaring it up and
 putting
  the jar in lib). Is this a bug or intended?
 
  Best regards,
  Per
 
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of
   lsanders
   Sent: Thursday, May 30, 2002 4:59 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [JBoss-dev] sar startup ordering
  
  
   This has been available since (I think) 3.0 RC2.  Take a look at
   the default
   jboss-service.xml file.   At the bottom in the Deployment
   Scanning section,
   look for an attribute named URLComparator.  The default comparator
   (DeploymentSorter) sorts by type in this order: *.sar, *service.xml,
 *rar,
   *jar, *war, *wsr, *ear, *zip, *.
  
   There is a second comparator (commented out) called
   PrefixDeploymentSorter.
   If you use this then all deployments that start with a numeric prefix
 will
   be deployed in order of those prefixes.  Non-prefixed deployments are
   deployed last.  Ties are broken using the sorting from
 DeploymentSorter
   above.
  
   If this is still not cutting it, then you are free to implement
   an instance
   of java.util.Comparator that is capable of comparing two URL objects.
  
   -Larry
  
   - Original Message -
   From: Per Nyfelt [EMAIL PROTECTED]
   To: Jboss-Development@Lists. Sourceforge. Net
   [EMAIL PROTECTED]
   Sent: Thursday, May 30, 2002 6:29 AM
   Subject: [JBoss-dev] sar startup ordering
  
  
I've been trying to find what was decided for how to specify in
   what order
sar archives should be loaded and started, but the mail discussions
 I've
found points in many different directions. Could anyone
 please set me
straight?
   
I have a jxta.sar that i want to start before a ozone.sar
From what i can see from testing the following works:
   
1. Label them 10-jxta.sar and 20-ozone.sar
   
2. keep the names but make sure the timestamp of the jxta.sar is
 earlier
than the ozone.sar
   
Is there any mechanism that allows this behaviour to be configured?
   
Best regards,
Per
   
   
___
   
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas --
http://devcon.sprintpcs.com/adp/index.cfm
  
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
  ___
 
  Don't miss the 2002 Sprint PCS Application Developer's Conference
  August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] sar startup ordering

2002-06-03 Thread lsanders

OK- I agree.  I will modify the existing PrefixDeploymentSorter.java.  I
will also make it the default comparator in jboss-system.xml.  Should I aply
these changes to Branch_3_0?

-Larry


 Yes, that is the only way that makes sence for me at least.

 I've submitted my sorter to patches...

 Best regards,
 Per

  Your applications depends on the system beind deployed so you better put
  your numbered deployments at the end.
 
  marcf
 
  |The best solution I have found is to use the classpath... / tag in
your
  |default jboss-service.xml.  Certainly putting it in your
jboss-system.jar
  |seems a bit extreme.
  |
  |-Larry
  |
  | I ended up creating my own Comparator since i want the
  non-numbered files
  |to
  | deploy first using the rules of the DeploymentSorter and then deploy
  | according to their numbered prefix. In order to actually use
  is however,
  |the
  | only way I found that worked was to add my class to jboss-system.jar,
  | otherwise i got a ClassNotFoundException (e.g. when jaring it up and
  |putting
  | the jar in lib). Is this a bug or intended?
  |
  | Best regards,
  | Per
  |
  |  This has been available since (I think) 3.0 RC2.  Take a look at
  |  the default
  |  jboss-service.xml file.   At the bottom in the Deployment
  |  Scanning section,
  |  look for an attribute named URLComparator.  The default
comparator
  |  (DeploymentSorter) sorts by type in this order: *.sar,
*service.xml,
  |*rar,
  |  *jar, *war, *wsr, *ear, *zip, *.
  | 
  |  There is a second comparator (commented out) called
  |  PrefixDeploymentSorter.
  |  If you use this then all deployments that start with a numeric
prefix
  |will
  |  be deployed in order of those prefixes.  Non-prefixed deployments
are
  |  deployed last.  Ties are broken using the sorting from
  DeploymentSorter
  |  above.
  | 
  |  If this is still not cutting it, then you are free to implement
  |  an instance
  |  of java.util.Comparator that is capable of comparing two URL
objects.
  | 
  |  -Larry
  | 
  |   I've been trying to find what was decided for how to specify in
  |  what order
  |   sar archives should be loaded and started, but the mail
discussions
  |I've
  |   found points in many different directions. Could anyone
  please set me
  |   straight?
  |  
  |   I have a jxta.sar that i want to start before a ozone.sar
  |   From what i can see from testing the following works:
  |  
  |   1. Label them 10-jxta.sar and 20-ozone.sar
  |  
  |   2. keep the names but make sure the timestamp of the jxta.sar is
  |earlier
  |   than the ozone.sar
  |  
  |   Is there any mechanism that allows this behaviour to be
configured?
  |  
  |   Best regards,
  |   Per



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] sar startup ordering

2002-06-03 Thread Jason Dillon

The system is already deployed at this time.  It would have been better to use 
a depends and link to another MBean for the UDS plugins, so that it does 
not have to perform class instantiation.

--jason


On Monday 03 June 2002 10:29 am, marc fleury wrote:
 Your applications depends on the system beind deployed so you better put
 your numbered deployments at the end.

 marcf

 |-Original Message-
 |From: [EMAIL PROTECTED]
 |[mailto:[EMAIL PROTECTED]]On Behalf Of Larry
 |Sandereson
 |Sent: Monday, June 03, 2002 8:25 AM
 |To: [EMAIL PROTECTED]
 |Subject: Re: [JBoss-dev] sar startup ordering
 |
 |
 |The best solution I have found is to use the classpath... / tag in your
 |default jboss-service.xml.  Certainly putting it in your jboss-system.jar
 |seems a bit extreme.
 |
 |-Larry
 |
 |- Original Message -
 |From: Per Nyfelt [EMAIL PROTECTED]
 |To: [EMAIL PROTECTED]
 |Sent: Monday, June 03, 2002 12:30 AM
 |Subject: RE: [JBoss-dev] sar startup ordering
 |
 | I ended up creating my own Comparator since i want the non-numbered
 | files
 |
 |to
 |
 | deploy first using the rules of the DeploymentSorter and then deploy
 | according to their numbered prefix. In order to actually use is however,
 |
 |the
 |
 | only way I found that worked was to add my class to jboss-system.jar,
 | otherwise i got a ClassNotFoundException (e.g. when jaring it up and
 |
 |putting
 |
 | the jar in lib). Is this a bug or intended?
 |
 | Best regards,
 | Per
 |
 |  -Original Message-
 |  From: [EMAIL PROTECTED]
 |  [mailto:[EMAIL PROTECTED]]On Behalf Of
 |  lsanders
 |  Sent: Thursday, May 30, 2002 4:59 PM
 |  To: [EMAIL PROTECTED]
 |  Subject: Re: [JBoss-dev] sar startup ordering
 | 
 | 
 |  This has been available since (I think) 3.0 RC2.  Take a look at
 |  the default
 |  jboss-service.xml file.   At the bottom in the Deployment
 |  Scanning section,
 |  look for an attribute named URLComparator.  The default comparator
 |  (DeploymentSorter) sorts by type in this order: *.sar, *service.xml,
 |
 |*rar,
 |
 |  *jar, *war, *wsr, *ear, *zip, *.
 | 
 |  There is a second comparator (commented out) called
 |  PrefixDeploymentSorter.
 |  If you use this then all deployments that start with a numeric prefix
 |
 |will
 |
 |  be deployed in order of those prefixes.  Non-prefixed deployments are
 |  deployed last.  Ties are broken using the sorting from
 |  DeploymentSorter above.
 | 
 |  If this is still not cutting it, then you are free to implement
 |  an instance
 |  of java.util.Comparator that is capable of comparing two URL objects.
 | 
 |  -Larry
 | 
 |  - Original Message -
 |  From: Per Nyfelt [EMAIL PROTECTED]
 |  To: Jboss-Development@Lists. Sourceforge. Net
 |  [EMAIL PROTECTED]
 |  Sent: Thursday, May 30, 2002 6:29 AM
 |  Subject: [JBoss-dev] sar startup ordering
 | 
 |   I've been trying to find what was decided for how to specify in
 | 
 |  what order
 | 
 |   sar archives should be loaded and started, but the mail discussions
 |
 |I've
 |
 |   found points in many different directions. Could anyone please set
 |   me straight?
 |  
 |   I have a jxta.sar that i want to start before a ozone.sar
 |   From what i can see from testing the following works:
 |  
 |   1. Label them 10-jxta.sar and 20-ozone.sar
 |  
 |   2. keep the names but make sure the timestamp of the jxta.sar is
 |
 |earlier
 |
 |   than the ozone.sar
 |  
 |   Is there any mechanism that allows this behaviour to be configured?
 |  
 |   Best regards,
 |   Per
 |  
 |  
 |   ___
 |  
 |   Don't miss the 2002 Sprint PCS Application Developer's Conference
 |   August 25-28 in Las Vegas --

 http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
  
   ___
  
   Don't miss the 2002 Sprint PCS Application Developer's Conference
   August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
  
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
 
  ___
 
  Don't miss the 2002 Sprint PCS Application Developer's Conference
  August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development

 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https

Re: [JBoss-dev] sar startup ordering

2002-05-30 Thread lsanders

This has been available since (I think) 3.0 RC2.  Take a look at the default
jboss-service.xml file.   At the bottom in the Deployment Scanning section,
look for an attribute named URLComparator.  The default comparator
(DeploymentSorter) sorts by type in this order: *.sar, *service.xml, *rar,
*jar, *war, *wsr, *ear, *zip, *.

There is a second comparator (commented out) called PrefixDeploymentSorter.
If you use this then all deployments that start with a numeric prefix will
be deployed in order of those prefixes.  Non-prefixed deployments are
deployed last.  Ties are broken using the sorting from DeploymentSorter
above.

If this is still not cutting it, then you are free to implement an instance
of java.util.Comparator that is capable of comparing two URL objects.

-Larry

- Original Message -
From: Per Nyfelt [EMAIL PROTECTED]
To: Jboss-Development@Lists. Sourceforge. Net
[EMAIL PROTECTED]
Sent: Thursday, May 30, 2002 6:29 AM
Subject: [JBoss-dev] sar startup ordering


 I've been trying to find what was decided for how to specify in what order
 sar archives should be loaded and started, but the mail discussions I've
 found points in many different directions. Could anyone please set me
 straight?

 I have a jxta.sar that i want to start before a ozone.jar
 From what i can see from testing the following works:

 1. Label them 10-jxta.jar and 20-ozone.jar

 2. keep the names but make sure the timestamp of the jxta.jar is earlier
 than the ozone.jar

 Is there any mechanism that allows this behaviour to be configured?

 Best regards,
 Per


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] sar startup ordering

2002-05-30 Thread Per Nyfelt

Perfect, this is the information i was looking for. Thanks a lot!

Best regards,
Per

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of
 lsanders
 Sent: Thursday, May 30, 2002 4:59 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] sar startup ordering


 This has been available since (I think) 3.0 RC2.  Take a look at
 the default
 jboss-service.xml file.   At the bottom in the Deployment
 Scanning section,
 look for an attribute named URLComparator.  The default comparator
 (DeploymentSorter) sorts by type in this order: *.sar, *service.xml, *rar,
 *jar, *war, *wsr, *ear, *zip, *.

 There is a second comparator (commented out) called
 PrefixDeploymentSorter.
 If you use this then all deployments that start with a numeric prefix will
 be deployed in order of those prefixes.  Non-prefixed deployments are
 deployed last.  Ties are broken using the sorting from DeploymentSorter
 above.

 If this is still not cutting it, then you are free to implement
 an instance
 of java.util.Comparator that is capable of comparing two URL objects.

 -Larry

 - Original Message -
 From: Per Nyfelt [EMAIL PROTECTED]
 To: Jboss-Development@Lists. Sourceforge. Net
 [EMAIL PROTECTED]
 Sent: Thursday, May 30, 2002 6:29 AM
 Subject: [JBoss-dev] sar startup ordering


  I've been trying to find what was decided for how to specify in
 what order
  sar archives should be loaded and started, but the mail discussions I've
  found points in many different directions. Could anyone please set me
  straight?
 
  I have a jxta.sar that i want to start before a ozone.jar
  From what i can see from testing the following works:
 
  1. Label them 10-jxta.jar and 20-ozone.jar
 
  2. keep the names but make sure the timestamp of the jxta.jar is earlier
  than the ozone.jar
 
  Is there any mechanism that allows this behaviour to be configured?
 
  Best regards,
  Per
 
 
  ___
 
  Don't miss the 2002 Sprint PCS Application Developer's Conference
  August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 


 ___

 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development




___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development