October 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: How to outject without @Out annotation

by smendenh＠redhat.com

You can look up the component and automatically create it if it doesn't exist like: MyBean myBean = Component.getInstance("myBean", true); Then set it to whichever context you want via: Contexts.getSessionContext().set("myBean", myBean); The above is not a perfect example, because if the myBean is ScopeType.SESSION, there is no reason to set it again in the Session context. -Samuel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097905#4097905 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097905

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Deployed service statistics

by oskar.carlstedt

Hi! http://repository.jboss.org/maven2/jboss/jbossws-spi/1.0.0.GA/jbossws-spi... //Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097904#4097904 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097904

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Remove variable from page context via Contexts.removeFro

by pete.muir＠jboss.org

n.b. pageContext.set("foo", "bar"); | assert !pageContext.contains("foo"); passes when you are in the INVOKE APPLICATION phase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097903#4097903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097903

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Remove variable from page context via Contexts.removeFro

by pete.muir＠jboss.org

Yes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097901#4097901 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097901

18 years, 8 months

1
0
0 / 0

[JBoss Portal] - Re: Problem with own User Management Portlet

by Soon5

Hy, I found out the source of the Problem. It's because i am using my own EJB with own Hibernate Mapping Classes to write the User data. I reduced the cache-time of the portal, so the Portal-Objects expire, and as i thougt, it works. Is there any command to force a refresh of the Portal-Hibernate Objects, so that I don't have to reduce the cache-time in the ehcache.xml File? Greetings Soon5 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097899#4097899 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097899

18 years, 8 months

1
0
0 / 0

[JBoss Portal] - Re: Problem with own User Management Portlet

by Soon5

Hy, I forgot, DB is Oracle 10g, Portal is Downloaded 2.6.1. Greetings Soon5 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097897#4097897 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097897

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Deployed service statistics

by abdujaparov

Hi Oskar! What are the jar files of that classes and what are the packages? What do I obtain with that classes? Thanks, bye bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097895#4097895 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097895

18 years, 8 months

1
0
0 / 0

[JBoss jBPM] - Re: Timer Task never fired

by Olivier.ch

I put my timer back on my task-node. I have a DBScheduler defined in my jbpm.cfg.xml I didn't have any jobscheduler, i just had this on my jbpm.cfg.xml : | | <bean name="jbpm.job.executor" | class="org.jbpm.job.executor.JobExecutor"> | <field name="jbpmConfiguration"> | <ref bean="jbpmConfiguration" /> | </field> | <field name="name"> | <string value="JbpmJobExector" /> | </field> | <field name="nbrOfThreads"> | <int value="1" /> | </field> | <field name="idleInterval"> | <int value="1000" /> | </field> | <field name="maxIdleInterval"> | <int value="10000" /> | </field> | </bean> | | But doesn't work ... It is a job, but do I have to start it programmaticaly ? How do I do this ... and when do I have to start it, at the beginging of my process instance ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097893#4097893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097893

18 years, 8 months

1
0
0 / 0

[JBoss jBPM] - how to set our jbpm.cfg.xml in classpath

by vishal423

hi, can anybody suggest, how and where to put our jbpm.cfg.xml file in classpath. I am new to eclipse as well as new to jbpm. jbpm-console application always takes default jbpm.cfg.xml file instead of one that i have modified in my project. As per documentation you have to place it in root classpath. But i am not getting how and where to put this file in classpath. looking for a positive reply. regards, vishal View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097892#4097892 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097892

18 years, 8 months

1
0
0 / 0

[JBossCache] - Re: Data gravitation synchronization issue

by FredrikJ

Using 2.1 beta does not solve the problem. I still get timeout exceptions from unsuccesful lock acquisition when enabling buddy replication. JBoss Cache version: JBossCache 'Alegrias' 2.1.0.BETA1[ $Id: Version.java 4592 2007-10-10 16:44:36Z manik.surtani(a)jboss.com $] | .... | JGroups version: 2.6.0 beta-1 | .... | Incoming Thread,TableSpace,172.16.0.5:7500 ERROR jboss.cache.interceptors.TxInterceptor - method invocation failed | org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/5, caller=GlobalTransaction:<172.16.0.7:7500>:1, lock=write owner=GlobalTransaction:<172.16.0.6:7500>:2 (activeReaders=0, activeWriter=Thread[Incoming Thread,TableSpace, | 172.16.0.5:7500,5,Incoming], waitingReaders=0, waitingWriters=0, waitingUpgrader=0) | at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528) | at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:598) | at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:412) | at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:348) | at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:185) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76) | at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76) | at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76) | at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:299) | at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76) | at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:123) | at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76) | at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62) | at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3954) | at org.jboss.cache.CacheImpl._dataGravitationCleanup(CacheImpl.java:3026) | .... | Caused by: org.jboss.cache.lock.TimeoutException: write lock for /5 could not be acquired after 5000 ms. Locks: Read lock owners: [] | Write lock owner: GlobalTransaction:<172.16.0.6:7500>:2 | (caller=GlobalTransaction:<172.16.0.7:7500>:1, lock info: write owner=GlobalTransaction:<172.16.0.6:7500>:2 (activeReaders=0, activeWriter=Thread[Incoming Thread,TableSpace,172.16.0.5:7500,5,Incoming], waitingReaders=0, waitingWriters=0 | , waitingUpgrader=0)) | at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:244) | at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167) | at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097891#4097891 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097891

18 years, 8 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 October 2007