how do you use an object in the uniqueconstraint configuration? i want the
unique constraint to be based on the user-entity's id and the name column. is
this possible with this attribute?
| @Entity
| @Table(name = "x",
| uniqueConstraints = [EMAIL PROTECTED](columnNames={"user.name"
i'm using 4.0.4.GA now with no issues and i found the answer i was looking for
by updating my persistence.xml properties with the correct flush modes: auto
and commit.
|
| java:/MySqlDS
|
|
|
|
|
|
|
|
|
View the original po
this worked like a charm for me...except i'm using 4.0.4.GA and there is no
conf/jboss-service.xml file that has a naming section and call by attribute...
so instead find the settings in the
$jboss-home/server/default/deploy/naming-service.xml file.
i was able to leave call-by-value=false in b
i updated the /default/deploy/ejb.deployer/Meta-inf/persistence.xml file based
on the release notes for 4.0.4.cr2 but it doesn't change the setting. my ejb3
app works great on 4.0.4.rc1 and shows flush=enabled but now after upgrade it
won't write to the db (flush) and my server startup output s
figured it out... i simply removed the 'resourceRef' property from the
JNDIObjectFactory bean config!!!
according to the spec about resource ref: it adds the java:comp crap at the
beginning of the jndi lookup, no wonder it couldn't find the beans.
anonymous wrote : resourceRef - if the lookup o
asack, thanks for the hint for the spring deployer...i'll check it out, will it
work with struts action injection using the plugin in struts-config.xml?
|
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932311#3932311
Reply to the po
looks i didn't look down into the root exception: NameNotFoundException, do i
need to prefix this if using spring, here is a snippet of the global jndi
listing also...
thanks.
| 21:12:35,456 WARN [RequestProcessor] Unhandled Exception thrown: class
java.lang.reflect.Undec
| laredThrowab
anyone?
no one has run into this? come on... i don't believe it.
i've been thru all of the tutorials and trailblazers, this is not complex but
the client lookup just doesn't work for a stateful session bean...
i found another posting on the wiki site that talks about classcastexception
for mu
since i can't use @ejb yet, and i don't want to litter the initial context
throughout my code (old school), i figured i'd use spring to wire my ejb3
stateless session bean to my action but i just get the following error:
| 23:46:21,310 ERROR [[action]] Servlet.service() for servlet action th
update: upgraded to 4.0.4RC1 and i get the same classcast exception! doh!
anyone have any ideas? should i be getting a statefulproxyfactory first since
that is what is loaded into jndi?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931749#3931749
Reply to t
sorry but here is some additional info:
1. using ejb3
2. i did notice that the trailblazer works with 4.0.4 only, but my question
still stands, why can't i lookup the stateful session bean?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931746#3931746
Reply
based on the trailblazer online examples, i setup a super simple stateless
session bean (TestSLSB) and a stateful session bean(TestSFSB). note: using
jboss 4.0.3sp1.
they both show up in the jndi output, and the stateless works like a champ, but
the stateful keeps throwing classcast exceptions
12 matches
Mail list logo
