You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Ate Douma <at...@douma.nu> on 2009/06/02 09:15:43 UTC
Re: Jetspeed 2.2: mssql database maven configuration
Frank Otto wrote:
> I have created a new JIRA issue -->
> https://issues.apache.org/jira/browse/JS2-1024
>
> Now, how can I apply a patch to my maven build and after this to
> jetspeed 2 repository?
>
> This is the first JIRA issue for me.
Hi Frank,
As you (and/or your team) probably are more experienced with mssql than most of us, I suggest proceeding as I described before.
Compare the manually written mssql/create-schema.sql script against a generated one, PostgreSQL/Derby/MySql/Oracle etc. and determine the
parts missing or (now) incorrect.
Then try to convert those missing parts in a format suitable for mssql and test it out.
Once you've got everything working again, you can attach a resulting new mssql/create-schema.sql file to this JIRA issue and I can help out
creating a patch file based upon that (or just provide a diff file against the original).
Once we've checked and confirmed the changes are complete and valid, I can check it in against the jetspeed-2 svn repository.
Regards,
Ate
>
> Ate Douma schrieb:
>> Frank Otto wrote:
>>> hi,
>>>
>>> thanks for your answer. We need MSSQL2000/2005/2008 and in jetspeed
>>> 2.1.3 it works correctly.
>>>
>>> The connectin is now ok, but I get following error:
>>>
>>> org.apache.jetspeed.serializer.SerializerException: Creating an
>>> instance from a
>>> serialized representation of SecurityDomains failed with message
>>> Could not creat
>>> e default and / or system domains!
>>> OJB operation; bad SQL grammar []; nested exception is
>>> java.sql.SQLException: Un
>>> g³ltiger Objektname 'SECURITY_DOMAIN'.
>>> at
>>> org.apache.jetspeed.serializer.JetspeedSecuritySerializer.recreateSec
>>> urityDomains(JetspeedSecuritySerializer.java:256)
>>
>> Yeah, I already expected something like that.
>> The hand written mssql create-schema.sql seems to be not in sync with
>> the generated sql scripts.
>>
>> I suggest comparing the mssql script with a generate one like one for
>> Oracle/MySql/PostgreSQL etc. and try to create a patch for mssql based
>> on that.
>>
>> All the sql scripts are contained within the
>> jetspeed-portal-resources-2.20.jar under folder /ddl (including the
>> one for mssql):
>>
>> http://repo2.maven.org/maven2/org/apache/portals/jetspeed-2/jetspeed-portal-resources/2.2.0/jetspeed-portal-resources-2.2.0.jar
>>
>>
>> I suggest creating a new JIRA issue for this (fix version: 2.2.1) so
>> you can apply a patch there too.
>>
>> Regards,
>>
>> Ate
>>
>>>
>>>
>>>
>>> kind regards,
>>>
>>> Frank
>>>
>>>
>>> Ate Douma schrieb:
>>>> Frank Otto wrote:
>>>>> Thanks, but I have no artifact properties for mssql jdbc driver.
>>>>>
>>>>> The property "org.apache.jetspeed.production.jdbc.drivers.path"
>>>>> doesn't work.
>>>> That property is no longer used for Jetspeed 2.2.0
>>>> Please use the instructions as described here:
>>>>
>>>> http://portals.apache.org/jetspeed-2/buildguide/maven-2-build.html
>>>>
>>>> An example mssql configuration I've used myself (quite) sometime ago
>>>> which worked for an earlier build of Jetspeed-2.2-SNAPSHOT
>>>> would be the following:
>>>>
>>>>
>>>> <org.apache.jetspeed.production.database.default.name>mssql</org.apachejetspeed.production.database.default.name>
>>>>
>>>>
>>>> <org.apache.jetspeed.production.jdbc.driver.groupId>net.sourceforge.jtds</org.apache.jetspeed.production.jdbc.driver.groupId>
>>>>
>>>>
>>>> <org.apache.jetspeed.production.jdbc.driver.artifactId>jtds</org.apachejetspeed.production.jdbc.driver.artifactId>
>>>>
>>>>
>>>> <org.apache.jetspeed.production.jdbc.driver.version>1.2.2</org.apache.jetspeed.production.jdbc.driver.version>
>>>>
>>>>
>>>> <org.apache.jetspeed.production.database.driver>net.sourceforge.jtds.jdbc.Driver</org.apache.jetspeed.production.database.driver>
>>>>
>>>> <org.apache.jetspeed.production.database.url>
>>>>
>>>> <![CDATA[jdbc:jtds:sqlserver://localhost:1433/j2;socketTimeout=150]]>
>>>> </org.apache.jetspeed.production.database.url>
>>>>
>>>> <org.apache.jetspeed.production.database.user>j2</org.apache.jetspeed.production.database.user>
>>>>
>>>>
>>>> <org.apache.jetspeed.production.database.password>j2</org.apache.jetspeed.production.database.password>
>>>>
>>>>
>>>> Be aware though that AFAIK the mssql support in the current 2.2.0
>>>> released version might not be up to par with the other databases.
>>>>
>>>> The problem with mssql is that it requires manual definition of its
>>>> database schema. Its so much different and lacking in certain areas
>>>> of standard SQL support that automatically generating the schema
>>>> like we do for all other databases just isn't doable.
>>>> We do have some handling for that, overriding the schema generation
>>>> with hand written mssql scripts, but AFAIK those might not be fully
>>>> updated yet with some recent model changes.
>>>> FYI, these mssql scripts are defined here (and applied during
>>>> database creation):
>>>>
>>>> http://svn.apache.org/repos/asf/portals/jetspeed-2/portal/trunk/jetspeed-portal-resources/src/main/resources/ddl/mssql
>>>>
>>>>
>>>> As none of the jetspeed committers has clients using mssql anymore
>>>> (either moved to more standard databases or elsewhere),
>>>> the priority to keep supporting mssql has dwindled a bit.
>>>> That doesn't mean we don't want or will keep supporting mssql, but
>>>> for that we have to rely on the community to support us with error
>>>> reports and patches.
>>>>
>>>> The above configuration is know to work if you check out the
>>>>
>>>> http://svn.apache.org/repos/asf/portals/jetspeed-2/portal/branches/JETSPEED-2.2-PRE-PLUTO-2-SNAPSHOT
>>>>
>>>> branch, but using that branch really is not advisable.
>>>>
>>>> If you really need to use mssql, I advise just trying the above
>>>> configuration out and see if/where it breaks.
>>>> From there, you can try to determine the changes needed (like
>>>> comparing it against the generated schema scripts for other databases)
>>>> and we'll be happy to help out applying patches and fixes.
>>>>
>>>> Regards,
>>>>
>>>> Ate
>>>>
>>>>>
>>>>> The maven build doesn't find the jdbc driver.
>>>>>
>>>>> Vivek Kumar schrieb:
>>>>>> See this
>>>>>>
>>>>>> http://portals.apache.org/jetspeed-2/buildguide/maven-2-build.html
>>>>>>
>>>>>> Vivek
>>>>>>
>>>>>> Frank Otto wrote:
>>>>>>> how are the settings for mssql database in jetspeed2.2?
>>>>>>>
>>>>>>> I find no informations on jetspeed2.2 documentation (only for
>>>>>>> derbydb and mysql).
>>>>>>>
>>>>>>>
>>>>>>> kind regards
>>>>>>>
>>>>>>> frank
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>>>> For additional commands, e-mail:
>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>
>>>>>>> Delivered-To: firevelocity@gmail.com
>>>>>>> Received: by 10.239.145.203 with SMTP id t11cs510731hba;
>>>>>>> Fri, 29 May 2009 02:10:40 -0700 (PDT)
>>>>>>> Received: by 10.114.192.17 with SMTP id
>>>>>>> p17mr3544424waf.196.12435882393 <http://www.snapanumber.com/>52;
>>>>>>> Fri, 29 May 2009 02:10:39 -0700 (PDT)
>>>>>>> Return-Path:
>>>>>>> <je...@portals.apache.org>
>>>>>>>
>>>>>>> Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
>>>>>>> by mx.google.com with SMTP id
>>>>>>> 26si1159924pxi.115.2009.05.29.02.10.38;
>>>>>>> Fri, 29 May 2009 02:10:39 -0700 (PDT)
>>>>>>> Received-SPF: pass (google.com: domain of
>>>>>>> jetspeed-user-return-26685-firevelocity=gmail.com@portals.apache.org
>>>>>>> designates 140.211.11.3 as permitted sender) client-ip=140.211.11.3;
>>>>>>> Authentication-Results: mx.google.com; spf=pass (google.com:
>>>>>>> domain of
>>>>>>> jetspeed-user-return-26685-firevelocity=gmail.com@portals.apache.org
>>>>>>> designates 140.211.11.3 as permitted sender)
>>>>>>> smtp.mail=jetspeed-user-return-26685-firevelocity=gmail.com@portals.apache.org
>>>>>>>
>>>>>>> Received: (qmail 81426 invoked by uid 500); 29 May 2009 09:10:37
>>>>>>> -0000
>>>>>>> Mailing-List: contact jetspeed-user-help@portals.apache.org; run
>>>>>>> by ezmlm
>>>>>>> Precedence: bulk
>>>>>>> List-Help: <ma...@portals.apache.org>
>>>>>>> List-Unsubscribe:
>>>>>>> <ma...@portals.apache.org>
>>>>>>> List-Post: <ma...@portals.apache.org>
>>>>>>> List-Id: <jetspeed-user.portals.apache.org>
>>>>>>> Reply-To: "Jetspeed Users List" <je...@portals.apache.org>
>>>>>>> Delivered-To: mailing list jetspeed-user@portals.apache.org
>>>>>>> Received: (qmail 81416 invoked by uid 99); 29 May 2009 09:10:37
>>>>>>> -0000
>>>>>>> Received: from athena.apache.org (HELO athena.apache.org)
>>>>>>> (140.211.11.136)
>>>>>>> by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009
>>>>>>> 09:10:37 +0000
>>>>>>> X-ASF-Spam-Status: No, hits=-0.0 required=10.0
>>>>>>> tests=SPF_PASS
>>>>>>> X-Spam-Check-By: apache.org
>>>>>>> Received-SPF: pass (athena.apache.org: domain of
>>>>>>> otto@delta-barth.de designates 80.243.61.50 as permitted sender)
>>>>>>> Received: from [80.243.61.50] (HELO po.depag.de) (80.243.61.50)
>>>>>>> by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009
>>>>>>> 09:10:29 +0000
>>>>>>> Received: from localhost (unknown [127.0.0.1])
>>>>>>> by po.depag.de (Postfix) with ESMTP id 400958D110
>>>>>>> for <je...@portals.apache.org>; Fri, 29 May 2009
>>>>>>> 11:13:30 +0200 (CEST)
>>>>>>> Received: from tati.lr3.depag.de (tati.lr3.depag.de [10.1.0.22])
>>>>>>> by po.depag.de (Postfix) with ESMTP id 74CE88D104
>>>>>>> for <je...@portals.apache.org>; Fri, 29 May 2009
>>>>>>> 11:13:28 +0200 (CEST)
>>>>>>> Received: from [10.1.21.120] (unknown [10.1.21.120])
>>>>>>> by tati.lr3.depag.de (Postfix) with ESMTP id 0BD6E8D84
>>>>>>> for <je...@portals.apache.org>; Fri, 29 May 2009
>>>>>>> 11:10:06 +0200 (CEST)
>>>>>>> Message-ID: <4A...@delta-barth.de>
>>>>>>> Date: Fri, 29 May 2009 11:10:05 +0200
>>>>>>> From: Frank Otto <ot...@delta-barth.de>
>>>>>>> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
>>>>>>> MIME-Version: 1.0
>>>>>>> To: Jetspeed Users List <je...@portals.apache.org>
>>>>>>> Subject: Jetspeed 2.2: mssql database maven configuration
>>>>>>> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>>>>>>> Content-Transfer-Encoding: 7bit
>>>>>>> X-Virus-Scanned: by AMaViS perl-11
>>>>>>> X-Virus-Checked: Checked by ClamAV on apache.org
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> how are the settings for mssql database in jetspeed2.2?
>>>>>>>
>>>>>>> I find no informations on jetspeed2.2 documentation (only for
>>>>>>> derbydb and mysql).
>>>>>>>
>>>>>>>
>>>>>>> kind regards
>>>>>>>
>>>>>>> frank
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>>>> For additional commands, e-mail:
>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Jetspeed 2.2: mssql database maven configuration
Posted by Ate Douma <at...@douma.nu>.
Ate Douma wrote:
> Frank Otto wrote:
>> Hi Ate,
>>
>> now, I have a working mssql script. But how do I integrate it in my
>> custom portal building? I want to test it.
>
> Hi Frank,
>
> Assuming you're using a custom portal project generated using the
> archetype there are several ways how you can do that.
> I'm providing one solution below.
>
> As an example I'll use an artifactId "MyPortal", you'll have to adjust
> for your own chosen artifactId of course.
>
> The generated MyPortal/MyPortal-portal/jetspeed-mvn-portal.xml custom
> maven project file is handling the mvn jetspeed:mvn -Dtarget=db
> execution which will create the database schema and seeding it.
> The "db" profile within this file contains several plugin executions to
> do so: <id>unpack</id>,<id>execute-sql</id> and <id>seed</id>.
>
> If you make the following changes:
>
> 1) store your custom create-schema.sql and drop-schema.sql files under
> new folder:
> MyPortal/MyPortal-portal/src/sql/ddl/mssql
> 2) comment out the whole <execution><id>unpack<id>...</execution>
> section in the "db" profile (optional, but you don't need it)
> 3) in the <execution><id>execute-sql</id>...</execution> section change
> the two <path> elements pointing to the drop-schema.sql
> and create-schema.sql by replacing the first part:
> <path>${project.build.directory}/ddl/ [...]</path>
> with:
> <path>${basedir}/sql/ddl/ [...]</path>
Sorry, I made a typo in the example above, of course it should be:
<path>${basedir}/src/sql/ddl/ [...]</path>
instead of
<path>${basedir}/sql/ddl/ [...]</path>
>
> you should be able to run mvn jetspeed-mvn -Dtarget=db which will then
> use your custom sql instead.
>
> Regards,
>
> Ate
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Jetspeed 2.2: mssql database maven configuration
Posted by Ate Douma <at...@douma.nu>.
Frank Otto wrote:
> Hi Ate,
>
> now, I have a working mssql script. But how do I integrate it in my
> custom portal building? I want to test it.
Hi Frank,
Assuming you're using a custom portal project generated using the archetype there are several ways how you can do that.
I'm providing one solution below.
As an example I'll use an artifactId "MyPortal", you'll have to adjust for your own chosen artifactId of course.
The generated MyPortal/MyPortal-portal/jetspeed-mvn-portal.xml custom maven project file is handling the mvn jetspeed:mvn -Dtarget=db
execution which will create the database schema and seeding it.
The "db" profile within this file contains several plugin executions to do so: <id>unpack</id>,<id>execute-sql</id> and <id>seed</id>.
If you make the following changes:
1) store your custom create-schema.sql and drop-schema.sql files under new folder:
MyPortal/MyPortal-portal/src/sql/ddl/mssql
2) comment out the whole <execution><id>unpack<id>...</execution> section in the "db" profile (optional, but you don't need it)
3) in the <execution><id>execute-sql</id>...</execution> section change the two <path> elements pointing to the drop-schema.sql
and create-schema.sql by replacing the first part:
<path>${project.build.directory}/ddl/ [...]</path>
with:
<path>${basedir}/sql/ddl/ [...]</path>
you should be able to run mvn jetspeed-mvn -Dtarget=db which will then use your custom sql instead.
Regards,
Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Jetspeed 2.2: mssql database maven configuration
Posted by Frank Otto <ot...@delta-barth.de>.
Hi Ate,
now, I have a working mssql script. But how do I integrate it in my
custom portal building? I want to test it.
kind regards,
Frank
Ate Douma schrieb:
> Frank Otto wrote:
>> I have created a new JIRA issue -->
>> https://issues.apache.org/jira/browse/JS2-1024
>>
>> Now, how can I apply a patch to my maven build and after this to
>> jetspeed 2 repository?
>>
>> This is the first JIRA issue for me.
>
> Hi Frank,
>
> As you (and/or your team) probably are more experienced with mssql than
> most of us, I suggest proceeding as I described before.
> Compare the manually written mssql/create-schema.sql script against a
> generated one, PostgreSQL/Derby/MySql/Oracle etc. and determine the
> parts missing or (now) incorrect.
> Then try to convert those missing parts in a format suitable for mssql
> and test it out.
> Once you've got everything working again, you can attach a resulting new
> mssql/create-schema.sql file to this JIRA issue and I can help out
> creating a patch file based upon that (or just provide a diff file
> against the original).
> Once we've checked and confirmed the changes are complete and valid, I
> can check it in against the jetspeed-2 svn repository.
>
> Regards,
>
> Ate
>
>>
>> Ate Douma schrieb:
>>> Frank Otto wrote:
>>>> hi,
>>>>
>>>> thanks for your answer. We need MSSQL2000/2005/2008 and in jetspeed
>>>> 2.1.3 it works correctly.
>>>>
>>>> The connectin is now ok, but I get following error:
>>>>
>>>> org.apache.jetspeed.serializer.SerializerException: Creating an
>>>> instance from a
>>>> serialized representation of SecurityDomains failed with message
>>>> Could not creat
>>>> e default and / or system domains!
>>>> OJB operation; bad SQL grammar []; nested exception is
>>>> java.sql.SQLException: Un
>>>> g³ltiger Objektname 'SECURITY_DOMAIN'.
>>>> at
>>>> org.apache.jetspeed.serializer.JetspeedSecuritySerializer.recreateSec
>>>> urityDomains(JetspeedSecuritySerializer.java:256)
>>>
>>> Yeah, I already expected something like that.
>>> The hand written mssql create-schema.sql seems to be not in sync with
>>> the generated sql scripts.
>>>
>>> I suggest comparing the mssql script with a generate one like one for
>>> Oracle/MySql/PostgreSQL etc. and try to create a patch for mssql
>>> based on that.
>>>
>>> All the sql scripts are contained within the
>>> jetspeed-portal-resources-2.20.jar under folder /ddl (including the
>>> one for mssql):
>>>
>>> http://repo2.maven.org/maven2/org/apache/portals/jetspeed-2/jetspeed-portal-resources/2.2.0/jetspeed-portal-resources-2.2.0.jar
>>>
>>>
>>> I suggest creating a new JIRA issue for this (fix version: 2.2.1) so
>>> you can apply a patch there too.
>>>
>>> Regards,
>>>
>>> Ate
>>>
>>>>
>>>>
>>>>
>>>> kind regards,
>>>>
>>>> Frank
>>>>
>>>>
>>>> Ate Douma schrieb:
>>>>> Frank Otto wrote:
>>>>>> Thanks, but I have no artifact properties for mssql jdbc driver.
>>>>>>
>>>>>> The property "org.apache.jetspeed.production.jdbc.drivers.path"
>>>>>> doesn't work.
>>>>> That property is no longer used for Jetspeed 2.2.0
>>>>> Please use the instructions as described here:
>>>>>
>>>>> http://portals.apache.org/jetspeed-2/buildguide/maven-2-build.html
>>>>>
>>>>> An example mssql configuration I've used myself (quite) sometime
>>>>> ago which worked for an earlier build of Jetspeed-2.2-SNAPSHOT
>>>>> would be the following:
>>>>>
>>>>>
>>>>> <org.apache.jetspeed.production.database.default.name>mssql</org.apachejetspeed.production.database.default.name>
>>>>>
>>>>>
>>>>> <org.apache.jetspeed.production.jdbc.driver.groupId>net.sourceforge.jtds</org.apache.jetspeed.production.jdbc.driver.groupId>
>>>>>
>>>>>
>>>>> <org.apache.jetspeed.production.jdbc.driver.artifactId>jtds</org.apachejetspeed.production.jdbc.driver.artifactId>
>>>>>
>>>>>
>>>>> <org.apache.jetspeed.production.jdbc.driver.version>1.2.2</org.apachejetspeed.production.jdbc.driver.version>
>>>>>
>>>>>
>>>>> <org.apache.jetspeed.production.database.driver>net.sourceforge.jtds.jdbc.Driver</org.apache.jetspeed.production.database.driver>
>>>>>
>>>>> <org.apache.jetspeed.production.database.url>
>>>>>
>>>>> <![CDATA[jdbc:jtds:sqlserver://localhost:1433/j2;socketTimeout=150]]>
>>>>> </org.apache.jetspeed.production.database.url>
>>>>>
>>>>> <org.apache.jetspeed.production.database.user>j2</org.apache.jetspeedproduction.database.user>
>>>>>
>>>>>
>>>>> <org.apache.jetspeed.production.database.password>j2</org.apache.jetspeed.production.database.password>
>>>>>
>>>>>
>>>>> Be aware though that AFAIK the mssql support in the current 2.2.0
>>>>> released version might not be up to par with the other databases.
>>>>>
>>>>> The problem with mssql is that it requires manual definition of its
>>>>> database schema. Its so much different and lacking in certain areas
>>>>> of standard SQL support that automatically generating the schema
>>>>> like we do for all other databases just isn't doable.
>>>>> We do have some handling for that, overriding the schema generation
>>>>> with hand written mssql scripts, but AFAIK those might not be fully
>>>>> updated yet with some recent model changes.
>>>>> FYI, these mssql scripts are defined here (and applied during
>>>>> database creation):
>>>>>
>>>>> http://svn.apache.org/repos/asf/portals/jetspeed-2/portal/trunk/jetspeed-portal-resources/src/main/resources/ddl/mssql
>>>>>
>>>>>
>>>>> As none of the jetspeed committers has clients using mssql anymore
>>>>> (either moved to more standard databases or elsewhere),
>>>>> the priority to keep supporting mssql has dwindled a bit.
>>>>> That doesn't mean we don't want or will keep supporting mssql, but
>>>>> for that we have to rely on the community to support us with error
>>>>> reports andpatches.
>>>>>
>>>>> The above configuration is know to work if you check out the
>>>>>
>>>>> http://svn.apache.org/repos/asf/portals/jetspeed-2/portal/branches/JETSPEED-2.2-PRE-PLUTO-2-SNAPSHOT
>>>>>
>>>>> branch, but using that branch really is not advisable.
>>>>>
>>>>> If you really need to use mssql, I advise just trying the above
>>>>> configuration out and see if/where it breaks.
>>>>> From there, you can try to determine the changes needed (like
>>>>> comparing it against the generated schema scripts for other databases)
>>>>> and we'll be happy to help out applying patches and fixes.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Ate
>>>>>
>>>>>>
>>>>>> The maven build doesn't find the jdbc driver.
>>>>>>
>>>>>> Vivek Kumar schrieb:
>>>>>>> See this
>>>>>>>
>>>>>>> http://portals.apache.org/jetspeed-2/buildguide/maven-2-build.html
>>>>>>>
>>>>>>> Vivek
>>>>>>>
>>>>>>> Frank Otto wrote:
>>>>>>>> how are the settings for mssql database in jetspeed2.2?
>>>>>>>>
>>>>>>>> I find no informations on jetspeed2.2 documentation (only for
>>>>>>>> derbydb and mysql).
>>>>>>>>
>>>>>>>>
>>>>>>>> kind regards
>>>>>>>>
>>>>>>>> frank
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail:
>>>>>>>> jetspeed-user-unsubscribe@portals.apache.org
>>>>>>>> For additional commands, e-mail:
>>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>>
>>>>>>>> Delivered-To: firevelocity@gmail.com
>>>>>>>> Received: by 10.239.145.203 with SMTP id t11cs510731hba;
>>>>>>>> Fri, 29 May 2009 02:10:40 -0700 (PDT)
>>>>>>>> Received: by 10.114.192.17 with SMTP id
>>>>>>>> p17mr3544424waf.196.12435882393 <http://www.snapanumber.com/>52;
>>>>>>>> Fri, 29 May 2009 02:10:39 -0700 (PDT)
>>>>>>>> Return-Path:
>>>>>>>> <je...@portals.apache.org>
>>>>>>>>
>>>>>>>> Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
>>>>>>>> by mx.google.com with SMTP id
>>>>>>>> 26si1159924pxi.115.2009.05.29.02.10.38;
>>>>>>>> Fri, 29 May 2009 02:10:39 -0700 (PDT)
>>>>>>>> Received-SPF: pass (google.com: domain of
>>>>>>>> jetspeed-user-return-26685-firevelocity=gmail.com@portals.apacheorg
>>>>>>>> designates 140.211.11.3 as permitted sender)
>>>>>>>> client-ip=140.211.11.3;
>>>>>>>> Authentication-Results: mx.google.com; spf=pass (google.com:
>>>>>>>> domain of
>>>>>>>> jetspeed-user-return-26685-firevelocity=gmail.com@portals.apacheorg
>>>>>>>> designates 140.211.11.3 as permitted sender)
>>>>>>>> smtp.mail=jetspeed-user-return-26685-firevelocity=gmail.com@portals.apache.org
>>>>>>>>
>>>>>>>> Received: (qmail 81426 invoked by uid 500); 29 May 2009 09:10:37
>>>>>>>> -0000
>>>>>>>> Mailing-List: contact jetspeed-user-help@portals.apache.org; run
>>>>>>>> by ezmlm
>>>>>>>> Precedence: bulk
>>>>>>>> List-Help: <ma...@portals.apache.org>
>>>>>>>> List-Unsubscribe:
>>>>>>>> <ma...@portals.apache.org>
>>>>>>>> List-Post: <ma...@portals.apache.org>
>>>>>>>> List-Id: <jetspeed-user.portals.apache.org>
>>>>>>>> Reply-To: "Jetspeed Users List" <je...@portals.apache.org>
>>>>>>>> Delivered-To: mailing list jetspeed-user@portals.apache.org
>>>>>>>> Received: (qmail 81416 invoked by uid 99); 29 May 2009 09:10:37
>>>>>>>> -0000
>>>>>>>> Received: from athena.apache.org (HELO athena.apache.org)
>>>>>>>> (140.211.11.136)
>>>>>>>> by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009
>>>>>>>> 09:10:37 +0000
>>>>>>>> X-ASF-Spam-Status: No, hits=-0.0 required=10.0
>>>>>>>> tests=SPF_PASS
>>>>>>>> X-Spam-Check-By: apache.org
>>>>>>>> Received-SPF: pass (athena.apache.org: domain of
>>>>>>>> otto@delta-barth.de designates 80.243.61.50 as permitted sender)
>>>>>>>> Received: from [80.243.61.50] (HELO po.depag.de) (80.243.61.50)
>>>>>>>> by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009
>>>>>>>> 09:10:29 +0000
>>>>>>>> Received: from localhost (unknown [127.0.0.1])
>>>>>>>> by po.depag.de (Postfix) with ESMTP id 400958D110
>>>>>>>> for <je...@portals.apache.org>; Fri, 29 May 2009
>>>>>>>> 11:13:30 +0200 (CEST)
>>>>>>>> Received: from tati.lr3.depag.de (tati.lr3.depag.de [10.1.0.22])
>>>>>>>> by po.depag.de (Postfix) with ESMTP id 74CE88D104
>>>>>>>> for <je...@portals.apache.org>; Fri, 29 May 2009
>>>>>>>> 11:13:28 +0200 (CEST)
>>>>>>>> Received: from [10.1.21.120] (unknown [10.1.21.120])
>>>>>>>> by tati.lr3.depag.de (Postfix) with ESMTP id 0BD6E8D84
>>>>>>>> for <je...@portals.apache.org>; Fri, 29 May 2009
>>>>>>>> 11:10:06 +0200 (CEST)
>>>>>>>> Message-ID: <4A...@delta-barth.de>
>>>>>>>> Date: Fri, 29 May 2009 11:10:05 +0200
>>>>>>>> From: Frank Otto <ot...@delta-barth.de>
>>>>>>>> User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
>>>>>>>> MIME-Version: 1.0
>>>>>>>> To: Jetspeed Users List <je...@portals.apache.org>
>>>>>>>> Subject: Jetspeed 2.2: mssql database maven configuration
>>>>>>>> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>>>>>>>> Content-Transfer-Encoding: 7bit
>>>>>>>> X-Virus-Scanned: by AMaViS perl-11
>>>>>>>> X-Virus-Checked: Checked by ClamAV on apache.org
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> how are the settings for mssql database in jetspeed2.2?
>>>>>>>>
>>>>>>>> I find no informations on jetspeed2.2 documentation (only for
>>>>>>>> derbydb and mysql).
>>>>>>>>
>>>>>>>>
>>>>>>>> kind regards
>>>>>>>>
>>>>>>>> frank
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail:
>>>>>>>> jetspeed-user-unsubscribe@portals.apache.org
>>>>>>>> For additional commands, e-mail:
>>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>>> For additional commands, e-mail:
>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org