December 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - old RichFaces bug: MethodNotFoundException back?

by beligum

Hi all, When I use "adviseNodeOpened" in a rich:tree component, I end up with a javax.faces.el.MethodNotFoundException: /app/tumbolia/panels/main/space/showSpace.xhtml @198,65 adviseNodeOpened="#{fileSystemManager.adviseFileSystemTreeNodeOpened}": Method not found: FileSystemManagerImpl:3j011-9i11xv-faathdgv-1-faauxftc-h.adviseFileSystemTreeNodeOpened(org.richfaces.component.UITree) The old solution (before RichFaces impl and api were splitted) was to set UseJBossWebLoader to true, but this breaks the mail functionality in Seam. Apparently, there are still issues with this, and I'm planning to post a JIRA-issue, but wanted to check this first. In the Wiki-example build.xml, I'm seeting this comment:  Could this be the reason (the fact that we can't split out the api in the war file just yet) for this exception to be thrown, or am I missing something else? thx, bram View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113335#4113335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113335

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Structure of Seam project for multi client distribution

by jcruise

If your persistence.xml is not in the same archive as your entity classes you might need to explicitly include class elements for the mapped classes e.g. | <jta-data-source>...stuff...</jta-data-source> | | <class>com.myco.model.Role</class> | <class>com.myco.model.User</class> | | <properties>...stuff...</properties> | Cheers J View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113334#4113334 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113334

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: where's the documentation about conversation control(ann

by pete.muir＠jboss.org

http://jira.jboss.com/jira/browse/JBSEAM-1896 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113333#4113333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113333

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: content assist for seam tag library in eclipse

by pete.muir＠jboss.org

It "just works" if you use JBoss Tools :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113332#4113332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113332

18 years, 4 months

1
0
0 / 0

[JBossWS] - How to set username/password in SoapMessage from the webserv

by wtnat

I have a login page, which on login has to call a webservice. The server side handlers will do the authentication in the handleRequest method. How do we set the username/password(entered by the user in the login page) into the SOAPMessage, so that in the serverside handler the handleRequest() method can retrieve username/password from the SOAPMessageContext and authenticate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113331#4113331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113331

18 years, 4 months

1
0
0 / 0

[JNDI/Naming/Network] - Naming problem after upgrade

by eminil

We have been using Tomcat 5.5 along with JBoss 4.0.3RC in the past. It has been working fine. Now we have updated JBoss to 4.2.2. The application works fine when connecting through EJB, but the webapp deployed in Tomcat gets a naming exception when it tries to fetch the EJBs. We have simply copied the ear into the new jboss deploy and set jboss to run with -b 0.0.0.0 Is there anything else that must be done for tomcat to be able to get the access to the ejbs through jndi? I presume it is something in the new jboss configuration that needs to be fixed, since tomcat runs fine with the old jboss 4.0.3... Best regards View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113330#4113330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113330

18 years, 4 months

1
0
0 / 0

[JNDI/Naming/Network] - Re: Multiple database JNDI calls in single EJB

by anacarda

Yep, it doesn't allow JTA transactions. This is fine I think. The datasources are defined within Pentaho, I am just reading about if they use JTA transactions or not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113329#4113329 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113329

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - bug in Seam + JbossWS

by beligum

Hi all, I wanted to check this before submitting it to JIRA: (cross-posted to JbossWS, but got no reply: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=125662) I don't really know where to post this, but I guess it's more WS-related than it is Seam-related. Here's the issue: When I start an (ear) application, and nobody went to the website, before a remote login()-webserviceservice is contacted (which uses the seam Identity component to login), I always get an error that the security.drl file couldn't be found. Though, when I try to do this after someone visited the site (and security.drl) was loaded appropriately, everything is ok. It seems like the initialization of the security-rules is something the webservice-integration (in Seam) isn't able to do? Here's the stacktrace: | 13:39:56,432 INFO [RuleBase] parsing rules: security.drl | 13:39:56,472 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | javax.ejb.EJBException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: | org.jboss.seam.security.identity | at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor | .java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.jav | a:77) | at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationIntercepto | r.java:110) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:1 | 06) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:1 | 03) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:414) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123 | ) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j | ava:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j | ava:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja | va:179) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java: | 157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja | va:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.se | am.security.identity | at org.jboss.seam.Component.newInstance(Component.java:1962) | at org.jboss.seam.Component.getInstance(Component.java:1865) | at org.jboss.seam.Component.getInstance(Component.java:1844) | at org.jboss.seam.Component.getInstance(Component.java:1821) | at org.jboss.seam.Component.getInstance(Component.java:1816) | at org.jboss.seam.security.Identity.instance(Identity.java:160) | at com.acepostproduction.tumbolia.webservice.SecurityServiceImpl.getAllSpaces(SecurityServic | eImpl.java:56) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) | at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) | at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:44) | at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) | at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) | at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) | at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:4 | 2) | at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) | at org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyI | nterceptor.java:26) | at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) | at org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSession | ProxyInterceptor.java:27) | at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) | at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) | at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java: | 50) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118) | at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor | .java:63) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedE | ntityManagerInterceptor.java:54) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | ... 39 more | Caused by: java.lang.IllegalStateException: could not locate rule file: security.drl | at org.jboss.seam.drools.RuleBase.compileRuleBase(RuleBase.java:51) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) | at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) | at org.jboss.seam.Component.callComponentMethod(Component.java:2074) | at org.jboss.seam.Component.callCreateMethod(Component.java:1997) | at org.jboss.seam.Component.newInstance(Component.java:1968) | at org.jboss.seam.Component.getInstance(Component.java:1865) | at org.jboss.seam.Component.getInstance(Component.java:1832) | at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) | at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) | at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) | at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) | at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) | at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) | at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) | at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112) | at org.jboss.seam.Component$ELInitialValue.getValue(Component.java:2352) | at org.jboss.seam.Component.initialize(Component.java:1381) | at org.jboss.seam.Component.instantiateJavaBean(Component.java:1307) | at org.jboss.seam.Component.instantiate(Component.java:1260) | at org.jboss.seam.Component.newInstance(Component.java:1958) | ... 75 more | I guess this is important enough to post a jira-issue, but maybe I'm doing something wrong, so I'm checking with others first. Comments? bram View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113328#4113328 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113328

18 years, 4 months

1
0
0 / 0

[Clustering/JBoss] - Re: Setting up multiple instances of JBoss in different mach

by shoeb1981

This is fairly simple. You start your server with the partition name (check out jboss manual for partition name variable to be used at the time of server start up, you might need to modify you run.bat/sh file also. You may also need to specify the mcast address the same way you would do the partition name. Start the server on all machines. They will form the cluster. To really take the advantage of the clustering, you might need to change the way you call components on the server from the client. If you have not changed the Ha-jndi port of the server, you would specify the server url from within your client, like this: String url="jnp://host1:1100/,jnp://host2:1100,....."; View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113327#4113327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113327

18 years, 4 months

1
0
0 / 0

[JBoss Portal] - Why loglevel ERROR for CMS resource access denied?

by roth

Hi One thing I was wondering for quite some time is why that "org.jboss.portal.cms.CMSException: Access to this resource is denied" actually is an exception. Isn't "access denied" to some cms resource a quite common event, that shows up during normal portal use? In my opinion, exceptions are only warranted for things that are outside of normal operation and they shouldn't be misused for 'normal', non-errorneous (btw, is that spelled correctly?) flow control. Thanks, Tobias View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113325#4113325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113325

18 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2007