AW: [opencms-dev] missing pl/sql procedures with genericsql insta ll
Stefan Marx
Stefan.Marx at framfab.de
Thu May 30 13:53:21 CEST 2002
Hi Dan,
in your last posting you ask:
[..]
Does OpenCMS need the PL/SQL packages to use Oracle effectively?
[..]
I'm afraid .. yes! As you may guess by looking at the names of the
PL/SQL procedures, OpenCMS uses the produres to maintain the accounts
and the virtual file system.
cu Stefan
-----Ursprüngliche Nachricht-----
Von: Dan Moore [mailto:Dan.Moore at xor.com]
Gesendet: Mittwoch, 29. Mai 2002 21:39
An: opencms-dev at www.opencms.org
Betreff: [opencms-dev] missing pl/sql procedures with genericsql install
Hi folks,
We are trying to get OpenCMS up and running in WebLogic 6.1 with Oracle as
the database. In order to avoid some of the setup headaches with WLS 6.1,
we used Tomcat (4.0.1 on NT) to run the setup servlets. The first time
we ran the setup, we used the OCI driver. The second time, we used the
genericSql driver.
However, with the OCI driver, a large number of PL/SQL packages were
installed. With the genericSql driver, no packages were installed. This
is cause for concern.
Does OpenCMS need the PL/SQL packages to use Oracle effectively?
I looked in the mailing list, but there was no recent mention of pl/sql
packages.
Thanks for your time,
Dan
PS Here's a list of the functions that were omitted on the second install:
FUNCTION accessCreate
FUNCTION accessLock
FUNCTION accessUnlock
FUNCTION accessProject
FUNCTION accessRead
FUNCTION accessWrite
FUNCTION accessOwner
FUNCTION accessOther
FUNCTION accessGroup
FUNCTION userInGroup
FUNCTION getGroupsOfUser
FUNCTION getParent (pGroupId NUMBER) RETURN NUMBER;
FUNCTION getParent(pResourceName VARCHAR2) RETURN VARCHAR2;
FUNCTION isManagerOfProject
FUNCTION getUsersOfGroup
FUNCTION getAllAccessibleProjects
FUNCTION onlineProject RETURN cms_projects%ROWTYPE;
FUNCTION onlineProject (pProjectId NUMBER) RETURN cms_projects%ROWTYPE;
FUNCTION ReadAllProperties
FUNCTION readFolderAcc
FUNCTION readFolder
FUNCTION readFileHeader(pUserId NUMBER, pProjectID NUMBER, pFileName
VARCHAR2) RETURN userTypes.anyCursor;
FUNCTION readFileHeader(pUserId NUMBER, pProjectID NUMBER, pOnlineProjectId
NUMBER, pFileName VARCHAR2) RETURN userTypes.anyCursor;
FUNCTION readFile(pUserId NUMBER, pProjectID NUMBER, pFileName VARCHAR2)
RETURN userTypes.anyCursor;
FUNCTION readFile(pUserId NUMBER, pProjectID NUMBER, pOnlineProjectId
NUMBER, pFileName VARCHAR2) RETURN userTypes.anyCursor;
FUNCTION readFileNoAccess(pUserId NUMBER, pProjectID NUMBER,
pOnlineProjectId NUMBER, pFileName VARCHAR2) RETURN userTypes.anyCursor;
FUNCTION getFilesInFolder(pUserId NUMBER, pProjectId NUMBER, pResourceName
VARCHAR2) RETURN userTypes.resourceTable;
FUNCTION getFoldersInFolder(pUserId NUMBER, pProjectId NUMBER, pResourceName
VARCHAR2) RETURN userTypes.anyCursor;
FUNCTION getParentId(pProjectID NUMBER, pResourceId NUMBER) RETURN NUMBER;
FUNCTION addInList(pAnyId NUMBER) RETURN BOOLEAN;
FUNCTION addInList(pId NUMBER) RETURN BOOLEAN;
FUNCTION addPathInList(pName VARCHAR2) RETURN BOOLEAN;
FUNCTION getErrMsg(pErrorCode NUMBER) RETURN VARCHAR2 IS
PROCEDURE createProject
PROCEDURE publishProject
PROCEDURE writeProperties(pUserId IN NUMBER, pProjectId IN NUMBER,
pResourceId IN NUMBER, pResourceType IN NUMBER, pPropertyInfo IN
userTypes.anyCursor);
PROCEDURE writeProperties(pProjectId IN NUMBER, pPropertyInfo IN
userTypes.anyCursor, pResourceId IN NUMBER, pResourceType IN NUMBER);
PROCEDURE writeProperty
PROCEDURE lockResource(pUserId IN NUMBER, pProjectId IN NUMBER, pFolderName
IN VARCHAR2, pForce IN VARCHAR2, pResource OUT userTypes.anyCursor);
PROCEDURE lockResource(pUserId IN NUMBER, pProjectId IN NUMBER,
pOnlineProject NUMBER, pFolderName IN VARCHAR2, pForce IN VARCHAR2);
PROCEDURE unlockResource(pUserId IN NUMBER, pProjectId IN NUMBER,
pFolderName IN VARCHAR2, pResource OUT userTypes.anyCursor);
PROCEDURE unlockResource(pUserId IN NUMBER, pProjectId IN NUMBER,
pOnlineProject IN NUMBER, pFolderName IN VARCHAR2);
PROCEDURE createFolder(pUserId NUMBER, pProjectId NUMBER, pParentResId
NUMBER, pFileId NUMBER,
pFolderName VARCHAR2, pFlags NUMBER);
PROCEDURE createFolder(pUserId IN NUMBER, pProjectId IN NUMBER,
pOnlineProjectId IN NUMBER,
pResource IN cms_resources%ROWTYPE, pParentId IN
NUMBER, pFolderName IN VARCHAR2,
oResource OUT userTypes.anyCursor);
PROCEDURE createFile(pProjectId IN NUMBER, pOnlineProjectId IN NUMBER,
pResource IN userTypes.fileRecord, pUserId IN NUMBER,
pParentId IN NUMBER, pFileName IN VARCHAR2, pCopy IN
VARCHAR2, oResource OUT userTypes.anyCursor);
PROCEDURE removeFolder(pUserId NUMBER, pProjectId NUMBER, pResourceID
NUMBER, pResourceName VARCHAR2);
PROCEDURE writeFolder(pProjectID IN NUMBER, pResource IN
cms_resources%ROWTYPE, pChange IN VARCHAR2);
PROCEDURE writeFolder(pProjectID IN NUMBER, pResource IN
cms_resources%ROWTYPE, pChange IN VARCHAR2, pUserId IN NUMBER);
PROCEDURE writeFileHeader(pProjectID IN NUMBER, pResource IN
cms_resources%ROWTYPE, pChange IN VARCHAR2);
PROCEDURE writeFileHeader(pProjectID IN NUMBER, pResource IN
cms_resources%ROWTYPE, pChange IN VARCHAR2, pUserId IN NUMBER);
PROCEDURE writeFile(pProjectID IN NUMBER, pResource IN userTypes.fileRecord,
pChange IN VARCHAR2);
PROCEDURE writeFile(pProjectID IN NUMBER, pResource IN userTypes.fileRecord,
pChange IN VARCHAR2, pUserId IN NUMBER);
PROCEDURE copyFile(pProjectId NUMBER, pUserId NUMBER, pSource VARCHAR2,
pDestination VARCHAR2);
PROCEDURE chstate(pUserId IN NUMBER, pProjectId IN NUMBER, pResourceName IN
VARCHAR2, pState IN NUMBER);
PROCEDURE backupFolder(pProjectId IN NUMBER, pFolder IN
cms_resources%ROWTYPE, pVersionId IN NUMBER, pPublishDate IN DATE);
PROCEDURE backupFile(pProjectId IN NUMBER, pFile IN userTypes.fileRecord,
pVersionId IN NUMBER, pPublishDate IN DATE);
PROCEDURE removeTemporaryFiles(pFilename IN VARCHAR2);
PROCEDURE backupProject (pProjectId NUMBER, pVersionId NUMBER, pPublishDate
DATE, pUserId NUMBER);
PROCEDURE raiseUserError(pError IN NUMBER) is
More information about the opencms-dev
mailing list