[JBoss jBPM] - Re: Deploying jbpm.war(3.1.3) to jboss as 4.0.5GA
by ngtdave
AH HA! I think that's it.
The problem is the dom4j-1.6.1.jar inside jbpm.war. Once that is removed from the war, you get past the hibernate.cfg.xml problem.
07:17:16,115 INFO [Environment] Hibernate 3.2.0.ga
| 07:17:16,505 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
| 07:17:17,021 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
| 07:17:17,052 INFO [JkMain] Jk running ID=0 time=0/62 config=null
| 07:17:18,021 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 51s:922ms
| 07:17:18,036 INFO [Environment] hibernate.properties not found
| 07:17:18,052 INFO [Environment] Bytecode provider name : javassist
| 07:17:18,083 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling
| 07:17:18,318 INFO [Configuration] configuring from resource: hibernate.cfg.xml
| 07:17:18,333 INFO [Configuration] Configuration resource: hibernate.cfg.xml
| 07:17:18,599 INFO [Configuration] Reading mappings from resource: org/jbpm/graph/action/Script.hbm.xml
| ...
Cool. I will see if there is an existing bug for this, otherwise I will add one.
Dave
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982086#3982086
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982086
19 years
[JBoss Seam] - Re: Use of @Out with JSTL/ui:include
by ekusnitz
Thank you for your replies. With regard to the scope,
I had tried it several ways, but predominantly like this:
@Out(required=false)
private boolean newObject;
What is the default scope for outjection? I couldn't find it in the docs. Furthermore, why wouldn't the expression find it in any scope? And, most important, why it is seen with the h:output and not c:f? I suppose the problem is, like you say, mixing JSF and JSTL. Similar code has worked for us, but I guess, the results are unpredictable, as many say.
I will try wrapping the ui:include in an h:panelGroup. I just wonder why the attribute is not supported. I thought all decendants of ui:component supported it.
I am really mostly concerned with how these things work, rather than just what works and what doesn't.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982083#3982083
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982083
19 years
[JBoss Seam] - Seam GUI development
by esfahan
Hi all,
I am just wondering if anyone can help me with a development related problem. We started our project of with a maven2 build structure as found under http://vyzivus.host.sk/maven2-seam.html. Our structure is looks some how likes (/dvdstore contains the top level parent pom) this:
| /dvdstore
| /dvdstore-ear
| /dvdstore-ejb
| /dvdstore-web
|
Running 'mvn install' in the /dvdstore directory will build all my artifacts and I can deploy my ear file via running 'mvn cargo:start' from within the /dvdstore-ear directory. So far so good, but I think it is a little bit tedious to rebuild the whole ear file all the time even though I just make changes to the GUI. I would like to deploy just the ejbs from within the /dvdstore-ejb directory and then run the webapp from within /dvdstore-web in a maven war:inplace fashion.
I am wondering if anyone has been able to do something like this or if this is actually even possible, eg does using seam imply that I cannot separate the webapp from the ejbs any more?
Thanks for your help.
--Hardy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982082#3982082
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982082
19 years
[JBossCache] - probable bug discovered --- failure acquiring lock
by indrit
Hello,
I have the following problem:
using jboss cache as a simple container for the GT tickets of a CAS server on a cluster based upon WebSphere 6 application server and running on two Solaris machines I'm getting on one of these machines an exception(please see the bottom of this page) when adding a new entry on the cache. I'm using the following config:
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.GenericTransactionManagerLookup</attribute>
| <attribute name="NodeLockingScheme">PESSIMISTIC</attribute>
| <attribute name="IsolationLevel">READ_UNCOMMITTED</attribute>
|
It seems the the code try to synchronise over a QueuedSemaphore object and waits for a notify that never arrives....
Can be this a jboss cache bug (because for some reason maybe a lock over the tree hasn't been released...) ??
The exception is:
ERROR JBossCacheTicketRegistry:50
| - org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/ticket, caller=Thread[WebCon
| tainer : 0,5,main], lock=write owner=GlobalTransaction:<"IP ADDRESS:PORT">:191 (org.jboss.cache.lo
| ck.LockStrategyReadUncommitted@13f82ef)
| org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/ticket, caller=Thread[WebContai
| ner : 0,5,main], lock=write owner=GlobalTransaction:<"IP ADDRESS:PORT">:191 (org.jboss.cache.lock.
| LockStrategyReadUncommitted@13f82ef)
| at org.jboss.cache.Node.acquire(Node.java:407)
| at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.
| java:228)
| at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockIntercepto
| r.java:160)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:32)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:3
| 4)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:345)
| at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:156)
| at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
| at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:157)
| at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5520)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3678)
| at org.jboss.cache.TreeCache.put(TreeCache.java:3616)
| at org.jasig.cas.ticket.registry.JBossCacheTicketRegistry.addTicket(JBossCacheTicketRegistr
| y.java:48)
| at org.jasig.cas.CentralAuthenticationServiceImpl.createTicketGrantingTicket(CentralAuthent
| icationServiceImpl.java:290)
| ......
| ........
| Caused by: org.jboss.cache.lock.TimeoutException: write lock for /ticket could not be acquired afte
| r 10000 ms. Locks: Read lock owners: []
| Write lock owner: GlobalTransaction:<"IP ADDRESS:PORT">:191
| (caller=Thread[WebContainer : 0,5,main], lock info: write owner=GlobalTransaction:
| <"IP ADDRESS:PORT">:191 (org.jboss.cache.lock.LockStrategyReadUncommitted@13f82ef))
| at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:202)
| at org.jboss.cache.Node.acquireWriteLock(Node.java:431)
| at org.jboss.cache.Node.acquire(Node.java:386)
| ... 50 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982080#3982080
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982080
19 years
[JBoss Eclipse IDE (users)] - Re: JBossWS Plugin gen code problem
by mwr0707
And here is the content of ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <ejb-jar id="ejb-jar_1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" version="2.1">
|
| <description><![CDATA[DemoProject generated by eclipse wtp xdoclet extension.]]></description>
| <display-name>DemoProject</display-name>
|
| <enterprise-beans>
|
| <!-- Session Beans -->
| <session id="Session_Power">
| <description><![CDATA[An EJB named Power]]></description>
| <display-name>Power</display-name>
|
| <ejb-name>Power</ejb-name>
|
| <home>com.acme.PowerHome</home>
| <remote>com.acme.Power</remote>
| <local-home>com.acme.PowerLocalHome</local-home>
| <local>com.acme.PowerLocal</local>
| <ejb-class>com.acme.PowerSession</ejb-class>
| <session-type>Stateless</session-type>
| <transaction-type>Container</transaction-type>
|
| </session>
|
| <!--
| To add session beans that you have deployment descriptor info for, add
| a file to your XDoclet merge directory called session-beans.xml that contains
| the <session></session> markup for those beans.
| -->
|
| <!-- Entity Beans -->
| <!--
| To add entity beans that you have deployment descriptor info for, add
| a file to your XDoclet merge directory called entity-beans.xml that contains
| the <entity></entity> markup for those beans.
| -->
|
| <!-- Message Driven Beans -->
| <!--
| To add message driven beans that you have deployment descriptor info for, add
| a file to your XDoclet merge directory called message-driven-beans.xml that contains
| the <message-driven></message-driven> markup for those beans.
| -->
|
| </enterprise-beans>
|
| <!-- Relationships -->
|
| <!-- Assembly Descriptor -->
| <!--
| To specify your own assembly descriptor info here, add a file to your
| XDoclet merge directory called assembly-descriptor.xml that contains
| the <assembly-descriptor></assembly-descriptor> markup.
| -->
|
| <assembly-descriptor id="AssemblyDescriptor_1">
| <!--
| To specify additional security-role elements, add a file in the merge
| directory called ejb-security-roles.xml that contains them.
| -->
|
| <!-- method permissions -->
| <!--
| To specify additional method-permission elements, add a file in the merge
| directory called ejb-method-permissions.ent that contains them.
| -->
|
| <!-- transactions -->
| <!--
| To specify additional container-transaction elements, add a file in the merge
| directory called ejb-container-transactions.ent that contains them.
| -->
|
| <!-- finder transactions -->
|
| <!-- message destinations -->
| <!--
| To specify additional message-destination elements, add a file in the merge
| directory called ejb-message-destinations.ent that contains them.
| -->
|
| <!-- exclude list -->
| <!--
| To specify an exclude-list element, add a file in the merge directory
| called ejb-exclude-list.xml that contains it.
| -->
| </assembly-descriptor>
|
| <ejb-client-jar>DemoProjectClient.jar</ejb-client-jar>
|
| </ejb-jar>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982077#3982077
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982077
19 years