geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piyush Agarwal (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (DAYTRADER-22) Set publichQuotePriceChange to true in ejb-jar.xml so that MDBs get accessed during Daytrader scenario runs
Date Mon, 13 Nov 2006 22:00:37 GMT
    [ http://issues.apache.org/jira/browse/DAYTRADER-22?page=comments#action_12449503 ] 
            
Piyush Agarwal commented on DAYTRADER-22:
-----------------------------------------

Matt, the only dependency on EJBs within the TradeDirect code is in the Asynch 1-phase mode.
It seems that the dependency on EJBs is due to need for support of multiple  transactions
within each other but not clear on that. Does anyone use the Async 1-phase mode. Wouldn't
the Async 2-phase be the relevant one? If no one is using the Async 1-phase then we can remove
it and simplify the runtime modes to be
1) Direct
2) EJB
3) Asynch 2-phase (or  Enable TradeBroker)

The publishQuotePriceChange would be another flag with the name "Enable TradeStreamer". We
can provide explanations of each of these in detail. 
Anything I overlooked ?

> Set publichQuotePriceChange to true in ejb-jar.xml so that MDBs get accessed during Daytrader
scenario runs
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DAYTRADER-22
>                 URL: http://issues.apache.org/jira/browse/DAYTRADER-22
>             Project: DayTrader
>          Issue Type: Bug
>          Components: EJB Tier
>    Affects Versions: 1.2
>            Reporter: Piyush Agarwal
>         Assigned To: Matt Hogstrom
>             Fix For: 1.2
>
>         Attachments: Daytrader-22.patch
>
>
> Currently the publishQuotePriceChange is set to False in the ejb-jar.xml and this causes
the TradeStreamerMDB to NOT be accessed during the Daytrader trading runs. The TradeStreamerMDB
listens to the JMS messages and invokes the logging code to log the debug and trace messages
during the runs. Updating the flag to true enables this functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message