|Not talking filesystems here. If one has a number of different domains
|(eg security, personnel, marketing, customer service etc) and they all
|have their own environment for developing applications and they are all
|using the same server to deploy. They all defer to the same mechanism
|for building the ears etc. If all of the jar paths were lumped into one
|generic classpath, then customer service could use, perhaps maliciously
|(sp?), an api specifically used for accessing certificates.
|
|That was the scenario I was thinking about.
|
|Have I blown it? Have I power nailed into my foot without realising it?
|Zut.
I really don't see it as a packaging issue.
case closed unless Scott has specific input
marcf
|
|
|marc fleury wrote:
|>
|> Be more precise about what security can be enforced at the
|packaging level.
|>
|> All I can see is the "file permission" on expanded directories
|but that is
|> all.
|>
|> marcf
|>
|> |-----Original Message-----
|> |From: [EMAIL PROTECTED]
|> |[mailto:[EMAIL PROTECTED]]On Behalf Of Nick
|> |Betteridge
|> |Sent: Saturday, September 22, 2001 12:54 PM
|> |To: [EMAIL PROTECTED]
|> |Subject: Re: [JBoss-dev] Proposed sar format change
|> |
|> |
|> |
|> |> Also, a question about j2ee deployment. (sorry I've only
|been looking at
|> |> j2ee pfd 3) There are a lot of classpath descriptions in
|section 8.3.1/2
|> |> etc. referring to using manifest classpath entries to figure
|out what to
|> |> include in the application classpath. However, it seems to
|me that if we
|> |> simply include _all_ packages found in the ear in the application
|> |> classpath, we will be satisfying this requirement without having
|> |to look at
|> |> these classpath entries. Is there a problem with this
|approach? Did I
|> |> miss something?
|> |
|> |
|> |What happens when there is a tiered structure within an enterprise, with
|> |security restrictions applying to certain domains/departments ...
|> |whatever.
|> |
|> |Surely the only way to manage access to api's is via a
|> |classpath/classloaders and security managers, and this is dealt with by
|> |the 'packaging' mechanism before passing the ear over to the deployer.
|> |
|> |Or have I missed something?
|> |
|> |_______________________________________________
|> |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
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
