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.
Maybe the dtd files should be put under www.jboss.org/dtds with a frozen
version for Jboss 2.2.2 named jboss.dtd, jboss-web.dtd and jaws.dtd. The
2.4 versions could be renamed jboss-1_1.dtd? jboss-2_4.dtd?
What problems would renaming the files cause in the development of JBoss? I
don't think it would cause any major grief to users of JBoss - if they are
using CVS they are going to expect some problems and inconsistencies :-)
I also think a very small tutorial example using all the XML files -
application, web, ejb, jboss, jboss-web and jaws would be a useful addition
to the documentation for developers new to ejb and/or jboss. The CDEjb
example with the jsp stuff added is probably a good candidate (except for
MDB). This needs a 2.2 version and then a 2.4 version to cover all the
additional stuff.
BTW the cdejb with jsp example that I've got with the latest deployer
generates all of the xml files from the Together diagrams. I'm planning on
keeping this example up to date with the deployer - so I want to get a 2.4
deployer plus example out that supports all the extras in the dtds. I was
also going to retrofit/correct the Ant build scripts and .bat .sh files so
that it can be used with or without Together ie put the generated .xml
files into resources so that the Ant build.xml can use them.
If you think its sensible to provide the tutorial example I can start
tidying it up/fixing it. If my updated versions of the dtds would be useful
I can mail them.
Mike S-R
At 09:20 15/06/2001 +0200, you wrote:
>Hi,
>IMHO, the re-deployment problem (see below) should stop you making a new
>release.
>
>For my part, I will test/validate the new DTD validation option as some
>elements are still missing from jaws.dtd (cmp-field is not defined). I will
>take care of dtd corrections.
>
>Vincent.
>
>[Container Management Proxy] Destroyed
>[Default] javax.management.InstanceAlreadyExistsException:
>Management:container=bank/Account
>[Default] at
>com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134
>)
>[Default]
>[Default] at
>com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.ja
>va:
>[Default]
>[Default] at
>com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:388)
>[Default]
>[Default] at
>org.jboss.ejb.ContainerFactory.registerContainer(ContainerFactory.java:716)
>[Default]
>[Default] at
>org.jboss.ejb.ContainerFactory.createEntityContainer(ContainerFactory.java:7
>00)
>[Default]
>[Default] at
>org.jboss.ejb.ContainerFactory.createContainer(ContainerFactory.java:599)
>[Default]
>[Default] at
>org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:471)
>[Default]
>[Default] at
>org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:366)
>[Default]
>[Default] at
>org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:305)
>[Default]
>[Default] at java.lang.reflect.Method.invoke(Native Method)
>[Default]
>[Default] at
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
>[Default]
>[Default] at
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>[Default]
>[Default] at
>org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:489)
>[Default]
>[Default] at
>org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:467)
>[Default]
>[Default] at
>org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:211)
>[Default]
>[Default] at java.lang.reflect.Method.invoke(Native Method)
>[Default]
>[Default] at
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
>[Default]
>[Default] at
>com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
>[Default]
>[Default] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379)
>[Default]
>[Default] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217)
>[Default]
>[Default] at java.lang.Thread.run(Unknown Source)
>[Default]
>
> > -----Message d'origine-----
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]De la part de
> > Scott M Stark
> > Envoyé : vendredi 15 juin 2001 2:24
> > À : JBoss Dev
> > Objet : [JBoss-dev] Is Monday still a good 2.4 freeze date
> >
> >
> > Is Monday still a good 2.4 freeze date for the features that will go into
> > the 2.4 release or is more time needed?
> >
> >
> >
> > _______________________________________________
> > 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
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
