You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Martin Poeschl <mp...@marmot.at> on 2002/07/13 00:00:04 UTC
tdk pre 2.2-b2 release
i uploaded a pre-release of the next tdk to
http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
it includes:
turbine-2.2-b2-dev
torque-3.0-b3-dev
velocity-1.3
tomcat-4.0.4
please give it a try!
changes:
- the coupled torque has been removed
- torque uses List instead of Vector now
- commons-jdbc2pool is used instead of the old torque pool
- upgrade to tomcat-4.0.4
the official release is planned for wednesday next week (i'm off 'til monday and i'll do some
additional testing on thursday ;-)
turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
you definitly have to change your code .. there will be a doc describing the change before the
finale release
martin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Fabio Daprile <fa...@wuerth-phoenix.com>.
Hello Martin,
does this release include fixes for some problems that arised with
Fulcrum services? (The scheduler for example?).
Is it possible to have a template of the TrubineResources.properties,
especially for what regards the Logging.
Personally i've never been able to log information about Fulcrum and Torque.
When starting my projects i always get this error.
log4j:ERROR No appenders could be found for category
(org.apache.stratum.component.ComponentLoader).
log4j:ERROR Please initialize the log4j system properly.
Hereafter my turbine and torque properties. Do not include the fulcrum
properties.
TURBINE PROPERTIES
# -------------------------------------------------------------------
# $Id: TurbineResources.master,v 1.11 2002/03/13 19:44:19 mpoeschl Exp $
#
# This is the configuration file for Turbine.
#
# Note that strings containing "," (comma) characters must backslash
# escape the comma (i.e. '\,')
#
# -------------------------------------------------------------------
# -------------------------------------------------------------------
#
# L O G S
#
# -------------------------------------------------------------------
# This is the configuration for the logging system. In most cases
# you don't need to modify anything. However, if you wish to add more
# facilities or modify the existing settings, then you can do so.
#
# destination.file: A path relative to the web app root
# -------------------------------------------------------------------
services.LoggingService.facilities=system,debug,security
services.LoggingService.default=system
services.LoggingService.loggingConfig=org.apache.turbine.services.logging.PropertiesLoggingConfig
# A facility for system logging.
services.LoggingService.system.destination.file=/logs/turbine.log
services.LoggingService.system.className=org.apache.turbine.services.logging.FileLogger
services.LoggingService.system.level=INFO
# A facility for the scheduler service
# To disable started/stopped messages set the level to ERROR
services.LoggingService.scheduler.destination.file=/logs/turbine.log
services.LoggingService.scheduler.className=org.apache.turbine.services.logging.FileLogger
services.LoggingService.scheduler.level=INFO
# A facility for debugging applications. Messages will go both
# to the log file and the server console.
services.LoggingService.debug.destination.file=/logs/turbine.log
services.LoggingService.debug.destination.console=true
services.LoggingService.debug.className=org.apache.turbine.services.logging.FileLogger
services.LoggingService.debug.level=INFO
# A facility for SQL query logging
# To enable SQL query logging, set the system and sql log level to DEBUG
services.LoggingService.sql.destination.file=/logs/turbine.log
services.LoggingService.sql.className=org.apache.turbine.services.logging.FileLogger
services.LoggingService.sql.level=ERROR
# A facility for security audit. NOTE! As of 23 Jan 2001
# Turbine does not have any standard security auditing
# functionality. It's up to your application.
services.LoggingService.security.destination.file=/logs/turbine.log
services.LoggingService.security.className=org.apache.turbine.services.logging.FileLogger
services.LoggingService.security.level=INFO
# An example configuration for automatic log rotation using Log4Java
# This will keep the log file size under 1MB and save up to 5 backup copies
services.LoggingService.rotation.destination.file=/logs/turbine.log
services.LoggingService.rotation.file.size=1048576
services.LoggingService.rotation.file.backups=5
services.LoggingService.rotation.className=org.apache.turbine.services.logging.Log4JavaLogger
services.LoggingService.rotation.level=INFO
# An example configuration for using *NIX syslogd with Log4Java
services.LoggingService.syslog.destination.syslogd.host=my.syslog.server.com
services.LoggingService.syslog.destination.syslogd.facility=LOG_DAEMON
services.LoggingService.syslog.className=org.apache.turbine.services.logging.Log4JavaLogger
services.LoggingService.syslog.level=INFO
# An example configuration for using remote Log4Java server
services.LoggingService.remote.destination.remote.host=my.remote.server.com
services.LoggingService.remote.destination.remote.port=1099
services.LoggingService.remote.className=org.apache.turbine.services.logging.Log4JavaLogger
services.LoggingService.remote.level=INFO
# An example configuration for sending error reports as email with Log4Java
# notes:
# * uses 'mail.server' as SMTP server to send mail through
# * log4j will send the email when an ERROR is logged, with
# 'buffer.size' previous (non-ERROR) logs included in the email
# * configured to log to a file as well otherwise stacktraces are lost
services.LoggingService.email.destination.file=/logs/turbine.log
services.LoggingService.email.destination.email.from=root@localhost
services.LoggingService.email.destination.email.to=root@localhost
services.LoggingService.email.destination.email.subject=Turbine Error Report
services.LoggingService.email.destination.email.buffer.size=512
services.LoggingService.email.className=org.apache.turbine.services.logging.Log4JavaLogger
services.LoggingService.email.level=INFO
# -------------------------------------------------------------------
#
# M A I L S E R V E R
#
# -------------------------------------------------------------------
# Your mail server for outgoing email.
#
# Default: null
# -------------------------------------------------------------------
mail.server=smtp-bolzano.it.wuerth.com
mail.administrative.adress=bugtrack@wuerth-phoenix.com
mail.administrative.user=bugtrack
# -------------------------------------------------------------------
# SMTP-From header for your outgoing messages
#
# All failed delivery messages will be returned to this address.
# If unset, these messages will be sent to the address in the
# From header (standard behaviour)
#
# Default: null
# -------------------------------------------------------------------
mail.smtp.from=
# -------------------------------------------------------------------
#
# M O D U L E C A C H I N G
#
# -------------------------------------------------------------------
# This determines whether or not to cache the modules in memory. For
# development, turn this off. For production, turn this on.
#
# Default: false
# -------------------------------------------------------------------
module.cache=false
# If module.cache=true, then how large should we make the hashtables
# by default.
action.cache.size=20
layout.cache.size=10
navigation.cache.size=10
page.cache.size=5
screen.cache.size=50
scheduledjob.cache.size=10
# -------------------------------------------------------------------
#
# M O D U L E P A C K A G E S
#
# -------------------------------------------------------------------
# This is the "classpath" for Turbine. In order to locate your own
# modules, you should add them to this path. For example, if you have
# com.company.actions, com.company.screens, com.company.navigations,
# then this setting would be "com.company,org.apache.turbine.modules".
# This path is searched in order. For example, Turbine comes with a
# screen module named "Login". If you wanted to have your own screen
# module named "Login", then you would specify the path to your
# modules before the others.
#
# Default: org.apache.turbine.modules
# -------------------------------------------------------------------
module.packages=com.wuerth.phoenix.bugtrack.modules,org.apache.turbine.flux.modules
# -------------------------------------------------------------------
#
# D A T A B A S E S E T T I N G S
#
# -------------------------------------------------------------------
# These are your database settings. Look in the
# org.apache.turbine.util.db.pool.* packages for more information.
# The default driver for Turbine is for MySQL.
#
# The parameters to connect to the default database. You MUST
# configure these properly.
# -------------------------------------------------------------------
database.bugtrack.driver=org.gjt.mm.mysql.Driver
database.bugtrack.url=jdbc:mysql://cvsbolzano.it.wuerth.com:3306/bugtrack
database.bugtrack.username=mysql
database.bugtrack.password=1234
#database.bugtrack.driver=org.gjt.mm.mysql.Driver
#database.bugtrack.url=jdbc:mysql://127.0.0.1/bugtrack
#database.bugtrack.username=fabio
#database.bugtrack.password=elirpadt
# The number of database connections to cache per ConnectionPool
# instance (specified per database).
database.bugtrack.maxConnections=50
# The amount of time (in milliseconds) that database connections will be
# cached (specified per database).
#
# Default: one hour = 60 * 60 * 1000
database.bugtrack.expiryTime=3600000
# The amount of time (in milliseconds) a connection request will have to
wait
# before a time out occurs and an error is thrown.
#
# Default: ten seconds = 10 * 1000
database.connectionWaitTimeout=10000
# The interval (in milliseconds) between which the PoolBrokerService logs
# the status of it's ConnectionPools.
#
# Default: No logging = 0 = 0 * 1000
database.logInterval=0
# These are the supported JDBC drivers and their associated Turbine
# adaptor. These properties are used by the DBFactory. You can add
# all the drivers you want here.
database.adaptor=DBMM
database.adaptor.DBMM=org.gjt.mm.mysql.Driver
# Determines if the quantity column of the IDBroker's id_table should
# be increased automatically if requests for ids reaches a high
# volume.
database.idbroker.cleverquantity=true
# Determines if IDBroker should prefetch IDs or not. If set to false
# this property has the effect of shutting off the housekeeping thread
# that attempts to prefetch the id's. It also sets the # of id's grabbed
# per request to 1 regardless of the settings in the database.
# Default: true
database.idbroker.prefetch=true
# -------------------------------------------------------------------
#
# F R A M E W O R K S E T T I N G S
#
# -------------------------------------------------------------------
# These are settings that control the behaviour of the framework,
# such as determining whether a template system is in use, what
# the default templates and screens are and session handling settings.
# -------------------------------------------------------------------
# Used to set the template homepage if you are using a template
# layout.
#
# Default: /
template.homepage=/Login.vm
# This is the default screen to show to people when they first access
# the system. Specify one of the template screens such as VelocityScreen
# to use a template system.
#
# Default: Login
screen.homepage=
# This is the template that is shown on an incorrect login attempt.
# Setting this property will override any value of screen.login specfied
# below.
#
# Default: Login.vm
template.login=/Login.vm
# This is the page that is shown on an incorrect login attempt. It is
# referenced in the LoginUser action. Note that it will only be used if
# a login template has not been specified (see template.login above).
#
# Default: Login
screen.login=
# This is the template that is used by the respective Template based
# ErrorScreen for displaying the error. If you are not using a Template
based
# ErrorScreen, then this is ignored.
#
# Default: /Error.vm
template.error=/Error.vm
# This is the default error screen.
#
# Default: VelocityErrorScreen
screen.error=VelocityErrorScreen
# This is the screen that is displayed when the user's web page is in
# an invalid state.
#
# Default: error.InvalidState
screen.invalidstate=error.InvalidState
# Set the default Doctype. The default Doctype can be set by using
# the single strings: Html40Strict, Html40Transitional, or
# Html40Frameset. Additionally the default can be supplied as two
# strings separated by a comma giving the DTD and URI.
#
# Default: ignored if not set to some value.
default.doctype=Html40Transitional
# This is the default action to log a user in.
action.login=LoginAction
# This is the default action to log a user out.
action.logout=LogoutUser
# This is the default action to validate whether or not a session is
# valid. For example, if you want to make sure if a user has already
# logged in or not.
#
# Default: SessionValidator
action.sessionvalidator=sessionvalidator.TemplateSessionValidator
# This is the timeout in seconds for sessions. If left commented out, the
# servlet container's default timeout will be left as is.
session.timeout=40000
# This is the default action that builds up the AccessControlList for
# the individual users session.
action.accesscontroller=AccessController
# -------------------------------------------------------------------
#
# J N D I C O N T E X T S
#
# -------------------------------------------------------------------
# This indicates whether Turbine should try to create JNDI contexts.
#
# Default: false
#
# contexts=true
# These are the JNDI context properties. Each context's properties
# are defined by the properties beginning with context.name.
#
# Default: none
#
# Example: The following will create a JNDI context named "name" in
# the data.contexts Hashtable. It will point at the RMI registry on
# localhost running on port 1099, and will use
# com.sun.jndi.rmi.registry.RegistryContextFactory as the initial
# context factory:
#
# context.name.java.naming.provider.url=rmi://localhost:1099
#
context.name.java.naming.factory.initial=com.sun.jndi.rmi.registry.RegistryContextFactory
# -------------------------------------------------------------------
#
# P E E R S
#
# -------------------------------------------------------------------
# Supplies Turbine with information about the database schema, which
# can simplify any required Peer classes.
#
# Default: org.apache.turbine.util.db.map.TurbineMapBuilder
# -------------------------------------------------------------------
database.maps.builder=org.apache.turbine.util.db.map.TurbineMapBuilder
# -------------------------------------------------------------------
#
# M E S S A G E S
#
# -------------------------------------------------------------------
# Note that strings containing "," (comma) characters must backslash
# escape the comma (i.e. '\,')
# The message that can be displayed before a user logs in.
login.message=Thank you for your visit. Please log into the system.
# The message that can be displayed when no screen is defined.
login.message.noscreen=There has been an error. Your session is valid
but the screen variable is not defined.
# The message that can be displayed when a user enters an incorrect
# password or username.
login.error=Sorry your username or password is incorrect!
# The message that can be displayed when a user logs out.
logout.message=Thank you for using the system. Please come back soon.
# -------------------------------------------------------------------
#
# S E C U R E S O C K E T S L A Y E R
#
# -------------------------------------------------------------------
# Whether the web server is able to use SSL. Links in Turbine can
# check this property to determine if SSL can be used.
#
# Default: true
# -------------------------------------------------------------------
use.ssl=true
# -------------------------------------------------------------------
#
# S E R V I C E S
#
# -------------------------------------------------------------------
# Classes for Turbine Services should be defined here.
# Format: services.[name].classname=[implementing class]
#
# To specify properties of a service use the following syntax:
# service.[name].[property]=[value]
#
# The order that these services is listed is important! The
# order that is stated here is the order in which the services
# will be initialized. Keep this is mind if you have services
# that depend on other services during initialization.
# -------------------------------------------------------------------
services.ResourceService.classname=org.apache.turbine.services.resources.TurbineResourceService
services.LoggingService.classname=org.apache.turbine.services.logging.TurbineLoggingService
services.FactoryService.classname=org.apache.turbine.services.factory.TurbineFactoryService
services.PoolService.classname=org.apache.turbine.services.pool.TurbinePoolService
services.RunDataService.classname=org.apache.turbine.services.rundata.TurbineRunDataService
services.ServletService.classname=org.apache.turbine.services.servlet.TurbineServletService
services.AssemblerBrokerService.classname=org.apache.turbine.services.assemblerbroker.TurbineAssemblerBrokerService
services.LocalizationService.classname=org.apache.turbine.services.localization.TurbineLocalizationService
services.MimeTypeService.classname=org.apache.turbine.services.mimetype.TurbineMimeTypeService
services.GlobalCacheService.classname=org.apache.turbine.services.cache.TurbineGlobalCacheService
services.SchedulerService.classname=org.apache.turbine.services.schedule.TurbineSchedulerService
services.XmlRpcService.classname=org.apache.turbine.services.xmlrpc.TurbineXmlRpcService
services.UniqueIdService.classname=org.apache.turbine.services.uniqueid.TurbineUniqueIdService
services.UploadService.classname=org.apache.turbine.services.upload.TurbineUploadService
services.SecurityService.classname=org.apache.turbine.services.security.db.DBSecurityService
services.PoolBrokerService.classname=org.apache.turbine.services.db.TurbinePoolBrokerService
services.MapBrokerService.classname=org.apache.turbine.services.db.TurbineMapBrokerService
services.PullService.classname=org.apache.turbine.services.pull.TurbinePullService
#services.IntakeService.classname=org.apache.turbine.services.intake.TurbineIntakeService
services.TemplateService.classname=org.apache.turbine.services.template.TurbineTemplateService
#services.XSLTService.classname=org.apache.turbine.services.xslt.TurbineXSLTService
# Turn on the appropriate template service.
services.VelocityService.classname=org.apache.turbine.services.velocity.TurbineVelocityService
# -------------------------------------------------------------------
#
# P O O L / M A P B R O K E R
#
# -------------------------------------------------------------------
# Default value: default
# -------------------------------------------------------------------
services.PoolBrokerService.defaultPool = bugtrack
services.MapBrokerService.defaultMap = bugtrack
# -------------------------------------------------------------------
#
# R U N D A T A S E R V I C E
#
# -------------------------------------------------------------------
# Default implementations of base interfaces for request processing.
# Additional configurations can be defined by using other keys
# in the place of the <default> key.
# -------------------------------------------------------------------
services.RunDataService.default.run.data=org.apache.turbine.services.rundata.DefaultTurbineRunData
services.RunDataService.default.parameter.parser=org.apache.turbine.util.parser.DefaultParameterParser
services.RunDataService.default.cookie.parser=org.apache.turbine.util.parser.DefaultCookieParser
# -------------------------------------------------------------------
#
# C A C H E S E R V I C E
#
# -------------------------------------------------------------------
# Interval at which the cache will be checked. The default is
# 5000ms or 5 seconds.
services.GlobalCacheService.cache.check.frequency = 5000
# -------------------------------------------------------------------
#
# A S S E M B L E R B R O K E R S E R V I C E
#
# -------------------------------------------------------------------
# A list of AssemblerFactory classes that will be registered
# with TurbineAssemblerBrokerService
# -------------------------------------------------------------------
services.AssemblerBrokerService.screen=org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory
#services.AssemblerBrokerService.screen=org.apache.turbine.services.assemblerbroker.util.python.PythonScreenFactory
services.AssemblerBrokerService.action=org.apache.turbine.services.assemblerbroker.util.java.JavaActionFactory
services.AssemblerBrokerService.layout=org.apache.turbine.services.assemblerbroker.util.java.JavaLayoutFactory
services.AssemblerBrokerService.page=org.apache.turbine.services.assemblerbroker.util.java.JavaPageFactory
services.AssemblerBrokerService.navigation=org.apache.turbine.services.assemblerbroker.util.java.JavaNavigationFactory
services.AssemblerBrokerService.scheduledjob=org.apache.turbine.services.assemblerbroker.util.java.JavaScheduledJobFactory
# -------------------------------------------------------------------
#
# T E M P L A T E S E R V I C E
#
# -------------------------------------------------------------------
# Roughly, the number of templates in each category.
#
# Defaults: layout=2, navigation=10, screen=50
services.TemplateService.layout.cache.size=2
services.TemplateService.navigation.cache.size=10
services.TemplateService.screen.cache.size=50
# -------------------------------------------------------------------
#
# P U L L S E R V I C E
#
# -------------------------------------------------------------------
# These are the properties for the Pull Service, the service
# that works in conjuction with the Turbine Pull Model API.
# -------------------------------------------------------------------
# This determines whether the non-request tools are refreshed
# on each request (request tools aren't ever, because they're
# instantiated for the request only anyway).
services.PullService.tools.per.request.refresh=true
# These are tools that are placed in the context by the service
# These tools will be made available to all your
# templates. You list the tools in the following way:
#
# tool.<scope>.<id> = <classname>
#
# <scope> is the tool scope: global, request, session
# or persistent (see below for more details)
# <id> is the name of the tool in the context
#
# You can configure the tools in this way:
# tool.<id>.<parameter> = <value>
#
# So if you find "global", "request", "session" or "persistent" as second
# part, it is a configuration to put a tool into the toolbox, else it is a
# tool specific configuration.
#
# For example:
#
# tool.global.ui = org.apache.turbine.util.pull.UIManager
# tool.global.mm = org.apache.turbine.util.pull.MessageManager
# tool.request.link = org.apache.turbine.util.template.TemplateLink
# tool.request.page =
org.apache.turbine.util.template.TemplatePageAttributes
#
# Then:
#
# tool.ui.skin = default
#
# configures the value of "skin" for the "ui" tool.
#
# Tools are accessible in all templates by the <id> given
# to the tool. So for the above listings the UIManager would
# be available as $ui, the MessageManager as $mm, the TemplateLink
# as $link and the TemplatePageAttributes as $page.
#
# You should avoid using tool names called "global", "request",
# "session" or "persistent" because of clashes with the possible Scopes.
#
# Scopes:
#
# global: tool is instantiated once and that instance is available
# to all templates for all requests. Tool must be threadsafe.
#
# request: tool is instantiated once for each request (although the
# PoolService is used to recycle instances). Tool need not
# be threadsafe.
#
# session: tool is instantiated once for each user session, and is
# stored in the user's temporary hashtable. Tool should be
# threadsafe.
#
# persistent: tool is instantitated once for each use session, and
# is stored in the user's permanent hashtable. This means
# for a logged in user the tool will be persisted in the
# user's objectdata. Tool should be threadsafe and
# Serializable.
#
# Defaults: none
tool.request.link=org.apache.turbine.util.template.TemplateLink
tool.request.page=org.apache.turbine.util.template.TemplatePageAttributes
tool.request.content=org.apache.turbine.util.ContentURI
tool.request.l10n=org.apache.turbine.services.localization.LocalizationTool
tool.request.flux=org.apache.turbine.flux.tools.FluxTool
# These are intake tools.
#tool.request.om=org.apache.turbine.om.OMTool
#tool.request.intake=org.apache.turbine.services.intake.IntakeTool
tool.global.ui=org.apache.turbine.services.pull.util.UIManager
# The UI Manager will allow you to skin your Turbine
# application using simple properties files that are
# located in the WEBAPP/resources/ui/skins/ directory
# hierarchy.
tool.ui.skin=default
# -------------------------------------------------------------------
#
# V E L O C I T Y S E R V I C E
#
# -------------------------------------------------------------------
# The location of Velocity configuration file, relative to webapp root
# These properties will override the default properties set by Velocity.
# You should specify the path to the templates directories as well as
# the path to the log file and they should also be relative to webapp root
services.VelocityService.template.extension=vm
services.VelocityService.default.page = VelocityPage
services.VelocityService.default.screen=VelocityScreen
services.VelocityService.default.layout = VelocityECSLayout
services.VelocityService.default.navigation=VelocityNavigation
services.VelocityService.default.error.screen = VelocityErrorScreen
services.VelocityService.default.layout.template = /Default.vm
services.VelocityService.runtime.log=/logs/velocity.log
#services.VelocityService.input.encoding=UTF-8
services.VelocityService.velocimacro.library = GlobalMacros.vm
services.VelocityService.resource.loader = file
services.VelocityService.file.resource.loader.description = Velocity
File Resource Loader
services.VelocityService.file.resource.loader.class =
org.apache.velocity.runtime.resource.loader.FileResourceLoader
services.VelocityService.file.resource.loader.path =
/templates/app,/templates/flux
services.VelocityService.file.resource.loader.cache = false
services.VelocityService.file.resource.loader.modificationCheckInterval = 2
services.VelocityService.resource.loader = classpath
services.VelocityService.classpath.resource.loader.description =
Velocity Classpath Resource Loader
services.VelocityService.classpath.resource.loader.class =
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
# -------------------------------------------------------------------
#
# J S P S E R V I C E
#
# -------------------------------------------------------------------
services.JspService.template.extension=jsp
services.JspService.default.page = JspPage
services.JspService.default.screen=BaseJspScreen
services.JspService.default.layout = JspLayout
services.JspService.default.navigation=BaseJspNavigation
services.JspService.default.error.screen = JspErrorScreen
services.JspService.default.layout.template = /Default.jsp
services.JspService.templates = /templates/app,/templates/flux
services.JspService.buffer.size = 8192
# -------------------------------------------------------------------
#
# W E B M A C R O S E R V I C E
#
# the webmacro-service is deprecated. you should use velocity instead!
# see http://jakarta.apache.org/velocity/migration.html
#
# -------------------------------------------------------------------
services.WebMacroService.template.extension=wm
services.WebMacroService.default.page = WebMacroSitePage
services.WebMacroService.default.screen=WebMacroSiteScreen
services.WebMacroService.default.layout = WebMacroSiteLayout
services.WebMacroService.default.navigation=WebMacroSiteNavigation
services.WebMacroService.default.error.screen = WebMacroSiteErrorScreen
services.WebMacroService.default.layout.template = /Default.wm
# The location of WebMacro configuration file, relative to webapp
# root.
services.WebMacroService.properties=/WEB-INF/conf/WebMacro.properties
# The path where WebMacro will look for templates, relative to webapp
# root. Use your system's path separator to specify multiple paths.
services.WebMacroService.templates=/templates/app,/templates/flux
# The class that will act as a template provider in webmacro. We can
# use default class from WebMacro (template path above is pushed into
# WebMacro configuration mechanism, so that class can pick it up), or
# some other custom class
services.WebMacroService.templates.provider=org.apache.turbine.services.webmacro.TurbineTemplateProvider
# -------------------------------------------------------------------
#
# F R E E M A R K E R S E R V I C E
#
# the freemarker-service is deprecated. you should use velocity instead!
# see http://jakarta.apache.org/velocity
# -------------------------------------------------------------------
# The path where FreeMarker will look for templates, relative to
# webapp root, if supported by the servlet engine.
#
# Default: /templates
services.FreeMarkerService.templates=/templates
# -------------------------------------------------------------------
#
# U P L O A D S E R V I C E
#
# -------------------------------------------------------------------
# Whether the files should be automatically picked up by
# ParameterParser.
services.UploadService.automatic=true
#
# The directory where files will be temporarily stored.
#
services.UploadService.repository=.
#
# The maximum size of a request that will be processed.
#
services.UploadService.size.max=10485760
#
# The maximum size of a request that will have it's elements cached in
# memory by TurbineUploadService class.
#
services.UploadService.size.threshold=10240
# -------------------------------------------------------------------
#
# L O C A L I Z A T I O N S E R V I C E
#
# -------------------------------------------------------------------
# Default ResourceBundle and language/country codes used by the
# TurbineLocalizationService.
#
locale.default.bundle=MyBundle
locale.default.language=en
locale.default.country=US
#
# This will set the charset= portion of the ContentType: header.
# Leave commented out unless you want to return stuff as a different
# charset.
#
# locale.default.charset=ISO-8859-1
# -------------------------------------------------------------------
#
# M I M E T Y P E S E R V I C E
#
# -------------------------------------------------------------------
# This property specifies a file containing mappings between MIME
# content types and the corresponding file name extensions. The
# service itself contains a hardcoded set of most common mappings.
# The file must use the same syntax as the mime.types file of
# the Apache Server, i.e.
# <mimetype> <ext1> <ext2>...
#
#services.MimeTypeService.mime.types=/WEB-INF/conf/mime.types
# This property specifies a file containing mappings between locales
# and the corresponding character encodings. The service itself
# contains a hardcoded set of most common mappings.
# The file should use the Java property file syntax, i.e.
# <lang_country_variant>=<charset>
#
#services.MimeTypeService.charsets=/WEB-INF/conf/charset.properties
# -------------------------------------------------------------------
#
# S C H E D U L E R S E R V I C E
#
# -------------------------------------------------------------------
#
# Set enabled to true to start the scheduler.
#
# Default = false
#
scheduler.enabled=true
# -------------------------------------------------------------------
#
# S E C U R I T Y S E R V I C E
#
# -------------------------------------------------------------------
#
# This is the class that implements the User interface.
# You want to override this setting only if you want your User
# implementation to provide application specific addtional
# functionality.
#
# Default: org.apache.turbine.om.security.TurbineUser
#
services.SecurityService.user.class=org.apache.turbine.om.security.TurbineUser
#
# This setting is DBSecurityService specific - this class is consulted
for the names
# of the columns in the users' tables for the purpose of creating join
queries.
# If you use your own User implementation in conjunction with
DBSecurityService,
# it's peer class must implement
org.apache.turbine.om.security.peer.UserPeer interface,
# and you need to specify the name of the peer class here.
#
# Defalut: org.apache.turbine.om.security.peer.TurbineUserPeer
#
services.SecurityService.userPeer.class=org.apache.turbine.om.security.peer.TurbineUserPeer
#
# This is the class that implements UserManager interface.
# Override this setting if you want your User information stored
# on a different medium (LDAP directory is a good example).
# Default implementation uses Peers and a relational database .
#
services.SecurityService.user.manager=org.apache.turbine.services.security.db.DBUserManager
#
# This is used by the SecurityService to make the password checking
# secure. When enabled, passwords are transformed by a one-way
# function into a sequence of bytes that is base64 encoded.
# It is impossible to guess the plain-text form of the password
# from the representation. When user logs in, the entered password
# is transformed the same way and then compared with stored value.
#
# Default: false
#
services.SecurityService.secure.passwords=false
#
# This property lets you choose what digest algorithm will be used
# for encrypting passwords. Check documentation of your JRE for
# available algorithms.
#
# Default: SHA
#
services.SecurityService.secure.passwords.algorithm=SHA
# Configuration for the LDAP Security Service implementation
#services.SecurityService.ldap.security.athentication=simple
#services.SecurityService.ldap.port=<LDAP PORT>
#services.SecurityService.ldap.host=<LDAP HOST>
#services.SecurityService.ldap.admin.username=<ADMIN USERNAME>
#services.SecurityService.ldap.admin.password=<ADMIN PASSWORD>
#services.SecurityService.ldap.user.basesearch=<SEARCH PATTERN>
#services.SecurityService.ldap.user.search.filter=<SEARCH FILTER>
#services.SecurityService.ldap.dn.attribute=userPrincipalName
#services.SecurityService.ldap.provider=com.sun.jndi.ldap.LdapCtxFactory
# -------------------------------------------------------------------
#
# X M L R P C S E R V I C E
#
# -------------------------------------------------------------------
# This property specifies which class should be used to parse
# xml for XmlRpc functionality.
#
# Default: org.apache.xerces.parsers.SAXParser
services.XmlRpcService.parser=org.apache.xerces.parsers.SAXParser
# This property specifies which port the server part of the XmlRpc
# should listen, if it is active.
#
# Default: 12345
services.XmlRpcService.port=12345
# If any classes are specified here, the Service will create an
# instance of them here and start up a listener on the specified
# port.
#
# Note that the handlers demonstrated are not very useful. You
# will have to invent your own services. They do however
# illustrate that any class with a default constructor can be
# added here
#
# The handler parameter without further extension determines
# the default handler for the service
#
# Default: no classes are specified by default
#services.XmlRpcService.handler.$default=java.util.Hashtable
#services.XmlRpcService.handler.stringhandler=java.lang.String
# The following properties allow the transfer of data between
# separate Turbine applications running on different servers.
# This allows B2B type behavior such as sending database
# updates in the form of XML or whatever type of data
# that needs to be shared between Turbine applications
# running on separate servers.
services.XmlRpcService.handler.file =
org.apache.turbine.services.xmlrpc.util.FileHandler
services.XmlRpcService.paranoid = false
services.XmlRpcService.acceptClient = 192.168.1.*
services.XmlRpcService.denyClient =
# Do we want a secure server
services.XmlRpcService.secure.server = false
# Secure server options
services.XmlRpcService.secure.server.option.java.protocol.handler.pkgs = \
com.sun.net.ssl.internal.www.protocol
services.XmlRpcService.secure.server.option.security.provider = \
com.sun.net.ssl.internal.ssl.Provider
services.XmlRpcService.secure.server.option.security.protocol = TLS
# You probably want to keep your key stores and trust stores
# clear out of your webapp.
services.XmlRpcService.secure.server.option.javax.net.ssl.keyStore =
/tmp/keystore
services.XmlRpcService.secure.server.option.javax.net.ssl.keyStoreType = jks
services.XmlRpcService.secure.server.option.javax.net.ssl.keyStorePassword
= password
services.XmlRpcService.secure.server.option.javax.net.ssl.trustStore =
/tmp/truststore
services.XmlRpcService.secure.server.option.javax.net.ssl.trustStoreType
= jks
services.XmlRpcService.secure.server.option.javax.net.ssl.trustStorePassword
= password
services.XmlRpcService.secure.server.option.sun.ssl.keymanager.type =
SunX509
services.XmlRpcService.secure.server.option.sun.ssl.trust.manager.type =
SunX509
# These values should be set to 'all' for debugging purposes.
services.XmlRpcService.secure.server.option.javax.net.debug = none
services.XmlRpcService.secure.server.option.java.security.debug = none
# -------------------------------------------------------------------
#
# P O O L S E R V I C E
#
# -------------------------------------------------------------------
# Default capacity of pools of the Object pooling service.
#
# Default: 128
services.PoolService.pool.capacity = 256
# Class specific capacities used instead of the default if specified.
#
#services.PoolService.pool.capacity.org.apache.turbine.services.rundata.DefaultTurbineRunData=512
# -------------------------------------------------------------------
#
# F A C T O R Y S E R V I C E
#
# -------------------------------------------------------------------
# A comma separated list of classloaders (very optional)
#
# Example: org.foo.bar.MyClassLoader, org.ack.joe.YourClassLoader
#
#services.FactoryService.class.loaders=
# Customized factories to be used instead of the default factory.
# E.g. to instantiate XML parsers, SSL sockets, etc., which require
# specific instantiation not supported by the default factory.
# The property name is prefixed with "factory" followed by the
# name of the production class. The value is the class name of
# the factory implementing the Factory interface. The factory
# will be instantiated by using the service itself.
#
# Examples:
#
#
services.FactoryService.factory.javax.xml.parsers.DocumentBuilder=org.foo.xml.DomBuilderFactory
#
services.FactoryService.factory.javax.xml.parsers.SAXParser=org.foo.xml.SaxParserFactory
#
services.FactoryService.factory.java.net.ServerSocket=org.foo.net.SslServerSocketFactory
#--------------------------------------------------------------------
#
# X S L T S E R V I C E
#
#--------------------------------------------------------------------
services.XSLTService.path = /path/to/stylesheets
services.XSLTService.cache = false
# -------------------------------------------------------------------
#
# I N T A K E S E R V I C E
#
# -------------------------------------------------------------------
# The location of the xml file specifying valid inputs
#
# Example: org.foo.bar.MyClassLoader, org.ack.joe.YourClassLoader
#
services.IntakeService.xml.path=WEB-INF/conf/intake.xml
#--------------------------------------------------------------------
#
# P A R A M E T E R P A R S E R
#
#--------------------------------------------------------------------
#
# This variable controls the case folding applied to URL variable
# names.
#
# Allowed values: none, lower, upper
# Default: lower
#
url.case.folding=lower
# -------------------------------------------------------------------
#
# C O M P O N E N T S
#
# -------------------------------------------------------------------
# Components implementing the lifecycle interfaces can be loaded,
# configured and initialized by Turbine
# -------------------------------------------------------------------
component.name = torque
component.torque.classname = org.apache.torque.Torque
component.torque.config = ${webappRoot}/WEB-INF/conf/Torque.properties
#component.name = fulcrum
#component.fulcrum.classname = org.apache.fulcrum.Fulcrum
#component.fulcrum.config = ${webappRoot}/WEB-INF/conf/Fulcrum.properties
# -------------------------------------------------------------------
#
# A D D I T I O N A L P R O P E R T I E S
#
# -------------------------------------------------------------------
# The full path name to an additional properties file. Properties in
# this file will be included in this property set. Duplicate name
# values will be replaced, so be careful.
#
# Default: none
# -------------------------------------------------------------------
include = Flux.properties
TORQUE PROPERTIES
# -------------------------------------------------------------------
# $Id: Torque.master,v 1.1 2002/02/13 14:21:08 mpoeschl Exp $
#
# This is the configuration file for Torque.
#
# Note that strings containing "," (comma) characters must backslash
# escape the comma (i.e. '\,')
#
# -------------------------------------------------------------------
torque.applicationRoot = .
# -------------------------------------------------------------------
#
# L O G G I N G
#
# -------------------------------------------------------------------
# We use Log4J for all Torque logging and we embed the log4j
# properties within our application configuration.
# -------------------------------------------------------------------
# This first category is required and the category
# must be named 'default'. This is used for all logging
# where an explicit category is not specified.
log4j.category.default = INFO, default
log4j.appender.default = org.apache.log4j.FileAppender
log4j.appender.default.file = ${webapp}/logs/turbine.log
log4j.appender.default.layout = org.apache.log4j.PatternLayout
log4j.appender.default.layout.conversionPattern = %d [%t] %-5p %c - %m%n
log4j.appender.default.append = false
log4j.category.org.apache.torque = DEBUG, torque
log4j.appender.torque = org.apache.log4j.FileAppender
log4j.appender.torque.file = ${applicationRoot}/logs/torque.log
log4j.appender.torque.layout = org.apache.log4j.PatternLayout
log4j.appender.torque.layout.conversionPattern = %d [%t] %-5p %c - %m%n
log4j.appender.torque.append = false
# -------------------------------------------------------------------
#
# T O R Q U E P R O P E R T I E S
#
# -------------------------------------------------------------------
# These are your database settings. Look in the
# org.apache.torque.pool.* packages for more information.
#
# The parameters to connect to the default database. You MUST
# configure these properly.
# -------------------------------------------------------------------
torque.database.default=bugtrack
torque.database.bugtrack.driver=org.gjt.mm.mysql.Driver
torque.database.bugtrack.url=jdbc:mysql://cvsbolzano.it.wuerth.com:3306/bugtrack
torque.database.bugtrack.username=mysql
torque.database.bugtrack.password=1234
#torque.database.bugtrack.driver=org.gjt.mm.mysql.Driver
#torque.database.bugtrack.url=jdbc:mysql://127.0.0.1/bugtrack
#torque.database.bugtrack.username=fabio
#torque.database.bugtrack.password=elirpadt
torque.database.default.driver=org.gjt.mm.mysql.Driver
torque.database.default.url=jdbc:mysql://cvsbolzano.it.wuerth.com:3306/bugtrack
torque.database.default.username=mysql
torque.database.default.password=1234
#torque.database.default.driver = org.gjt.mm.mysql.Driver
#torque.database.default.url = jdbc:mysql://127.0.0.1/bugtrack
#torque.database.default.username = fabio
#torque.database.default.password = elirpadt
# The number of database connections to cache per ConnectionPool
# instance (specified per database).
torque.database.bugtrack.maxConnections=80
torque.database.default.maxConnections=80
# The amount of time (in milliseconds) that database connections will be
# cached (specified per database).
#
# Default: one hour = 60 * 60 * 1000
torque.database.bugtrack.expiryTime=3600000
torque.database.default.expiryTime=3600000
# The amount of time (in milliseconds) a connection request will have to
wait
# before a time out occurs and an error is thrown.
#
# Default: ten seconds = 10 * 1000
torque.database.connectionWaitTimeout=10000
# The interval (in milliseconds) between which the PoolBrokerService logs
# the status of it's ConnectionPools.
#
# Default: No logging = 0 = 0 * 1000
torque.database.logInterval=0
# Determines if the quantity column of the IDBroker's id_table should
# be increased automatically if requests for ids reaches a high
# volume.
torque.idbroker.cleverquantity=true
Martin Poeschl wrote:
> i uploaded a pre-release of the next tdk to
>
> http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
>
> it includes:
>
> turbine-2.2-b2-dev
> torque-3.0-b3-dev
> velocity-1.3
> tomcat-4.0.4
>
> please give it a try!
>
> changes:
>
> - the coupled torque has been removed
> - torque uses List instead of Vector now
> - commons-jdbc2pool is used instead of the old torque pool
> - upgrade to tomcat-4.0.4
>
> the official release is planned for wednesday next week (i'm off 'til
> monday and i'll do some additional testing on thursday ;-)
>
> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
> you definitly have to change your code .. there will be a doc
> describing the change before the finale release
>
> martin
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
Fabio Daprile
Würth-Phoenix Srl
Via Kravogl 4, I-39100 Bolzano
Tel: +39 0471/564111 - (direct 564070)
Fax: +39 0471/564122
mailto:fabio.daprile@wuerth-phoenix.com
http://www.wuerth-phoenix.com
http://www.wuerth.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Jason van Zyl <ja...@zenplex.com>.
On Fri, 2002-07-19 at 21:52, Daniel Rall wrote:
> Fabio Daprile <fa...@wuerth-phoenix.com> writes:
>
> > Hello,
> > i got this error whene trying to rebuild my project with this tdk.
> >
> > [torque-data-model] Using classpath
> > [torque-data-model] Generating to file
> > C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
> > [torque-data-model] Resolver: used
> > http://jakarta.apache.org/turbine/dtd/database.dtd
> > [torque-data-model] Couldn't read DTD specified in XML schema:
> > Operation timed out: no further information
> > [torque-data-model] java.lang.NullPointerException
>
> This may be a problem with the Maven build files for Torque. The
> build file was not copying the DTD into the JAR, from where Torque
> attempts to load it (from the classpath) before opening a socket
> connection to apache.org and trying to load it over the network.
I popped in a little fix that should work with Maven HEAD. My local copy
is hosed at the moment, but I believe the postGoal in the maven.xml file
should do the trick. This should also fix the fulcrum build as the
sources won't generate without access to the database.dtd.
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
jason@apache.org
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Fabio Daprile <fa...@wuerth-phoenix.com> writes:
> Hello,
> i got this error whene trying to rebuild my project with this tdk.
>
> [torque-data-model] Using classpath
> [torque-data-model] Generating to file
> C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
> [torque-data-model] Resolver: used
> http://jakarta.apache.org/turbine/dtd/database.dtd
> [torque-data-model] Couldn't read DTD specified in XML schema:
> Operation timed out: no further information
> [torque-data-model] java.lang.NullPointerException
This may be a problem with the Maven build files for Torque. The
build file was not copying the DTD into the JAR, from where Torque
attempts to load it (from the classpath) before opening a socket
connection to apache.org and trying to load it over the network.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Frederic Gedin <fr...@Jaluna.COM>.
I use Linux Mandrake 8.2 and J2SE 1.4.
I noticed that, if you replace torque-3.0-b3-dev with torque-3.0-b2, the
problem does not appear anymore : you can complie even though you are not
connected to the internet.
Frederic
----- Original Message -----
From: "Martin Poeschl" <mp...@marmot.at>
To: "Turbine Users List" <tu...@jakarta.apache.org>
Sent: Tuesday, July 16, 2002 8:59 AM
Subject: Re: tdk pre 2.2-b2 release
> Frederic Gedin wrote:
> > I noticed this one too.
> > I you are connected to internet and then have access to the DTD in
> > http://jakarta,apache.org, it works fine.
>
> which os, jvm are you using???
> torque should use the dtd from the xml file .. only if this fails it is
loaded from the jakarta-site
>
> martin
>
> >
> > Frederic
> >
> > Fabio Daprile wrote:
> >
> >> Hello,
> >> i got this error whene trying to rebuild my project with this tdk.
> >>
> >> [torque-data-model] Using classpath
> >> [torque-data-model] Generating to file
> >> C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
> >> [torque-data-model] Resolver: used
> >> http://jakarta.apache.org/turbine/dtd/database.dtd
> >> [torque-data-model] Couldn't read DTD specified in XML schema:
> >> Operation timed out: no further information
> >> [torque-data-model] java.lang.NullPointerException
> >>
> >> i do not know why.
> >>
> >> can you help me?
> >>
> >> hereafter the build.properties:
> >>
> >> # This currently duplicated because the torque templates have
> >> # a dependency on $project.
> >> project = bugtrack
> >> app.root = ../${tdk.project}
> >> build.webappRoot = ${tdk.home}/webapps/${tdk.project}
> >> target.package = com.wuerth.phoenix.bugtrack
> >> target.directory = com/wuerth/phoenix/bugtrack
> >> build.dest = ${build.webappRoot}/WEB-INF/classes
> >> version = 0.1
> >> src.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/src
> >> conf.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/conf
> >> master.conf.dir =
> >> ${tdk.home}/tdk/ancillary/${tdk.turbineVersion}/src/conf
> >> debug = on
> >> optimize = off
> >> deprecation = on
> >> idTableDatabase = bugtrack
> >>
> >> # todo!!!
> >> lib.dir = ${build.webappRoot}/WEB-INF/lib
> >> torque.home = ${build.webappRoot}/WEB-INF
> >> outputDirectory = src
> >> schemaDirectory = conf
> >>
> >> # -------------------------------------------------------------------
> >> #
> >> # D A T A B A S E S E T T I N G S
> >> #
> >> # -------------------------------------------------------------------
> >>
> >> database.name = bugtrack
> >> database = mysql
> >> createDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> >> buildDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> >> databaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> >> databaseDriver = org.gjt.mm.mysql.Driver
> >> databaseUser = fabio
> >> databasePassword = elirpadt
> >> databaseHost = 127.0.0.1
> >>
> >> # -------------------------------------------------------------------
> >> #
> >> # T O R Q U E C O N F I G U R A T I O N
> >> #
> >> # -------------------------------------------------------------------
> >> # These settings will allow you to customize the way your
> >> # Peer-based object model is created.
> >> # -------------------------------------------------------------------
> >>
> >> torque.buildFile=build-torque.xml
> >>
> >> extend=TurbineMapBuilder
> >> mapname=TurbineMap
> >> suffix=MapBuilder
> >> targetPackage=com.wuerth.phoenix.bugtrack.om
> >> targetDirectory=com/wuerth/phoenix/bugtrack/om
> >> addSaveMethod=true
> >> addGetByNameMethod=false
> >> complexObjectModel=true
> >> basePrefix=Base
> >> useManagers=false
> >> overloadKeySetters=true
> >> useClasspath=true
> >> templatePath=use_classpath
> >>
> >> # -------------------------------------------------------------------
> >> #
> >> # C O N T R O L T E M P L A T E S
> >> #
> >> # -------------------------------------------------------------------
> >>
> >> SQLControlTemplate = sql/base/Control.vm
> >> OMControlTemplate = om/Control.vm
> >> idTableControlTemplate = sql/id-table/Control.vm
> >> securityControlTemplate = sql/security/Control.vm
> >> DataDTDControlTemplate = data/Control.vm
> >> DataDumpControlTemplate = data/dump/Control.vm
> >> DataSQLControlTemplate = sql/load/Control.vm
> >>
> >> #
>
>> -------------------------------------------------------------------------
> >> # The values for the ID_TABLE_ID column in the ID_TABLE start
> >> # at 101 for tables used in projects.
> >> #
>
>> -------------------------------------------------------------------------
> >> initialID = 101
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Frederic Gedin wrote:
> >>
> >>> Martin
> >>>
> >>>
> >>> Fine job, it works well!
> >>> Did you notice that the "second" and "third" databases are created
> >>> but are leaved empty? This may be a problem for those people who
> >>> like to work with several databases.
> >>>
> >>> Frederic
> >>>
> >>> Martin Poeschl wrote:
> >>>
> >>>> i uploaded a pre-release of the next tdk to
> >>>>
> >>>>
http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
> >>>>
> >>>>
> >>>> it includes:
> >>>>
> >>>> turbine-2.2-b2-dev
> >>>> torque-3.0-b3-dev
> >>>> velocity-1.3
> >>>> tomcat-4.0.4
> >>>>
> >>>> please give it a try!
> >>>>
> >>>> changes:
> >>>>
> >>>> - the coupled torque has been removed
> >>>> - torque uses List instead of Vector now
> >>>> - commons-jdbc2pool is used instead of the old torque pool
> >>>> - upgrade to tomcat-4.0.4
> >>>>
> >>>> the official release is planned for wednesday next week (i'm off
> >>>> 'til monday and i'll do some additional testing on thursday ;-)
> >>>>
> >>>> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
> >>>> you definitly have to change your code .. there will be a doc
> >>>> describing the change before the finale release
> >>>>
> >>>> martin
> >>>>
> >>>>
> >>>> --
> >>>> To unsubscribe, e-mail:
> >>>> <ma...@jakarta.apache.org>
> >>>> For additional commands, e-mail:
> >>>> <ma...@jakarta.apache.org>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> To unsubscribe, e-mail:
> >>> <ma...@jakarta.apache.org>
> >>> For additional commands, e-mail:
> >>> <ma...@jakarta.apache.org>
> >>>
> >>
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Fabio Daprile <fa...@wuerth-phoenix.com>.
Hello,
the problem is solved. I simply copied the dtdt on our intranet site and
changed the adress in all the files that reference the dtdt file.
I now have two other problems.
The first is when starting turbine i got this exception:;
Exception: org.apache.turbine.services.InstantiationException: Failed
to instantiate service XmlRpcService
Stack Trace follows:
java.lang.NoClassDefFoundError: helma/xmlrpc/WebServer
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at
org.apache.turbine.services.BaseInitableBroker.getInitableInstance(BaseInitableBroker.java:257)
rethrown as org.apache.turbine.services.InstantiationException: A class
referenced by org.apache.turbine.services.xmlrpc.TurbineXmlRpcService is
unavailable. Check your jars and classes.
at
org.apache.turbine.services.BaseInitableBroker.getInitableInstance(BaseInitableBroker.java:295)
at
org.apache.turbine.services.BaseServiceBroker.getServiceInstance(BaseServiceBroker.java:359)
rethrown as org.apache.turbine.services.InstantiationException: Failed
to instantiate service XmlRpcService
at
org.apache.turbine.services.BaseServiceBroker.getServiceInstance(BaseServiceBroker.java:369)
at
org.apache.turbine.services.BaseServiceBroker.doInitService(BaseServiceBroker.java:221)
at
org.apache.turbine.services.BaseServiceBroker.initServices(BaseServiceBroker.java:193)
at org.apache.turbine.Turbine.init(Turbine.java:232)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:918)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:810)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3279)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3421)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:478)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:738)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:300)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:389)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:232)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:155)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1131)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:638)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:343)
at
org.apache.catalina.core.StandardService.start(StandardService.java:388)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:506)
at org.apache.catalina.startup.Catalina.start(Catalina.java:781)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
I checked my project and i have the following jars:
xmlrpc.jar
xmlrpc-helma.jar
another problem is that i do not have any logging for torque and fulcrum.
I do not know if the scheduler has started.
Certainly it has not because jobs do not run.
Here the messages when tomcat starts:
Starting service Tomcat-Standalone
Apache Tomcat/4.0.4
loading component: name=torque class=org.apache.torque.Torque
config=C:\TDK3\tdk\webapps\bugtrack/WEB-INF/conf/Torque.properties
attempting to load 'org.apache.torque.Torque' with the config file
'C:\TDK3\tdk\webapps\bugtrack/WEB-INF/conf/Torque.properties'.
log4j:ERROR No appenders could be found for category
(org.apache.torque.adapter.DBFactory).
log4j:ERROR Please initialize the log4j system properly.
good news! org.apache.torque.Torque successfully configured and initialized
loading component: name=fulcrum class=org.apache.fulcrum.Fulcrum
config=C:\TDK3\tdk\webapps\bugtrack/WEB-INF/conf/Fulcrum.properties
attempting to load 'org.apache.fulcrum.Fulcrum' with the config file
'C:\TDK3\tdk\webapps\bugtrack/WEB-INF/conf/Fulcrum.properties'.
good news! org.apache.fulcrum.Fulcrum successfully configured and
initialized
Starting service Tomcat-Apache
Apache Tomcat/4.0.4
attached are my configuration files:
Martin Poeschl wrote:
> Frederic Gedin wrote:
>
>> I noticed this one too.
>> I you are connected to internet and then have access to the DTD in
>> http://jakarta,apache.org, it works fine.
>
>
> which os, jvm are you using???
> torque should use the dtd from the xml file .. only if this fails it
> is loaded from the jakarta-site
>
> martin
>
>>
>> Frederic
>>
>> Fabio Daprile wrote:
>>
>>> Hello,
>>> i got this error whene trying to rebuild my project with this tdk.
>>>
>>> [torque-data-model] Using classpath
>>> [torque-data-model] Generating to file
>>> C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
>>> [torque-data-model] Resolver: used
>>> http://jakarta.apache.org/turbine/dtd/database.dtd
>>> [torque-data-model] Couldn't read DTD specified in XML schema:
>>> Operation timed out: no further information
>>> [torque-data-model] java.lang.NullPointerException
>>>
>>> i do not know why.
>>>
>>> can you help me?
>>>
>>> hereafter the build.properties:
>>>
>>> # This currently duplicated because the torque templates have
>>> # a dependency on $project.
>>> project = bugtrack
>>> app.root = ../${tdk.project}
>>> build.webappRoot = ${tdk.home}/webapps/${tdk.project}
>>> target.package = com.wuerth.phoenix.bugtrack
>>> target.directory = com/wuerth/phoenix/bugtrack
>>> build.dest = ${build.webappRoot}/WEB-INF/classes
>>> version = 0.1
>>> src.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/src
>>> conf.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/conf
>>> master.conf.dir =
>>> ${tdk.home}/tdk/ancillary/${tdk.turbineVersion}/src/conf
>>> debug = on
>>> optimize = off
>>> deprecation = on
>>> idTableDatabase = bugtrack
>>>
>>> # todo!!!
>>> lib.dir = ${build.webappRoot}/WEB-INF/lib
>>> torque.home = ${build.webappRoot}/WEB-INF
>>> outputDirectory = src
>>> schemaDirectory = conf
>>>
>>> # -------------------------------------------------------------------
>>> #
>>> # D A T A B A S E S E T T I N G S
>>> #
>>> # -------------------------------------------------------------------
>>>
>>> database.name = bugtrack
>>> database = mysql
>>> createDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
>>> buildDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
>>> databaseUrl = jdbc:mysql://127.0.0.1/bugtrack
>>> databaseDriver = org.gjt.mm.mysql.Driver
>>> databaseUser = fabio
>>> databasePassword = elirpadt
>>> databaseHost = 127.0.0.1
>>>
>>> # -------------------------------------------------------------------
>>> #
>>> # T O R Q U E C O N F I G U R A T I O N
>>> #
>>> # -------------------------------------------------------------------
>>> # These settings will allow you to customize the way your
>>> # Peer-based object model is created.
>>> # -------------------------------------------------------------------
>>>
>>> torque.buildFile=build-torque.xml
>>>
>>> extend=TurbineMapBuilder
>>> mapname=TurbineMap
>>> suffix=MapBuilder
>>> targetPackage=com.wuerth.phoenix.bugtrack.om
>>> targetDirectory=com/wuerth/phoenix/bugtrack/om
>>> addSaveMethod=true
>>> addGetByNameMethod=false
>>> complexObjectModel=true
>>> basePrefix=Base
>>> useManagers=false
>>> overloadKeySetters=true
>>> useClasspath=true
>>> templatePath=use_classpath
>>>
>>> # -------------------------------------------------------------------
>>> #
>>> # C O N T R O L T E M P L A T E S
>>> #
>>> # -------------------------------------------------------------------
>>>
>>> SQLControlTemplate = sql/base/Control.vm
>>> OMControlTemplate = om/Control.vm
>>> idTableControlTemplate = sql/id-table/Control.vm
>>> securityControlTemplate = sql/security/Control.vm
>>> DataDTDControlTemplate = data/Control.vm
>>> DataDumpControlTemplate = data/dump/Control.vm
>>> DataSQLControlTemplate = sql/load/Control.vm
>>>
>>> #
>>> -------------------------------------------------------------------------
>>>
>>> # The values for the ID_TABLE_ID column in the ID_TABLE start
>>> # at 101 for tables used in projects.
>>> #
>>> -------------------------------------------------------------------------
>>>
>>> initialID = 101
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Frederic Gedin wrote:
>>>
>>>> Martin
>>>>
>>>>
>>>> Fine job, it works well!
>>>> Did you notice that the "second" and "third" databases are created
>>>> but are leaved empty? This may be a problem for those people who
>>>> like to work with several databases.
>>>>
>>>> Frederic
>>>>
>>>> Martin Poeschl wrote:
>>>>
>>>>> i uploaded a pre-release of the next tdk to
>>>>>
>>>>> http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
>>>>>
>>>>>
>>>>> it includes:
>>>>>
>>>>> turbine-2.2-b2-dev
>>>>> torque-3.0-b3-dev
>>>>> velocity-1.3
>>>>> tomcat-4.0.4
>>>>>
>>>>> please give it a try!
>>>>>
>>>>> changes:
>>>>>
>>>>> - the coupled torque has been removed
>>>>> - torque uses List instead of Vector now
>>>>> - commons-jdbc2pool is used instead of the old torque pool
>>>>> - upgrade to tomcat-4.0.4
>>>>>
>>>>> the official release is planned for wednesday next week (i'm off
>>>>> 'til monday and i'll do some additional testing on thursday ;-)
>>>>>
>>>>> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
>>>>> you definitly have to change your code .. there will be a doc
>>>>> describing the change before the finale release
>>>>>
>>>>> martin
>>>>>
>>>>>
>>>>> --
>>>>> To unsubscribe, e-mail:
>>>>> <ma...@jakarta.apache.org>
>>>>> For additional commands, e-mail:
>>>>> <ma...@jakarta.apache.org>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> To unsubscribe, e-mail:
>>>> <ma...@jakarta.apache.org>
>>>> For additional commands, e-mail:
>>>> <ma...@jakarta.apache.org>
>>>>
>>>
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
Fabio Daprile
W�rth-Phoenix Srl
Via Kravogl 4, I-39100 Bolzano
Tel: +39 0471/564111 - (direct 564070)
Fax: +39 0471/564122
mailto:fabio.daprile@wuerth-phoenix.com
http://www.wuerth-phoenix.com
http://www.wuerth.com
Re: tdk pre 2.2-b2 release
Posted by Frederic Gedin <fr...@Jaluna.COM>.
Linux Mandrake 8.2
J2SE 1.4
TDK pre 2.2-b2 uses torque-3.0-b3-dev. If you use torque-3.0-b2, the
problem does not appear, you can compile even though you are not
connected to the internet.
Frédéric
----- Original Message -----
From: "Martin Poeschl" <mp...@marmot.at>
To: "Turbine Users List" <tu...@jakarta.apache.org>
Sent: Tuesday, July 16, 2002 8:59 AM
Subject: Re: tdk pre 2.2-b2 release
> Frederic Gedin wrote:
> > I noticed this one too.
> > I you are connected to internet and then have access to the DTD in
> > http://jakarta,apache.org, it works fine.
>
> which os, jvm are you using???
> torque should use the dtd from the xml file .. only if this fails it is
loaded from the jakarta-site
>
> martin
>
> >
> > Frederic
> >
> > Fabio Daprile wrote:
> >
> >> Hello,
> >> i got this error whene trying to rebuild my project with this tdk.
> >>
> >> [torque-data-model] Using classpath
> >> [torque-data-model] Generating to file
> >> C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
> >> [torque-data-model] Resolver: used
> >> http://jakarta.apache.org/turbine/dtd/database.dtd
> >> [torque-data-model] Couldn't read DTD specified in XML schema:
> >> Operation timed out: no further information
> >> [torque-data-model] java.lang.NullPointerException
> >>
> >> i do not know why.
> >>
> >> can you help me?
> >>
> >> hereafter the build.properties:
> >>
> >> # This currently duplicated because the torque templates have
> >> # a dependency on $project.
> >> project = bugtrack
> >> app.root = ../${tdk.project}
> >> build.webappRoot = ${tdk.home}/webapps/${tdk.project}
> >> target.package = com.wuerth.phoenix.bugtrack
> >> target.directory = com/wuerth/phoenix/bugtrack
> >> build.dest = ${build.webappRoot}/WEB-INF/classes
> >> version = 0.1
> >> src.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/src
> >> conf.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/conf
> >> master.conf.dir =
> >> ${tdk.home}/tdk/ancillary/${tdk.turbineVersion}/src/conf
> >> debug = on
> >> optimize = off
> >> deprecation = on
> >> idTableDatabase = bugtrack
> >>
> >> # todo!!!
> >> lib.dir = ${build.webappRoot}/WEB-INF/lib
> >> torque.home = ${build.webappRoot}/WEB-INF
> >> outputDirectory = src
> >> schemaDirectory = conf
> >>
> >> # -------------------------------------------------------------------
> >> #
> >> # D A T A B A S E S E T T I N G S
> >> #
> >> # -------------------------------------------------------------------
> >>
> >> database.name = bugtrack
> >> database = mysql
> >> createDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> >> buildDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> >> databaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> >> databaseDriver = org.gjt.mm.mysql.Driver
> >> databaseUser = fabio
> >> databasePassword = elirpadt
> >> databaseHost = 127.0.0.1
> >>
> >> # -------------------------------------------------------------------
> >> #
> >> # T O R Q U E C O N F I G U R A T I O N
> >> #
> >> # -------------------------------------------------------------------
> >> # These settings will allow you to customize the way your
> >> # Peer-based object model is created.
> >> # -------------------------------------------------------------------
> >>
> >> torque.buildFile=build-torque.xml
> >>
> >> extend=TurbineMapBuilder
> >> mapname=TurbineMap
> >> suffix=MapBuilder
> >> targetPackage=com.wuerth.phoenix.bugtrack.om
> >> targetDirectory=com/wuerth/phoenix/bugtrack/om
> >> addSaveMethod=true
> >> addGetByNameMethod=false
> >> complexObjectModel=true
> >> basePrefix=Base
> >> useManagers=false
> >> overloadKeySetters=true
> >> useClasspath=true
> >> templatePath=use_classpath
> >>
> >> # -------------------------------------------------------------------
> >> #
> >> # C O N T R O L T E M P L A T E S
> >> #
> >> # -------------------------------------------------------------------
> >>
> >> SQLControlTemplate = sql/base/Control.vm
> >> OMControlTemplate = om/Control.vm
> >> idTableControlTemplate = sql/id-table/Control.vm
> >> securityControlTemplate = sql/security/Control.vm
> >> DataDTDControlTemplate = data/Control.vm
> >> DataDumpControlTemplate = data/dump/Control.vm
> >> DataSQLControlTemplate = sql/load/Control.vm
> >>
> >> #
>
>> -------------------------------------------------------------------------
> >> # The values for the ID_TABLE_ID column in the ID_TABLE start
> >> # at 101 for tables used in projects.
> >> #
>
>> -------------------------------------------------------------------------
> >> initialID = 101
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Frederic Gedin wrote:
> >>
> >>> Martin
> >>>
> >>>
> >>> Fine job, it works well!
> >>> Did you notice that the "second" and "third" databases are created
> >>> but are leaved empty? This may be a problem for those people who
> >>> like to work with several databases.
> >>>
> >>> Frederic
> >>>
> >>> Martin Poeschl wrote:
> >>>
> >>>> i uploaded a pre-release of the next tdk to
> >>>>
> >>>>
http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
> >>>>
> >>>>
> >>>> it includes:
> >>>>
> >>>> turbine-2.2-b2-dev
> >>>> torque-3.0-b3-dev
> >>>> velocity-1.3
> >>>> tomcat-4.0.4
> >>>>
> >>>> please give it a try!
> >>>>
> >>>> changes:
> >>>>
> >>>> - the coupled torque has been removed
> >>>> - torque uses List instead of Vector now
> >>>> - commons-jdbc2pool is used instead of the old torque pool
> >>>> - upgrade to tomcat-4.0.4
> >>>>
> >>>> the official release is planned for wednesday next week (i'm off
> >>>> 'til monday and i'll do some additional testing on thursday ;-)
> >>>>
> >>>> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
> >>>> you definitly have to change your code .. there will be a doc
> >>>> describing the change before the finale release
> >>>>
> >>>> martin
> >>>>
> >>>>
> >>>> --
> >>>> To unsubscribe, e-mail:
> >>>> <ma...@jakarta.apache.org>
> >>>> For additional commands, e-mail:
> >>>> <ma...@jakarta.apache.org>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> To unsubscribe, e-mail:
> >>> <ma...@jakarta.apache.org>
> >>> For additional commands, e-mail:
> >>> <ma...@jakarta.apache.org>
> >>>
> >>
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Martin Poeschl <mp...@marmot.at>.
Frederic Gedin wrote:
> I noticed this one too.
> I you are connected to internet and then have access to the DTD in
> http://jakarta,apache.org, it works fine.
which os, jvm are you using???
torque should use the dtd from the xml file .. only if this fails it is loaded from the jakarta-site
martin
>
> Frederic
>
> Fabio Daprile wrote:
>
>> Hello,
>> i got this error whene trying to rebuild my project with this tdk.
>>
>> [torque-data-model] Using classpath
>> [torque-data-model] Generating to file
>> C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
>> [torque-data-model] Resolver: used
>> http://jakarta.apache.org/turbine/dtd/database.dtd
>> [torque-data-model] Couldn't read DTD specified in XML schema:
>> Operation timed out: no further information
>> [torque-data-model] java.lang.NullPointerException
>>
>> i do not know why.
>>
>> can you help me?
>>
>> hereafter the build.properties:
>>
>> # This currently duplicated because the torque templates have
>> # a dependency on $project.
>> project = bugtrack
>> app.root = ../${tdk.project}
>> build.webappRoot = ${tdk.home}/webapps/${tdk.project}
>> target.package = com.wuerth.phoenix.bugtrack
>> target.directory = com/wuerth/phoenix/bugtrack
>> build.dest = ${build.webappRoot}/WEB-INF/classes
>> version = 0.1
>> src.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/src
>> conf.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/conf
>> master.conf.dir =
>> ${tdk.home}/tdk/ancillary/${tdk.turbineVersion}/src/conf
>> debug = on
>> optimize = off
>> deprecation = on
>> idTableDatabase = bugtrack
>>
>> # todo!!!
>> lib.dir = ${build.webappRoot}/WEB-INF/lib
>> torque.home = ${build.webappRoot}/WEB-INF
>> outputDirectory = src
>> schemaDirectory = conf
>>
>> # -------------------------------------------------------------------
>> #
>> # D A T A B A S E S E T T I N G S
>> #
>> # -------------------------------------------------------------------
>>
>> database.name = bugtrack
>> database = mysql
>> createDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
>> buildDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
>> databaseUrl = jdbc:mysql://127.0.0.1/bugtrack
>> databaseDriver = org.gjt.mm.mysql.Driver
>> databaseUser = fabio
>> databasePassword = elirpadt
>> databaseHost = 127.0.0.1
>>
>> # -------------------------------------------------------------------
>> #
>> # T O R Q U E C O N F I G U R A T I O N
>> #
>> # -------------------------------------------------------------------
>> # These settings will allow you to customize the way your
>> # Peer-based object model is created.
>> # -------------------------------------------------------------------
>>
>> torque.buildFile=build-torque.xml
>>
>> extend=TurbineMapBuilder
>> mapname=TurbineMap
>> suffix=MapBuilder
>> targetPackage=com.wuerth.phoenix.bugtrack.om
>> targetDirectory=com/wuerth/phoenix/bugtrack/om
>> addSaveMethod=true
>> addGetByNameMethod=false
>> complexObjectModel=true
>> basePrefix=Base
>> useManagers=false
>> overloadKeySetters=true
>> useClasspath=true
>> templatePath=use_classpath
>>
>> # -------------------------------------------------------------------
>> #
>> # C O N T R O L T E M P L A T E S
>> #
>> # -------------------------------------------------------------------
>>
>> SQLControlTemplate = sql/base/Control.vm
>> OMControlTemplate = om/Control.vm
>> idTableControlTemplate = sql/id-table/Control.vm
>> securityControlTemplate = sql/security/Control.vm
>> DataDTDControlTemplate = data/Control.vm
>> DataDumpControlTemplate = data/dump/Control.vm
>> DataSQLControlTemplate = sql/load/Control.vm
>>
>> #
>> -------------------------------------------------------------------------
>> # The values for the ID_TABLE_ID column in the ID_TABLE start
>> # at 101 for tables used in projects.
>> #
>> -------------------------------------------------------------------------
>> initialID = 101
>>
>>
>>
>>
>>
>>
>>
>> Frederic Gedin wrote:
>>
>>> Martin
>>>
>>>
>>> Fine job, it works well!
>>> Did you notice that the "second" and "third" databases are created
>>> but are leaved empty? This may be a problem for those people who
>>> like to work with several databases.
>>>
>>> Frederic
>>>
>>> Martin Poeschl wrote:
>>>
>>>> i uploaded a pre-release of the next tdk to
>>>>
>>>> http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
>>>>
>>>>
>>>> it includes:
>>>>
>>>> turbine-2.2-b2-dev
>>>> torque-3.0-b3-dev
>>>> velocity-1.3
>>>> tomcat-4.0.4
>>>>
>>>> please give it a try!
>>>>
>>>> changes:
>>>>
>>>> - the coupled torque has been removed
>>>> - torque uses List instead of Vector now
>>>> - commons-jdbc2pool is used instead of the old torque pool
>>>> - upgrade to tomcat-4.0.4
>>>>
>>>> the official release is planned for wednesday next week (i'm off
>>>> 'til monday and i'll do some additional testing on thursday ;-)
>>>>
>>>> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
>>>> you definitly have to change your code .. there will be a doc
>>>> describing the change before the finale release
>>>>
>>>> martin
>>>>
>>>>
>>>> --
>>>> To unsubscribe, e-mail:
>>>> <ma...@jakarta.apache.org>
>>>> For additional commands, e-mail:
>>>> <ma...@jakarta.apache.org>
>>>>
>>>
>>>
>>>
>>> --
>>> To unsubscribe, e-mail:
>>> <ma...@jakarta.apache.org>
>>> For additional commands, e-mail:
>>> <ma...@jakarta.apache.org>
>>>
>>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Frederic Gedin <fr...@Jaluna.COM>.
I noticed this one too.
I you are connected to internet and then have access to the DTD in
http://jakarta,apache.org, it works fine.
Frederic
Fabio Daprile wrote:
> Hello,
> i got this error whene trying to rebuild my project with this tdk.
>
> [torque-data-model] Using classpath
> [torque-data-model] Generating to file
> C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
> [torque-data-model] Resolver: used
> http://jakarta.apache.org/turbine/dtd/database.dtd
> [torque-data-model] Couldn't read DTD specified in XML schema: Operation
> timed out: no further information
> [torque-data-model] java.lang.NullPointerException
>
> i do not know why.
>
> can you help me?
>
> hereafter the build.properties:
>
> # This currently duplicated because the torque templates have
> # a dependency on $project.
> project = bugtrack
> app.root = ../${tdk.project}
> build.webappRoot = ${tdk.home}/webapps/${tdk.project}
> target.package = com.wuerth.phoenix.bugtrack
> target.directory = com/wuerth/phoenix/bugtrack
> build.dest = ${build.webappRoot}/WEB-INF/classes
> version = 0.1
> src.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/src
> conf.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/conf
> master.conf.dir = ${tdk.home}/tdk/ancillary/${tdk.turbineVersion}/src/conf
> debug = on
> optimize = off
> deprecation = on
> idTableDatabase = bugtrack
>
> # todo!!!
> lib.dir = ${build.webappRoot}/WEB-INF/lib
> torque.home = ${build.webappRoot}/WEB-INF
> outputDirectory = src
> schemaDirectory = conf
>
> # -------------------------------------------------------------------
> #
> # D A T A B A S E S E T T I N G S
> #
> # -------------------------------------------------------------------
>
> database.name = bugtrack
> database = mysql
> createDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> buildDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> databaseUrl = jdbc:mysql://127.0.0.1/bugtrack
> databaseDriver = org.gjt.mm.mysql.Driver
> databaseUser = fabio
> databasePassword = elirpadt
> databaseHost = 127.0.0.1
>
> # -------------------------------------------------------------------
> #
> # T O R Q U E C O N F I G U R A T I O N
> #
> # -------------------------------------------------------------------
> # These settings will allow you to customize the way your
> # Peer-based object model is created.
> # -------------------------------------------------------------------
>
> torque.buildFile=build-torque.xml
>
> extend=TurbineMapBuilder
> mapname=TurbineMap
> suffix=MapBuilder
> targetPackage=com.wuerth.phoenix.bugtrack.om
> targetDirectory=com/wuerth/phoenix/bugtrack/om
> addSaveMethod=true
> addGetByNameMethod=false
> complexObjectModel=true
> basePrefix=Base
> useManagers=false
> overloadKeySetters=true
> useClasspath=true
> templatePath=use_classpath
>
> # -------------------------------------------------------------------
> #
> # C O N T R O L T E M P L A T E S
> #
> # -------------------------------------------------------------------
>
> SQLControlTemplate = sql/base/Control.vm
> OMControlTemplate = om/Control.vm
> idTableControlTemplate = sql/id-table/Control.vm
> securityControlTemplate = sql/security/Control.vm
> DataDTDControlTemplate = data/Control.vm
> DataDumpControlTemplate = data/dump/Control.vm
> DataSQLControlTemplate = sql/load/Control.vm
>
> # -------------------------------------------------------------------------
> # The values for the ID_TABLE_ID column in the ID_TABLE start
> # at 101 for tables used in projects.
> # -------------------------------------------------------------------------
> initialID = 101
>
>
>
>
>
>
>
> Frederic Gedin wrote:
>
>> Martin
>>
>>
>> Fine job, it works well!
>> Did you notice that the "second" and "third" databases are created but
>> are leaved empty? This may be a problem for those people who like to
>> work with several databases.
>>
>> Frederic
>>
>> Martin Poeschl wrote:
>>
>>> i uploaded a pre-release of the next tdk to
>>>
>>> http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
>>>
>>>
>>> it includes:
>>>
>>> turbine-2.2-b2-dev
>>> torque-3.0-b3-dev
>>> velocity-1.3
>>> tomcat-4.0.4
>>>
>>> please give it a try!
>>>
>>> changes:
>>>
>>> - the coupled torque has been removed
>>> - torque uses List instead of Vector now
>>> - commons-jdbc2pool is used instead of the old torque pool
>>> - upgrade to tomcat-4.0.4
>>>
>>> the official release is planned for wednesday next week (i'm off 'til
>>> monday and i'll do some additional testing on thursday ;-)
>>>
>>> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
>>> you definitly have to change your code .. there will be a doc
>>> describing the change before the finale release
>>>
>>> martin
>>>
>>>
>>> --
>>> To unsubscribe, e-mail:
>>> <ma...@jakarta.apache.org>
>>> For additional commands, e-mail:
>>> <ma...@jakarta.apache.org>
>>>
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Fabio Daprile <fa...@wuerth-phoenix.com>.
Hello,
i got this error whene trying to rebuild my project with this tdk.
[torque-data-model] Using classpath
[torque-data-model] Generating to file
C:\TDK3\tdk\webapps\bugtrack\WEB-INF\src\sql\create-db.sql
[torque-data-model] Resolver: used
http://jakarta.apache.org/turbine/dtd/database.dtd
[torque-data-model] Couldn't read DTD specified in XML schema: Operation
timed out: no further information
[torque-data-model] java.lang.NullPointerException
i do not know why.
can you help me?
hereafter the build.properties:
# This currently duplicated because the torque templates have
# a dependency on $project.
project = bugtrack
app.root = ../${tdk.project}
build.webappRoot = ${tdk.home}/webapps/${tdk.project}
target.package = com.wuerth.phoenix.bugtrack
target.directory = com/wuerth/phoenix/bugtrack
build.dest = ${build.webappRoot}/WEB-INF/classes
version = 0.1
src.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/src
conf.dir = ${tdk.home}/webapps/bugtrack/WEB-INF/conf
master.conf.dir = ${tdk.home}/tdk/ancillary/${tdk.turbineVersion}/src/conf
debug = on
optimize = off
deprecation = on
idTableDatabase = bugtrack
# todo!!!
lib.dir = ${build.webappRoot}/WEB-INF/lib
torque.home = ${build.webappRoot}/WEB-INF
outputDirectory = src
schemaDirectory = conf
# -------------------------------------------------------------------
#
# D A T A B A S E S E T T I N G S
#
# -------------------------------------------------------------------
database.name = bugtrack
database = mysql
createDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
buildDatabaseUrl = jdbc:mysql://127.0.0.1/bugtrack
databaseUrl = jdbc:mysql://127.0.0.1/bugtrack
databaseDriver = org.gjt.mm.mysql.Driver
databaseUser = fabio
databasePassword = elirpadt
databaseHost = 127.0.0.1
# -------------------------------------------------------------------
#
# T O R Q U E C O N F I G U R A T I O N
#
# -------------------------------------------------------------------
# These settings will allow you to customize the way your
# Peer-based object model is created.
# -------------------------------------------------------------------
torque.buildFile=build-torque.xml
extend=TurbineMapBuilder
mapname=TurbineMap
suffix=MapBuilder
targetPackage=com.wuerth.phoenix.bugtrack.om
targetDirectory=com/wuerth/phoenix/bugtrack/om
addSaveMethod=true
addGetByNameMethod=false
complexObjectModel=true
basePrefix=Base
useManagers=false
overloadKeySetters=true
useClasspath=true
templatePath=use_classpath
# -------------------------------------------------------------------
#
# C O N T R O L T E M P L A T E S
#
# -------------------------------------------------------------------
SQLControlTemplate = sql/base/Control.vm
OMControlTemplate = om/Control.vm
idTableControlTemplate = sql/id-table/Control.vm
securityControlTemplate = sql/security/Control.vm
DataDTDControlTemplate = data/Control.vm
DataDumpControlTemplate = data/dump/Control.vm
DataSQLControlTemplate = sql/load/Control.vm
# -------------------------------------------------------------------------
# The values for the ID_TABLE_ID column in the ID_TABLE start
# at 101 for tables used in projects.
# -------------------------------------------------------------------------
initialID = 101
Frederic Gedin wrote:
> Martin
>
>
> Fine job, it works well!
> Did you notice that the "second" and "third" databases are created but
> are leaved empty? This may be a problem for those people who like to
> work with several databases.
>
> Frederic
>
> Martin Poeschl wrote:
>
>> i uploaded a pre-release of the next tdk to
>>
>> http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
>>
>>
>> it includes:
>>
>> turbine-2.2-b2-dev
>> torque-3.0-b3-dev
>> velocity-1.3
>> tomcat-4.0.4
>>
>> please give it a try!
>>
>> changes:
>>
>> - the coupled torque has been removed
>> - torque uses List instead of Vector now
>> - commons-jdbc2pool is used instead of the old torque pool
>> - upgrade to tomcat-4.0.4
>>
>> the official release is planned for wednesday next week (i'm off 'til
>> monday and i'll do some additional testing on thursday ;-)
>>
>> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
>> you definitly have to change your code .. there will be a doc
>> describing the change before the finale release
>>
>> martin
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
Fabio Daprile
Würth-Phoenix Srl
Via Kravogl 4, I-39100 Bolzano
Tel: +39 0471/564111 - (direct 564070)
Fax: +39 0471/564122
mailto:fabio.daprile@wuerth-phoenix.com
http://www.wuerth-phoenix.com
http://www.wuerth.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: tdk pre 2.2-b2 release
Posted by Frederic Gedin <fr...@Jaluna.COM>.
Martin
Fine job, it works well!
Did you notice that the "second" and "third" databases are created but
are leaved empty? This may be a problem for those people who like to
work with several databases.
Frederic
Martin Poeschl wrote:
> i uploaded a pre-release of the next tdk to
>
> http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
>
> it includes:
>
> turbine-2.2-b2-dev
> torque-3.0-b3-dev
> velocity-1.3
> tomcat-4.0.4
>
> please give it a try!
>
> changes:
>
> - the coupled torque has been removed
> - torque uses List instead of Vector now
> - commons-jdbc2pool is used instead of the old torque pool
> - upgrade to tomcat-4.0.4
>
> the official release is planned for wednesday next week (i'm off 'til
> monday and i'll do some additional testing on thursday ;-)
>
> turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
> you definitly have to change your code .. there will be a doc describing
> the change before the finale release
>
> martin
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: tdk pre 2.2-b2 release
Posted by Brent Hale <bh...@eventronix.com>.
I downloaded this latest beta, changed the default appname from "newapp" to
"fb" and changed the other appropriate properties. When I build the
generated app with "ant init" I get the following:
[torque-data-model] Resolver: used database.dtd from
org.apache.torque.engine.database.transform package
[echo] Executing the create-db.sql script ...
[echo]
BUILD FAILED
C:\devtools\tdk-2.2-b2\webapps\fb\WEB-INF\build\build-torque.xml:202:
java.sql.SQLException: General error: Unknown database 'fb'
I noticed another post that said they were getting the same error. Do you
know what else we need to change to get this working with this latest beta
so that others won't run into it when it gets released?
Brent
-----Original Message-----
From: Martin Poeschl [mailto:mpoeschl@marmot.at]
Sent: Friday, July 12, 2002 4:00 PM
To: Turbine Developers List; Turbine Users List
Subject: tdk pre 2.2-b2 release
i uploaded a pre-release of the next tdk to
http://jakarta.apache.org/builds/jakarta-turbine/alpha/tdk-pre-2.2.tar.gz
it includes:
turbine-2.2-b2-dev
torque-3.0-b3-dev
velocity-1.3
tomcat-4.0.4
please give it a try!
changes:
- the coupled torque has been removed
- torque uses List instead of Vector now
- commons-jdbc2pool is used instead of the old torque pool
- upgrade to tomcat-4.0.4
the official release is planned for wednesday next week (i'm off 'til monday
and i'll do some
additional testing on thursday ;-)
turbine 2.2 will be NO drop-in replacement for turbine 2.1!!
you definitly have to change your code .. there will be a doc describing the
change before the
finale release
martin
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>