[JBoss Seam] - Re: Ajax¤JSF with Seam
by gus888
I got a feedback from the Ajax4jsf developer as follows for the exception when using Ajax4jsf + Seam, maybe it is helpful for Seam integration with Ajax4jsf in future:
anonymous wrote : Date: Thu, 13 Jul 2006 10:29:56 +0400
| From: Alexander Smirnov <asmirnov(a)exadel.com>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Subject: Cannot run ajax4jsf on Seam
|
|
| It's problem from JBOSS ClassLoader configuration - see
| http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingOverview .
| We use apache commons-degetester for got web application configuration
| details, and this message mean that class for store filter
| configuration can't be loaded by degitester. See Jboss wiki for possible
| workaroutd, I thing that You must turn web-app classloading from
| JBOSS-specific to JEE spec - see jboss-service.xml for embedded tomcat.
| I will be made sample application and provide detail instructions.
The exception which I got is reposted again as below:
java.lang.ClassNotFoundException: No ClassLoaders found for: org.ajax4jsf.framework.util.config.FilterBean
| at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
| at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
| at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java :204)
| .......
Thank you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957904#3957904
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957904
19 years, 9 months
[EJB/JBoss] - When is the optimistic lock check done?
by sdawson
Hello,
I have a question regarding when an optimistic lock check is performed. As per the EJB 3.0 specification, when we attempt to merge a detatched entity that has a stale version, the exception is thrown. However, consider the following case:
| @TransactionAttribute(value = TransactionAttributeType.REQUIRED)
| public void versionTest(Long id, String value) {
| DbSample sample = entityManager.find(DbSample.class, id);
| id.setValue(value);
| entityManager.flush();
| }
|
(where DbSample is an entity bean with a @Version property)
Now, consider the following set of events:
Client A calls versionTest(1, "ClientA") and a breakpoint is set after the sample is fetched
Client B calls versionTest(1, "ClientB") and a breakpoint is set after the sample is fetched
Client B is allowed to continue its transaction and commit.
Client A is then allowed to continue its transaction and commit.
Instead of an optimistic lock exception being thrown, the result is that the value "ClientB" is saved to the database, and the version is incremented by 1. The ClientA method call seems to be silently ignored despite committing last.
Is this the expected behaviour? The EJB 3.0 specification states that the optimistic lock check is supposed to be done at transaction commit time. This seems like a bug. Thoughts?
-Sean
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957902#3957902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957902
19 years, 9 months
[Management, JMX/JBoss] - How to make my service wait for port 1099 to come up?
by yantriki
I have the following dependencies in the jboss-service.xml file.
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=invoker,type=jrmp</depends>
| <depends>jboss:service=invoker,type=http,target=Naming</depends>
|
but the service, where I am registering an object in the naming service fails to start during boot because it's start lifecycle method is getting called even before the port 1099 is created.
Appreciate any insight.
Regards
Vivek
| Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
| at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
| at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
| ... 101 more
| Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
| at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
| ... 102 more
| Caused by: java.net.ConnectException: Connection refused: connect
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957899#3957899
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957899
19 years, 9 months