[JBoss Tools] - Adding some grease to JBoss Tools 3.3 M3
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post:
" Adding some grease to JBoss Tools 3.3 M3 "
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/09/19/adding-some-gr...
--------------------------------------------------------------
It's time for a new fresh milestone update of JBoss Tools:
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-17004/gr... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1700...
h4. 3.3 M3 (Greased Lightning)
[ http://www.jboss.org/tools/download/dev Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution. For this release we continue to move Maven, CDI, Java EE support forward and also add in a few new "surprise" features.
h2. Installation
As always, get and install http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 3.7 (Indigo) JEE bundle - with the JEE bundle you majority of the dependencies letting you save bandwidth:
Once you have installed Eclipse, you either find us on http://marketplace.eclipse.org/content/jboss-tools-indigo Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.
The updatesite URL to use from Help > Install New Software... is:
http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/
h3. Maven Profile Selection
In this release we've therefore included an UI which allows you to easily set/change the profiles on single and multiple projects.
This is especially something that becomes useful when you use Arquillian where it is a common practice to use Maven profiles to toggle the various dependency sets for each server you wish to test against.
It works by you selecting the relevant project(s), press *Ctrl+Alt+P* or use *Maven > Select Maven Profiles...* and then a dialog box allowing you to enable/disable the available profiles for the project(s):
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-16994/ma... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1699...
h3. Easier Remote Debugging
Ever been tired of having to manually configure ports, projects and source path lookups for debugging on Remote Applications in Eclipse ?
We are, especially after we learned that JVM's running on Hotspot provides API to discover such applications and allow for easy configuration of your debugger. In this release we've thus added a command available from *Debug As... > Remote Java Application*... in the context menu on any set of resources.
Once you select this command we use the Hotspot API to discover the remote running applications, allow you to select which you application want to connect to and then we do the tedious work of configuring the ports, names and source code lookups (including maven dependencies if applicable) for your Remote debugging.
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-16996/re... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1699...
No need for manual tweaking anymore.
Thanks to http://community.jboss.org/people/aslak Aslak Knutsen for bringing us the idea and initial code to make this happen!
h3. Running Server Detection
The server adapters now attempt to detect if a server is already running to avoid port conflicts and UI inconcistencies. If a server is detected running you are shown a dialog allowing you to choose to either have the server adapter assume it is already running or force the launch anyway.
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-17003/se... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1700...
h3. CDI & Seam Solder
The CDI tooling add a bunch of quickfixes to have JBoss Tools fix common issues. To aid in searching and navigating your CDI application Find References (*Ctrl+Shift+G*) will now show the full list of injection points and EL usage of your beans and Seam Solder and Config annotations and XML now have easy hyperlink navigation to it's declarations.
h3. @ManagedBean's
The JSF tooling now detects @ManagedBean annotations. This avoids false warnings/errors when importing JSF 2 examples. Do consider using @Named instead for better integration into the JavaEE stack.
h3. SAR Projects
For a long time we have been asked about providing support for SAR style projects for use on older versions of JBoss AS. This style of project packaging is now supported both in pure WTP style projects and via Maven.
h3. GWT Tools are back
Since last time Google released their GWT eclipse plugin in a version that supports Eclipse 3.7 allowing us to reenable the GWT Tools.
h3. And more...
There are additional bugfixes and more features to browse over at http://docs.jboss.org/tools/whatsnew/ What's New & Noteworthy
Like the new features ? Leave a comment to let us know!
And by all means,
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/09/19/adding-some-gr...]
12 years, 9 months
[JBoss Tools] - Adding some grease to JBoss Tools 3.3 M3
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post:
" Adding some grease to JBoss Tools 3.3 M3 "
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/09/19/adding-some-gr...
--------------------------------------------------------------
It's time for a new fresh milestone update of JBoss Tools:
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-17004/gr... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1700...
h4. 3.3 M3 (Greased Lightning)
[ http://www.jboss.org/tools/download/dev Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution. For this release we continue to move Maven, CDI, Java EE support forward and also add in a few new "surprise" features.
h2. Installation
As always, get and install http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 3.7 (Indigo) JEE bundle - with the JEE bundle you majority of the dependencies letting you save bandwidth:
Once you have installed Eclipse, you either find us on http://marketplace.eclipse.org/content/jboss-tools-indigo Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.
The updatesite URL to use from Help > Install New Software... is:
http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/
h3. Maven Profile Selection
In this release we've therefore included an UI which allows you to easily set/change the profiles on single and multiple projects.
This is especially something that becomes useful when you use Arquillian where it is a common practice to use Maven profiles to toggle the various dependency sets for each server you wish to test against.
It works by you selecting the relevant project(s), press *Ctrl+Alt+P* or use *Maven > Select Maven Profiles...* and then a dialog box allowing you to enable/disable the available profiles for the project(s):
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-16994/ma... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1699...
h3. Easier Remote Debugging
Ever been tired of having to manually configure ports, projects and source path lookups for debugging on Remote Applications in Eclipse ?
We are, especially after we learned that JVM's running on Hotspot provides API to discover such applications and allow for easy configuration of your debugger. In this release we've thus added a command available from *Debug As... > Remote Java Application*... in the context menu on any set of resources.
Once you select this command we use the Hotspot API to discover the remote running applications, allow you to select which you application want to connect to and then we do the tedious work of configuring the ports, names and source code lookups (including maven dependencies if applicable) for your Remote debugging.
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-16996/re... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1699...
No need for manual tweaking anymore.
Thanks to http://community.jboss.org/people/aslak Aslak Knutsen for bringing us the idea and initial code to make this happen!
h3. Running Server Detection
The server adapters now attempt to detect if a server is already running to avoid port conflicts and UI inconcistencies. If a server is detected running you are shown a dialog allowing you to choose to either have the server adapter assume it is already running or force the launch anyway.
http://community.jboss.org/servlet/JiveServlet/showImage/38-4159-17003/se... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4159-1700...
h3. CDI & Seam Solder
The CDI tooling add a bunch of quickfixes to have JBoss Tools fix common issues. To aid in searching and navigating your CDI application Find References (*Ctrl+Shift+G*) will now show the full list of injection points and EL usage of your beans and Seam Solder and Config annotations and XML now have easy hyperlink navigation to it's declarations.
h3. @ManagedBean's
The JSF tooling now detects @ManagedBean annotations. This avoids false warnings/errors when importing JSF 2 examples. Do consider using @Named instead for better integration into the JavaEE stack.
h3. SAR Projects
For a long time we have been asked about providing support for SAR style projects for use on older versions of JBoss AS. This style of project packaging is now supported both in pure WTP style projects and via Maven.
h3. GWT Tools are back
Since last time Google released their GWT eclipse plugin in a version that supports Eclipse 3.7 allowing us to reenable the GWT Tools.
h3. And more...
There are additional bugfixes and more features to browse over at http:// What's New & Noteworthy
Like the new features ? Leave a comment to let us know!
And by all means,
Have fun!
h3.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/09/19/adding-some-gr...]
12 years, 9 months
[jBPM] - problems using jbpm5 integrated with oracle and tomcat
by kishore t
kishore t [http://community.jboss.org/people/kishoret] created the discussion
"problems using jbpm5 integrated with oracle and tomcat"
To view the discussion, visit: http://community.jboss.org/message/624917#624917
--------------------------------------------------------------
Hi,
I'm trying to develop a web application using jBPM5 integrating with Tomcat7, Oracle10. I could able to start tomcat server and execute code snippet successfully after integration.
*But while opening "Process Overview" under "Console", I'm getting below exception,*
Sep 2, 2011 5:39:07 PM org.apache.mina.filter.logging.LoggingFilter log
INFO: CREATED
Sep 2, 2011 5:39:07 PM org.apache.mina.filter.logging.LoggingFilter log
INFO: OPENED
*No properties file: roles.properties found*
Sep 2, 2011 5:39:07 PM org.apache.mina.filter.logging.LoggingFilter log
INFO: RECEIVED: HeapBuffer[pos=0 lim=178 cap=2048: 00 00 00 AE AC ED 00 05 73 72 01 00 1D 6F 72 67...]
Sep 2, 2011 5:39:07 PM org.apache.mina.filter.logging.LoggingFilter log
INFO: SENT: HeapBuffer[pos=0 lim=188 cap=256: 00 00 00 B8 AC ED 00 05 73 72 01 00 1D 6F 72 67...]
Sep 2, 2011 5:39:07 PM org.apache.mina.filter.logging.LoggingFilter log
INFO: SENT: HeapBuffer[pos=0 lim=0 cap=0: empty]
*jbpm.console.directory property not found*
Sep 2, 2011 5:39:13 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [Resteasy] in context with path [/gwt-console-server] threw exception
*org.jboss.resteasy.spi.UnhandledException: java.lang.RuntimeException: Could not initialize stateful knowledge session: No Persistence provider for EntityManager named org.jbpm.persistence.jpa*
at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319)
at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230)
at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360)
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:722)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
...........
Even in console its reporting about the properties file, I've set the path in Catalina.bat as, [I'm not sure about roles.properties where to set in tomcat path?]
* set JBPM_DIRECTORY=-Djbpm.console.directory=C:/jbpm-installer/sample/evaluation/src/main/resources*
*my code snippet:*
KnowledgeBase kbase;
try {
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newClassPathResource("Evaluation.bpmn"), ResourceType.BPMN2);
kbase = kbuilder.newKnowledgeBase();
System.out.println("Process flow started ");
StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();
KnowledgeRuntimeLogger logger = KnowledgeRuntimeLoggerFactory.newThreadedFileLogger(ksession, "test", 1000);
ksession.getWorkItemManager().registerWorkItemHandler("Human Task", new WSHumanTaskHandler());
// start a new process instance
Map<String, Object> params = new HashMap<String, Object>();
params.put("employee", "krisv");
params.put("reason", "Yearly performance evaluation");
ksession.startProcess("com.sample.evaluation", params);
System.out.println("Process Id : " + ksession.getId());
logger.close();
} catch (Exception e) {
System.out.println("Exception occurred : ");
e.printStackTrace();
}
}
Also I couldn't able to start " *http://localhost:8080/drools-guvnor http://localhost:8080/drools-guvnor*", do we need any extra configurations other than libraries?
Your immediate response/help would be really greatfull. Please let me know if you need any information.
Thanks,
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/624917#624917]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 9 months
[JBoss Tools] - Error configuring application listener, Jboss-Birt integration 3.7
by Sarah Shalaby
Sarah Shalaby [http://community.jboss.org/people/sara.shalaby] created the discussion
"Error configuring application listener, Jboss-Birt integration 3.7"
To view the discussion, visit: http://community.jboss.org/message/626126#626126
--------------------------------------------------------------
Hi
I am new to birt.
I am using eclipse 3.7,birt 3.7 , apache 7
I downloaded the birt plugin and the jboss-birt integration
through the eclipse download manager
I created a web project and enabled seam2.2 facets
I created a report and tried to call it in the xhtml page.
When i run the server i get this error.
Has the jboss-birt integration been upgraded for the birt 3.7 runtime?
09-Sep-2011 02:50:58 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class org.eclipse.birt.report.listener.ViewerHttpSessionListener
java.lang.ClassNotFoundException: org.eclipse.birt.report.listener.ViewerHttpSessionListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1676)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1521)
at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:415)
at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:397)
at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:118)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4638)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5204)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5199)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
09-Sep-2011 02:50:58 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class org.eclipse.birt.report.listener.ViewerServletContextListener
java.lang.ClassNotFoundException: org.eclipse.birt.report.listener.ViewerServletContextListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1676)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1521)
at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:415)
at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:397)
at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:118)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4638)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5204)
at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5199)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
09-Sep-2011 02:50:58 org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)
09-Sep-2011 02:50:58 org.apache.catalina.core.StandardContext startInternal
Thanks
Sarah
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/626126#626126]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 9 months
[jBPM] - Re: StatefulKnowledgeSession signalEvent method
by Geoff Pole
Geoff Pole [http://community.jboss.org/people/instanceof] created the discussion
"Re: StatefulKnowledgeSession signalEvent method"
To view the discussion, visit: http://community.jboss.org/message/627079#627079
--------------------------------------------------------------
Hi,
In case this helps others.
I had this slightly backwards. It wasn't the second signal event call that was making the ProcessInstancesWaitingForEvent run. Instead this query appears to run every time a process enters and 'End' node. Presumably it does this so that it can find any workflows that may be listening for an End event.
I don't know the reason why the ProcessInstancesWaitingForEvent runs so slowly (Oracle 11g) when there are many workflow instances that are waiting for events, but I did find that by applying this index reduced the running time from around 45 seconds to under 1 second with 20000 workflow instances.
CREATE unique INDEX idx_eventtypes_id_elem
ON EventTypes (instanceid, element)
I tested this up to 100000 workflow instances and the query still runs sub second.
Cheers,
Geoff
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627079#627079]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 9 months
Re: [jboss-user] [JBoss Tools] - Coping with versions in large multi-module osgi projects
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] commented on
"Coping with versions in large multi-module osgi projects"
To view all comments on this blog post, visit: http://community.jboss.org/community/tools/blog/2011/09/17/coping-with-ve...
--------------------------------------------------
Ian,
regarding PDE/Build - Tycho does the exact same thing with 1.0.0.qualifier - this is no different at all, the same version is never reused for the same bundle for releases.
regarding "If *nothing* changes in a bundle then the version should not change", I agree that is the optimal goal but as you just wrote .qualifier gets changed anyway by the build so this actually happens anyway if you dont remove the .qualifier. And please note, I'm not saying we are putting the same version on all 628 artifacts - just setting one version per module (so 628 becomes 42 instead which )
"Eclipse project has 400 bundles and they manage their versions without bumping each bundle for each build" - that is not what im seeing, they have .qualifier too. Anyway, Eclipse project also have a good deal of more people to handle these versions. That is another approach we could take, reduce the number of modules and version them individually but the end result would be similar... smaller set of managable artifacts all released at the same time - but now you can install smaller parts :)
note, map files is actually the key part missing in Tycho/maven workflow to avoid full rebuilds at release builds IMO, but that does not solve the problems for continous integration builds.
I know about jar.comparator/API Tools (which btw. is pretty good but *awfully* slow and tricky to get setup all across modules without either having PDE or Tycho die in the process ;( - and even if we had it up and running it would just help about detecting the needed version bumps and there would still need to be a step that goes through and ensures pom.xml, manifest.mf, feature's, etc. are in sync.
--------------------------------------------------
12 years, 9 months
