It occurred to me that a classloader plug-in reader for LCF would not achieve
the goal of allowing a fully prebuilt LCF with connector add-ons. The reason,
which should have been obvious from the beginning, is because each connector
consists not only of the Java implementation, but also a UI
@incubator.apache.org
Subject: Some more thoughts on a classloader plug-in style architecture
It occurred to me that a classloader plug-in reader for LCF would not
achieve the goal of allowing a fully prebuilt LCF with connector add-ons.
The reason, which should have been obvious from the beginning, is because
be one 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
: 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 (like
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 (like Solr's VelocityResponseWriter, for example)
and embed the UI bits into plugin JAR
[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 only snippets
[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 only snippets
]
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 Java code just fine via tools (Java
objects
@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 Java code just fine via tools (Java
objects) that are injected into the Velocity context. Any
sophisticated
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-compatibility issues involved. It is, however, quite a heavy
: Some more thoughts on a classloader plug-in style architecture
Sounds good to me, assuming that LCF remains relatively stable. I am
presuming that a fair number of people can and will be using LCF for various
purposes well before actual formal first release anyway. The point being
11 matches
Mail list logo
