For those that are not on jaws. Sorry for the cross post. Thank you Sebastien, yet another kick ass fix regards marc -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Sebastien Alborini Sent: Friday, September 08, 2000 8:20 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [JAWS] New jaws metadata package Hi! I've just checked in the new jaws metadata package. New features: - as for jboss.xml, you now only provide in jaws.xml what is specific to your configuration. No need to paste all the type mappings any more. - the default behavior of jaws is now stored in a <default-entity> section in standardjaws.xml (suggestion from Nils Hartmann). You can override this <default-entity> section in jaws.xml. For example, if you want to drop the tables of all your beans at undeployment, just add a jaws.xml file with <default-entity> <remove-table>true</remove-table> </default-entity> - deployment should show better error messages, and less SQL NPE - jaws now stores ejb-references by serializing their handle. (from the javadoc: "A handle is intended to be used as a "robust" persistent reference to an EJB object.", so let's use it!) The previous behavior used the jaws metadata of the primary key of the referenced entity, which meant you could only store jaws-managed CMP entities from the same application unit on the same server, which was sort of a limitation. This has not been heavily tested (though testbeans work, and storage of ejbreferences on Hypersonic as well), so please report any bugs. A DTD for jaws.xml, plus howtos, will be provided soon. IMPORTANT NOTE: now your type-mappings updates should go to src/resources/org/jboss/ejb/plugins/jaws/metadata/standardjaws.xml Enjoy, Sebastien -- This is the JAWS mailing list. Please send email to '[EMAIL PROTECTED]' with the command 'unsubscribe jaws [email@address]' in the body of the mail to be removed from this list.
