[JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd

2003-03-18 Thread MNewcomb
Updating XDoclet and there are a couple of small backwards compatibility issues: JBoss 3.0: - any order - at least one JBoss 3.2: - 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

Re: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd

2003-03-18 Thread Scott M Stark
ay, March 18, 2003 10:34 AM Subject: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd > Updating XDoclet and there are a couple of small backwards compatibility > issues: > > JBoss 3.0: > > > - any order > - at least one > > JBoss 3.2: > > > - session

RE: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd

2003-03-19 Thread MNewcomb
> -Original Message- > From: Scott M Stark [mailto:[EMAIL PROTECTED] > Subject: Re: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd > > ... > the enterprise-beans element model would have to be: > > content model for backward compability and consistency with the

Re: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dtd

2003-03-19 Thread Scott M Stark
Fine. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 19, 2003 6:29 AM Subject: RE: [JBoss-dev] jboss_3_0.dtd vs jboss_3_2.dt