So the problem was caused by using log4j in the interceptor classes. Should
have done a global search I don't know why I thought it was in the 2 SFSB's
somehow...
However, when I replaced the log4j with Seam log I was getting
NullPointerException:
@Name("loggerInterceptor")
| public class L
http://jira.jboss.org/jira/browse/JBSEAM-2354
I attached the xhtml, SFSB implementation class and local interface. Only
thing is the em.createQuery is based on MS SQL server data.
Exception occurs with or w/o the Seam logger and with or w/o injecting the
session-scoped SFSB. thx.
View the or
You stated "Please attach a runnable example with step by step instructions to
reproduce so we can take a look." in
http://jira.jboss.org/jira/browse/JBSEAM-2256
In this case, the use case/app is dependent on data (via JPA entities) in SQL
server db as well as using NTLM authentication. That m
"[EMAIL PROTECTED]" wrote : You will get an exception.
|
| If you can put something simple together that reliably shows this, then
create a jira issue and we can take a look.
I'm not sure exactly what the root cause is here so I'm not sure I can put
together a simple example. I tried to in
"[EMAIL PROTECTED]" wrote : You will get an exception.
|
| If you can put something simple together that reliably shows this, then
create a jira issue and we can take a look.
why will I get the exception? And are you talking about the
InstantionException specifically?
View the original po
You will get an exception.
If you can put something simple together that reliably shows this, then create
a jira issue and we can take a look.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109636#4109636
Reply to the post :
http://www.jboss.com/index.html?
"[EMAIL PROTECTED]" wrote : "asookazian" wrote : Is it safe to assume, then,
that @In(create=true) will only instantiate a session-scoped SFSB once per
session from a conversation-scoped SFSB as long as it is not destroyed somehow
or nulled after the first instantiation?
|
| Yes.
|
| P
more curious behavior today...
09:29:45,317 INFO [LoggerInterceptor] *** Entering method: destroy
| 09:29:45,317 INFO [Manager] destroying conversation with garbage lock: 4
| 09:29:45,317 INFO [SecurityAuditAction] in preDestroy
| 09:29:45,317 WARN [Component] Exception calling component
package com.cox.beans.session;
|
| import java.util.ArrayList;
| import java.util.Calendar;
| import java.util.GregorianCalendar;
| import java.util.List;
|
| import javax.annotation.PostConstruct;
| import javax.annotation.PreDestroy;
| import javax.ejb.PostActivate;
| import
"asookazian" wrote : Is it safe to assume, then, that @In(create=true) will
only instantiate a session-scoped SFSB once per session from a
conversation-scoped SFSB as long as it is not destroyed somehow or nulled after
the first instantiation?
Yes.
Post the *whole* source of the SecurityAuditA
10 matches
Mail list logo
