RE: Problem on testing J2
Yes I did started the database. Is there a possibility that it is not started normally even if I can login? Note that I run tomcat on a non-default ports but different from 9001 used by hsql. Vangelis -Original Message- From: Roger Ruttimann [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 7:04 AM To: Jetspeed Developers List Subject: Re: Problem on testing J2 The non-java and third party portlets have other dependencies (perl,php engines or other components) and fail for that reason. I agree some more documentation is needed how to run these portlets. The login which asks you to changes the password is a problem with HSQL. MySQL and other databases just work fine. About the error: Did you start the database (HSQL requires to be started e.g $TOMCAT_HOME/jetspeed-database/start-database.sh)? Roger Vlachogiannis Evangelos wrote: Hi all, I have just downloaded J2 binary ver. While I am running tomcat I am getting some exceptions that do not allow me to view non-java and third party portlets. I then tried to login .. I guessed right the password;) but it asked me to change that. Then I got the following exception which do not allow me to experience the logged in ver. org.springframework.transaction.CannotCreateTransactionException: Could not create OJB transaction; nested exception is org.apache.ojb.broker.accesslayer.Lookup Exception: SQLException thrown while trying to get Connection from Datasource (j ava:comp/env/jdbc/jetspeed) Any suggestions please? Thnx, Vangelis --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.804 / Virus Database: 546 - Release Date: 30/11/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.804 / Virus Database: 546 - Release Date: 30/11/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.804 / Virus Database: 546 - Release Date: 30/11/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JS1-528) error and display incorrectly in windows xp,
[ http://nagoya.apache.org/jira/browse/JS1-528?page=comments#action_56374 ] chen xiao sheng commented on JS1-528: - i am using windows xp sp1,ie sp1/xpsp2 now, how cannot i solve it?? error and display incorrectly in windows xp, Key: JS1-528 URL: http://nagoya.apache.org/jira/browse/JS1-528 Project: Jetspeed Type: Bug Versions: 1.4 Environment: tomcat 4.1.31 jetspeed 1.5 windows xp xpsp2 ie sp1 xpsp2 Reporter: chen xiao sheng In xp,jetspeed display incorrectly ,like: when visit: http://localhost:8080/jetspeed there are login information like Username: Password: but it display : $l10n.USERFORM_USERNAMEMSG $l10n.USERFORM_PASSWORDMSG after i login, i cannot customize correctly, the display so strange,and some function cannot work exactly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JS1-528) error and display incorrectly in windows xp,
[ http://nagoya.apache.org/jira/browse/JS1-528?page=comments#action_56375 ] chen xiao sheng commented on JS1-528: - i am using windows xp sp1,ie sp1/xpsp2 now, how cannot i solve it?? error and display incorrectly in windows xp, Key: JS1-528 URL: http://nagoya.apache.org/jira/browse/JS1-528 Project: Jetspeed Type: Bug Versions: 1.4 Environment: tomcat 4.1.31 jetspeed 1.5 windows xp xpsp2 ie sp1 xpsp2 Reporter: chen xiao sheng In xp,jetspeed display incorrectly ,like: when visit: http://localhost:8080/jetspeed there are login information like Username: Password: but it display : $l10n.USERFORM_USERNAMEMSG $l10n.USERFORM_PASSWORDMSG after i login, i cannot customize correctly, the display so strange,and some function cannot work exactly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PSML from role
Hi people, Anybody know how to get the screen configuration( psml file) from a role set when a new user is created? I need to set some panels and portlets for any role and when create user for any role this user be setted with this configuration(psml file). Thank you very much Regards, Carlos Torres
Re: J2 autodeployment.catalina.base jetspeed.properties setting
Randy Watler wrote:
Guys,
I use JPackage RPM installs for tomcat4 and tomcat5 on Linux. Over the
last day or two, I have been struggling to get a clean startup on
tomcat5. After I eliminated all of my stupid user tricks, I was able
to get everything to deploy cleanly only after customizing the setting
of autodeployment.catalina.base in
jetspeed.properties/override.properties. The reason this is necessary
is that the default setting, ${applicationRoot}/../../, does not
resolve to the base tomcat5 install directory that contains conf,
(primarily due to copious use of symbolic links and the relocation of
config files to /etc on Linux). The deployer requires access to this
directory to install the security.xml file in conf/Catalina/localhost.
I'd like to propose setting the autodeployment.catalina.base property
from the org.apache.jetspeed.server.home customized build.properties
setting. In development, this could be integrated into
portal/maven.xml as is done with the other autodeployment properties.
Of course, this will definitely kill the property-less install goal.
We could also apply some kind of search path specification there as
well, (i.e. '${applicationRoot}/../../,
/etc/tomcat${autodeployment.catalina.version.major}/,
/usr/share/tomcat${autodeployment.catalina.version.major}/, c:/Program
Files/Tomcat/'), that would work for most common deployments.
If this were only a production issue, I'd just set the property in
override.properties and be done with it. However, my primary concern
is for development ease of use.
Thoughts?
+1, sounds good to me.
Randy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Great minds discuss ideas. Average minds discuss events. Small minds discuss
people. - Admiral Hyman Rickover
***
* Scott T. Weaver *
* [EMAIL PROTECTED] *
* http://www.einnovation.com*
* -- *
* Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container *
* *
* OpenEdit, Website Content Management*
* http://www.openedit.org *
***
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (JS2-170) Im getting org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null'
Matthew, Please make sure that your jetspeed.xml configuration file is installed in the correct location. For Tomcat5, it should be installed in $TOMCAT_HOME/conf/Catalina/localhost. For Tomcat4, it should be installed in $TOMCAT_HOME/webapps. Randy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-jetspeed-2/installer - New directory
weaver 2004/12/08 08:56:56 jakarta-jetspeed-2/installer - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-jetspeed-2/installer/src - New directory
weaver 2004/12/08 08:56:56 jakarta-jetspeed-2/installer/src - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-jetspeed-2/installer/src/resources tomcat-users.xml
weaver 2004/12/08 08:57:03
Added: installer/src build.xml install.xml userInputSpec.xml
build.properties jetspeed-logo.gif installdir.txt
ProcessPanel.Spec.xml Readme.txt LICENSE.TXT
installer project.properties project.xml maven.xml
README.TXT
installer/src/resources tomcat-users.xml
Log:
Jetspeed 2 multi-platform binary installer.
Revision ChangesPath
1.1 jakarta-jetspeed-2/installer/src/build.xml
Index: build.xml
===
?xml version=1.0 encoding=UTF-8?
project basedir=$INSTALL_PATH default=install name=utilities
property file=${basedir}/build.properties/
target name=install
antcall target=build.db inheritall=true /
antcall target=install.tomcat inheritall=true /
antcall target=install.jetspeed inheritall=true /
/target
target name=build.db
property name=database.arg.script
value=${basedir}/sql/${ojb.platform}/phase3ojb-schema.sql /
antcall target=db.execute inheritall=true /
property name=database.arg.script
value=${basedir}/sql/${ojb.platform}/phase1-schema.sql /
antcall target=db.execute inheritall=true /
property name=database.arg.script
value=${basedir}/sql/${ojb.platform}/phase2-schema.sql /
antcall target=db.execute inheritall=true /
property name=database.arg.script
value=${basedir}/sql/${ojb.platform}/registry-schema.sql /
antcall target=db.execute inheritall=true /
property name=database.arg.script
value=${basedir}/sql/${ojb.platform}/refs-schema.sql /
antcall target=db.execute inheritall=true /
property name=database.arg.script
value=${basedir}/sql/${ojb.platform}/security-schema.sql /
antcall target=db.execute inheritall=true /
property name=database.arg.script
value=${basedir}/sql/populate-db-default.sql /
antcall target=db.execute inheritall=true /
/target
target name=db.execute
echoExecing SQL: ${database.arg.script}/echo
echo${driver.path}/echo
sql driver=${jdbc.driver}
url=${db.url}
userid=${db.username}
password=${db.password}
src=${database.arg.script}
classpath
pathelement path=${driver.path}/
/classpath
/sql
/target
target name=install.tomcat
unzip dest=${basedir}
src=${basedir}/tomcat/jakarta-tomcat-5.0.30.zip overwrite=true /
copy file=${basedir}/resources/tomcat-users.xml
todir=${tomcat.home}/conf overwrite=true /
chmod perm=ugo+x verbose=true
fileset dir=${tomcat.home}/bin /
/chmod
/target
target name=install.jetspeed
copy todir=${tomcat.home}/webapps/jetspeed
fileset dir=${basedir}/jetspeed /
/copy
!-- Set up tomcat's local security --
copy file=${basedir}/resources/jetspeed.xml
tofile=${tomcat.home}/conf/Catalina/localhost/jetspeed.xml overwrite=true
filterset begintoken=@ endtoken=@
filter token=USERNAME value=${db.username}/
filter token=PASSWORD value=${db.password}/
filter token=DRIVER value=${jdbc.driver}/
filter token=URL value=${db.url}/
filter token=USE_CONTEXTCLASSLOADER value=/
/filterset
/copy
!-- Copy and filter our OJB database platform definition so that it
matches the users selection --
copy file=${basedir}/resources/repository_database.xml
todir=${tomcat.home}/webapps/jetspeed/WEB-INF/classes overwrite=true
filterset begintoken=@ endtoken=@
filter token=PLATFORM value=${ojb.platform}/
/filterset
/copy
!-- Set up our main properties file per user variables --
copy file=${basedir}/resources/jetspeed.properties
tofile=${tomcat.home}/webapps/jetspeed/WEB-INF/conf/jetspeed.properties
overwrite=true
filterset begintoken=@ endtoken=@
filter token=AUTODEPLOYMENT_SERVER value=${tomcat.server}/
filter token=AUTODEPLOYMENT_USER value=${deployment.user}/
filter token=AUTODEPLOYMENT_PASSWORD
value=${deployment.password}/
/filterset
!-- Below filter is special because this concerns a numeric
property for which a non-numeric token results
in a test failure (TestSpringEngine)
This property therefore MUST remain defined EXACTLY as
specified for this filter to be able to work
--
filterset begintoken=autodeployment.catalina.version.major
endtoken=4
filter token==
value=autodeployment.catalina.version.major=5/
/filterset
filterset
Re: Problem on testing J2
Running Tomcat on a different port than 8080 doesn't affect the db connectivity. What Java version are you using? Tomcat version? OS? Roger Vlachogiannis Evangelos wrote: Yes I did started the database. Is there a possibility that it is not started normally even if I can login? Note that I run tomcat on a non-default ports but different from 9001 used by hsql. Vangelis -Original Message- From: Roger Ruttimann [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 7:04 AM To: Jetspeed Developers List Subject: Re: Problem on testing J2 The non-java and third party portlets have other dependencies (perl,php engines or other components) and fail for that reason. I agree some more documentation is needed how to run these portlets. The login which asks you to changes the password is a problem with HSQL. MySQL and other databases just work fine. About the error: Did you start the database (HSQL requires to be started e.g $TOMCAT_HOME/jetspeed-database/start-database.sh)? Roger Vlachogiannis Evangelos wrote: Hi all, I have just downloaded J2 binary ver. While I am running tomcat I am getting some exceptions that do not allow me to view non-java and third party portlets. I then tried to login .. I guessed right the password;) but it asked me to change that. Then I got the following exception which do not allow me to experience the logged in ver. org.springframework.transaction.CannotCreateTransactionException: Could not create OJB transaction; nested exception is org.apache.ojb.broker.accesslayer.Lookup Exception: SQLException thrown while trying to get Connection from Datasource (j ava:comp/env/jdbc/jetspeed) Any suggestions please? Thnx, Vangelis --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.804 / Virus Database: 546 - Release Date: 30/11/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.804 / Virus Database: 546 - Release Date: 30/11/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.804 / Virus Database: 546 - Release Date: 30/11/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-jetspeed-2/applications/pam project.xml
rogerrut2004/12/08 12:35:04 Modified:components/capability project.xml components/portlet-factory project.xml components/id-generator project.xml components/locator project.xml components/page-manager project.xml applications/struts-demo project.xml components/registry project.xml components/web-content project.xml components/persistence project.xml applications/jsf-demo project.xml components/jetspeed project.xml taglibs project.xml layout-portlets project.xml components/sso project.xml applications/security project.xml components/search project.xml portal maven.xml project.xml components/security project.xml applications/php project.xml .project.xml commons project.xml components/rdbms project.xml components/cm project.xml components/prefs project.xml components/profiler project.xml components/file-cache project.xml applications/perl project.xml taglibs/treecontrol project.xml components/deploy-tool project.xml jetspeed-api project.xml applications/demo project.xml applications/pam project.xml Log: Changed the version in the root project file to 2.0-M2-dev Removed all versions from project files (except portals-bridges) so that they inherit from root project Revision ChangesPath 1.14 +5 -6 jakarta-jetspeed-2/components/capability/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-jetspeed-2/components/capability/project.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- project.xml 5 Dec 2004 00:54:53 - 1.13 +++ project.xml 8 Dec 2004 20:35:02 - 1.14 @@ -23,7 +23,6 @@ idjetspeed-capability/id groupIdjetspeed2/groupId nameJetspeed-2 Capability Components/name - currentVersion2.0-M1/currentVersion packageorg.apache.jetspeed/package description Capability Components defines an api for guessing what client is accessing a @@ -48,27 +47,27 @@ dependency idjetspeed-cm/id groupIdjetspeed2/groupId - version2.0-M1/version + version2.0-M2-dev/version properties war.bundletrue/war.bundle /properties /dependency dependency idjetspeed2:jetspeed-commons/id - version2.0-M1/version + version2.0-M2-dev/version /dependency dependency idjetspeed2:jetspeed-api/id - version2.0-M1/version + version2.0-M2-dev/version /dependency dependency idjetspeed2:jetspeed-registry/id - version2.0-M1/version + version2.0-M2-dev/version /dependency !-- Testing only -- dependency idjetspeed2:jetspeed-rdbms/id - version2.0-M1/version + version2.0-M2-dev/version /dependency dependency idcommons-lang/id 1.5 +3 -3 jakarta-jetspeed-2/components/portlet-factory/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-jetspeed-2/components/portlet-factory/project.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- project.xml 5 Dec 2004 00:54:53 - 1.4 +++ project.xml 8 Dec 2004 20:35:02 - 1.5 @@ -24,7 +24,7 @@ idjetspeed-portlet-factory/id groupIdjetspeed2/groupId nameJetspeed-2 Portlet Factory/name - currentVersion2.0-M1/currentVersion + packageorg.apache.jetspeed/package description Jetspeed Portlet Factory @@ -62,11 +62,11 @@ /dependency dependency idjetspeed2:jetspeed-commons/id - version2.0-M1/version + version2.0-M2-dev/version /dependency dependency idjetspeed2:jetspeed-api/id - version2.0-M1/version + version2.0-M2-dev/version /dependency dependency idcommons-logging/id 1.9 +3 -3 jakarta-jetspeed-2/components/id-generator/project.xml Index: project.xml === RCS file: /home/cvs/jakarta-jetspeed-2/components/id-generator/project.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- project.xml 5 Dec 2004 00:54:53 - 1.8 +++ project.xml 8 Dec 2004 20:35:02 - 1.9 @@ -23,7 +23,7 @@
[jira] Created: (JS2-171) table capability is a reserved word in sybase
table capability is a reserved word in sybase - Key: JS2-171 URL: http://nagoya.apache.org/jira/browse/JS2-171 Project: Jetspeed 2 Type: Wish Environment: windows 2000, tomcat 5.x, sql anywhere 9.0 Reporter: Chandra Sunkara Priority: Minor I was trying to install jetspeed-2 onto tomcat 5.0, sql anywhere 9.0 (aka sybase) and came accross following error. db.execute: [sql] Executing file: C:\Tools\jakarta\jakarta-jetspeed-2\target\src\sql\syb ase\phase1-schema.sql [sql] [ERROR] Failed to execute: IF EXISTS (SELECT 1 FROM sysobjects WHERE t ype = 'U' AND name = 'CAPABILITY') BEGIN DROP TABLE CAPABILITY END BUILD FAILED File.. C:\Tools\jakarta\jakarta-jetspeed-2\maven.xml Element... sql Line.. 372 Column 39 com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -131: Syntax error near 'CAPABI LITY' on line 1 Total time: 8 seconds After looking through sybase site seems like capability is a sysbase reserved word and hence would not create table. Please ignore if this is already a known issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[J2] Vote: Torque schema generation problems - how to proceed?
Team, Today, I dived into our usage of torque and what we are getting from it. I didn't really know torque yet, but I was dismayed by what I encountered and how it is affecting the way we are configuring J2 right now. The problems with drop table statements and foreign key violations we have had recently (and still have) are really caused by the current (lack of) functionality of torque and its quirks. After reviewing the velocity scripts used by torque, I can see these are easily fixable. But, it'll require heavy changes to them and therefore I'm not so sure the torque team would quickly accept them. I would like to propose to create and maintain our own set of torque scripts instead of using the packaged ones. Because of the way torque processes these scripts, this will mean we need to maintain *all* of the torque-sql scripts: only supplying those which need to be changed won't do. Maybe, after some time, our versions of these scripts can be incorporated back into torque, but that I don't find too important right now. I would like to get rid of several workarounds and auxiliary sql scripts we currently have to use just to get things working: - no need anymore for several drop goals and drop scripts - no need anymore for special instructions to get an initial installation on Oracle, nor post processing the oracle sql scripts to strip out unwanted drop statements - no need anymore for manual table creation on Oracle when a new table is added (no automatic solution possible) Whats more, I would also like to get rid of all the different populate-userinfo-for-default-psml.sql variants. I looked into the capabilities (capability also being another issue with torque it seems on sybase: a reserved word) of torque on transforming data xml to sql. Well, don't hold your breath: it won't do right now. Although the schema xml parsing engine is nice enough as it is, other than that I really don't see much added value for J2 as we also don't use the Peer functionality (which takes up by far the biggest part of its codebase). What I really would like to see is an new/rewritten/forked torque implementation, only used for schema and (proper) data xml parsing which can both generate sql and/or perform direct sql/jdbc execution on the fly. Then we can provide schema installation (and upgrades! using version attributes in the xml) at runtime (optionally of course). New, but still missing tables, constraints, configuration data, et cetera could be created only when needed. I don't think this would be very hard, nor too much work to provide using (only a small part of) the current torque codebase as starting point. If we would agree on this path, I'm more than willing to put in time realizing this goal. Of course, I've been searching the net today for alternatives capable of this but really couldn't find anything coming near these requirements *and* with an ASF compatible license. Only hibernate has something like this build in (automatic schema creation and/or upgrade), but that one is off limits (isn't it?). So, I'd like to call a vote on the following proposals: - maintain our own torque-sql scripts: [ ] - provide our own data xml to sql (torque based) scripts: [ ] - (re)write our own database config engine based on torque allowing runtime schema/data installation/upgrade: [ ] Regards, Ate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [J2] Vote: Torque schema generation problems - how to proceed?
Ate Douma wrote: So, I'd like to call a vote on the following proposals: - maintain our own torque-sql scripts: [X] - provide our own data xml to sql (torque based) scripts: [X] - (re)write our own database config engine based on torque allowing runtime schema/data installation/upgrade: [X] Ate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [J2] Vote: Torque schema generation problems - how to proceed?
I think you may want to consider these items in the context of fixing the total nightmare of using torque-gen with Postgres as well. I have posted several times about the hoops I jump through to get JS2 and Postgres to work together, and your suggestions look like a good opportunity to fix those problems with torque-gen and Postgres. To be clear, no single project is at fault (Postgres, Torque, or JS2), but some minor bad choices in each are making Postgres support really crappy right now in JS2. I use Postgres every day with JS2, so if you need help with checking ongoing Postgres compatibility, especially with regards to these proposals, I am happy to help. Chris On Thu, 09 Dec 2004 03:10:25 +0100, Ate Douma [EMAIL PROTECTED] wrote: Team, Today, I dived into our usage of torque and what we are getting from it. I didn't really know torque yet, but I was dismayed by what I encountered and how it is affecting the way we are configuring J2 right now. The problems with drop table statements and foreign key violations we have had recently (and still have) are really caused by the current (lack of) functionality of torque and its quirks. After reviewing the velocity scripts used by torque, I can see these are easily fixable. But, it'll require heavy changes to them and therefore I'm not so sure the torque team would quickly accept them. I would like to propose to create and maintain our own set of torque scripts instead of using the packaged ones. Because of the way torque processes these scripts, this will mean we need to maintain *all* of the torque-sql scripts: only supplying those which need to be changed won't do. Maybe, after some time, our versions of these scripts can be incorporated back into torque, but that I don't find too important right now. I would like to get rid of several workarounds and auxiliary sql scripts we currently have to use just to get things working: - no need anymore for several drop goals and drop scripts - no need anymore for special instructions to get an initial installation on Oracle, nor post processing the oracle sql scripts to strip out unwanted drop statements - no need anymore for manual table creation on Oracle when a new table is added (no automatic solution possible) Whats more, I would also like to get rid of all the different populate-userinfo-for-default-psml.sql variants. I looked into the capabilities (capability also being another issue with torque it seems on sybase: a reserved word) of torque on transforming data xml to sql. Well, don't hold your breath: it won't do right now. Although the schema xml parsing engine is nice enough as it is, other than that I really don't see much added value for J2 as we also don't use the Peer functionality (which takes up by far the biggest part of its codebase). What I really would like to see is an new/rewritten/forked torque implementation, only used for schema and (proper) data xml parsing which can both generate sql and/or perform direct sql/jdbc execution on the fly. Then we can provide schema installation (and upgrades! using version attributes in the xml) at runtime (optionally of course). New, but still missing tables, constraints, configuration data, et cetera could be created only when needed. I don't think this would be very hard, nor too much work to provide using (only a small part of) the current torque codebase as starting point. If we would agree on this path, I'm more than willing to put in time realizing this goal. Of course, I've been searching the net today for alternatives capable of this but really couldn't find anything coming near these requirements *and* with an ASF compatible license. Only hibernate has something like this build in (automatic schema creation and/or upgrade), but that one is off limits (isn't it?). So, I'd like to call a vote on the following proposals: - maintain our own torque-sql scripts: [ ] - provide our own data xml to sql (torque based) scripts: [ ] - (re)write our own database config engine based on torque allowing runtime schema/data installation/upgrade: [ ] Regards, Ate - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
