[jBPM] - JBPM console throw jbpm console javax.el.PropertyNotFoundException: Cannot resolve identifier
by Patrick Lam
Patrick Lam [http://community.jboss.org/people/pclam] created the discussion
"JBPM console throw jbpm console javax.el.PropertyNotFoundException: Cannot resolve identifier"
To view the discussion, visit: http://community.jboss.org/message/571851#571851
--------------------------------------------------------------
When I try to start the example packed in JBPM 4.4 in JBPM web console, it throws the following exception in JBoss server log.
Grateful if anyone can solve this problem.
11:02:12,358 INFO [DefaultCommandService] exception while executing command mailto:org.jbpm.pvm.internal.cmd.StartProcessInstanceCmd@1b07168 org.jbpm.pvm.internal.cmd.StartProcessInstanceCmd@1b07168
javax.el.PropertyNotFoundException: Cannot resolve identifier 'content'
at de.odysseus.el.tree.impl.ast.AstIdentifier.eval(AstIdentifier.java:86)
at de.odysseus.el.tree.impl.ast.AstBinary$SimpleOperator.eval(AstBinary.java:31)
at de.odysseus.el.tree.impl.ast.AstBinary.eval(AstBinary.java:110)
at de.odysseus.el.tree.impl.ast.AstEval.eval(AstEval.java:51)
at de.odysseus.el.tree.impl.ast.AstNode.getValue(AstNode.java:28)
at de.odysseus.el.TreeValueExpression.getValue(TreeValueExpression.java:122)
at org.jbpm.pvm.internal.el.UelValueExpression.evaluateInScope(UelValueExpression.java:52)
at org.jbpm.pvm.internal.el.Expression.evaluate(Expression.java:108)
at org.jbpm.pvm.internal.model.ExpressionCondition.evaluate(ExpressionCondition.java:41)
at org.jbpm.jpdl.internal.activity.DecisionConditionActivity.findTransitionUsingConditions(DecisionConditionActivity.java:62)
at org.jbpm.jpdl.internal.activity.DecisionConditionActivity.execute(DecisionConditionActivity.java:47)
at org.jbpm.jpdl.internal.activity.DecisionConditionActivity.execute(DecisionConditionActivity.java:43)
at org.jbpm.pvm.internal.model.op.ExecuteActivity.perform(ExecuteActivity.java:60)
at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:672)
at org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperation(ExecutionImpl.java:632)
at org.jbpm.pvm.internal.model.ExecutionImpl.start(ExecutionImpl.java:217)
at org.jbpm.pvm.internal.cmd.StartProcessInstanceCmd.execute(StartProcessInstanceCmd.java:60)
at org.jbpm.pvm.internal.cmd.StartProcessInstanceCmd.execute(StartProcessInstanceCmd.java:37)
at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
at org.jbpm.pvm.internal.tx.JtaTransactionInterceptor.executeInNewTx(JtaTransactionInterceptor.java:83)
at org.jbpm.pvm.internal.tx.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:62)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:56)
at org.jbpm.pvm.internal.tx.JtaRetryInterceptor.executeWithRetry(JtaRetryInterceptor.java:52)
at org.jbpm.pvm.internal.tx.JtaRetryInterceptor.execute(JtaRetryInterceptor.java:45)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.startProcessInstanceById(ExecutionServiceImpl.java:51)
at org.jbpm.integration.console.ProcessManagementImpl.newInstance(ProcessManagementImpl.java:139)
at org.jboss.bpm.console.server.ProcessMgmtFacade.newInstance(ProcessMgmtFacade.java:204)
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:597)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117)
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166)
at org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:662)
11:02:12,467 ERROR [SynchronousDispatcher] failed to execute
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/571851#571851]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 5 months
[JBoss Tools] - Manage SWTBot bits used by builds and developers
by Nick Boldt
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
"Manage SWTBot bits used by builds and developers"
To view the document, visit: http://community.jboss.org/docs/DOC-16087
--------------------------------------------------------------
JBT/JBDS builds and JBT/JBDS SWTBot tests developers have to use the same version of SWTBot to ensure consistency.
Current version of SWTBot release used is specified in the target platform definition files (*.target) stored in SVN repository here: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/.
There are two files available. *Multiple.target* contains all the source URLs from whichc the target is built. *Unified.target* contains the same IUs (installable units) but swaps out the URLs for our own JBoss mirror, located here: http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/
Open the .target file in your favourite Text or XML Editor, and search (CTRL-F or /) for "swtbot" to find the relevant IUs and their versions. ".feature.group" means "this feature and all its contained plugins".
h5. Updating JBoss Tools Hudson Builds To The Latest SWTBot Release
When SWTBot needs to be updated, verify your tests will still work with the latest release:
1. Compile complete SWTBot test suite in your workspace (using M2Eclipse) or via commandline (using Tycho) to verify updated SWTBot release does not break your tests.* If there are compilation errors, fix them or report them in JIRA. Test locally before committing changes to the tests back to SVN
2. Update SWTBot target file to specify proper SWTBot release version and commit it to SVN. 1. The easiest way to do this is to do a Maven build in the target-platform directory and generate the target platform repo locally. * cd ~/trunk/build/target-platform; mvn3 clean install -P get.*local.target*
2. This will fetch all the contents from the target platform, and update the .target files to use the versions found in the repo you generate locally. You can also update the .target files by hand, if you prefer, but the automated approach is easier and less error-prone.
3. As a result of running a build of the target platform locally, you can now *OPTIONALLY* use that repo instead of the remote one when running your builds. To activate this *local.target* repo, do this:* cd ~/trunk/build/parent; mvn3 clean install -P *local.target*
* cd ~/trunk/build; mvn3 clean install -P*+componentToBuild+*,*local.target*
(where +*componentToBuild*+ may be as, archives, esb, ... or as-bootstrap, archives-bootstrap, esb-bootstrap, ...)
While a build will run automatically in response to your committed changes, you can also kick one manually to save time:
* http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf... http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf...
h5. Updating JBoss Developer Studio ("Uberbuilder") Hudson Builds To The Latest SWTBot Release
1. Create a collection of new zips of the for the updated releases.
2. Create new md5sums.
3. Publish them somewhere that Hudson can see them
4. Update the properties file that JBDS uses to access them:
* http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.r... http://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.r...
h5. Communication Strategy, or, Letting People Know About Changes
It's important to let others know that you've updated the SWTBot baseline against which everyone's tests will be run. Send an email to the mailing list here:
* mailto:external-exadel-list@redhat.com external-exadel-list(a)redhat.com
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16087]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
15 years, 5 months
[JBoss Tools] - Manage SWTBot bits used by builds and developers
by Nick Boldt
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
"Manage SWTBot bits used by builds and developers"
To view the document, visit: http://community.jboss.org/docs/DOC-16087
--------------------------------------------------------------
JBT/JBDS builds and JBT/JBDS SWTBot tests developers have to use the same version of SWTBot to ensure consistency.
Current version of SWTBot release used is specified in the target platform definition files (*.target) stored in SVN repository here: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/ http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/.
There are two files available. *Multiple.target* contains all the source URLs from whichc the target is built. *Unified.target* contains the same IUs (installable units) but swaps out the URLs for our own JBoss mirror, located here: http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/
Open the .target file in your favourite Text or XML Editor, and search (CTRL-F or /) for "swtbot" to find the relevant IUs and their versions. ".feature.group" means "this feature and all its contained plugins".
h5. Updating JBoss Tools Hudson Builds To The Latest SWTBot Release
When SWTBot needs to be updated, verify your tests will still work with the latest release:
1. Compile complete SWTBot test suite in your workspace (using M2Eclipse) or via commandline (using Tycho) to verify updated SWTBot release does not break your tests.* If there are compilation errors, fix them or report them in JIRA. Test locally before committing changes to the tests back to SVN
2. Update SWTBot target file to specify proper SWTBot release version and commit it to SVN. 1. The easiest way to do this is to do a Maven build in the target-platform directory and generate the target platform repo locally. * cd ~/trunk/build/target-platform; mvn3 clean install -P get.*local.target*
2. This will fetch all the contents from the target platform, and update the .target files to use the versions found in the repo you generate locally. You can also update the .target files by hand, if you prefer, but the automated approach is easier and less error-prone.
3. As a result of running a build of the target platform locally, you can now *OPTIONALLY* use that repo instead of the remote one when running your builds. To activate this *local.target* repo, do this:* cd ~/trunk/build/parent; mvn3 clean install -P *local.target*
* cd ~/trunk/build; mvn3 clean install -P*+componentToBuild+*,*local.target*
(where +*componentToBuild*+ may be as, archives, esb, ... or as-bootstrap, archives-bootstrap, esb-bootstrap, ...)
While a build will run automatically in response to your committed changes, you can also kick one manually to save time:
* http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf... http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2.0.Beta2.target-platf...
It's important to let others know that you've updated the SWTBot baseline against which everyone's tests will be run. Send an email to the mailing list here:
* mailto:external-exadel-list@redhat.com external-exadel-list(a)redhat.com
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16087]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
15 years, 5 months
[jBPM] - Re: JBPM4.1, JBoss 4.23 and Seam 2.2.0
by Carlos Andres
Carlos Andres [http://community.jboss.org/people/andrescarlospa] created the discussion
"Re: JBPM4.1, JBoss 4.23 and Seam 2.2.0"
To view the discussion, visit: http://community.jboss.org/message/571816#571816
--------------------------------------------------------------
Hi all.
I'm trying to configure this environment, I'm using jbpm4.4, seam 2.2, I followed this instructions: http://www.lunatech-research.com/archives/2010/03/09/jbpm4-and-seam-worki... http://www.lunatech-research.com/archives/2010/03/09/jbpm4-and-seam-worki...
but there is something missed. I'm getting this exception:
java.lang.NullPointerException
13:18:20,818 ERROR [STDERR] at org.jbpm.pvm.internal.processengine.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:152)
13:18:20,818 ERROR [STDERR] at org.jbpm.pvm.internal.processengine.ProcessEngineImpl.<init>(ProcessEngineImpl.java:105)
13:18:20,818 ERROR [STDERR] at org.jbpm.pvm.internal.cfg.ConfigurationImpl.instantiateProcessEngine(ConfigurationImpl.java:100)
13:18:20,818 ERROR [STDERR] at org.jbpm.pvm.internal.cfg.ConfigurationImpl.buildProcessEngine(ConfigurationImpl.java:92)
13:18:20,818 ERROR [STDERR] at org.jbpm.api.Configuration.getProcessEngine(Configuration.java:126)
13:18:20,818 ERROR [STDERR] at xx.xx.xx.jbpm.Jbpm.init(Jbpm.java:37)
It is related with jbpm.cfg.xml file:
<jbpm-configuration>
<jbpm-context>
<service name="persistence">
<factory>
<bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory">
<field name="isTransactionEnabled"><false/></field>
</bean>
</factory>
</service>
<service name="tx" factory="org.jbpm.tx.TxServiceFactory" />
<service name="message" factory="org.jbpm.msg.db.DbMessageServiceFactory" />
<service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" />
<service name="logging" factory="org.jbpm.logging.db.DbLoggingServiceFactory" />
<service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory" />
</jbpm-context>
</jbpm-configuration>
What is wrong???
Thanks in advance!!!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/571816#571816]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 5 months
[JBoss Messaging] - MyQueue not bound
by Everson Ballack JR
Everson Ballack JR [http://community.jboss.org/people/Sefo] created the discussion
"MyQueue not bound"
To view the discussion, visit: http://community.jboss.org/message/571808#571808
--------------------------------------------------------------
Hi everyone,
First of all, sorry for any english mistakes.
I've used the Jboss 4.2 for my applications for a long time.
But now, I need to upgrade to the 5.1 version.
In the older version, when I deployed my app and the destination mapping of my queues weren't found , a new temporary queue was created and bounded for a JNDI name.
In the 5.1 version, this not happens and I receive a "GetrafProvisaoTDMA not bound", where GetrafProvisaoTDMA is the name of my queue.
I can't edit the destination-service.xml only for create a new destination, so I hope do this in another way.
Is it possible to configure the JBoss to create automatic a new queue, when it's not found in destination-service.xml file? There are any other JBoss configuration or EJB annotation...
Can someone help me??
My MDB:
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/GetrafProvisaoTDMA"),
@ActivationConfigProperty(propertyName="maxSession",
propertyValue="2")
})
@TransactionManagement(TransactionManagementType.BEAN)
public class InternalizaTDMA extends ControleArquivo implements MessageListener {
(some stuffs here...)
}
thks
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/571808#571808]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 5 months
[JBoss Tools] - JBosstoolsVisualEditorFAQ
by Yahor Radtsevich
Yahor Radtsevich [http://community.jboss.org/people/yradtsevich] modified the document:
"JBosstoolsVisualEditorFAQ"
To view the document, visit: http://community.jboss.org/docs/DOC-10862
--------------------------------------------------------------
*Q: Which platforms are supported by* *Visual Editor?*
*A:* The list of supported platforms (and their IDs):
* Windows x86 (32-bit) (win32.win32.x86)
* Linux x86 (gtk.linux.x86)
* Linux x86-64 (gtk.linux.x86_64)
* Mac OS X Carbon (carbon.macosx)
* Mac OS X Cocoa (cocoa.macosx)
*Q: Visual Editor does not start under Linux*
*A:* Linux users may need to do the following to get the visual editor to work correctly on their machines.
* The Visual Page Editor (before JBoss Tools 3.1.0.M4) requires the library libstdc++.so.5. This library is contained in the compat-libstdc++-33.i386 package.
* To install this package on Fedora Core or Red Hat Enterprise Linux run the following command:
yum install compat-libstdc++-33.i386
** On any other rpm based distributions download libstdc++.so.5 and run the following command:
rpm -Uvh compat-libstdc++-33.i386
** On Debian and Debian based distributions (e.g. Ubuntu) run the following command:
apt-get install libstdc++5
* In case you have the library installed and you still have issue with starting the visual page editor then close all browser views/editors and leave one visual page editor open and restart eclipse. This should force a load of the right XULRunner viewer.
*Q: Visual Editor doesn't start at any platform and shows message 'The VPE editor can't be run because your system environment needs to be changed slightly'*
*A:* Check if you version of JBoss Developer Studio/JBoss Tools is compatible with you version of Eclipse, see the compatibility matrix http://community.jboss.org/docs/DOC-14297 http://www.jboss.org/community/wiki/Matrixofsupportedplatformsruntimesand...
*Q: Visual Editor starts OK, but the following message dialog appears:*
http://community.jboss.org/servlet/JiveServlet/showImage/102-10862-36-195... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-10862-36...
*A:* Some functionality of Visual Editor may not work if a project doesn't have org.jboss.tools.jsf.jsfnature or org.jboss.tools.jst.web.kb.kbnature in .project configuration. To fix this problem and turn off the message box execute next steps:
* Right mouse button click on a project in Package Explorer.
* Select +Configure -> Add JSF Capabilities+ from the context menu.
* Configure your project using +Add JSF Capabilities+ wizard and press Finish.
*P.S.* If you are shure that your project does not need JSF capabilities, just disable this message box by checking "+Do not show this dialog again!+" checkbox.
*Q: Visual Part doesn't start and "XPCOM error -2147467259" is shown*
*A:* Something bad happened with buildin xulrunner. To check it you should:
* Go to Eclipse -> Help -> About -> Installation Details... -> Configuration
* find +org.eclipse.swt.browser.XULRunnerPath+ and open this path in terminal
* try xulrunner.exe -version or ./xulrunner -version and it should show what is needed for XR to work
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-10862]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
15 years, 5 months
