David Jencks wrote:
>>As soon as you get the first error, the deployment should stop and 
>>unroll.  Correct?  
> 
> 
> I don't think so.  This tends to produce behavior like stopping the server
> when your ejb doesn't deploy on server startup.

Yes.  I don't want a half deployed application.  It either works or it 
doesn't.

> I really think it is more useful to deploy everything possible and record
> errors for each object.  In my experience this provides much more
> information and lets you fix several problems at once. This is the point of
> the IncompleteDeploymentException, it lists everything that went wrong. 
> You may be able to fix stuff and start your mbeans or whatever without
> redeploying.

Complexity.  This will make the code much harder to write if I can not 
assume that a DeploymentException immedately stops all deployment.  It 
could do very weird things to the persistence store.

There is no reason for this.  Deployment problems should be worked out 
in development and testing, and developers and testers are used to the 
you only get the first error type of deployment.  Maybe we can run the 
entire verifier and then try the real deployment, but once the real 
deployment starts the first deployment exception should stop all 
deployment of the file and rollback.

>  The repeated exceptions here IMO are due to bad design of the xml parsing
> and are not a reason to change the behavior of the deployment system.

I'm not bitching about the exceptions (yet), just the weird deployment 
problems (and the confusing results).

> So you should end up with on exception trace and an 
> 
>>undeployment messages.
> 
> 
> I find undeploying on error removes most of the information I use to find
> out what is wrong.

I don't think this is necessary, but if it can be done without making 
the code to complex (I know you are the king of complexity, but I can't 
handle it), then it would be nice.

-dain



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to