We have used JBoss basically for controlling satellite broadact equipment for
digital tv. Usually the problem lied in stability of software runing on
equipment itself.
There are several factory you want to consider before making your decision:
You are not allowed to use native code in J2EE;
You
"svadu" wrote : "WebSel" wrote : For the XDoclet users here's my 5$
| |
| | This is the finder in jboss
| |
| |
| | |
| | | * @jboss.query
| | | * query="SELECT OBJECT(o) FROM Person o WHERE LCASE(o.lastName) =
"WebSel" wrote : For the XDoclet users here's my 5$
|
| This is the finder in jboss
|
|
| |
| | * @jboss.query
| | * query="SELECT OBJECT(o) FROM Person o WHERE LCASE(o.lastName) =
LCASE(?1) ORDER BY o.foreName"
| | * signature="java.util.Collection
findByIn
"loubyansky" wrote : To workaround cascade-delete problem use
http://www.jboss.org/wiki/Wiki.jsp?page=BatchCascadeDelete
Looks nice, but I am getting an exception while trying to delete a bean (I would like
to notice that it works without batch cascade delete and without "NOT NULL"
constraint):
insert-after-ejb-post-create will not work if you use container generated primary keys
(like autoincrement) because orimary key must be known before you set the relationship.
And youwill have problems during cascade deletes anyway because when the bean is about
to be removed it will get cmr fiel
