[JBoss Seam] - java.lang.NoClassDefFoundError: net/sf/ehcache/CacheExceptio
by fady.matar
I'm using the CVS version of seam currently at 1.3.0.ALPHA, and I'm using seam-gen to reverse engineers cruds from the database. I'm sure that the setup is proper since I'm pretty familiar with it and generated a number of applications since version 1.0
Now the thing is that I'm getting the following exception when I'm reversing the code from the database:
| $ ./seam.bat generate-entities
| Buildfile: d:\workspace\src\java\jboss\jboss-seam-1.3.0.ALPHA\seam-gen\build.xml
|
| validate-workspace:
|
| validate-project:
|
| generate-entities:
| [hibernate] Executing Hibernate Tool with a JDBC Configuration (for reverse engineering)
| [hibernate] 1. task: hbm2java (Generates a set of .java files)
| [hibernate] log4j:WARN No appenders could be found for logger (org.hibernate.cfg.Environment).
| [hibernate] log4j:WARN Please initialize the log4j system properly.
|
| BUILD FAILED
| java.lang.NoClassDefFoundError: net/sf/ehcache/CacheException
|
| Total time: 2 seconds
|
| fady.matar@grouch /cygdrive/d/workspace/src/java/jboss/jboss-seam-1.3.0.ALPHA
|
Any hint on how to solve this? Is it the ehcache.jar that's missing?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051753#4051753
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051753
19Â years
[Clustering/JBoss] - Re: setting up cluster on JBoss 4.2.0 GA (messaging conflict
by mohali
Some more information on the error. I am not sure if it is service name conflict issue as I mentioned in my previous message. The whole error is:
| 09:47:56,908 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
|
| --- MBeans waiting for other MBeans ---
| ObjectName: jboss.messaging.connectionfactory:service=ConnectionFactory
| State: CONFIGURED
| I Depend On:
| jboss.messaging:service=ServerPeer
| jboss.messaging:service=Connector,transport=bisocket
| jboss.messaging:service=PostOffice
|
| ObjectName: jboss.messaging.connectionfactory:service=NonClusteredConnectionFa
| ory
| State: CONFIGURED
| I Depend On:
| jboss.messaging:service=ServerPeer
| jboss.messaging:service=Connector,transport=bisocket
| jboss.messaging:service=PostOffice
|
| ObjectName: jboss.messaging:service=ServerPeer
| State: CONFIGURED
| I Depend On:
| jboss.messaging:service=PersistenceManager
| jboss.messaging:service=JMSUserManager
| jboss.messaging:service=Connector,transport=bisocket
| Depends On Me:
| jboss.messaging.connectionfactory:service=ConnectionFactory
| jboss.messaging.connectionfactory:service=NonClusteredConnectionFactory
| jboss.messaging:service=Bootstrap
| jboss.jca:service=ManagedConnectionFactory,name=JmsXA
|
| ObjectName: jboss.messaging:service=Bootstrap
| State: CONFIGURED
| I Depend On:
| jboss.messaging:service=ServerPeer
|
| ObjectName: jboss.jca:service=TxCM,name=JmsXA
| State: CONFIGURED
| I Depend On:
| jboss.jca:service=ManagedConnectionPool,name=JmsXA
| jboss.jca:service=CachedConnectionManager
| jboss.security:service=JaasSecurityManager
| jboss:service=TransactionManager
| Depends On Me:
| jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
|
| ObjectName: jboss.jca:service=ManagedConnectionPool,name=JmsXA
| State: CONFIGURED
| I Depend On:
| jboss.jca:service=ManagedConnectionFactory,name=JmsXA
| Depends On Me:
| jboss.jca:service=TxCM,name=JmsXA
|
| ObjectName: jboss.jca:service=ManagedConnectionFactory,name=JmsXA
| State: CONFIGURED
| I Depend On:
| jboss.messaging:service=ServerPeer
| jboss.jca:service=RARDeployment,name='jms-ra.rar'
| Depends On Me:
| jboss.jca:service=ManagedConnectionPool,name=JmsXA
|
| ObjectName: jboss.jca:service=ConnectionFactoryBinding,name=JmsXA
| State: CONFIGURED
| I Depend On:
| jboss.jca:service=TxCM,name=JmsXA
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.messaging:service=PersistenceManager
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.messaging:service=ServerPeer
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051749#4051749
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051749
19Â years
[Clustering/JBoss] - setting up cluster on JBoss 4.2.0 GA (messaging conflict)
by mohali
I am setting up the cluster of two nodes on windows XP but having problems starting up even a single node. I have taken the base server/all configuration as the starting point and adding on my application specific configuration to it. I have also added JBoss messaging (1.2.0 GA) to it (instead of using default jms which lacks clustering support). Now that seems to conflicts with jms which is installed with all configuration that seems to be used for clustering (not sure). Currently I am getting the following error:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging:service=PersistenceManager
State: NOTYETINSTALLED
Depends On Me:
jboss.messaging:service=ServerPeer
Seems like this may be because there is a PersistenceManager defined in JBoss messaging and also in deploy-hasingleton/jms that comes with server/all config. So my question is What, if it all can I strip off from messaging components/services in server/all configuration so that it does not conflict with JBoss messaging or is it just a matter of changing the service names like PersistenceManager in this case?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051744#4051744
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051744
19Â years
[Management, JMX/JBoss] - Parsing a deployment descriptor
by sergeypk
Is there a class I could use to parse a deployment descriptor such as the one below? I need to get the attribute values programmatically (for testing purposes).
Thanks,
Sergey
<server>
|
| <!-- Standard bisocket connector - the bisocket transport only opens connection from client->server
| so can be used with firewalls where only outgoing connections are allowed.
| For examples of HTTP and SSL transports see docs/examples -->
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.messaging:service=Connector,transport=bisocket"
| display-name="Bisocket transport Connector">
| <attribute name="Configuration">
| <config>
| <invoker transport="bisocket">
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| ...
| </invoker>
| </config>
| </attribute>
| </mbean>
| </server>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051740#4051740
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051740
19Â years