This content has been marked as final.
Show 5 replies
-
1. Re: wire enlist operation
tom.baeyens Aug 16, 2007 9:56 AM (in response to porcherg)no should be done only once.
-
2. Re: wire enlist operation
porcherg Aug 17, 2007 2:42 AM (in response to porcherg)Can we change the List of resource in StandardTransaction to a Set or can there be situations where duplicate elements are allowed ?
Guillaume -
3. Re: wire enlist operation
tom.baeyens Aug 17, 2007 2:49 AM (in response to porcherg)no. resources should be listed only once. we'll have to fine tune the auto enlisting.
-
4. Re: wire enlist operation
porcherg Aug 17, 2007 5:47 AM (in response to porcherg)I modified auto-enlist to be used only on objectDescriptor (not from references) , and only if no EnlistOperation is defined for this descriptor.
I have a question about this test:EnvironmentFactory environmentFactory = EnvironmentParser.parseEnvironmentFactoryFromXmlString( "<contexts>" + " <application/>"+ " <block>" + " <standard-transaction name='transaction' />" + " <standard-transaction name='tx' />" + " <object name='o' class='"+ MyResource.class.getName()+"'>" + " <enlist transaction='tx'/>" + " </object>" + " </block>" + "</contexts>" );
Is this declaration valid ? Which transaction should be taken as the block context transaction ?
Guillaume -
5. Re: wire enlist operation
tom.baeyens Aug 17, 2007 5:51 AM (in response to porcherg)if there are more then one standard-transaction in a block, you could add a problem in the parse. behaviour in case of more standard-transactions is irrelevant