[jboss-dev-forums] [Design of POJO Server] - Re: The DeploymentManager and ProfileService

[emuckenhuber]

"scott.stark at jboss.org" wrote : That's fine, I'll checkout the spi project and take a look until its in trunk.

Okay i've updated trunk with the my current changes.

"scott.stark at jboss.org" wrote : 
  | I'm begining to think that there is no point to a Profile without a DeploymentRepository though.The reason is that at its most explicit a profile has a list of URLs/URIs that define the deployments in some VFS. 
  | 

Hmm, there are some use cases where you don't need any repository.
For example the transient application profile managed by the DeploymentManager.
This will be just a hashMap containing the isCopyContent == false deployments, so that they
are also visible in the ManagementView.
But it's still a independent profile, which can be activated / deactivated by the DeploymentManager.

Furthermore i think a VFS/uri does not make up a profile, as you still can could have a different (maybe static) profile,
where you create non-vfs based deployments - this is now also possible with the abstraction of ProfileDeployment (although not fully implemented)

Also if you look at FilteredDeploymentRepositoryFactory - this would not really be needed,
as all the profile has to do is once to get it deployments.
That's basically the reason why i think that a DeploymentRepository is optional.

Even having an OBR based Profile, would not change much - as the profile implementation would map
the deployments with the help of a OBR repository service.
There could also be a requirement/capability resolving, but this should be similar to the RequirementDependencyItem
from jboss-classloading, where you just get a dependency on a different profile instead of resources.
[OT: that's why i was mentioning that i want to review getSubProfiles(), as this would might be better to have a
ProfileVisitor where you can create your specific DependencyItems for your Profile.]

Although i also think that there is something missing - but more in the sense of a ResourceDiscovery or ProfileSource.
Something where you can share the same source and don't need to maintain the profile root uris in each profile.
Maybe this also matches somehow to the work you want to do with a DeploymentRepository?

Can you provide some more information and/or use cases why you think this is not enough?
I mean maybe i'm just missing something :)


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206116#4206116

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206116