January 2008 - jboss-user - Jboss List Archives

by tom_goring

Hi, I have a simple page flow and want to know how to link to it from another page. I do not want to reference the start page but the page flow. All the examples I can see link using the start page (for me that will be determined when the flow starts). I.e. I want to do something like: | .. some other page... | <s:button value="New Starter" pageflow="ContractorJoinWizard"/> | | <pageflow-definition | xmlns="http://jboss.com/products/seam/pageflow" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://jboss.com/products/seam/pageflow http://jboss.com/products/seam/pageflow-2.0.xsd" | name="ContractorJoinWizard"> | | <start-state name="Start"> | <transition to="JoinWizardPickScheme"></transition> | </start-state> | | <start-page name="JoinWizardPickScheme" view-id="/contractor/JoinWizardPickScheme.xhtml"> | <redirect/> | <transition name="next" to="JoinWizardComplete"/> | <transition name="cancel" to="JoinWizardComplete"></transition> | </start-page> | | <page name="JoinWizardComplete" view-id="/contractor/JoinWizardComplete.xhtml"> | <end-conversation/> | <redirect/> | </page> | | </pageflow-definition> | Thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117139#4117139 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117139

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: JBOSS Seam 2.0.0.GA and the latest JSF RI -- Stack over

by hvram

Solved the problem. I was using the HEAD of the SUN JSF-RI and I guess people are still checking the code since I saw a lot of UnSupportedMethod Exception being throws delberately . I used the last tagged version and things are fine Thanks Regards Hari View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117138#4117138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117138

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Seam transaction problem (maybe unclear)

by pete.muir＠jboss.org

1) Extend the transaction timeout Transaction.instance().setTransactionTimeout(100000000); 2) Control the transaction manually View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117132#4117132 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117132

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Calling the same method on different beans from the same

by pete.muir＠jboss.org

You outject this, which isn't managed. The normal approach here is to pass the correct manager name into the xhtml fragment <ui:include ...> | <ui:param name="manager" value="#{auditOrderManager}" /> | </ui:include> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117131#4117131 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117131

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: CAsh Config (where to find the annotation ??

by pete.muir＠jboss.org

That annotation comes from the JBoss EJB3 implementation. Try asking on the EJB3 forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117129#4117129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117129

18 years, 3 months

1
0
0 / 0

[JBoss Messaging] - Re: MDB and clustered Topics

by jduty

THanks for the quick reply Tim. I guess a better description of what I'm using is a clustered durable subscription. In that case, would only one receive the message? On another note I do need a topic because on each node I have multiple MDBs, all subscribing to different clustered durable subscriptions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117128#4117128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117128

18 years, 3 months

1
0
0 / 0

[JBossCache] - Re: Buddyrep issue

by FredrikJ

I tried a snapshot build from SVN (revision 4982) but the result is still the same . Actually I was not entirely accurate in the sequence description. It should be like this: 1. Cache A starts 2. Cache A adds 10 nodes to the cache 3. Cache B starts 4. Cache B 'gets' 9 nodes thus causing a gravitation I'm not sure why I decided to gravitate 9/10 nodes, but there it is. I have modified a producer log to include the sequence numbers so you can follow the sequences in the log better. You can find a log containing the sequences here: http://www.robotsociety.com/cache/br/producer_seq.log You can see a comparison between running the provided test for 2.0.0 GA and 2.1.0 CR2 here: 2.0.0 GA producer log : http://www.robotsociety.com/cache/br/2.0.0/producer_2.0.0.log 2.1.0 CR2 producer log : http://www.robotsociety.com/cache/br/2.1.0%20CR2/producer_2.1.0_cr2.log To sum the comparison up, the 2.0.0 GA and 2.1.0 CR2 are equal until data has gravitated. Then we can see that for 2.0.0 GA the cache in the producer looks like: 2.0.0 GA: | null {} | /9 {4=85969gehp9xt} | /_BUDDY_BACKUP_ {} | /192.168.1.135_51890 {} | /3 {4=xapfkubptgx0} | /5 {2=17z0dcpunsivo} | /7 {2=1kr0r0fpucxmy} | /2 {1=1cdp3dootdbu9} | /0 {0=cvwo5pn5r7ou} | /4 {4=1wzvk2sq01r1p} | /8 {0=1vfthyv0lbkvw} | /6 {2=i5az9hje5gxo} | /1 {0=10eaf93uzvsru} And for 2.1.0 CR2: 2.1.0 CR2: | null {} | /9 {0=13gmz9ol9twc} | /_BUDDY_BACKUP_ {} | /192.168.1.135_51892 {} | /3 {1=kf0p8vtuad5y} | /5 {4=uvykukzoi2h0} | /7 {1=zaouao7ntsy7} | /2 {0=ib5tifo2tqco} | /0 {4=1d1boyx12sha7} | /4 {2=gyxlbtnjgpc} | /8 {3=1ivb35jlxspf2} | /6 {0=pte5ws2mpe11} | /1 {1=1erqp88pgexrv} | /192.168.1.135_51891 {} // <--- wtf? As I stated before in my first slightly confusing post, it is not the fact that we get an additional (recursive) buddy node in the cache that is the dealbreaker for us. But I strongly believe that this is one of, if not the, cause for the lock timeouts we see. Remember that for 2.0.0 GA buddy rep works like a charm for us, but with 2.1.0 CR2 it is broken. Given that and the fact that the caches are in different states after a gravitation has occurred using the simple test code provided, indicates to me that something has changed and/or a regression has occurred. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117127#4117127 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117127

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: Extended EL support (with parameters) -> MethodNotFoundE

by pete.muir＠jboss.org

Do you have the method declared on the interface? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117126#4117126 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117126

18 years, 3 months

1
0
0 / 0

[JBoss Seam] - Re: authenticator invocation / EL issue

by pete.muir＠jboss.org

Why not extend identity with your own implementation, and override isLoggedIn @Override | public boolean isLoggedIn() { | return isLoggedIn(false); | } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117125#4117125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117125

18 years, 3 months

1
0
0 / 0

[JBoss Messaging] - Re: MDB and clustered Topics

by timfox

A Topic is JMS mechanism for publish-subscribe messaging. This basically means that multiple subscribers can subscribe to a particular topic (e,g, a news feed), and _all_ the subscribers will receive messages posted to that topic. JMS also supports what is known as point to point messaging using Queues. In this mode, a message is posted to a queue, and is only consumed by a single consumer. An example of this would be an order processing queue, where you only want each order to be processed by one order processor. Since you only want your message processed by one consumer, sounds like you want to use a queue rather than a topic. If you use a non clustered topic, then all consumers on *that node* will receive all messages published to the topic. If you use a clustered topic, then all consumers on *all nodes* will receive all messages published to the topic. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117124#4117124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117124

18 years, 3 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 January 2008