[JBoss Seam] - Re: question about conversation scope
by jacob.orshalick
Seam by default is going to start on conversation when the page loads initially, you simply control whether the conversation is promoted to long-running. If not the conversation is destroyed once the request completes.
You could tell Seam to always promote the conversation to long-running when you company information screen is accessed through pages.xml (there are other ways of doing this as well):
<page view-id="company-information.xhtml" action="#{conversation.begin}" />
Then on the submit method:
| ...
| @End
| public void submit() {
| // do submit
| }
| ...
which would end the long-running conversation regardless of whether the company-address view was accessed or not.
This also helps if you have edit scenarios where you have to edit company information. You would definitely want to start a long-running conversation as soon as the data is loaded for editing on access of company-information.xhtml so you can maintain the state of your company instance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086761#4086761
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086761
18 years, 9 months
[JBoss Tools (User)]J2EE Attributes dropped from a Module/Project???
by Stephen Davidson
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings.
what would cause Eclipse/JBoss Tools(Beta3) to drop the J2EE Attributes
from a project (including the Module Dependencies)?
And how do I add them back on? Every time I try to replace .classpath
with the one stored in the repository, the Module gets dropped
immediately. Right now, its only for one project.
If somebody wants to take a look< I am in Dallas and can meet for
coffee/beer/etc. Houston & Austin is also quite doable (especially for
this!)
Regards,
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFG8o9LPtiPEDq7o8YRAv2ZAJ4/FHpo08tubNwOCmr56RQcFGN8HQCfQ+qd
A4bMOGl2dOH+ROlew1oRb+8=
=PEi9
-----END PGP SIGNATURE-----
18 years, 9 months
[Management, JMX/JBoss] - Error when deploy MBean on JBoss 4.2.1 GA
by matt4400
Hello!!
I trie to deploy a MBean in a JBoss 4.2.1 GA and I have this error :
| ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/C:/outils/jboss-4.2.1.GA/server/default/deploy/helloService.sar
| org.jboss.deployment.DeploymentException: Class does not expose a management interface: java.lang.Object; - nested throwable: (javax.management.NotCompliantMBeanException: Class does not expose a management interface: java.lang.Object)
| at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
| at org.jboss.system.ServiceController.install(ServiceController.java:226)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.install(Unknown Source)
| at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: javax.management.NotCompliantMBeanException: Class does not expose a management interface: java.lang.Object
| at org.jboss.mx.metadata.MBeanCapability.of(MBeanCapability.java:102)
| at org.jboss.mx.metadata.MBeanCapability.of(MBeanCapability.java:100)
| at org.jboss.mx.metadata.MBeanCapability.of(MBeanCapability.java:100)
| at org.jboss.mx.metadata.MBeanCapability.of(MBeanCapability.java:100)
| at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:182)
| at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1422)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1417)
| at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1350)
| at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:345)
| at org.jboss.system.ServiceCreator.install(ServiceCreator.java:157)
| at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449)
| at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
I have a SAR file which is composed like that:
| helloService.sar/META-INF/jboss-service.xml
| helloService.sar/lib/helloService.jar
|
In the jboss-service.xml
| <?xml version='1.0' encoding='UTF-8' ?>
| <server>
| <mbean code="org.cap2j.jbp.service.HelloService"
| name="cap2j:service=HelloService">
| <attribute name="JndiName">inmemory/maps/MapTest</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
| </server>
|
And I have an interface ItHelloService.java
| public interface ItHelloService extends ServiceMBean{
|
| public String getJndiName();
| public void setJndiName(String jndiName) throws NamingException;
| public void start() throws Exception;
| public void stop() throws Exception;
| }
|
And the class HelloService.java
| public class HelloService extends ServiceMBeanSupport implements ItHelloService {
|
| private String jndiName;
| private HashMap contextMap = new HashMap();
| private boolean started;
| public String getJndiName() {
| return jndiName;
| }
|
| public void setJndiName(String jndiName) throws NamingException {
| String oldName = this.jndiName;
| this.jndiName = jndiName;
| if (started) {
| unbind(oldName);
| try {
| rebind();
| } catch(Exception e) {
| NamingException ne = new NamingException("Failedto update jndiName");
| ne.setRootCause(e);
| throw ne;
| }
| }
| }
|
| public void startService() throws Exception{
| started = true;
| rebind();
| }
|
| public void stopService(){
| started = false;
| unbind(jndiName);
| }
| ...
| }
|
This code come from the example of the documentation of JBoss 4.2.0
If you have a solution !
Thinks for regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086759#4086759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086759
18 years, 9 months
[JBoss jBPM] - Re: jBPM ... confused...
by Jean-LucT
I'm quite new to jBPm too. But according to my understanding :
you can define your own workflow in jBPM.
You can ask jBPM to create a simple form for you. You can if you know Facelet complete and adapt this form.
The jBPM console provides a kind of portal to the workflow you define. This portal relies on the form it generates, so you can have pretty quickly a user interface for your process :
a login page
a portal that display your to do task list, the list of processes you can start.
when you click on a to do task, you call a simple form to input data
This is in theory all you need, nevertheless, I do not consider this user interface user friendly, is more a debugging tool to me.
Hope, It helps you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086755#4086755
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086755
18 years, 9 months
