[JBoss Seam] - Form submission problems using s:decorate
by chris.simons
I'm attempting to convert our forms using IceFaces, Seam (2.0), and some core JSF elements to use what seems to be the best way to go - <s:decorate>.
I've taken a form that was otherwise working and converted the form to use <s:decorate template="/layout/forms/edit.xhtml">.
"edit.xhtml" is your standard usage of <s:decorate> which I have seen again and again in Seam docs, forum posts, and blogs.
I can confirm that the form is validating correctly as the validation messages (using <s:message>) appear appropriately. However, my issue is that when there are no validation issues - the page simply will not "submit". I've checked pages.xml and the "submit" button; remember, this form worked prior to using <s:decorate>.
I am hoping someone here may use an eye ball or two and look at my problem.
Here is a code snippet:
The Form:
<ice:form id="modifyPersonalProfileForm">
| <s:validateAll>
| <s:decorate id="designatorDecoreate" template="/layout/forms/edit.xhtml">
| <ui:define name="label">First Name:</ui:define>
| <ice:inputText id="firstName" required="true" value="#{cvUser.firstName}" size="40"></ice:inputText>
| </s:decorate>
| ....
| <ice:commandLink value="Cancel" action="#{userProfileManager.cancelUserProfile}" />
|
...
The "edit.xhtml":
<table>
| <tr>
| <td>
| <s:label styleClass="label #{invalid?'errors':''}">
| <ui:insert name="label"/>
| <s:span styleClass="required" rendered="#{required}">*</s:span>
| </s:label>
| </td>
| <td>
| <span class="input #{invalid?'errors':''}">
| <!-- <h:graphicImage value="/themes/englink-earth-final/img/error.gif" rendered="#{invalid}"/> -->
| <ui:insert/>
| </span>
|
| <small class="small #{invalid?'errors':''}">
| <s:message styleClass="error errors"/>
| </small>
| </td>
| </tr>
| </table>
P.S. I tried to post this message on the new forums, but as soon as I copied/pasted some actual JSF code, the program crashed and I received a JBoss "internal 500" page error.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129201#4129201
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129201
18 years, 2 months
[JBoss Seam] - Re: Named conversation and new instance redirected to Home?
by enda
Hi Erik this is my working solution (I am handling conversation on my own)
entityManager that inherits generalManager
|
| @Begin(flushMode = FlushModeType.MANUAL, join = true, pageflow = "teamHomeFlow")
| public String select(Team team) {
| // set conversation
| setConversationId(team.getId());
| // manually join conversation
| if(joinConversation()) {
| return null;
| } else {
| return super.select(team);
| }
| }
|
|
generalManager
|
| /**
| * joins conversations
| * expects conversationName set with the same name as in pages.xml
| *
| * @return true if joined, false if not
| *
| * @see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126294#4126294
| */
| protected boolean joinConversation() {
| //ConversationEntries.getInstance().updateConversationId(Conversation.instance().getId(), getConversationId());
|
| ConversationEntry ce = ConversationEntries.getInstance().getConversationEntry(conversationName + ":" + conversationId);
| if(ce != null) {
| ce.redirect();
| getFacesMessages().add("Conversation already exists");
| return true;
| } else {
| return false;
|
| }
|
| }
|
|
pages.xml
|
| <conversation name="teamHome"
| parameter-name="team"
| parameter-value="#{teamActionManager.conversationId}"/>
|
|
the idea is that every xxManager has unique instance ID (entity.ID) and this id is assigned to its whole conversational life (it solves the problem with creating new entity too)
Conversation has the same name as instance ID
I am joining that on my own by instance ID.
The disadvantages is your naming convention for conversation and its usage also in xxManager not only in pages.xml (coupling)
I hope that it helps. Good thing is that I tested it from various scenarios and it works!
I also thank you for comments to convince Seam documentation to do this as their example.
Tomas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129197#4129197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129197
18 years, 2 months
[JBoss Messaging] - JBoss Messaging RA configuration
by kdeboer
Hi Everybody
I have been playing with JBoss Messaging for a few days and want to achieve something which i cannot get to work:
The idea is the following:
Have a JBoss Appserver procuce message to a clustered JBoss Mesaging implementation via JCA RA adapter connected to teh remote cluster. I would like to achieve this without a local JBoss Messaging Instance in the appserver. The JCA access here is not required but would be nice to have because the consumer side should work this way.
On the consumer side i wuold like to have an EJB3 MDB agin connected via a JCA resource adapter to the cluster. (again preferrably without the local Jboss Messaging service, only libs)
I have been experimenting with extending the Local JNDI with part of the remote JNDI tree to get access to the remote queue
I also tested setting up a XA Connection to the remote cluster but then i got stuck trying to make a remote queue into in administered object. I don't know what properties this admin object would accept.
There are plenty of examples how to get this done with ActiveMq, WebsphereMQ but nothing with Jboss Messaging.
I would like to know if there is any change of success in this scenario.
Thnx
Karl de Boer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129195#4129195
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129195
18 years, 2 months