Matt...

I've been looking into the de-coupling topic and have some ideas... will post a short explanation later today once I can put a diagram together.

Chris

On 11/13/06, Matt Hogstrom (JIRA) <dev@geronimo.apache.org> wrote:
    [ http://issues.apache.org/jira/browse/DAYTRADER-22?page=comments#action_12449378 ]

Matt Hogstrom commented on DAYTRADER-22:
----------------------------------------

Sounds good Piyush.  So this raises the $64k dollar question about what modes shoud run and how do they get loaded?

In direct mode I think it would be beneficial to not require any EJBs but still use JMS.  Perhaps we should open a separate JIRA to address the decoupling of components in DT.

> 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





--
"I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden