Hi Forrest,

Are you planning to do anything more with the Daytrader?

There was some discussion in http://issues.apache.org/jira/browse/DAYTRADER-68 about next steps with this web-only version of daytrader ... but that was a while ago and I'm not sure if you are still working on these items or if they were displaced by other more pressing issues.

Included in jira discussion you mentioned that you would be working on several things, among those: - a description of how the web-only version differs from the full Daytrader including changes made for removal of EJB/JPA dependencies.
- support for jetty in addition to tomcat for the web-only version
- better instructions in readme for installation on both the minimal assemblies and tomcat/jetty containers
- investigation into non-container managed JPA for db access
- possible creation of plugins for the webonly installation
- and perhaps some work on the dependencies and datasource deployment plan.

Can you fill us in on the latest on these items?

Thanks,
Joe

Joe Bohn wrote:
Are you getting any closer Forrest? As Kevan mentioned, it might be helpful to get this contributed so that others can collaborate.

Thanks,
Joe


Kevan Miller wrote:

On Apr 9, 2009, at 11:26 AM, Forrest Xia wrote:

Hi Joe,

We recently found some problems in some primitive servlets, so the tomcat version is not really ready for contribution.

As to how to package it into daytrader code base, rough idea is to create a sub module in daytrader root, and use maven-war-plugin to create a war ball for tomcat deployment.

|-- It would be cool if we could figure out a way (using plugins?) to install the core Daytrader (simplified) and extend it with the full function |-- by another plugin for more robust environments.

I will try to see if it is possible, thank you for your suggestion :)

Hi Forrest,
Things don't have to be perfect before you can start collaborating with community members. Understand the desire to get everything "just so". But you might find that other people are willing to help and answer questions.

--kevan




Reply via email to