|Well the ConnectionFactoryLoader mbean is but needing a RAR to be deployed
|is not -- there is no mbean for a rar.

That's a point.

|> that's great but we don't have a single real life scenario that warrants
|> this, do we?
|
|Don't lots of people have app-specific mbeans? Don't they want to include
|the configuration for them somehow in the ear?  Isn't this what
|application-server specific info in an ear is for?

but then it is in the ear and the sar is in the ear just like jars and wars.
Then 2 points
1- keep the format of the sar as close as jars as possible (don't include
anything, just the sar classes)
2- don't make the sar the top, make it the ear.  Only we extend it to
includes sars,

|Someone did ask recently for Datasources that were unavailable to other
|apps.  If you deploy the ConnectionFactoryLoader mbean for that datasource
|inside the app deployment process, you can put it in the apps private jndi
|namespace so it is unavailable to other apps.

yes as part of an ear.

sar C (mathematical in included in ) ear

ear !C sar

The following makes sense to me
(jar, war, rar, sar) C ear

While the following doesn't
(jar, war, rar, ear) C sar


|I can't think of a reason to put an ear in the classpath of a sar, and I'm

It is the other way around.

|I can't find any info on jsr88 - do you have a link?
|
|Which areas of the spec is it not compliant with?  Is it worse than
|optimized local calls? ;-)

:) yes much much much worse, the boogy man will eat you alive for not making
it squeaky clean

marcf

|
|david jencks
|>
|> marcf
|>
|>
|> _______________________________________________
|> Jboss-development mailing list
|> [EMAIL PROTECTED]
|> https://lists.sourceforge.net/lists/listinfo/jboss-development
|>
|>
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development


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

Reply via email to