Marina Vatkina wrote:
> Hi Anissa,
>
> Thank you for the update.
>
> Anissa Lam wrote:
>> Hi Marina,
>>
>> If you are talking about just the configuration, ie, the
>> Configuration -> Transaction Service tree node and screen, then
>> there is no special backend code needed. The standard AMX bean will
>> do.
>
> Let's keep our fingers crossed - not everything is smooth when
> transactions from v2 to v3 :(.
>
>>
>> There is also a screen to 'Recover Transaction' which is presented
>> as a tab for server instance. In v2, there is no AMX method to
>> support this, and we have to invoke the method
>> 'recoverTransactions' on the mbean
>> "com.sun.appserv:type=transactions-recovery,category=config", passing
>> in the instance name and the log directory. We probably need
>> someone to make this method avaiable through AMX.
>
> I think there was an event listener for this and/or CLI-based
> requests. The tx recovery is there, so only the glue code is needed
> (AMX or whatever it is in v3).
>
>>
>> As for when this plugin will be available, I am not sure at this
>> point. My estimate for this work, assuming AMX bean and method is
>> there, is about 1 week time to create a plugin module to support the
>> above functionality.
>
>
> On which side of the code?
I mean if the backend is ready, and there is the API for GUI to call to
support the configuration and recover Transaction, it will take me 1
week to create this plugin module and provide the support.
>
> I also want to know if it makes sense to have a
>> EJB plugin module to configure the EJB container, the Transaction
>> Service and support Recover Transaction.
>
> Transaction Service is separate from EJB (you can use transactions in
> a pure web container). So there should be 2 plugins.
>
So, in this plugin, you only want 2 screen, Transaction Service and
Recover Transaction, is this correct ?
thanks
Anissa
> thanks,
> -marina
>
>>
>>
>> thanks
>> Anissa.
>>
>>>
>>> Anissa Lam wrote:
>>>
>>>>
>>>> Hi Marina,
>>>>
>>>> I will need to look at the GUI code to see if we need any 'special'
>>>> API besides the standard AMX mbean that I assume will be provided
>>>> to us. I am with another high priority task right now, will look
>>>> at that late next week.
>>>> If you don't from me by next Friday, please ping me again.
>>>>
>>>> thanks
>>>> Anissa
>>>>
>>>> Marina Vatkina wrote:
>>>>
>>>>> Ken, Anissa, admin team,
>>>>>
>>>>> Happy New Year!
>>>>>
>>>>> Can somebody please answer my question:
>>>>>
>>>>> >> Do I need to do anything to have tx service support back in place
>>>>> >> in adminGUI in V3 final or will the admin team do all the work?
>>>>> And if
>>>>> >> it's the latter, is there a due date when I can expect it to be
>>>>> >> available?
>>>>>
>>>>>
>>>>> thanks,
>>>>> -marina
>>>>>
>>>>>> Marina Vatkina wrote:
>>>>>>
>>>>>>> Ken,
>>>>>>>
>>>>>>> To make sure we are on the same page: I know it's not there in
>>>>>>> the adminGUI in prelude. I also know that CLI support in prelude
>>>>>>> was available only for asadmin set operations.
>>>>>>>
>>>>>>> What I'm asking about is if I need to do anything to have it in
>>>>>>> place in adminGUI in V3 final or will the admin team do all the
>>>>>>> work? And if it's the latter, is there a due date when I can
>>>>>>> expect it to be available?
>>>>>>>
>>>>>>> thanks,
>>>>>>> -marina
>>>>>>>
>>>>>>> Ken Paulsen wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Hi Marina,
>>>>>>>>
>>>>>>>> For v3 prelude, we did not provide any UI to configure the TX
>>>>>>>> Service. I'm not sure if CLI has a way, they might... I cc'd
>>>>>>>> the admin_at_gf alias, maybe someone there knows more than me (not
>>>>>>>> hard!). ;)
>>>>>>>>
>>>>>>>> Good luck!
>>>>>>>>
>>>>>>>> Ken
>>>>>>>>
>>>>>>>> Marina Vatkina wrote:
>>>>>>>>
>>>>>>>>> Ken, Anissa,
>>>>>>>>>
>>>>>>>>> What needs to be done to enable it in V3 for the same set of
>>>>>>>>> functionality as in V2? It's not there in prelude...
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> -marina
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>