[jira] Commented: (CONNECTORS-38) There should be an LCF startup path that uses Jetty for running lcf-crawler-ui and lcf-authority-service

2010-07-06 Thread Karl Wright (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12885746#action_12885746
 ] 

Karl Wright commented on CONNECTORS-38:
---

Code complete.  There's now a dist/example directory, and you run lcf with the 
command java -jar start.jar from that directory, just like Solr.

Documentation needs updating, but otherwise this ticket is complete.


 There should be an LCF startup path that uses Jetty for running 
 lcf-crawler-ui and lcf-authority-service
 

 Key: CONNECTORS-38
 URL: https://issues.apache.org/jira/browse/CONNECTORS-38
 Project: Lucene Connector Framework
  Issue Type: Improvement
  Components: Framework core
Reporter: Karl Wright

 Integrating with Jetty would allow LCF to be deployed in simple cases without 
 requiring Tomcat, which would simplify the setup in such cases.  This of 
 course should not be construed as removing the support for Tomcat-style web 
 applications.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (CONNECTORS-38) There should be an LCF startup path that uses Jetty for running lcf-crawler-ui and lcf-authority-service

2010-07-02 Thread Karl Wright (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12884651#action_12884651
 ] 

Karl Wright commented on CONNECTORS-38:
---

I've started to look at what would be necessary to perform this work.  If the 
quick-start implementation will be using embedded derby, then it must run in 
a single process (or derby is not happy at all).  That would include the 
crawler ui, the authority service, and the crawler daemon.

If jetty can be configured to run in such a way as to use system classes for 
all of its web applications, then in theory it should be possible to put 
together an LCF which, on startup, spawns the crawler daemon before starting up 
jetty within the same process.  For the classloader issue, there seems to be a 
considerable degree of configuration flexibility, as described here:

http://docs.codehaus.org/display/JETTY/Classloading

The rest of the problem, i.e. starting and stopping jetty programmatically, may 
be doable based on this page:

http://docs.codehaus.org/display/JETTY/Embedding+Jetty

However, (1) it's really not clear what model I should be using.  I basically 
need to be able to fire up two entire web applications, which don't need to be 
in wars necessarily, but which certainly need to contain JSPs, .css files, 
.jpg's, tld's, and other standard webish content.  And (2), it's not clear 
if/how you properly perform Jetty shutdown using the chosen model.  Any advice 
welcome.



 There should be an LCF startup path that uses Jetty for running 
 lcf-crawler-ui and lcf-authority-service
 

 Key: CONNECTORS-38
 URL: https://issues.apache.org/jira/browse/CONNECTORS-38
 Project: Lucene Connector Framework
  Issue Type: Improvement
  Components: Framework core
Reporter: Karl Wright

 Integrating with Jetty would allow LCF to be deployed in simple cases without 
 requiring Tomcat, which would simplify the setup in such cases.  This of 
 course should not be construed as removing the support for Tomcat-style web 
 applications.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.