July 2006 - jboss-user - Jboss List Archives

[JBoss jBPM] - Re: issue for Assignment to Group

by falazar

Posted some more information on: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957080#3957080 It appears that when you assign a task to a Group(NAME) it WILL save it in the database to the appropriate group. The web interface, does not however display tasks to the users that have been assigned to their groups correctly. So it appears the first part was done correctly, just the web interface section was never implemented. This problem is referenced throughou the forums, and multiple times in the jira as well, with no good resolution. Search Forum: groups 'assignment expression' Regards James Ratcliff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957081#3957081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957081

19 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: Assigning a task to->{group, rolebased, ...}

by falazar

Sorry, some more information for the above comment: It appears that when you assign a task to a Group(NAME) it WILL save it in the database to the appropriate group. The web interface, does not however display tasks to the users that have been assigned to their groups correctly. So it appears the first part was done correctly, just the web interface section was never implemented. This problem is referenced throughou the forums, and multiple times in the jira as well, with no good resolution. Forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73106 Jira:http://jira.jboss.com/jira/browse/JBPM-480 Search Forum: groups 'assignment expression' Regards James Ratcliff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957080#3957080 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957080

19 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Breaking changes to pageflow

by gavin.king＠jboss.com

The same statement holds for a page action. Basically, <start-state> is only usable when the JSF NavigationHandler is going to be subsequently called. You need to use <start-page>. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957079#3957079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957079

19 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Breaking changes to pageflow

by rpiaggio

I think I understand what there is in the documentation (and above in this thread):anonymous wrote : If we are beginning the pageflow during the RENDER_RESPONSE phase?during a @Factory or @Create method, for example?we consider ourselves to be already at the page being rendered, and use a <start-page> node as the first node in the pageflow, as in the example above. In my example, the pageflow is starting as a page action in one case and as an action in the other, so I don't think <start-page> applies. (Am I missing something?) It was probably a mistake to express my problem in this thread, I thought it was related to the change, sorry about that. The unnamed transition suggestion is orthogonal to both <start-page> and the problem and I was having. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957077#3957077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957077

19 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Facelets error or Seam error?

by bsmithjj

| @Name("linkEditor") | @Scope(ScopeType.CONVERSATION) | public class LinkEditor implements Serializable { | | public String deleteLink() { | log.info("deleteLink() - linkId="+linkId); | if (linkId != null) { | Transaction tx = appssoDB.beginTransaction(); | final Link l = getLink(linkId,user.getId()); | final User u = (User)appssoDB.get(User.class,user.getId()); | if (l != null) { | u.removeLink(l); | appssoDB.delete(l); | } | tx.commit(); | appssoDB.refresh(u); | user = u; | return "success"; | } else { | facesMessages.add("Unable to delete requested link."); | return null; | } | } | | ... | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957076#3957076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957076

19 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: Remote Client to EJB 3.0 fail .. :( javax.naming.Communi

by PeterJ

I copied your code, ran it, and finally figured out what was wrong. The annotation @Stateless(name="SimpleEJB") names the EJB, but it does not provide the JNDI name for the EJB. The JNDI name, by default, is "SimpleEJB/remote" (or "SimpleEJB/local"). So you can do one of two things. Change your lookup code to read: SimpleEJB sessEJBTest = (SimpleEJB)context.lookup("SimpleEJB/remote"); Or add a JBoss-specific annotation to your bean class: @Stateless(name="SimpleEJB") | @org.jboss.annotation.ejb.RemoteBinding(jndiBinding="SimpleEJB") | public final class SimpleEJBBean implements SimpleEJB { | ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957075#3957075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957075

19 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Seam + Ajax4jsf

by gus888

Hi Gavin, Thank you for your reply. In fact, the ajax4jsf document does not specify the "server" setting in web.xml, but in its demo examples and document, they alway use the "server". I need to ask ajax4jsf developers for the question. Thank you. P.S. Ajax4jsf document: https://ajax4jsf.dev.java.net/nonav/documentation/ajax-documentation/deve... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957074#3957074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957074

19 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: JBPM_LOG: who performed the transition?

by bdruth

I've looked through the documentation & googled around a bit and I haven't found what "the" way is to enable logging to JBPM_LOG. I have <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" /> in my jbpm.cfg.xml, but that itself doesn't seem to do the trick. What I currently have is this | processInstance.getInstance(LoggingInstance.class); | after I create a new ProcessInstance, and that seems to work. Is there a global way of enabling logging, though? Cheers, Brice p.s. The JBPM docs reference a LoggingDefinition, which no longer exists. You also can't addInstance(new LoggingInstance()) on a ProcessInstance, JBPM throws an exception. So, may I suggest cleaning up the docs on chapter 12. Logging? :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957073#3957073 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957073

19 years, 9 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: pages with different security domains in one portal

by sohil.shah＠jboss.com

krupinskir- I don't think you can associate security domain on a per page basis in the portal. The security domain that is specified is applied to the entire portal as a whole View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957072#3957072 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957072

19 years, 9 months

1
0
0 / 0

[JBossWS] - Re: jbossws 1.0.1GA sample not working

by palin

We did some more experiments; prepared a fresh jboss installation, rebuild the tests and tried again; now the deployment fails with the following error: | 18:24:02,757 INFO [TomcatDeployer] deploy, ctxPath=/jbossws-samples-eventing, warUrl=.../tmp/deploy/tmp25008jbossws-samples-eventing-exp.war/ | 18:24:03,206 INFO [WSDLFilePublisher] WSDL published to: file:/home/oracle/stefano/jboss/server/default/data/wsdl/jbossws-samples-eventing.war/sysmon.wsdl | 18:24:03,245 ERROR [MainDeployer] Could not start deployment: file:/home/oracle/stefano/jboss/server/default/deploy/jbossws-samples-eventing.war | org.jboss.ws.WSException: Cannot publish wsdl to: /home/oracle/stefano/jboss/server/default/data/wsdl/jbossws-samples-eventing.war/sysmon.wsdl | at org.jboss.ws.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:141) | at org.jboss.ws.deployment.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:138) | at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:104) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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 $Proxy38.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor14.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.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy6.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.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | 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.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755) | 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:464) | at java.lang.Thread.run(Thread.java:595) | Caused by: WSDLException: faultCode=CONFIGURATION_ERROR: Unsupported Java encoding for writing wsdl file: 'ISO8859_15'.: | at com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(WSDLWriterImpl.java:1053) | at org.jboss.ws.server.WSDLFilePublisher.publishWsdlImports(WSDLFilePublisher.java:171) | at org.jboss.ws.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:124) | ... 78 more | 18:24:03,279 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/ | 18:24:03,700 ERROR [URLDeploymentScanner] Incomplete Deployment listing: | | --- Incompletely deployed packages --- | org.jboss.deployment.DeploymentInfo@2a608860 { url=file:/home/oracle/stefano/jboss/server/default/deploy/jbossws-samples-eventing.war } | deployer: MBeanProxyExt[jboss.web:service=WebServer] | status: Deployment FAILED reason: Cannot publish wsdl to: /home/oracle/stefano/jboss/server/default/data/wsdl/jbossws-samples-eventing.war/sysmon.wsdl | state: FAILED | watch: file:/home/oracle/stefano/jboss/server/default/deploy/jbossws-samples-eventing.war | altDD: null | lastDeployed: 1152635040508 | lastModified: 1152635040000 | mbeans: | jboss.web:j2eeType=Servlet,name=jsp,WebModule=//localhost/jbossws-samples-eventing,J2EEApplication=none,J2EEServer=none (state not available) | jboss.web:j2eeType=Servlet,name=default,WebModule=//localhost/jbossws-samples-eventing,J2EEApplication=none,J2EEServer=none (state not available) | jboss.web:j2eeType=Servlet,name=EventSourceServlet,WebModule=//localhost/jbossws-samples-eventing,J2EEApplication=none,J2EEServer=none (state not available) | jboss.web:j2eeType=Servlet,name=SubscriptionManagerServlet,WebModule=//localhost/jbossws-samples-eventing,J2EEApplication=none,J2EEServer=none (state not available) | Thank you in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957071#3957071 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957071

19 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2006