[JBoss Seam] - Seam 2Beta - Examples - Todo
by enda
Hi,
I was browsing Seam 2 examples and the third one had minor problem
it is in JSP so it took longer time :)
To finish task is in documentation
----------------------------------------------------
<h:column>
<s:button value="Done" action="#{todoList.done}" taskInstance="#{task}"/>
</h:column>
----------------------------------------------------
but server cried.
this works
----------------------------------------------------
<s:button action="#{todoList.done}" value="Done">
<s:taskId name="taskInstance" value="#{task}"></s:taskId>
</s:button>
----------------------------------------------------
Hopefully will help
How should I put it into JIRA system I was looking for duplicity but I did not find it?
Tomas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078176#4078176
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078176
18Â years, 8Â months
[Management, JMX/JBoss] - Re: Jboss-4.0.3SP1 shutting down itself without any explicit
by mark81
Unfortunately, JBoss shut itself down again today -- the -Xrs option is not helping my problem of JBoss shutting itself down.
Is this problem still happening for anyone?
Better yet, has anyone found a resolution?
A little more background:
- running 4.0.4GA
- running jdk 1.5_09-b03
- running CentOS 4.4
- using the jboss_init_redhat.sh script found in JBoss bin directory to start/stop server (we placed it in /etc/init.d and start/stop jboss with the following command: service jboss start).
- by default, jboss starts in runlevel 3 (which is what our server starts up in)
Like I said in the previous post, JBoss shuts down about once every two weeks (of otherwise continuous operation).
Our log files indicate a normal shutdown -- forceHalt: true etc etc, everything undeploys as if i called service jboss stop, and the shutdown is clean. Our server also shuts down when there is no load -- our load today was essentially nothing at all and the server shut down.
Am I doing something wrong with using the jboss_init_redhat.sh script? During development, I do sometimes start jboss from an SSH session, but on disconnect, jboss IS still running (and I thought it's like starting/stopping any other service, such as httpd, which is fine after doing so from an SSH session... ) (and a ps command yiels me '?' for the TTY for jboss's java process).
Thanks for any help, sorry to report the -Xrs option is NOT working for me...
Oh, and just to make sure it's clear, there's NO System.exit() calls in our code :-) (and the shutdowns happen when nothing is going on anyway)
-Mark
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078170#4078170
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078170
18Â years, 8Â months
[EJB 3.0] - Re: Client-interceptor
by vummarao
I could get it to work by making these changes.
Is this the right way??
//ClientInterceptor
package com.acme.ejb;
import java.io.Serializable;
import org.jboss.aop.advice.Interceptor;
import org.jboss.aop.joinpoint.Invocation;
import org.jboss.aop.util.PayloadKey;
public class AcmeOPClientInterceptor implements Interceptor, Serializable
{
public String getName()
{
return "AcmeClientInterceptor";
}
public Object invoke(Invocation invocation) throws Throwable
{
invocation.getMetaData().addMetaData("TEST", PayloadKey.MARSHALLED, "IDDD");
return invocation.invokeNext();
}
}
//ServerInterceptor
package com.acme.ejb;
import java.io.Serializable;
import java.util.Date;
import org.jboss.aop.advice.Interceptor;
import org.jboss.aop.joinpoint.Invocation;
import org.jboss.aop.metadata.SimpleMetaData;
import org.jboss.aop.util.PayloadKey;
public class AcmeServerInterceptor implements Interceptor, Serializable
{
public String getName()
{
return "AcmeServerInterceptor";
}
public Object invoke(Invocation invocation) throws Throwable
{
SimpleMetaData sm = invocation.getMetaData();
Object o = invocation.getMetaData("TEST",PayloadKey.MARSHALLED));
return invocation.invokeNext();
}
}
Add client interceptor to StatelessSessionClientInterceptors to ejb3-interceptors-aop.xml
<interceptor-ref name="org.jboss.ejb3.remoting.IsLocalInterceptor"/>
<interceptor-ref name="org.jboss.aspects.security.SecurityClientInterceptor"/>
<interceptor-ref name="org.jboss.aspects.tx.ClientTxPropagationInterceptor"/>
<interceptor-ref name="com.acme.ejb.AcmeClientInterceptor"/>
<interceptor-ref name="org.jboss.aspects.remoting.InvokeRemoteInterceptor"/>
for the domain name "Stateless Bean" add the interceptor
com.acme.ejb.AcmeServerInterceptor
to the bind pointcut="execution(public * *->*(..))"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078169#4078169
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078169
18Â years, 8Â months
[JBoss Seam] - FK violation persist ignored with many-to-many parent & join
by eellis
I've done a bit of research and had mulled over this for several days before changing my schema to not require a many-to-many join. The issue is very simple:
I am using Seam-2.0.0-Beta with Hibernate.
The user registration form on the website that I'm building has a checkbox for "receive email alerts". The client has asked that email alerts be a feature type where a user may subscribe to different features using the many-to-many user_features join table.
Table: user
Table user_feature
Table: feature
I have a fairly good understanding of the wiring involved with joining EntityHome instances but am not able to submit the form and within the same "userProfileAction" both create a new user (using UserHome), persist that user, then use that UserHome.getInstance() to persist the UserFeature join entity.
For some reason UserHome.persist() does not persist before attempting to persist the UserFeature. No matter what I try or how verbose I am about persisting and flushing, the transaction seems to wait until all Hibernate commands are complete.
I am not able to write the User record, obtain it's ID, then use that ID to obtain a real User record to be used in joining the UserFeature. Again, because hibernate will not persist the record to the database for me before attempting to write the join record.
I am actually able to query (EJBQL) for the new User record after calling UserHome.persist() and it actually returns the correct ID and instance for that record. I still receive the FK violation though because Hibernate has not written that record to the DB.
Can anyone assist me in getting my join table record to persist? There are quite a few items to cover here so I will be as prompt as possible in responding with code snippets and more detailed information.
It is very possible that I have simply missed out on a proven technique for doing this. Please share the wealth if you've done this before.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078163#4078163
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078163
18Â years, 8Â months
