[jboss-user] [EJB 3.0] - Re: Couldn't handle invocation directly within...StatelessRe

Wow! two replies @jaikiran jaikiran, thanks for your response. You are right that they are just debug messages. The only real error (Please ignore the trinidad error, further down) is in the following line: | 2009-02-13 15:19:25,750 ERROR [com.xxxxxxxx.xxxx.web.bean.AbstractDocumentPageBean] (http-localhost%2F127.0.0.1-8080-2) Exiting createButton_action : Unexpected error when creating Document. | If I may refer you back to "JSf Backing beans: AbstractDocumentPageBean, Package: web.war" above, this error is generated in the [try] catch. The issue--as I see it but you might tell me otherwise--is that "getDocumentManager().createEntity(bean)" is not accessed. If it did, I would see in the jboss log the following: "Entering createEntity" And I thought this might be related to the "Couldn't handle invocation directly within...StatelessRemoteProxyInvocationHandler" messge--I don't know. Thanks jaikiranfor any further suggestions. | 2009-02-13 15:19:24,264 DEBUG [org.jboss.ejb3.proxy.handler.ProxyInvocationHandlerBase] (http-localhost%2F127.0.0.1-8080-2) Couldn't handle invocation directly within org.jboss.ejb3.proxy.handler.session.stateless.StatelessRemoteProxyInvocationHandler@142cbba: Current invocation "public abstract com.xxxxxxxx.xxxx.entity.model.DocumentEntity com.xxxxxxxx.xxxx.ejb.intf.DocumentService.createEntity(com.xxxxxxxx.xxxx.entity.model.DocumentEntity) throws com.xxxxxxxx.xxxx.dao.exception.DAOException" is not eligible for direct handling by org.jboss.ejb3.proxy.handler.session.stateless.StatelessRemoteProxyInvocationHandler@142cbba | 2009-02-13 15:19:24,317 DEBUG [org.jboss.ejb3.proxy.invocation.InvokableContextStatefulRemoteProxyInvocationHack] (http-localhost%2F127.0.0.1-8080-2) Received invocation request to method com.xxxxxxxx.xxxx.ejb.intf.DocumentRemote: com.xxxxxxxx.xxxx.ejb.intf.DocumentService.createEntity(com.xxxxxxxx.xxxx.entity.model.DocumentEntity); using hash: 5676740933045534775 | 2009-02-13 15:19:25,140 DEBUG [org.jboss.ejb3.stateless.StatelessContainer] (http-localhost%2F127.0.0.1-8080-2) Received dynamic invocation for method with hash: 5676740933045534775 | 2009-02-13 15:19:25,750 ERROR [com.xxxxxxxx.xxxx.web.bean.AbstractDocumentPageBean] (http-localhost%2F127.0.0.1-8080-2) Exiting createButton_action : Unexpected error when creating Document | 2009-02-13 15:19:25,897 DEBUG [javax.enterprise.resource.webcontainer.jsf.context] (http-localhost%2F127.0.0.1-8080-2) Adding Message[sourceId=<<NONE>>,summary=Unexpected error when creating Document) | 2009-02-13 15:19:25,899 DEBUG [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost%2F127.0.0.1-8080-2) No navigation rule found for null outcome and viewId /pages/document/new.jspx Explicitly remain on the current view | 2009-02-13 15:19:25,899 DEBUG [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-localhost%2F127.0.0.1-8080-2) Exiting InvokeApplicationsPhase | 2009-02-13 15:19:25,900 DEBUG [javax.enterprise.resource.webcontainer.jsf.timing] (http-localhost%2F127.0.0.1-8080-2) [TIMING] - [1755ms] : Execution time for phase (including any PhaseListeners) -> INVOKE_APPLICATION 5 | 2009-02-13 15:19:25,901 DEBUG [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-localhost%2F127.0.0.1-8080-2) render(org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit@3b474f) | 2009-02-13 15:19:25,901 DEBUG [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-localhost%2F127.0.0.1-8080-2) Entering RenderResponsePhase | 2009-02-13 15:19:25,902 DEBUG [javax.enterprise.resource.webcontainer.jsf.lifecycle] (http-localhost%2F127.0.0.1-8080-2) About to render view /pages/document/new.jspx | 2009-02-13 15:19:25,905 ERROR [STDERR] (http-localhost%2F127.0.0.1-8080-2) Feb 13, 2009 3:19:25 PM org.apache.myfaces.trinidadinternal.skin.SkinFactoryImpl getSkin | WARNING: Can't find a skin that matches family xxxx-skin and renderkit org.apache.myfaces.trinidad.desktop, so we will use the simple skin | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- @Wolfgang Knauf Wolfgang Knauf, thanks for your reply. Yes "getDocumentManager() is the getter method for the 'documentManager." I did not include it in my post to save space. DocumentService is a super class of "DocumentRemote" I have something like the following: | import com.xxxxxxxx.xxxx.entity.model.DocumentEntity; | | /** | * The DocumentService interface. | */ | interface DocumentService extends java.io.Serializable{ | public DocumentEntity createEntity(DocumentEntity bean) | ... | | } | | public interface DocumentRemote extends DocumentService, java.io.Serializable{ | ... | } | | public interface DocumentLocal extends DocumentService, java.io.Serializable{ | ... | } | | Please note that DocumentService, DocumentRemote and DocumentLocal and packaged in an ejbclient.jar--seperate from their implementation class i.e.,DocumentController. Also the jpa e.g. DocumentEntity and persistence.xml is package called entity.jar as plain POJO I therefore have | xxx.ear | ----lib/ejbclient.jar [contains DocumentService, DocumentRemote and DocumentLocal] | ----lib/entity.jar [contains DocumentEntity, persistence.xml] | ----ejb.jar [contains DocumentController ] | ----web.war [contains AbstractDocumentPageBean jsf pages etc] | Thanks Wolfgang Knauf for any further suggestions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209955#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...