[JBoss Tools] - JBoss Tools vs Developer Studio
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the document:
"JBoss Tools vs Developer Studio"
To view the document, visit: http://community.jboss.org/docs/DOC-13300
--------------------------------------------------------------
Below is a comparison matrix to illustrate what parts of JBoss Tools have been included in the various releases of Developer Studio and which additional out-of-the-box setup and software Developer Studio provides. It should be noted that JBoss Tools is a set of plugins that can be installed into Eclipse while Developer Studio makes the getting started out-of-the-box experience easier and simpler. This is evident in the matrix below with entries showing that Developer Studio has an installer that helps in configuring your runtimes, distributes Eclipse and WTP, and includes support for the supported platforms from JBoss (EAP, EWP, EWS, SOA, and EPP).
||
|| *JBoss Tools 2.x* || *JBoss Tools 3.0.x* || *JBoss Tools 3.1* || JBoss Tools 3.2.x
|| JBoss Tools 3.3.x
(Core & SOA) || *Developer Studio 1.x* || *Developer Studio 2.x* || *Developer Studio 3.0.x* || *Developer Studio 4.0.x* || *Developer Studio 4.1.x* || Developer Studio 5.0.x
(Core & SOA) ||
| *Features:* |
|
|
|
|
|
|
|
|
|
|
|
| Hibernate | X | X | X | X | X | X | X | X | X | X | X |
| Seam | X | X | X | X | X | X | X | X | X | X | X |
| CDI (JSR-299) |
|
| X | X | X |
|
| X (Tooling Tech Preview) | X (Tech preview) | X (Tech preview) | X |
| jBPM | X | X | X | X (v3 & 4) | X (SOA) | X | X | X | X (v3 only) | X (v3) | X (SOA) |
| Visual Page Editor | X | X | X | X | X | X | X | X | X | X | X |
| FreeMarker | X | X | X | X | X | X | X | X | X | X | X |
| Struts | X | X | X | X | X | X | X | X | X | X | X |
| JBoss AS | X | X | X | X | X | X | X | X | X | X | X |
| Project Archives | X | X | X | X | X | X | X | X | X | X | X |
| Drools |
| X | X | X | X (SOA) |
| X | X | X | X | X (SOA) |
| Portlet |
| X | X | X | X |
| X | X | X | X | X |
| ESB |
| X | X | X | X (SOA) |
| X | X | X | X | X (SOA) |
| JBoss Webservices |
| X | X | X | X |
| X | X | X | X | X |
| Smooks |
| X | X | X | X (SOA) |
|
| X | X | X | X (SOA) |
| Birt Integration |
| X | X | X | X |
|
|
|
|
|
|
| TPTP Integration |
| X | X | X | (TPTP not part of Indigo) |
|
| X (requires TPTP to be installed) | X (requires TPTP to be installed) | X (requires TPTP to be installed) | (TPTP not part of Indigo) |
| Maven |
|
| X (requires m2eclipse) | X (requires m2eclipse) | X (requires m2e) |
|
|
|
|
| X |
| Usage (tracking) |
|
|
| X | X |
|
|
| X | X | X |
| Modeshape |
|
|
| X | X (SOA) |
|
|
| X | X | X (SOA) |
| Teiid |
|
|
| X | X (SOA) |
|
|
| X | X | X (SOA) |
| Delta Cloud |
|
|
| X | X |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| *Setup:* |
|
|
|
|
|
|
|
|
|
|
|
| Zip | X | X | X (deprecated) |
|
|
|
|
|
|
|
|
| Update site | X | X | X | X | X |
| X (since 2.1) | X | X | X (+extras) | X (Core & SOA) |
| Archived Update Site |
|
| X | X | X |
|
|
| (X) |
|
|
| Installer |
|
|
|
|
| X | X | X | X | X | X (Core) |
|
|
|
|
|
|
|
|
|
|
|
|
|
| *3rd Party plugins:* |
|
|
|
|
|
|
|
|
|
|
|
| Eclipse |
|
|
|
| X | X | X (3.4) | X (3.5) | X (3.6) | X (3.6+) | X (3.7) |
| Web Tools |
|
|
|
| X | X | X | X | X | X | X |
| SpringIDE |
|
|
|
| X | X | X | X | X | X | X (extras) |
| TestNG |
|
|
|
| X | X | X | X | X | X | X (extras) |
|
|
|
|
|
|
|
|
|
|
|
|
|
| *Integrated Platforms:* |
|
|
|
|
|
|
|
|
|
|
|
| JBoss Enterprise Application Platform |
|
|
|
|
| X (EAP 4) | X (EAP 4) | X (EAP 4) | X (EAP 5) | X (EAP 5) | X (EAP 6) |
| JBoss SOA Platform |
|
|
|
|
|
| X (separate download) | X (separate download) | X (separate download) | X (seperate download) | X (seperate download) |
| JBoss Enterprise Portal Platform |
|
|
|
|
|
| X (separate download) | X (separate download) | X (separate download) | X (separate download) | X (separate download) |
| JBoss Enterprise Web Server |
|
|
|
|
|
|
| X (separate download) | X (separate download) | X (seperate download) | X (seperate download) |
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-13300]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 7 months
- 1
- 0
[jBPM] - When does jBPM instantiate its assignment related classes?
by Ramiro Pereira de Magalhães
Ramiro Pereira de Magalhães [http://community.jboss.org/people/ramiro] created the discussion
"When does jBPM instantiate its assignment related classes?"
To view the discussion, visit: http://community.jboss.org/message/624171#624171
--------------------------------------------------------------
I have some questions regarding the exact moment of instantiation (and persistence) of certain jBPM classes. Can someone explain to me...
1) ...when Swimlanes are instantiated? Is it when the process is instantiated, or when a task that depends on a swimlane is instantiated? Maybe when we enter a task node?
2) ...when PooledActors are instantiated? Is it when Swimlanes are instantiated?
3) ...when jBPM assigns tasks to someone? When it creates a process instance? When it enters a node? When it leaves a node?
Cheers,
Ramiro Pereira de Magalhães
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/624171#624171]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 7 months
- 1
- 0
[jBPM] - Is there a way to plug into jBPM another default AssignmentHandler?
by Ramiro Pereira de Magalhães
Ramiro Pereira de Magalhães [http://community.jboss.org/people/ramiro] created the discussion
"Is there a way to plug into jBPM another default AssignmentHandler?"
To view the discussion, visit: http://community.jboss.org/message/624170#624170
--------------------------------------------------------------
Hi guys,
is there a way to plug into jBPM a custom default AssignmentHandler? Is there a factory, like other jBPM services?
Note that I'm aware of the existence of the "class" attribute of JPDL's assignment element. It happens that I have some very peculiar assignment rules that all processes' tasks will share and I just don't want to copy and paste the same value for every task node I create.
Thanks,
Ramiro Pereira de Magalhães
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/624170#624170]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 7 months
- 1
- 0
[JBoss Messaging] - Stalled Queue Consumer on Windows(NIO) with Large Message and ConsumerWindow
by Adam Malter
Adam Malter [http://community.jboss.org/people/amalter] created the discussion
"Stalled Queue Consumer on Windows(NIO) with Large Message and ConsumerWindow"
To view the discussion, visit: http://community.jboss.org/message/624167#624167
--------------------------------------------------------------
Hi All,
We use HornetQ as our development JMS provider, and I'm trying to get everyone comfortable enough to upgrade it to production. Having some troubles however when we really start to bang on it.
This is the case:
HornetQ running in our old customized JBoss instance (I won't even mention the version number, needless to say we've re-written enough stuff that I worry my case is not generic/easily reproducible)
Anyway - this is what I'm seeing..
Server config is:
Configuration config = new ConfigurationImpl();
config.setPersistenceEnabled(true);
config.setJournalDirectory(FileUtil.buildPath(rootData, "journal").getPath());
config.setBindingsDirectory(FileUtil.buildPath(rootData, "bindings").getPath());
config.setPagingDirectory(FileUtil.buildPath(rootData, "paging").getPath());
config.setLargeMessagesDirectory(FileUtil.buildPath(rootData, "lobs").getPath());
config.setPersistDeliveryCountBeforeDelivery(true); //required for redelivery count to work on rollbacks
if (SystemUtils.IS_OS_WINDOWS) {
config.setJournalType(JournalType.NIO);
}
//HornetQ requires cluster user and pw or spits out warnings
config.setClustered(false);
config.setClusterUser("tcuser");
config.setClusterPassword("tradecard");
config.setSecurityEnabled(false);
//Simple Q Service for now - only in VM transport
config.getAcceptorConfigurations().add(new TransportConfiguration(InVMAcceptorFactory.class.getName()));
config.setCreateJournalDir(true);
config.setCreateBindingsDir(true);
Contents of hornetq-version.properties from our jar file:
hornetq.version.versionName=HQ_2_2_5_FINAL_AS7
hornetq.version.majorVersion=2
hornetq.version.minorVersion=2
hornetq.version.microVersion=5
hornetq.version.incrementingVersion=121
hornetq.version.versionSuffix=Final
hornetq.version.versionTag=Final
hornetq.netty.version=3.2.3.Final-r${buildNumber}
hornetq.version.compatibleVersionList=121
We're running in XA mode with durable queues and no selectors or funny priorities. Additionally, the issue only occurs when I leave the consumer window size at default. If I change setConsumerWindowSize(0), my issue disappears.
So inside a single transaction, I send about 10 ~512kb to the same destination. Destination receives them okay, starts to process them, and then triggers an application level error (In this case I'm purposefully triggering it to test our resubmit handling)
Our application logic is that we try to process the message a pre-set number of times (lets say 3) and before moving it to dead letter. This usually happens on the very first rollback, but not always - essentially the consumer/mdb picks up a message, rolls it back, starts new tx, tries to pick up another one and then hangs with the following stack:
"AuditMDB[000]" - Thread t@113
java.lang.Thread.State: TIMED_WAITING
at java.lang.Object.wait(Native Method)
- waiting on <1a647ea> (a org.hornetq.core.client.impl.LargeMessageControllerImpl)
at org.hornetq.core.client.impl.LargeMessageControllerImpl.waitCompletion(LargeMessageControllerImpl.java:304)
at org.hornetq.core.client.impl.LargeMessageControllerImpl.saveBuffer(LargeMessageControllerImpl.java:283)
at org.hornetq.core.client.impl.ClientLargeMessageImpl.checkBuffer(ClientLargeMessageImpl.java:201)
at org.hornetq.core.client.impl.ClientLargeMessageImpl.getBodyBuffer(ClientLargeMessageImpl.java:101)
at org.hornetq.jms.client.HornetQBytesMessage.getBuffer(HornetQBytesMessage.java:451)
at org.hornetq.jms.client.HornetQBytesMessage.readBytes(HornetQBytesMessage.java:248)
at com.tradecard.server.util.BytesMessageInputStream.read(BytesMessageInputStream.java:68)
at com.tradecard.framework.util.ChunkedByteBuffer.append(ChunkedByteBuffer.java:344)
at com.tradecard.framework.util.ChunkedByteBuffer.append(ChunkedByteBuffer.java:332)
at com.tradecard.server.mdb.HornetQContainerInvoker$HornetQServerSession.run(HornetQContainerInvoker.java:287)
at java.lang.Thread.run(Thread.java:662)
Locked ownable synchronizers:
- None
The somewhat relevant portions of our Hornet Invoker are:
xaResource = ((XAQueueSession)session).getXAResource();
txManager.begin();
tx = txManager.getTransaction();
tx.enlistResource(xaResource);
pooledSession.syncRegister();
tx.registerSynchronization(pooledSession);
//cache the session/senders for QueueSender to use
TransactionCache.put(TransactionCache.MQXA_SESSION, pooledSession);
txid = TransactionToolbox.getGlobalTransactionId();
Message requestMessage = null;
requestMessage = receiver.receive(2000);
if (requestMessage != null && !quit) {
Message message = null;
try {
BytesMessage bytesMessage = (BytesMessage)requestMessage;
BytesMessageInputStream stream = new BytesMessageInputStream(bytesMessage);
ChunkedByteBuffer buffer = new ChunkedByteBuffer(10000, 100);
buffer.append(stream); // <--- hanging here
....
There doesn't seem to be anyone owning the lock. Eventually I get timeout warnings from my TxManager and have to bounce the server. As soon as I bounce, it picks up another message and processes, quickly getting the error again.
Additionally, I can see a number of files pending in my lobs directory.
All of our custom infrastructure makes it difficult to extract the case into a postable test case. However, if anyone thinks it worthwhile and this doesn't seem like anything straight forward, I'll make the attempt.
The idea for setting the consumer window size to zero came from the following closed bug - https://issues.jboss.org/browse/HORNETQ-111 https://issues.jboss.org/browse/HORNETQ-111
Thanks for your time and any help!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/624167#624167]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 7 months
- 1
- 0