What I don't like, really, is the SAR format. Having the files in there is a
pain in the ass, there is no way to get at the configuration simply. End of
story. It is the same nightmare with the JAR in EJB, dumb packaging. Sure
packaging is nice in some cases (I drop everything) but really
I usually end up creating a disabled directory under the deploy
directory. In here I put the clustering xml along with the JBossMQ
stuff, and the HSQL DB items. Perhaps this kind of packaging would make
it clearer that these services exist, but are simply not activated.
At some point someone
(comments to all proposals...)
I do something like this disabled directory also, but not as good... I like
the disabled.
Some things have mbeans that really don't need configuration, just
lifecycle services. These are good candidates for the current sar
structure. TransactionManager comes to
|Then under here are deployable snippets for groups of components rather
|than a single file.
reread my email that is the format
marcf
___
Jboss-development mailing list
[EMAIL PROTECTED]
|I usually end up creating a disabled directory under the deploy
|directory. In here I put the clustering xml along with the JBossMQ
real life stuff is good, at least it makes sense to you :)
marcf
___
Jboss-development mailing list
[EMAIL
|Native libraries are loaded by MainDeployer out of any package it unpacks
|(sar, ear, rar). Maybe it should deploy bare libraries? I don't know.
it does already, a jar is picked up and deployed, the fact that it is
inside a russian doll or outside is transparent. That is the way it works
On 2002.02.28 13:08:33 -0500 marc fleury wrote:
|Native libraries are loaded by MainDeployer out of any package it
unpacks
|(sar, ear, rar). Maybe it should deploy bare libraries? I don't know.
it does already, a jar is picked up and deployed, the fact that it is
inside a russian doll or
|native libraries as in native.dll or libnative.so are only deployed if they
|are found inside a jar-format package that is being unpacked.
Yes, ok, I think this is one of the most interesting features proposed by
Jason in the very beginning. I was looking at this deal where the
management
; Scott M Stark;
[EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
and clustering
Hello,
I also think that clustering shouldn't be deployed by default.
Nevertheless,
the problem was to have, in the official distribution, a place
where to put
PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of marc
|fleury
|Sent: Thursday, February 28, 2002 10:06 AM
|To: James Cook; [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
|and clustering
|
|
|
||I usually end up creating a disabled directory under
JBoss Group, LLC
- Original Message -
From: marc fleury [EMAIL PROTECTED]
To: marc fleury [EMAIL PROTECTED]; James Cook [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Thursday, February 28, 2002 11:20 AM
Subject: RE: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0
On 2002.02.28 13:19:44 -0500 Holger Baxmann wrote:
My experience with native libraries is limited, thankfully. The one I
have
to experiment with appears to load ok with the current code. I hope
someone else who knows more and has some will find out if anything
needs
improvement.
]
Sent: Thursday, February 28, 2002 11:20 AM
Subject: RE: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
and
clustering
real life thinking,
My wife is on the phone with a potential partner and they are asking
how
can
they drop their application in JBoss (with services
What are these and how do they relate to the service descriptor?
(3) IMHO is best handled by xmbean/modelmbean interceptors. The xdoclet
task I just wrote will generate appropriate descriptors, however the
xmbean
implementation is not complete enough to implement this at the moment.
I
|I like it, but the disabled directory is pointless in this scheme
|as any directory that is not specified to the deployer is disabled.
you are correct
|It seems like we need at least the following changes to support
|this:
|
|1. Externalize the MainDeployer configuration to allow the
|I think possibly much of the functionality of ServiceController can be
|moved to modelmbean interceptors.
kwel!
Can we get the fat fin out of his cave??? Mr lindfors still hibernating?
You know I will kick your ass at JBossOne...
marcf
___
-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
|and clustering
|
|
|
|
| Some things have mbeans that really don't need configuration, just
| lifecycle services. These are good candidates for the current sar
| structure. TransactionManager comes to mind. Switch tm's with no code
| bloat
On 2002.02.28 14:32:02 -0500 Scott M Stark wrote:
What are these and how do they relate to the service descriptor?
If you look at the jboss_xmbean_1_0.dtd I checked in today you will see a
bunch of descriptors that can be applied to various parts of the mbean
info, in particular these service
Some things have mbeans that really don't need configuration, just
lifecycle services. These are good candidates for the current sar
structure. TransactionManager comes to mind. Switch tm's with no code
bloat just by changing jbosstm.sar to tyrextm.sar.
I personally have had to set the
]
[mailto:[EMAIL PROTECTED]]On Behalf Of Sacha
Labourey
Sent: Thursday, February 28, 2002 3:12 AM
To: marc fleury; Andreas Schaefer; Scott M Stark;
[EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
and clustering
Hello,
I also think that clustering shouldn't
|It seems like we need at least the following changes to support
|this:
|
|1. Externalize the MainDeployer configuration to allow the specification
|of directories via a descriptor
yes
Why not externalize the functionality... MD does not and probably
should not be handling any of the
On 2002.02.28 21:28:02 -0500 Jason Dillon wrote:
Some things have mbeans that really don't need configuration, just
lifecycle services. These are good candidates for the current sar
structure. TransactionManager comes to mind. Switch tm's with no code
bloat just by changing jbosstm.sar
|Why not externalize the functionality... MD does not and probably
|should not be handling any of the deployment/file scanning that it does
|now. Lets move this functionality outside and make it a configurable
|component from jboss-service.xml which depends on MD.
good idea
go
g
marcf
|
PROTECTED]
|Objet : RE: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
|and clustering
|
|
|which brings us to the configuration story going around the list for the
|past month or so...
|
|oka, I will just do a summary since I haven't really sat down
|
|and thought,
|
|just sat here on my
I personally have had to set the timeout here to avoid bugs with mdb
not supportted attibutes.
Are you switching tms while jboss is running?
No, just had to set the timeout on certain nodes to insainly high to
avoid tx timeouts when an mdb was set to not use tx with not supported
On 2002.02.28 21:52:48 -0500 Jason Dillon wrote:
|It seems like we need at least the following changes to support
|this:
|
|1. Externalize the MainDeployer configuration to allow the
specification
|of directories via a descriptor
yes
Why not externalize the functionality... MD
Should be done shortly... in a few hours that is.
--jason
marc fleury wrote:
|Why not externalize the functionality... MD does not and probably
|should not be handling any of the deployment/file scanning that it does
|now. Lets move this functionality outside and make it a configurable
so?
where is it?
marcf
|-Original Message-
|From: Jason Dillon [mailto:[EMAIL PROTECTED]]
|Sent: Thursday, February 28, 2002 8:07 PM
|To: marc fleury
|Cc: Scott M Stark; [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
|and clustering
Hi
If you running a laptop without the network card and therefore
network services are down the start of the cluster will hang
JBoss forever.
I think clustering should not be part of the default configuration
because it should used on purpose (for distribution).
On the other hand maybe
: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
|and clustering
|
|
|Hi
|
|If you running a laptop without the network card and therefore
|network services are down the start of the cluster will hang
|JBoss forever.
|
|I think clustering should not be part of the default configuration
Of
|Andreas Schaefer
|Sent: Wednesday, February 27, 2002 9:57 PM
|To: Scott M Stark; [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Fw: [JBoss-user] Multiple JBOSS 3.0 developers
|and clustering
|
|
|Hi
|
|If you running a laptop without the network card and therefore
|network services
31 matches
Mail list logo
