Hi,
Thanks.
jboss.dtd works for me :) (and I have some MDBs)
I just change standardsjaws.xml to avoid using type-mapping for 2 different
things.
It will look like :
<?xml version="1.0" encoding="UTF-8"?>
<jaws>
<datasource>java:/DefaultDS</datasource>
<type-mapping>Hypersonic SQL</type-mapping> <=== I did not touch that
<debug>false</debug>
<default-entity>
<create-table>true</create-table>
<remove-table>false</remove-table>
<tuned-updates>false</tuned-updates>
<read-only>false</read-only>
<time-out>300</time-out>
<select-for-update>false</select-for-update>
</default-entity>
<type-mappings>
===> <type-mapping-definition> <====
<name>InterBase</name>
<mapping>
<java-type>java.lang.Boolean</java-type>
...
===> </type-mapping-definition> <====
Also note that I remove the messages from the dtd like current CVS.
Finally note that now JBoss can validate DTD for ejb-jar and jboss but not
jaws.
If anybody is working on it, I can do it.
Vincent.
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de Mike
> Swainston-Rainford
> Envoye : mardi 19 juin 2001 0:06
> A : [EMAIL PROTECTED]
> Objet : Re: [JBoss-dev] Is Monday still a good 2.4 freeze date
>
>
> Scott, Vincent
>
> The jboss.dtd I have differs from the latest CVS in that I have included
> the message driven bean stuff. Its supported in 2.2 so is there
> any reason
> it shouldn't be in the DTD - apart from strict EJB 1.1 compliance?
>
> I have included it because Together 5 supports MDB so I added them to the
> deployer.
>
> The jaws.dtd is radically different. I dug out all the obscure stuff like
> debug, pk-constraint, select-for-update etc and included them. It also
> didn't parse because cmp-field (and others) weren't defined. (However, it
> won't ever parse because of the duplicate type-mapping definitions as
> mentioned in the comments.)
>
> I have attached the two DTDs for perusal/use/abuse as you see fit. If the
> jaws.dtd is no go I'd like to know so that I can back out the changes I
> made to ejx jaws plugin to support it all :-)
>
> I am still working on the ejx jboss plugin to add interceptors
> plus one or
> two other nasties. Hope to have it complete before end of this week.
>
> Mike S-R
>
> At 07:51 15/06/2001 -0700, you wrote:
> >The dtd was fixed yesterday. All official dtds are in the jboss cvs
> >module under src/resources/org/jboss/metadata.
> >
> >I'll fork new versions of the dtds that have changed since 2.2 and
> >label then with a 2_4(jboss_2_4.dtd, jaws_2_4.dtd). The only change
> >this entails is adding additional local entity resolver paths as far as
> >I can see. The only place the name shows up is in the DOCTYPE statement
> >of the deployment descriptor. There is no reference to
> jboss.dtd, jaws.dtd
> >in the codebase.
> >
> >Sure, create a comprehensive example. The users are begging for one.
> >
> >----- Original Message -----
> >From: "Mike Swainston-Rainford" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Sent: Friday, June 15, 2001 2:45 AM
> >Subject: RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
> >
> >
> >Aren't there still some errors in the jboss.dtd as well? If I remember
> >correctly max-bean-life and overager-period are not defined.
> >
> >I was trying to get the dtds corrected for the Together JBoss
> deployer and
> >then submit them for incorporation in CVS but they are such a
> moving target
> >I had to freeze them for 2.2.2 and include them with the deployer
> >distribution to guarantee that the Together XML editor would
> open them OK.
> >(I have what I believe are valid and complete DTDs for the 2.2 release -
> >some of the comments need the wording tidying up but the structure is
> >correct).
> >
> >Is there an 'official' public URL for the dtd files. The documentation
> >pages link to www.jboss.org/documentation/jboss.dtd and jaws.dtd is there
> >as well. (jboss-web.dtd isn't) But I believe they are out of date with
> >respect to the current 2.2.2 release (the debug element isn't
> mentioned in
> >jaws.dtd for example).
> >
> >In view of the major changes to the dtd betwixt 2.2 and 2.3/2.4 shouldn't
> >there be a version number added to the files so that the 2.4 file is a
> >different beast to the 2.2 file? The jboss.xml secure element has been
> >sensibly renamed but its no longer backwards compatible with 2.2.
> >
> >
> >
> >_______________________________________________
> >Jboss-development mailing list
> >[EMAIL PROTECTED]
> >http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
