[JBoss jBPM] - Problem with starting Simple process in JBPM 3.2 Head
by clandestino_bgd
Dear community,
After I finally installed JBPM from CVS, I started to play with it.
I have started Designer and successfully deployed Simple process, which is added in Designer by default (at least no errors are reported).
I use default configurations (JBoss 4.0.4AG with HSSQLDB)
When I log as ernie on jbpm-console, I can see Simple Process Instance, but when I click start I get this:
com.sun.facelets.tag.TagAttributeException: /common/taskform.xhtml @21,50 src="#{taskBean.taskFormPath}" /common/taskform.xhtml @21,50 src="#{taskBean.taskFormPath}": org.jbpm.JbpmException: couldn't get inputstream for file 'forms.xml'
And there is indeed no forms.xml among Simple Process files.
The opposite situation is for Websale process!?
In addition I have checked all other processes in examples folder, and none of them has forms.xml.
And, yes, I have checked JIRA and Design Forums, but as far as I have concluded, forms.xml is used for custom forms (definition of various input controls), but shouldn't automagical (default) form generation remain supported as it is the case with 3.1.x version?
One thing more, this is related to provided examples:
How I can add them easily to my JBPM Project in Designer.
I see build.xml and example.base.build.xml, but it seems they are not functional (besides that I do not know what is their purpose)
The trace is:
D:\work\java\jbpm-3.2\examples>ant
Buildfile: build.xml
build:
BUILD FAILED
D:\work\java\jbpm-3.2\examples\build.xml:8: The following error occurred while executing this line:
D:\work\java\jbpm-3.2\examples\websale\build.xml:6: The following error occurred while executing this line:
D:\work\java\jbpm-3.2\examples\example.base.build.xml:101: XML document structures must start and end within the same entity.
Thank you for your clarifications and any hint.
Regards
Milan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980981#3980981
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980981
19 years, 6 months
[Installation, Configuration & Deployment] - Re: JMX Deployment error
by galo.navarro
Thanks for answering.
It seems the deployer tries to install it, but still doesn't work. Now my interface is
public interface NOCManagerServiceMBean extends ServiceMBean
and the class is
public class NOCManagerService extends ServiceMBeanSupport implements NOCManagerServiceMBean
It tries to deploy but I get this error:
12:29:13,639 INFO [ServiceConfigurator] Problem configuring service java:NOC=NOCManagerService
| org.jboss.deployment.DeploymentException: No Attribute found with name: serviceStatus
|
Which is an evil lie as my interface declares both:
| public String getServiceStatus();
| public void setServiceStatus(String s);
|
and they're implemented
| private static String serviceStatus = "I DO EXIST";
|
| public String getServiceStatus() {
| return serviceStatus;
| }
|
| public void setServiceStatus(String s) {
| serviceStatus=s;
| }
|
Am I missing something?
Thanks again
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980979#3980979
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980979
19 years, 6 months
[Remoting] - Re: InvokerLocator already exists for listener
by dunks80
Well i think I found the problem...
In org.jboss.remoting.Client the createListenerMetadata uses the callbackHandlers hashCode to create the listenerId which is later used to in the AbstractInvokerLocator to detemine whether a listener already has a clientLocator registered for it.
Client
| private Map createListenerMetadata(InvokerCallbackHandler callbackHandler)
| {
| String listenerId = String.valueOf(callbackHandler.hashCode());
| Map metadata = new HashMap();
| metadata.put(LISTENER_ID_KEY, listenerId);
| return metadata;
| }
|
AbstractInvoker
| /**
| * Sets the callback server locator for the specified callback listener id
| *
| * @param locator
| */
| public void addClientLocator(String listenerId, InvokerLocator locator)
| {
| Object obj = localServerLocators.put(listenerId, locator);
| if(obj != null)
| {
| throw new RuntimeException("InvokerLocator already exists for listener id " + listenerId + ". " +
| "Remove this listener before adding again.");
| }
| }
|
I was using JRockit 64-bit jdk for linux (R26.4.0-jdk1.5.0.6). I switched over to the normal Sun jdk and the problem magically went away. I'm not sure if this is a problem with the way JRockit handles hashcodes or if it's a problem with using the hashcode of the callbackHandler as the listenerId.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980974#3980974
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980974
19 years, 6 months