[
http://issues.ops4j.org/jira/browse/QI-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11563#action_11563
]
Niclas Hedhman commented on QI-121:
-----------------------------------
Edward Yakop commented on QI-121:
---------------------------------
IMHO, it would be difficult to integrate longwell with these requirement
without forking longwell code.
Primary reasons:
o LongwellServlet code relies on WEB-INF folder to exists.
o It's hard to override longwell servlet code because:
o All field members are private
o Initialization is done inside GenericServlet#init( ServletConfig ), instead
of GenericServlet#init()
o Other classes depends on LongwellServlet.
Other concerns:
o Longwell periodically checks configuration directories for changes in
configuration files.
Longwell creates its own classloader to serve this purposes. Look at
ConfigurationListener, LongwellClassLoaderWatcher, LongwellClassLoader.
Note:
Configuration files includes velocity templates, velocity macros, xslts,
configuration rdf data, configuration java classes and its dependency jars.
Need feedback on how to proceed.
> Integrate Longwell
> ------------------
>
> Key: QI-121
> URL: http://issues.ops4j.org/jira/browse/QI-121
> Project: Qi4j
> Issue Type: New Feature
> Reporter: Rickard Öberg
> Assignee: Edward Yakop
> Fix For: 0.4
>
>
> Integrate SIMILE Longwell. Basically, the Longwell servlet should be
> deployable in the Jetty service and should be hooked up to the RDF repository
> used by the indexing. This will allow browsing of the index through a web
> browser.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
