[JBoss Tools] - Let's go to Kepler!
by Max Rydahl Andersen
Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] modified the blog post:
"Let's go to Kepler!"
To view the blog post, visit: https://community.jboss.org/community/tools/blog/2013/03/12/lets-go-to-ke...
--------------------------------------------------------------
Today we are releasing with the first Alpha of JBoss Tools 4.1 and Developer Studio 7.0 targeting Eclipse 4.3 also known as the Kepler release.
https://community.jboss.org/servlet/JiveServlet/showImage/38-4854-18193/j... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-4854-181...
Developer Studio: [ http://devstudio.jboss.com/earlyaccess Download] | Tools: [ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/development/kepler/ 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 exists for JBoss and related technologies in the default Eclipse distribution.
JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation.
If you are into doing your own bleeding edge eclipse plugin assembly, JBoss Tools is for you; if you are more into having something that "Just Works" then JBoss Developer Studio is the way to go.
h2. Installation
This release is an alpha and is built against http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 4.3 M5, and as such things can and will still change before the final Kepler release.
We therefore recommend you use the https://devstudio.jboss.com/earlyaccess/7.0/ JBoss Developer Studio installer to be sure you got the right Eclipse distribution, but you can of course use http://download.jboss.org/jbosstools/updates/development/kepler/ JBoss Tools updatesite (note: url has changed since the Juno based release) if you wish - just be sure you are using Eclipse 4.3 Kepler M5 when doing so.
h2. Improvements
As mentioned above we are now targeting Eclipse Kepler to pickup the new features, bugfixes and performance improvements made since Eclipse Juno - we are releasing this Alpha to get early feedback on our tools but just as much on Kepler so we can actually get any remaining issues fixed before the release train ships this summer. Please report bugs to us or eclipse.org directly if you find an issue that is reproducible even without JBoss Tools installed.
Beyond that a few other highlights sneaked into this Alpha...
h3. JBoss Enterprise Application Platform 6.1 Alpha Support
Last week Mark Little announced that https://community.jboss.org/blogs/mark.little/2013/03/07/eap-binaries-ava... EAP 6.1 Alpha is now freely available for Developers and you can get it from http://www.jboss.org/jbossas/downloads http://www.jboss.org/jbossas/downloads JBoss AS download page. This release of tools provides support for EAP 6.1 Alpha.
Note: we will soon have an update to JBoss Tools 4.0 and Developer Studio 6.0 to provide similar support but if you want to get started today with the alpha of JBoss EAP use this alpha tooling with it.
h3. BrowserSim w/Firebug
BrowserSim now includes Firebug for easy inspection of dom and css styles.
http://docs.jboss.org/tools/whatsnew/vpe/images/4.1.0.Alpha1/Firebug-Lite... http://docs.jboss.org/tools/whatsnew/vpe/images/4.1.0.Alpha1/Firebug-Lite...
h3. Content assist for JSF xml namespace
XML namespace (xmlns) content assist now looks at your other pages and a list of standard xmlns when you are editing JSF pages and insert
the appropriate xmlns declaration if your page is missing it. Alexey made a nice video showing how this works.
h3. CDI DeltaSpike 0.3
The initial DeltaSpike CDI integration now work with DeltaSpike 0.3.
h2. Forge updates
Forge tools now bundles Forge 1.2
http://docs.jboss.org/tools/whatsnew/forge/images/4.1.0.Alpha1/about.png http://docs.jboss.org/tools/whatsnew/forge/images/4.1.0.Alpha1/about.png
h3. Maven JPA/JSF/JAX-RS Configurators moved to Eclipse
As Fred wrote earlier we contributed the JPA/JSF/JAX-RS Configurators we made to eclipse.org and thus in this Kepler
release we no longer bundle our own but rely on the new. This means the configuration of these moved under the main
Maven > Java EE Integration preference.
http://docs.jboss.org/tools/whatsnew/images/m2e-wtp-optional-configurator... http://docs.jboss.org/tools/whatsnew/images/m2e-wtp-optional-configurator...
These configurators enables the JSF, JPA and JAX-RS tooling if your maven pom and project are depending or
using these features.
h2. Giving Feedback
There are more news and screenshots in What's New, and if you got an idea to an improvement or found a bug do not hestiate to open an issue in our https://jira.jboss.org/jira/browse/JBIDE issue tracker.
h2. What's Next ?
We are not standing still and our roadmap for the upcoming release includes JQuery Mobile support in our palette and html5 source editor, a whole new feature using LiveReload, Apache Cordova tooling and simulator, Better JavaScript support in Eclipse, easier management of your OpenShift applications and more...
Follow this blog for more or contact us on our https://community.jboss.org/community/tools?view=discussions forum and irc if you are interested in contributing!
And don't forget....Have fun!
h2.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/community/tools/blog/2013/03/12/lets-go-to-ke...]
13 years, 1 month
[jBPM] - jBPM5 - Can't Scale, Won't Scale
by M Arnold
M Arnold [https://community.jboss.org/people/m_arnold123] created the discussion
"jBPM5 - Can't Scale, Won't Scale"
To view the discussion, visit: https://community.jboss.org/message/771731#771731
--------------------------------------------------------------
Hi,
I'm having great trouble designing an application which uses jBPM5 in a scalable way. It seems to be impossible on a practical level. I hope that this is just due to my misunderstandings of the way the jBPM5 works.
I have listed each of my assumptions, and the ramifications of each below. I hope that someone from the community will be able to point out where these assumptions are incorrect.
I would particularly appreciate it if anyone has managed to scale jBPM5, and could described how they achieved it.
1. Everytime jBPM5 executes a process the database transaction updates the process instance info AND the session info, therefore:
1a. it's not scalable to use a single session to execute all processes, or you would suffer contention on the session info.
1b, it's not scalable to use a single session to execute all processes in a cluster, or the updated session info would have to be continually synchronised across the cluster.
2. When using BPMN2 events, jBPM5 only allows you to send events to the process instances within a single session at a time. You need to maintain a list of all the sessions which have incompleted process instances(*), and loop through them all to send events. Therefore:
2a. you should execute all processes in as few sessions as possible, to lessen the number of iterations through this loop.
3. jBPM5 persists BPMN2 timer info in the session info, but the session must be active (ie. loaded from persistence) in order for the timers to activate. Therefore:
3a. when your application starts, you must load all sessions that have active process instances that have timers(**).
3b. you must not have the same session active in two different nodes of a cluster, or the same timers will expire around the same time
3c. when a node crashes, your application must detect this and reload the sessions that were active in the crashed node
4. If you start a process instance in a session, that process instance must always be executed in that session.
4a. when a node wishes to resume a process instance that was persisted, it must first (due to 3b) ask all other nodes if they have the session active, and if so instruct them to dispose it. It can then load the session, load and resume the process. All while preventing race conditions.
4b. when a node receives an event it must (due to 2) carry out all the processing in 4a for each session with active process instances.
(*) I don't think it's possible to know if a session has incompleted process instances..?
(**) I don't think it's possible to know if a session and timers..?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/771731#771731]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 1 month
