DTD Validation was RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
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 datasourcejava:/DefaultDS/datasource type-mappingHypersonic SQL/type-mapping=== I did not touch that debugfalse/debug default-entity create-tabletrue/create-table remove-tablefalse/remove-table tuned-updatesfalse/tuned-updates read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update /default-entity type-mappings ===type-mapping-definition nameInterBase/name mapping java-typejava.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
Re: DTD Validation was RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
Hi Vincent The reason I had to add the MDB stuff to the DTD was so that the Together XML editor would read the generated jboss.xml. I will use a copy of the DTD in the Together deployer so that this works OK. (The problem will go away when EJB 2.0 is supported). However, anyone else using a parsing xml editor trying to use MDBs will probably have the same problem. The defaultjaws.xml is out of sync with the standardjaws.xml. The type-mappings element and its contents in defaultjaws.xml should be identical to that in standardjaws.xml. EJX creates a duff jaws.xml at the moment because defaultjaws is written into the jaws.xml file by EJX. There is a bug reported describing this problem. Could you update defaultjaws so that its type-mappings element is the same as standardjaws? regards Mike S-R At 09:32 19/06/2001 +0200, you wrote: 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 datasourcejava:/DefaultDS/datasource type-mappingHypersonic SQL/type-mapping=== I did not touch that debugfalse/debug default-entity create-tabletrue/create-table remove-tablefalse/remove-table tuned-updatesfalse/tuned-updates read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update /default-entity type-mappings ===type-mapping-definition nameInterBase/name mapping java-typejava.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
RE: DTD Validation was RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
The reason I had to add the MDB stuff to the DTD was so that the Together XML editor would read the generated jboss.xml. I will use a copy of the DTD in the Together deployer so that this works OK. (The problem will go away when EJB 2.0 is supported). However, anyone else using a parsing xml editor trying to use MDBs will probably have the same problem. Absolutely. The defaultjaws.xml is out of sync with the standardjaws.xml. The type-mappings element and its contents in defaultjaws.xml should be identical to that in standardjaws.xml. EJX creates a duff jaws.xml at the moment because defaultjaws is written into the jaws.xml file by EJX. There is a bug reported describing this problem. Could you update defaultjaws so that its type-mappings element is the same as standardjaws? Just done :) regards Mike S-R Vincent _ 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
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 ?xml version='1.0' encoding='UTF-8' ? !-- This is the XML DTD for the JBoss 2.2 EJB deployment descriptor. The DOCTYPE is: !DOCTYPE jboss PUBLIC -//JBoss//DTD JBOSS//EN http://www.jboss.org/j2ee/dtd/jboss.dtd; Overview of the architecture of jboss.xml jboss secure / security-domain / enterprise-beans entity ejb-name / jndi-name / resource-ref res-ref-name / resource-name / /resource-ref /entity session ejb-name / jndi-name / resource-ref res-ref-name / resource-name / /resource-ref /session message-driven ejb-name / destination-jndi-name / configuration-name / security-proxy / ejb-ref / resource-ref / /message-driven /enterprise-beans resource-managers resource-manager res-name / res-jndi-name / /resource-manager resource-manager res-name / res-url / /resource-manager /resource-managers container-configurations container-configuration container-name / container-invoker / container-interceptors / instance-pool / instance-cache / persistence-manager / transaction-manager / container-invoker-conf / container-cache-conf / container-pool-conf / commit-option / role-mapping-manager/ authentication-module/ /container-configuration /container-configurations /jboss -- !-- The jboss element is the root element of the jboss.xml file. It contains all the information used by jboss but not described in the ejb-jar.xml file. All of it is optional. 1- the application assembler can define custom container configurations for the beans. Standard configurations
Re: [JBoss-dev] Is Monday still a good 2.4 freeze date
Vesco Claudio wrote: My patches to implement JCA deployment are applied? :-) I thought you were getting RW access and were going to do it yourself? Toby. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
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
RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
We're not making a new FINAL release on Monday, it's a feature freeze for 2.4 BETA. AFAIK, Monday is still ok. -- Juha On Fri, 15 Jun 2001, Vincent Harcq 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
Re: [JBoss-dev] Is Monday still a good 2.4 freeze date
This is just a suprious exception that can easily be cleaned up. Its also just a feature freeze to create the 2.4 branch, not a 2.4 release build as Juha said. The first release on the 2.4 branch will be a beta. - Original Message - From: Vincent Harcq [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 12:20 AM Subject: RE: [JBoss-dev] Is Monday still a good 2.4 freeze date 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
Re: [JBoss-dev] Is Monday still a good 2.4 freeze date
I would have liked to have added the ROWID bit, but don't want to rush it thru! Vinay - Original Message - From: Scott M Stark [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 9:09 AM Subject: Re: [JBoss-dev] Is Monday still a good 2.4 freeze date This is just a suprious exception that can easily be cleaned up. Its also just a feature freeze to create the 2.4 branch, not a 2.4 release build as Juha said. The first release on the 2.4 branch will be a beta. - Original Message - From: Vincent Harcq [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 12:20 AM Subject: RE: [JBoss-dev] Is Monday still a good 2.4 freeze date 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 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
My patches to implement JCA deployment are applied? :-) -Original Message- From: Scott M Stark [SMTP:[EMAIL PROTECTED]] Sent: Friday, June 15, 2001 10:09 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Is Monday still a good 2.4 freeze date This is just a suprious exception that can easily be cleaned up. Its also just a feature freeze to create the 2.4 branch, not a 2.4 release build as Juha said. The first release on the 2.4 branch will be a beta. - Original Message - From: Vincent Harcq [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 12:20 AM Subject: RE: [JBoss-dev] Is Monday still a good 2.4 freeze date 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.ja va:134 ) [Default] [Default] at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerI mpl.ja va: [Default] [Default] at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.jav a: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:5 99) [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:162 8) [Default] [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:152 3) [Default] [Default] at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:489) [Default] [Default] at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:4 67) [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:162 8) [Default] [Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:152 3) [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 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Is Monday still a good 2.4 freeze date
Please send you version of good dtds, I can review them as well. Or better : post them on sourceforge. Thanks. Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Mike Swainston-Rainford Envoyé : vendredi 15 juin 2001 11:46 À : [EMAIL PROTECTED] Objet : 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. 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(RepositorySuppo rt.java:134 ) [Default] [Default] at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanSe rverImpl.ja va: [Default] [Default] at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImp l.java:388) [Default] [Default] at org.jboss.ejb.ContainerFactory.registerContainer(ContainerFactory .java:716) [Default] [Default] at org.jboss.ejb.ContainerFactory.createEntityContainer(ContainerFac tory.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
