Hi!
> 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
All good so far. We need to update the EJX GUI to use the above though, which is some
work.
> - 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 will make it impossible to use the "findByX" pattern I'm afraid, since those
finders are done by comparing primary key values. I'm afraid this is a very bad idea,
and propose that it is changed back.
In addition, the handle contains server name information, so if the server changes the
entire database would break, which is not a good thing.
These are the core reasons I coded JAWS to use the primitive fields of the PK's in the
first place.
The first changes are ok, but I think it will make the EJX GUI even more out of date,
and it is sad that our users will not have that as a viable option to deploy since it
makes it much simpler IMHO. (heck, even I use the EJX GUI as much as possible for
deployment information editing)
/Rickard
