[JBoss JIRA] Created: (JBESB-531) Scoped queue-service.xml's for quick starts
by Tom Cunningham (JIRA)
Scoped queue-service.xml's for quick starts
-------------------------------------------
Key: JBESB-531
URL: http://jira.jboss.com/jira/browse/JBESB-531
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 1
Environment: Mac OS X, java 1.5.0_07
Reporter: Tom Cunningham
Assigned To: Mark Little
For the helloworld quick start we provide both a jbm-queue-service.xml and a jbm-queue-service-scoped.xml for deployment to different appservers. We should probably be consistent and supply this across the board. However, for the rest of the quickstart samples, we only supply a jbm-queue-service.xml.
Also, maybe there should be an ant target which incorporates the scoped version of the xml? The jar target always seems to pick up the jbm-queue-service.xml (non-scoped) version.
Also, the GettingStarted.pdf which covers the HelloWorld example doesn't talk about the situations where we'd want to use one version over the other. Should that be something that should be added to the documentation?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBESB-530) GettingStarted.pdf should be updated with service information
by Tom Cunningham (JIRA)
GettingStarted.pdf should be updated with service information
-------------------------------------------------------------
Key: JBESB-530
URL: http://jira.jboss.com/jira/browse/JBESB-530
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.2 Milestone Release 1, 4.2 Milestone Release 2
Environment: Mac OS X 10.4.9, java 1.5.0_07
Reporter: Tom Cunningham
Assigned To: Mark Little
The GettingStarted.pdf information on how to get the Hello World QuickStart working that seem old.
Step 1 says "Copy samples/quickstarts/esb-quickstart-service.xml to your JBoss application server".
In MR1, there isn't a esb-quickstart-service.xml, we have two service xml's, one for jboss-messaging and another for jboss-mq. There are:
esb-quickstart-jbm-service.xml
esb-quickstart-jbmq-service.xml
There probably should be another step in there which explains how to install the jboss-messaging stuff if they want to use the esb-quickstart-jbm-service.xml xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBESB-849) Should smooks test be an integration test?
by Mark Little (JIRA)
Should smooks test be an integration test?
------------------------------------------
Key: JBESB-849
URL: http://jira.jboss.com/jira/browse/JBESB-849
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Tom Fennelly
Priority: Trivial
[java] [junit] 10:22:35,254 ERROR [main][SmooksInstanceManager] Lookup of the JMS ConnectionFactory failed for the Transformation configuration Update Listener. Update listener not enabled!
[java] [junit] org.jboss.soa.esb.ConfigurationException: JNDI lookup of JMS Connection Factory [ConnectionFactory] failed.
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.getJmsConnectionFactory(SmooksInstanceManager.java:161)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.connect(SmooksInstanceManager.java:203)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:122)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:109)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager.<init>(SmooksInstanceManager.java:67)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialiseLocalSmooksInstanceManager(SmooksTransformer.java:236)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialise(SmooksTransformer.java:218)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.transform(SmooksTransformerUnitTest.java:82)
[java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.test_trans(SmooksTransformerUnitTest.java:69)
indicates that the test needs JMS set up beforehand. So doesn't that tend to imply it's an integration test?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBESB-1438) JMS Courrier does not support transacted mode
by Jiri Pechanec (JIRA)
JMS Courrier does not support transacted mode
---------------------------------------------
Key: JBESB-1438
URL: http://jira.jboss.com/jira/browse/JBESB-1438
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow, Rosetta
Affects Versions: 4.2.1
Reporter: Jiri Pechanec
Assigned To: Mark Little
Priority: Blocker
Fix For: 4.2.1 CP1
JMS Courrier (deliver side) operates only with non-transacted queue sessions. This prevents jBPM integration to work correctly. The problem can be sketched this way
1) The message is received via JMS/JCA listener, transaction is started
2) jBPM process is invoked
3) jBPM process sends message (calls service) in non-transacted mode
Three situations can happen
1) Exception is thrown later, it means that global transaction is rolled back but another service was already invoked - BUG
2) jBPM process goes to the wait state and waits for response from ESB, global transaction is committed, called service sends back signal to continue process - OK
3) jBPM process goes to the wait state and waits for response from ESB, called service sends back signal to continue process - but the global transaction was not committed yet - BUG
This is key feature to have ESB/jBPM integration working safely.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months