|I am not quite happy with this because of:
|
|- Whereas JAR, RAR, WAR and EAR files are vendor
| neutral archives is the SAR/JSR not vendor neutral
| (it also has nothing to do with J2EE but with JMX).
See my previous mail, sars are not "encompassing" units in my mind, or at
least David has given no justification as to why this would be the case.
|- SAR/JSR components (resources) servers more than
| just one application therefore it would become a problem
| if a second application uses the same resource which was
| not deployed with the SAR and the SAR gets undeployed.
Bingo. But (if I run ahead of myself) I would imagine a SAR being deployed
with depending EARs, not the other way around. If for example you want to
deploy management beans or JSPs that are geared to that service only then it
might make sense.
But keep it simple is my key feeling... if it wasn't requested don't go and
invent the feature.
The only feature that was requested was the directory and security on
directory structure. I don't understand where this fits.
I will tell you what worries me, we have lenghty email discussions on stuff
that should already be there in code... it is a trend that I don't like.
David just go ahead and don't try to over design it... put only the *first*
features that come to mind... if you have to invent the feature then nuke
it. 50% chance it is absolutely useless in the first place.
FYI
marcf
|
|Andy
|
|
|
|_______________________________________________
|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
