"bstansberry(a)jboss.com" wrote :
| So with the kind of setup I'm talking about, having the default profile be the one
associated with ProfileKey($jboss.server.name}) would not work, since it will have no
URIs associated with it.
| I think the key question for 5.1 is how embedded-console/jopr are using the
DeploymentManager -- what ProfileKey are the passing to loadProfile (or to your new
distribute(String name, URL url, ProfileKey key) method.
Well we can create a additional application (deploy/) profile by default, as it's more
likely to be similar with the XmlProfileFactory - and would match what you are doing.
Furthermore we could add a getProfiles() to the DeploymentManager (maybe with the notion
of mutable profiles) then jopr could provide a dropdown menu to select where you actually
want to upload your content to. As the profiles from ProfileService are not necessarily
And we can also make those names configurable over the profile.xml.
View the original post :
Reply to the post :