JBossDeveloper

Emanuel Muckenhuber wrote:

 

Hmm, the thing i'm not really sure is the hash in the deployment. This does not seem to be something you want to edit manually in the xml, rather something used internally.

I agree that this is something that you don't want to edit manually, but that doesn't matter.  A deployment entry can't be added to the domain.xml file until and unless it has been validated (to the extent that the DC does validate), indexed (at the very least with a package index, maybe an annotation index too), and added to the domain model.  So it follows that deployment cannot and should not be done by editing domain.xml.

If we are going to end up persisting other hashes, shouldn't the deployment hashes be kept in the same place?

David Lloyd wrote:

 

I agree that this is something that you don't want to edit manually, but that doesn't matter.  A deployment entry can't be added to the domain.xml file until and unless it has been validated (to the extent that the DC does validate), indexed (at the very least with a package index, maybe an annotation index too), and added to the domain model.  So it follows that deployment cannot and should not be done by editing domain.xml.

Hmm, what i was rather thinking about is keeping configuration separate from runtime information and state. Where the domain.xml as configuration / management policy might not be the best place to maintain/persist this kind of information. Maybe the hash of a deployment might not be a big deal, however we most likely need some more runtime information anyway - so it would make sense to also consider other options to deal with this?