[JBoss Seam] - More then one start state?
by timony
Hi,
is is possible to have more than one start-state elements in the page-flow? As I am new in Seam, I need to help with quiet simple problem: I want to have just one pageflow:
I have a non pageflow element list, when I click on one item of the list, the pageflow starts on "view detail", from the detail site I need to go to the edit page to be able to edit the details of the element. To this point all is clear and the pageflow works fine.
But what I need is to connect the same pageflow from the list by "new item" link, which should point dirrectly to the edit page.
When saved, even the new element or the updated one, the flow should always jump to the view-detail page. Flow shoudl end, when "done" brings the user back to the element list page.
Do you know, is this generaly possible? Eg. to have two "start-state" elements? One for the view-detail and one for the dirrect "edit page" for the new item?
Thanks Tomas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052493#4052493
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052493
18Â years, 10Â months
[JBoss Messaging] - Re: failed to add topic in JBM 1.3
by timfox
The way to deal with this is to first find a destination lookup that works for you.
E.g. try looking up one of the example destinations e.g. queue/testQueue that is shipped with JBM.
Once you have done that and are satisified that lookups do, in general work (you can also run the examples for examples of working lookups), you should then start looking at how that example destination differs from your problematic destination.
You could then start changing the working destination's name (maybe slowly character by character) into the name of the problematic destination. At each time step of the way ensure the lookup still works. At some point you will have a destination with the name you desire that works, and you will know what was wrong with your original config.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052489#4052489
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052489
18Â years, 10Â months
[JBoss Seam] - trouble with conversations
by gothmog
Hi,
Im new to seam and liking what i see, however I'm having real trouble with conversations.
I set my class up to be in conversation scope (this class will feed the UI field info that I want to work with over several pages.)
@Name("cardFields")
@Scope(ScopeType.CONVERSATION)
public class CardFields implements Serializable {
...
And then set it to start a conversation in pages.xml
<page view-id="/addcard.xhtml" action="#{conversation.begin}">
This worked fine but I noticed that if I continually refreshed the addCard page then another conversation would get started (I could see this by using the debug page). When I thought about it this was expected as everytime a new page refresh happened seam would start another conversation because of the action in pages.xml.
I wanted more control, so I changed pages.xml to the following
<page view-id="/addcard.xhtml">
<begin-conversation join="true" />
...
thinking that only 1 conversation would happen.
when i deployed this after restarting the server the same thing happend, on a refresh more conversations started happening even tho pages.xml explictly says join=true.
Surley this can't be right? just to be doubly sure, I tried it with join=false but the same thing happened.
Not convinced that I'd got it right I fired up the sample app called numberguess and sure enough the same thing was happening ?
Is this a bug or have I missed something ? BTW where is the docu for pages.xml for running in navigation rules and not page flow mode ?
Thanks
Troy
BTW running on OSX 10.4, java 5, jboss 4.05, seam, 1.2.1.GA
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052485#4052485
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052485
18Â years, 10Â months