"bstansberry(a)jboss.com" wrote :
| Semi-OT, but one think that makes it hard to discuss is the term "profile"
is overloaded.
|
Yes i also do think it's a bit overloaded - therefore i think a named group of
deployments which belong together fits quite good :)
"bstansberry(a)jboss.com" wrote :
| I still see those as two different although related things. Perhaps from the point of
view of an SPI it doesn't matter. I'd think management tools would care though:
can the tool add or remove content from this subprofile? Can the tool update existing
content? Will the repository itself detect and allow content added or removed not via the
management tool? Will the repository itself detect updates to existing content? This is
all information that should be exposed.
|
I think also the term sub-profile seems to need some more definition.
Actually a sub-profile is just a profile - it is a notion which implies a
relationship/dependency between two profiles.
What you actually can do with the profile then depends on the implementation itself.
"bstansberry(a)jboss.com" wrote :
| Yep, looking at Emmanuels XML examples last week...
One "m" is enough - just Emanuel ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206054#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...