[JBoss Seam] - Re: How do folks layout pages: panelgrids (embedded tables)
by Delphi's Ghost
In theory, it should be easier if you are using facelets since you should already have your view code split into sections such as header, body, menu, footer etc, it's just a matter of putting the <ui:insert> facelet tags into the right place in the layout table, or wrapping the <ui:insert> in a div set to the style of the layout css.
I think a more important question is intra-page layout such as form layout. Css is good for overall page layout and design, but not so much for in-page items such as form layout.
I hate having to use a panel grid to layout forms, and then in one cell, have another panel grid or other wrapper, because I want a button next to the edit box, and the panel grid won't by default let me put two items in the same cell.
Of course, one could argue that the ability to easily change layout when css is used is moot when you start using facelets since you are already grouping your content into sections. Whether it is wrapped in a table or css divs amounts to personal choice based on the arguments for using either one.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055798#4055798
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055798
19Â years
[JBoss Seam] - Re: javax.el.ELException , unable to localize the error
by dkane
"ChristopheA" wrote : Is your findPart method declared in the PartSearch interface ?
|
Yes
@Local
| public interface PartSearch
| {
| public int getPageSize();
| public void setPageSize(int pageSize);
|
| public String getSearchString();
| public void setSearchString(String searchString);
| public String getSearchPattern();
|
| public void findParts();
| public void nextPage();
| public boolean isNextPageAvailable();
|
| public void destroy();
|
|
| }
|
I've just played a bit with (un)commenting references to partSearch component in xhtml page.
Interesting results :
action="#{partSearch.findParts}" - throws Exception
actionListener="#{partSearch.findParts}" - throws Exception
value="#{partSearch.pageSize} - works
action="#{partSearch.nextPage}" - throws Exception
rendered="#{partSearch.nextPageAvailable}" - works
Looks like property-invoking methods works but action-methods of type void does not work.
Any ideas ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055789#4055789
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055789
19Â years
[JBoss Seam] - Re: User Navigation Design Pattern
by Delphi's Ghost
Hey,
I had considered that, and part of my reluctance is the messyness involved in keeping a new subwidget informed of it's widget and vice versa. The subwidget has a property called Widget which refers to the owning widget. The Widget has a property called getSubWidgets which returns the list of subwidgets.
The edit widget page is in a long running conversation, so I think the only way to start a separate conversation is by issuing a GET request and not use any conversation propagation, starting a new conversation using a link such as /editSubWidget?subWidgetId=123. You don't need to pass any parent widget information since you are editing an existing subWidget, and it already has a parent Widget.
However, when you want to create a new subWidget, say by not sending in the subWidgetId, then you do need to provide a widgetId to indicate which widget is the parent, and you need to load that widget and use it with the new subWidget.
By keeping everything in the same conversation, I can just reference the bijected widget variable to get the widget I am currently working on and will be the parent of my new subWidget.
Additionally, if I create a new subWidget in a separate conversation, I then have to find a way to notify the original Widget instance that it has a new child. I could start getting into seam event handlers to do that but again, it starts getting messy.
Neither are overly complex, but we are aiming to keep things simple due to really tight deadlines, and our inexperience with web development and seam.
To add to the problems, we are trying to do it all using pageflows since the editing process can have multiple steps, which complicates matters as far as nested conversations go.
I don't know, maybe we're looking for too simple a solution, does everyone else go through these kinds of hurdles in order to deliver web sites with seemingly logical editing navigation?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055785#4055785
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055785
19Â years