esday, June 02, 2010 9:00 AM
To:
Subject: RE: Some more thoughts on a classloader plug-in style architecture
> I've entered a ticket CONNECTORS-40 for this work. What I propose is that
> this gets done before first official LCF release, because of the potential
> backwards-compati
Message-
From: ext Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Wednesday, June 02, 2010 8:51 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Some more thoughts on a classloader plug-in style
architecture
Yeah, definitely embedded Java (ala JSP's <%%> stuff) isn't how
V
sage-
From: ext Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Wednesday, June 02, 2010 8:19 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Some more thoughts on a classloader plug-in style
architecture
Velocity is just a simple templating engine, so it could be used in
the interme
ik.hatc...@gmail.com]
Sent: Wednesday, June 02, 2010 8:51 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Some more thoughts on a classloader plug-in style architecture
Yeah, definitely embedded Java (ala JSP's <%%> stuff) isn't how
Velocity works. It can call J
rik.hatc...@gmail.com]
Sent: Wednesday, June 02, 2010 8:19 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Some more thoughts on a classloader plug-in style
architecture
Velocity is just a simple templating engine, so it could be used in
the intermediate fashion to produce only snippet
xt Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Wednesday, June 02, 2010 8:19 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Some more thoughts on a classloader plug-in style architecture
Velocity is just a simple templating engine, so it could be used in
the intermediate fashion to produce onl
ache.org
Subject: Re: Some more thoughts on a classloader plug-in style
architecture
Actually the problem is quite tractable. We switch the UI over to
Velocity templates (like Solr's VelocityResponseWriter, for example)
and embed the UI bits into plugin JAR files that can live externally.
From: ext Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Wednesday, June 02, 2010 7:27 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Some more thoughts on a classloader plug-in style architecture
Actually the problem is quite tractable. We switch the UI over to
Velocity templates
ne of
them.
Karl
-Original Message-
From: ext Jack Krupansky [mailto:jack.krupan...@lucidimagination.com]
Sent: Wednesday, June 02, 2010 6:56 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Some more thoughts on a classloader plug-in style architecture
Good point. LCF is a bit
Actually the problem is quite tractable. We switch the UI over to
Velocity templates (like Solr's VelocityResponseWriter, for example)
and embed the UI bits into plugin JAR files that can live externally.
JSPs aren't really workable in this fashion.
Velocity templates can be loaded from the
Good point. LCF is a bit more complex than Solr in that sense.
Maybe a separate class is needed that has methods to retrieve the crawl and
UI components of a connector.
Or a small XML file with whatever info about the connector is needed. Or
maybe it is simple enough for a properties file.
11 matches
Mail list logo
