[Design of JCA on JBoss] - Re: Problems JCA JMS inflow issue and tx NotSupported
by timfox
The tests really shouldn't care if the underlying implementation is using JCA or ASF.
We just need some tests that test every combination (there aren't that many), i.e.:
CMT:
tx Required:
test message receipt.
test message is not acked until onMessage returned
test throwing RuntimeException
test throwing Checked exception
test setRollbackOnly
etc
tx Not Supported
first define what the behaviour should be then do the same tests as tx required and check results conform to defined behaviour
BMT:
Check that message is acked according to ack mode specified in config, i.e. AUTO_ACK, DUPS_OK.
Check that defaults to AUTO_ACK if not specified.
use UT to being and commit /rollback tx. do some other transactional operation in the UT (e.g. send to another MDB)
Then repeat all the above using MDB on queue, topic with durable and non durable subscripton, selector etc.
So this isn't about testing the adapter, AFAIK the adapter tests look pretty thorough.
This is about testing MDB functionality, and should be agnostic of the implementation.
Then we just run the exact same of tests swapping out the invoker-proxy-binding for either JMSContainerInvoker or JCA inflow, and repeat again for JbossMQ and JBM.
Should pass all tests in all 4 configurations.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002238#4002238
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002238
19 years, 2 months
[Design of JBoss jBPM] - Re: committing content from our
by camunda
Hi tom,
anonymous wrote : sorry for late reply
no problem...
anonymous wrote : even better would be a client based on eclipse rcp. ever thought of doing that ?
Sorry, I have no experience with RCP clients, and I think they are much different from Swing ones. Also I have only be in projects working with Swing, not RCP (I experienced in bigger companies the Webstart argument is very strong, so they do not go with RCP, but I will not start this discussion here :-))
anonymous wrote : process migration is a good command. providing that functionality is on my todo list as well. i want to do this as follows: input is a processInstance, a new processDefinition and a map of old node names to new node names. any help in that is appreciated. even if your code doesn't yet have the node map integrated.
|
Our code currently updates one processInstance if the node exists with the same name in the new definition. changing that to a node-name-map should not be a big deal....
How do you organize commits, can I add everything to the HEAD in cvs and commit then when I am ready?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002210#4002210
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002210
19 years, 2 months