[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[lyo-dev] New default runtime for OSLC4J samples Fwd: Proposed changes to improve OSLC4J sample app experience
|
Some initial changes in this area have now been committed:
- Jetty is now the default runtime - Tomcat will still work if desired.
- No need for separate servers for sample apps and OSLC4JRegistry - run them together on port 8080 using either Jetty or Tomcat
- Jetty launches for sample apps also launch OSLC4JRegistry in the same server. For Tomcat, publish to the same server on 8080
Regards,
Mike
---------- Forwarded message ----------
From:
Michael Fiedler <fiedler.mf@xxxxxxxxx>
Date: Fri, Jul 6, 2012 at 9:06 AM
Subject: Proposed changes to improve OSLC4J sample app experience
To: Lyo project developer discussions <
lyo-dev@xxxxxxxxxxx>
I'm proposing/working on a set of changes to improve the out of the box experience running the OSLC4J samples and reference implementations and would like any comments or concerns regarding the changes.
Bug 384472 [1] currently captures the overall work and the child bugz. Please comment there if you would like.
A summary of the proposed changes:
1. Don't require a Tomcat runtime - make Jetty the default and provide OOTB Jetty launches. But, make sure things still work on Tomcat.
2. Don't require separate app server instances for the sample apps and the OSLC4JRegistry app - let them run in the same app server
A later follow-up to #2 is:
3. Make the OSLC4JRegistry app optional. It is an interesting concept, but some/most service providers using OSLC4J will not want a separate app for the catalog.
Regards,
Mike
