I'll give that a try.. On that note, what is a way to debug these kind
of messages:
javax.naming.NameNotFoundException: Name "UserFacadeLocal" not found.
As in, how can I see what names are registered?
On 09/17/2012 03:25 PM, Romain Manni-Bucau wrote:
hmm
i saw some exception swallowed some days before, i think it is fixed on
trunk and in the branch we'll use for the release but not sure it is
deployed.
another check you can do is to valid your datasource config through JMX
if not please share a sample (mvn project is perfect) to let us reproduce
the issue
*Romain Manni-Bucau*
*Twitter: @rmannibucau*
*Blog: http://rmannibucau.wordpress.com*
2012/9/17 David Nordahl <da...@thinkology.org>
At last I have faces deploying, but the persistence link isn't there and
I'm not getting any error messages that I can find regarding why. Attached
is the startup log which includes the messages returned when trying to add
an entity through a faces form.
It seems like db access or the persistence module is simply not working,
but I don't see anything in the startup log, and the only thing it says
trying to run the faces form is 'null', and that's only on log level fine.
From a previous thread, it seemed that me and another user both
experienced that an unsupported annotation attribute (in our case
@Basic(optional=false) in an EJB was able to mysteriously cripple
functionality with no corresponding error messages anywhere. Has this issue
been addressed or does a bug report need to be created? After regenerating
my ejbs with a lot more DB attributes and constraints in place there are a
lot more kinds of annotations and attributes than I had before.
