I think the changes to both jaws and jboss should be merged into 2.4 but it
should be into the jboss_2_4 and jaws_2_4 files.
I think actually this is where the changes should have been made in the
first place (the _2_4 files) since Scott froze jboss.dtd and jaws.dtd for
the 2.2 release and created the new ones for 2.4.
It needs to be made very clear that there have been incompatible changes in
the dtds.
I think the best way to make this clear would be to revert jboss.dtd and
jaws.dtd on the main branch and do the updates to the 2_4 dtd files.
Actually it may be sensible to remove jboss.dtd and jaws.dtd from the 2.4
and main branches entirely?
I think there also needs to be a new version of defaultjaws.xml for the ejx
stuff because of the type-mapping element name change. This probably should
be defaultjaws_2_4.xml so that a new plugin for ejx can be built to handle
the backwards incompatible jaws changes. (see below)
So the jboss/jaws files are only for Jboss up to release 2.2 and ejb 1.1
and the _2_4 dtd files for jboss 2.4+ and ejb 2.0. Do you agree?
It would probably be a good idea to create an ejb2.0 plugin for ejx
(current ejb plugin only supports 1.1) to work with an new 2.4 jboss plugin
for ejx
So, leave the jboss.dtd and jaws.dtd files intact for release 2.2 - these
are ejb 1.1 compliant
Fix the jboss ejx plugin to handle the container interceptors on branch 2.2
and do another build. (2.2.3?)
Then on branch 2.4 (and main) create a new jboss plugin and ejb2 plugin for
ejx that handles jboss/jaws 2.4 dtds and ejb2.0 dtd.
Yes I know that ejx is not the best of frameworks for doing this but until
a new tool comes along I think its sensible to get them fixed. I have
exchanged a few emails offline with marc about this. I am prepared to do
the updates to the ejx plugins (I have some fixes already done but the
decisions about 'which branch and what files' need to be made before any
changes can be submitted).
It does fit in nicely with the deployer I have developed for the Together
UML tool (which is an alternative to using ejx to create the xml - and it
handles war and ear generation as well). I'm having to keep a close eye on
changes to the DTDs anyway to get the deployer ready for 2.4 so I might as
well do the ejx stuff.
But I think the updates to ejx should be an interim until something else
under the umbrella of the new jboss gui tools is developed. If not then
web.xml/jboss-web.xml and application.xml need to be supported as well :-(
Comments from Mad Andy the ejx expert? :-)
Mike S-R
At 15:24 20/06/2001 -0700, you wrote:
>Does this change needs to be merged to the 2.4 branch as well?
>
>----- Original Message -----
>From: <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Wednesday, June 20, 2001 2:14 PM
>Subject: [JBoss-dev] CVS update: jboss/src/resources/org/jboss/metadata
>jaws.dtd
>
>
> > User: vharcq
> > Date: 01/06/20 14:14:16
> >
> > Modified: src/resources/org/jboss/metadata jaws.dtd
> > Log:
> > Correct type-mapping definition
> >
> > Revision Changes Path
> > 1.8 +2 -2 jboss/src/resources/org/jboss/metadata/jaws.dtd
> >
> > Index: jaws.dtd
> > ===================================================================
> > RCS file:
> /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jaws.dtd,v
> > retrieving revision 1.7
> > retrieving revision 1.8
> > diff -u -r1.7 -r1.8
> > --- jaws.dtd 2001/06/19 07:38:22 1.7
> > +++ jaws.dtd 2001/06/20 21:14:16 1.8
> > @@ -38,8 +38,8 @@
> >
> > <!ELEMENT table-name (#PCDATA)>
> >
> > -<!ELEMENT type-mappings (type-mapping*)>
> > -<!ELEMENT type-mapping-definitions (name, mapping*)>
> > +<!ELEMENT type-mappings (type-mapping-definition*)>
> > +<!ELEMENT type-mapping-definition (name, mapping*)>
> > <!ELEMENT mapping (java-type, jdbc-type, sql-type)>
> > <!ELEMENT java-type (#PCDATA)>
> > <!ELEMENT jdbc-type (#PCDATA)>
> >
> >
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
