steps to reproduce:
-add <session> tag with duplicate name
what is the behaviour in web area when in web.xml the user add a
duplicate entry for a servlet?
We need the same consistent behaviour in ejbs.
hand editing ejb-jar.xml is always possible.
I did try a duplicate servlet entry in web.xml and could save the file.
As xml validation (manual step, the error agaisnt the schema was detected)
Exactely the same behaviour is happening for ejb-jar: I can save the file.
If I invoke the xml validation, I have:
Referenced entity at
Duplicate key value [Test] declared for identity constraint of element
So I don't understand why this bug is filed... A user can for example
enterely corrupt a java file and still save this file.
Or what is the equivalent bug number in Web Apps?
When I duplicate session bean, it adds duplicate entry in project tab,
and when I try to deploy project i fails without any reason. Only
"Deployment failed" appears.
At least there should be provided xml validation while deploying a
I see and agree
Move issues from temprorary component.
This is related to the validation which should occur after compilation
and before / during deployment. I am changing to appserver category as
this should be done as part of the deployment cycle.
We may be able to user the xmlvalidate task to catch this before we
send the jar off to the server.
*** Issue 52629 has been marked as a duplicate of this issue. ***
moving to j2eeserver, as validation of j2ee dd or schemas should be done
regardless of the app server target before calling a real deployment task.
This way, jboss, oracle, bea etc would benefit from this validation step,
I still do not see this as a bug. You cannot corrupt the deployment descriptor
in this way from UI (like wizard or visual editor of ejb-jar.xml), only from
text editor, correct?
Validation cannot be added generally, tomcat's context.xml does not have a DTD
so validation fails for it. We have already integrated verifier which catches
this problem. User can run this (verifier or xml validate) manually. If we add
xml validation (and maybe verifier) as build steps they should be made optional,
just like the JSP compilation is. Note that JSP compiation is actually OFF by
default. Adding these options will require UI changes.
TM 5.0 -> TBD
Based on Pavel's feedback, the validation can only apply to the 'standard dd files'
Since DD files are less relevant... this issue has a lower priority