Scratch jboss-annotations-ejb3.jar, thats too obvious. :-)
Looks like they are in jboss-ejb3x.jar
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916788#3916788
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916788
--
hibernate-annotations.jar only pertains to hibernate annotations and the
overlap with EJB3 entities.
Based on the JBoss EJB3 download, I am assuming the EJB3 annotations are in
jboss-annotations-ejb3.jar.
I was under the impression that JBoss 4.0.3 came with EJB3 preinstalled.
However, it do
I've looked at both JBoss and Hibernate source, and I am thinking the quick
answer is NO. At least in JBoss 4.0.3.
Currently, the JBoss Hibernate MBean uses a Configuration object to initialize
the session factory. In order to support annotations, it will need to use an
AnnotationConfiguration
If I want to use annotations in Hibernate, and still use JBoss' Hibernate mbean
for the session factory, how do I configure the factory to know about the
annotated classes?
In the Hibernate docs, this is done via modifications to the session in
HibernateUtil before the session is built, or via
Hello,
I'm getting a NoClassDefFoundError when trying to deploy an EAR on
4.0.3. I've pruned the EAR down to one component, the EJB JAR causing
the problem.
Of course, the EAR deploys fine on JBoss 3.2.6.
The class in question is present in one of the included jars in the
META-INF/lib directory
Just looked up the bug#, its 1038696
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854146#3854146
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854146
---
This SF
Hi Adini,
What version of JBoss are you using? I believe this is fixed in the nightlies for both
3.2.6 and 4.0. (I believe). I logged a bug against this very issue, and it has since
been marked as fixed.
If you wish to know more, search this forum (good luck, the search stinks) or head
over to
Is there a way to specify row-locking at anything but the entity level?
I would like to set row-locking on a per finder/select basis. However, it appears that
if you turn this on, you turn it on for all finders/selects for the given entity.
Thanks, Craig.
View the original post :
http://www.jbo
Thanks Tim, good point.
But I don't think that is the problem. I am using the xdoclet ejb.finder tag, and it
appropriately wraps the query entry (ejb-ql element) as a CDATA section.
I am getting a parser error much like the one I would see from the EJB-QL 2.0 compiler
used in 3.2.3. The parser
If so, it seems to barf on string comparisons other than the equality tests available
in EJB-QL 2.0.
That is, <|>|<=|>= don't seem to be supported. Is that true, or have I screwed
something up?
Thanks, Cc.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=38496
anonymous wrote : query = "SELECT OBJECT(p) FROM Tag p WHERE p.Parent.id = ?1"
My guess is that the p.Parent.id should read: p.parent.id following bean naming
patterns. Your setter/getter reads getParent()/setParent() so the attribute name is
'parent' with a lowercase 'p'.
-Craig.
View the o
11 matches
Mail list logo
