Updating XDoclet and there are a couple of small backwards compatibility
issues:

JBoss 3.0:
<!ELEMENT enterprise-beans (session | entity | message-driven)+>

- any order
- at least one

JBoss 3.2:
<!ELEMENT enterprise-beans (session*, entity*, message-driven*)>

- session beans, then entity beans, then message-driven beans
- none required

3.2 will break if beans interspersed or listed out of this order.  Can we go
back to
<!ELEMENT enterprise-beans (session | entity | message-driven)*> but use '*'
instead of '+'?  Or did the parser change to reflect the new definition?

JBoss 3.0:
<!ELEMENT jboss (enforce-ejb-restrictions?, security-domain?,
unauthenticated-principal?, enterprise-beans?, resource-managers?,
container-configurations?)>

- enterprise beans come before resource managers

JBoss 3.2:
<!ELEMENT jboss (enforce-ejb-restrictions?, security-domain?,
unauthenticated-principal?, resource-managers?, invoker-proxy-bindings?,
enterprise-beans?, container-configurations?)>

- enterprise beans come after resource managers

I have to update the XDoclet templates and now need to check jboss revision
to put enterprise-beans after resource-managers for 3.2+ and vice-versa for
< 3.2.

Should I fix the 3.2 dtd to reflect 3.0?  Or have the parsers changed...

Thanks,
Michael


-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? 
You could win a Tablet PC. Get a free Tablet PC hat just for playing. 
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to