Hi,
I have installed Turbine running on Apache server on a Sparc/Solaris 2.6
Apache/1.3.12 (Unix) ApacheJServ/1.1.1b1 DAV/0.9.16
I have :
java -version
java version "1.2.2"
Classic VM (build JDK-1.2.2-W, native threads, sunwjit)
Following the instruction from docs/install.txt, I
1. Make sure you are able to read the Visitor table from any other client
you may have for your db.
2. Make sure your configurations in TurbineResources agree with what worked
in step 1.
3. Turn off your jit and include debugging info when compiling. It will
make your stack traces much more
On Fri, Jun 02, 2000 at 10:39:32AM -0700, Tarang Patel wrote:
[24/05/2000 13:23:36:539 PDT] servletLog Turbine: init
[24/05/2000 13:23:36:639 PDT] servletLog Turbine: Turbine init()!
[24/05/2000 13:23:52:837 PDT] servletLog Turbine: java.lang.Error: Error in
BasePeer.initTableSchema(Visitor):
Jon Stevens wrote:
http://www.cnetinvestor.com/newsitem-investor.asp?symbol=89538820Ticker=AA
PL
"The EC members represent a diverse cross-section of technology leaders in
both the desktop/server and consumer/embedded markets, including: Apache
Software Foundation,"
Right on.
But
Just following up:
Changed org.apache.turbine.util.db.pool.DB interface into an abstract class.
All database classes extend this and override defaults when required. The
DBFactory will now use the driver string passed as the JDBC driver class name.
This allows the JDBCDriver class name to be
A sample Screen (I think BaseJSPScreen, I should look, but its there
somewhere) has been written. Frank will have to respond as to how much he
tested it. It may not be tested at all. It should be fairly easy to get it
working. I do not think the modularity (layout, navigation, screen) that is
Hi All
I've got the Turbine Search interface working along with a default
implementation. Also got a separate set of wrapper classes going for
Lucene.
If anybody is interested you can get it from www.opticode.co.za
Regards
Leon.
Hi,
I think I'm just a little late with this feedback, but here goes...
At the moment I propose two interfaces to add search capability to turbine.
This is a first draft and I would appreciate any comments and suggestions.
It is not a service yet, but will probably be after some issues have
On Thu, 01 Jun 2000, you wrote:
How about lines in TurbineResources.properties like:
webmacro.context.page = org.apache.turbine.util.webmacro.WebMacroPageAttributes
webmacro.context.formatter = org.apache.turbine.util.webmacro.WebMacroFormatter
I think this could run into a problem if the
Yeah BaseJSPScreen...not thoroughly tested though. You can already use JSP
with Turbine...just set up the appropiate data for your JSP to use (either
as beans or other Java objects like Hashtable) and call
RequestDispatcher.forward/include() from your Screens, Navs, etc. Thoughts?
Let us know
On Fri, Jun 02, 2000 at 04:50:01PM -0500, dave bryson wrote:
On Thu, 01 Jun 2000, you wrote:
How about lines in TurbineResources.properties like:
webmacro.context.page = org.apache.turbine.util.webmacro.WebMacroPageAttributes
webmacro.context.formatter =
Leon Messerschmidt wrote:
Hi All
I've got the Turbine Search interface working along with a default
implementation. Also got a separate set of wrapper classes going for
Lucene.
If anybody is interested you can get it from www.opticode.co.za
Cool. I will try to give you feedback. We
On Tue, Jul 08, 2036 at 08:20:45PM -0500, Jeff Brekke wrote:
I have a patch for the database pooling stuff. It is on
http://sites.netscape.com/ekkerbj/patches/pool.patch
I'll throw in my +1
I looked over this and it looked fine to me. I think it's definitely
right to have the driver names
13 matches
Mail list logo
