[JBoss Seam] - Re: Seam+Trinidad Table+h:commandLink+DataModelSelection
by brachie
Hi all,
since I am also using Seam + Trinidad (1.2.5) + Richfaces in our current project, I encountered the same problem:
It seems to be a serious problem when using a h:commandButton/h:commandLink or a4j:commandButton/a4jcommandLink inside of a <tr:table>.
E.g. I have a a4j:commandLink for every row to select the data and show details.
The actionMethod of the commandLink is called several times (this number seems to be the same as the number of rows displayed).
Also, I have an editable tr:table. When I use a non-trinidad commandLink/Button to submit the form, only the first row gets updated...
Until now I am using a tr:commandLink/Button, but then I have to use Trinidad's partial Page rendering and not Richface's...
Is there anyone who encountered the same strange behavoir and knows a better solution or at least an explanation for this?
Regards,
Alexander
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124091#4124091
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124091
18 years, 3 months
[Clustering/JBoss] - Re: Avoid service to start at startup
by rotula
OK! I've create a very simple test project similar to ExampleHelloWorldService:
The Management Interface:
| package com.demo;
|
| public interface HelloWorldServiceMBean extends ServiceMBean{
| public void perform(Date now, long remainingRepetitions);
| }
|
The Service Implementation:
| package com.demo.mbean;
|
| public class HelloWorldService extends ServiceMBeanSupport implements HelloWorldServiceMBean{
|
| public void perform( Date now, long remainingRepetitions ){
| log.info( "[perform]: " + now.toString() );
| }
| }
|
The deployment descriptor (jboss-service.xml):
| <server>
| <mbean code="org.jboss.varia.scheduler.ScheduleManager"
| name="jboss:service=ScheduleManagerDemo">
| <attribute name="StartAtStartup">false</attribute>
| </mbean>
|
| <mbean code="com.demo.mbean.HelloWorldService"
| name="com.demo:service=HelloWorldService">
| </mbean>
|
| <mbean code="org.jboss.varia.scheduler.SingleScheduleProvider"
| name="jboss:service=HAImportScheduleProviderDemo">
|
| <depends>jboss:service=ScheduleManagerDemo</depends>
| <depends>com.demo:service=HelloWorldService</depends>
|
| <attribute name="ScheduleManagerName">jboss:service=ScheduleManagerDemo</attribute>
| <attribute name="TargetName">com.demo:service=HelloWorldService</attribute>
| <attribute name="TargetMethod">perform( DATE, REPETITIONS )</attribute>
| <attribute name="DateFormat" />
| <attribute name="StartDate">NOW</attribute>
| <attribute name="Period">2000</attribute>
| <attribute name="Repetitions">-1</attribute>
| </mbean>
| </server>
|
And everything deployed in a sar file with the following structure:
hello-world.sar
| hello-world.sar/META-INF/jboss-service.xml
| hello-world.sar/com/demo/HelloWorldService.class
| hello-world.sar/com/demo/HelloWorldServiceMBean.class
|
Despite the element StartAtStartup of ScheduleManager is set to false, the service trigger anyway.
Is this a bug or did I missing?
thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124079#4124079
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124079
18 years, 3 months
[Management, JMX/JBoss] - Re: Avoid service to start at startup
by rotula
OK! I've create a very simple test project similar to ExampleHelloWorldService:
The Management Interface:
| package com.demo;
|
| public interface HelloWorldServiceMBean extends ServiceMBean{
| public void perform(Date now, long remainingRepetitions);
| }
|
The Service Implementation:
| package com.demo.mbean;
|
| public class HelloWorldService extends ServiceMBeanSupport implements HelloWorldServiceMBean{
|
| public void perform( Date now, long remainingRepetitions ){
| log.info( "[perform]: " + now.toString() );
| }
| }
|
The deployment descriptor (jboss-service.xml):
| <server>
| <mbean code="org.jboss.varia.scheduler.ScheduleManager"
| name="jboss:service=ScheduleManagerDemo"><attribute name="StartAtStartup">false</attribute>
| </mbean>
|
| <mbean code="com.demo.mbean.HelloWorldService"
| name="com.demo:service=HelloWorldService">
| </mbean>
|
| <mbean code="org.jboss.varia.scheduler.SingleScheduleProvider"
| name="jboss:service=HAImportScheduleProviderDemo">
|
| <depends>jboss:service=ScheduleManagerDemo</depends>
| <depends>com.demo:service=HelloWorldService</depends>
|
| <attribute name="ScheduleManagerName">jboss:service=ScheduleManagerDemo</attribute>
| <attribute name="TargetName">com.demo:service=HelloWorldService</attribute>
| <attribute name="TargetMethod">perform( DATE, REPETITIONS )</attribute>
| <attribute name="DateFormat" />
| <attribute name="StartDate">NOW</attribute>
| <attribute name="Period">2000</attribute>
| <attribute name="Repetitions">-1</attribute>
| </mbean>
| </server>
|
And everything deployed in a sar file with the following structure:
hello-world.sar
| hello-world.sar/META-INF/jboss-service.xml
| hello-world.sar/com/demo/HelloWorldService.class
| hello-world.sar/com/demo/HelloWorldServiceMBean.class
|
Despite the element StartAtStartup of ScheduleManager is set to false, the service trigger anyway.
Is this a bug or did I missing?
thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124078#4124078
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124078
18 years, 3 months