This is wrong.
e.g. What if I want to deploy an EAR programatically where I tell it upfront
what the structure and metadata is.
i.e. it doesn't go through either the structure or the parsing deployer,
it uses the structure and metadata I've told it to use when I did the programmtic
I'm I supposed to know to add the transient managed object that represents
the context root to the war context I create manually, or should I expect it to
pick it from the J2eeApplicationMetaData where I defined it?
The correct solution is to have a seperate deployer that looks
for application level metadata when processing subdeployments.
In principle there is not just the context-root that can defined at the ear
level, one could also provide things like a default "call-by-value" in
The creator of the deployment (including the profile service) should not
be expected to know what transient managed objects need to be created.
That is just an implementation detail of one way the deployers can "talk to each
Also to make this work at all, the transient managed objects would
have to be serialized such that a remote caller can add this information
and the profile service can remember what they were when re-creating the deployment,
this doesn't sound correct to me.
View the original post :
Reply to the post :