I was thinking last night <g> David came back with the original proposal I did when designing it and I kind of like it.
It goes like this, we can 1- keep the current sar format with xml and classes inside. This kind of packaging is heavy and today is prone to class duplication in the different packages that make up the master package. ANT is really good at generating these "russian dolls" one inside the other and actually the russian doll image is not that good as we can have many jars at the same level. (it is a large family russian doll). 2- generalize the xml snippet usage. All we do is DROP the xml snippet with a classpath entry in there that says what *URL* to use to distribute the code. This way the structure you distribute is the xml skeleton and nothing more, not the classes, never. From a packaging standpoint this is simpler but also from a classloading point of view as we can reference URLCLassLoaders pointer to a repository. This becomes very lightweight, no replication of *code* across the nodes, just a central URL repository and you distribute the xml skeletons across nodes. *that* is deployment. In fact that is already supported in RH (xml only) I mean that it could be generalized to EAR/JAR/WAR so that you never have "I can't see my application classes from my web layers" etc etc etc.... we should use the scoped deployment from Dr JUNG and possible (he he) "grand" unify the classloaders for this as many of you pointed that application will need to see the resources. I will forward the mail from David as it is the source. regards marcf |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Jung |, Dr. Christoph |Sent: Thursday, September 27, 2001 3:20 AM |To: '[EMAIL PROTECTED]' |Subject: AW: [JBoss-dev] JBossFilesystemRoot mbean and sar local |directories. (rh/3.0) | | |-----Ursprüngliche Nachricht----- |>Von: David Jencks [mailto:[EMAIL PROTECTED]] |>Gesendet: Mittwoch, 26. September 2001 20:41 |>An: [EMAIL PROTECTED] |>Betreff: Re: [JBoss-dev] JBossFilesystemRoot mbean and sar local |>directories. (rh/3.0) | |>Hmm, I guess I should experiment and see if a url like |>jar:jar:http://.../myrar.rar!/path/myjar.jar!/ works to get to the jar |>inside a rar... maybe we don't need to unpack these things. | |If I remember my experiments from a while ago, the URL is valid, but there |is no way |to get a sun.net.www.protocol.jar.Handler sitting on a stream that is |extracted by another jar.Handler. The guy who did the name resolution code |was seemingly more intelligent than the guy who did the specific jar |provider ;-) | |But the URL solution generally does not allow services to manipulate the |resource. So a file abstraction or something like that would be more |suitable. | |CGJ | |_______________________________________________ |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
