February 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Conversation management in a framework

by gavin.king＠jboss.com

My latest take on how this stuff should work is in the latest seam-gen in CVS. Run generate-entities, and see how I handle associations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015888#4015888 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015888

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Seam Mail and multipart/alternative bug ?

by gavin.king＠jboss.com

"petemuir" wrote : Thanks, this is fixed in CVS Oops, missed the reply. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015887#4015887 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015887

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Schema and DTD validation

by gavin.king＠jboss.com

"lightbulb432" wrote : I had this problem before as well...if you're using one version of Seam, but the DTD on the site is for a different version, your IDE will give you trouble. | | Why not version the DTD at the level of granularity of releases (i.e. pages-1.1.5.dtd)? Then when you're using a given version of Seam or pages.xml, you update your DOCTYPE accordingly. | | For example, the people using 1.1.0 today will get IDE errors. I dunno, just my suggestion anyways... We don't usually break the schema between point releases (not unless the schema had an error in it). We just add new stuff. We don't want to force people to change all their schema declarations every time we do a point release. That would be nuts. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015886#4015886 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015886

19 years, 2 months

1
0
0 / 0

[Clustering/JBoss] - Re: Clustering begginner..please HELP

by davewebb

With apache in place, you _never_ go to the JBoss port again. Always go through apache. It monitors the server states and directs traffic accordingly. Apache knows server 1 is dead, so it sends all traffic to server 2. If both server 1 and server 2 are alive, it load balances reuqests between the 2 servers. You have this notion that a dead jboss server can do something. If the server process is dead, it is non-existent and can not do anything. Apache and Mod_jk do the management piece of the puzzle. Keep hitting the apache port and watch the requests failover to the remaining "live" server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015885#4015885 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015885

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Schema and DTD validation

by gavin.king＠jboss.com

anonymous wrote : Yes, seems to be an eclipse/exadel problem. Turn off schema caching in eclipse. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015883#4015883 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015883

19 years, 2 months

1
0
0 / 0

[Clustering/JBoss] - Re: Annoying UDP warnings in serverlog from different cluste

by bstansberry＠jboss.com

In a standard "all" config there are two JGroups channels created -- one in cluster-service.xml and one in tc5-cluster.sar/META-INF/jboss-service.xml. (The latter was formerly tc5-cluster-service.xml in 4.0.3.SP1 and earlier.) You need to use distinct names, mcast_addr and mcast_port configs between these two files. But, for each file, the name, mcast_addr and mcast_port should be the same on all servers. Thus the cluster-service channels see each other and form a group and the tc5 channels see each other and form a group, and the two sets of channels don't see each other. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015882#4015882 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015882

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: s:selectDate component continues to be displayed after l

by gavin.king＠jboss.com

I asked Shane to take a look. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015881#4015881 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015881

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Conversation management in a framework

by quilleashm

Hi there, I am building a mini-framework using Seam to allow our developers to build search and detail pages easily. Screen page is basically search parameters + grid and the detail is just input fields with OK/Cancel. The important thing is the basis of the Search and Detail components be reusable. Sometimes input fields on a detail view need to be links/buttons through to another search page where an entity is selected and a relationship is established (many-to-one). I'm trying to figure out how to do the conversation handling and state management/passing between the pages/components. I have this page flow the user will follow. Entity A Search -> Entity A Detail -> Entity B Search -> Back to Entity A Detail (after selection) -> Back to Entity A Search (after OK/Cancel) And I need to pass to the selection from the Entity B Search back to the Entity A detail for population of one of the input fields. So far I have thought of the following. Entity A Search component has a conversation for storing the search state (pagination, current selection etc). This conversation should never be propogated to other views (maybe this should be page scope but I use s:link which precludes this I think). On selecting to Edit an entity redirect to the detail view (propogation=none). Entity A Detail component starts a new conversation. On selecting the button to the Entity B search redirect and propogate the conversation to the search view. Entity B Search starts a nested conversation. User selects. Now I'm not sure how to pass the selected row(s) back from search B to detail A. Maybe just have a conversational component that the detail A creates and B writes it's selection to? Then when the nested conversation is popped the selected values will still be held in the parent conversation. I plan on using "Conversation.endAndRedirect()" to get back to detail A from search B. An additional problem is how to resume the search A conversation when detail A is done. Should I just pass the conversation id as a parameter and have detail A switch to it when it completes? Many thanks if you even read this far! Any suggestions/critiquing welcome. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015880#4015880 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015880

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Seam Mail and multipart/alternative bug ?

by sebdoby

Sorry, I've not seen it ;) Thanks for your reactivity. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015879#4015879 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015879

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Seam Mail and multipart/alternative bug ?

by gavin.king＠jboss.com

Please report this solution in JIRA. Different email clients seem to have different rules for deciding which version to display. We couldn't work out what rule thunderbird uses. Looks like you got it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015878#4015878 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015878

19 years, 2 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 February 2007