(1 possible bug detected and 2 issues I cam having)
Just to let you know that there seems to be a bug in JBoss 3 beta.
It seems to ignore me trying to force the naming of cmr-field (foreign key) columns in the database.
Originally I let JBoss handle the naming itself. In Alpha it chose something like "interest_interestpk" as the name, where "interest" is a CMR field to InterestLocal. This was ok.
I have switched to JBoss beta because of problems with EJB-QL in alpha. It now names the column as "interest". The problem I had with this was the fact that the database I am creating is sometimes accessed by people using the alpha version (we haven't all made the switch yet). So I decided to force the mapping by modifying the jbosscmp-jdbc.xml file (and jaws.xml - I'm making the two identical atm... which I still have to correct and find out what I AM SUPPOSED to do, but that's another days work). This had no effect in Beta but when I tried it on Alpha it worked ok.
Therefore I think the foreign key mapping is broken in JBoss beta. I will try in on the latest CVS version if I have time.
Another issue I have is that the beta version does not like the following ejb-ql syntax, can anybody see a reason for this?
FROM MemberEJB AS m,
IN( m.interests ) AS mi
WHERE m.memberPk = ?1 AND mi.interest = ?2
- interests is a cmr field setup as a Set of MemberInterests
- Method call is:
public abstract Set ejbSelectMemberInterest(Integer memberPk, InterestLocal interest) throws FinderException;
The beta version seems a little less stable to me than the alpha version. Not so much in continuous runtime, but when an application is being redeployed. Sometimes it will just bomb out when attempting to redeploy the new application. It also requires that "tmp" be cleared out before restarting the server. Has anyone else experienced this?
How long before another, more stable, beta release... or even final release? Any ideas?
Many thanks and all the best,