You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Kevin Sutter <kw...@gmail.com> on 2006/09/13 18:18:49 UTC
Status of LockGroups...
Hi,
Are LockGroups supported by OpenJPA? The manual still describes their usage
and I have found a message that indicates an upgrade to "enterprise edition"
is required to use LockGroups... :-)
lock-group-requires-perf-pack: Field "{0}" declares the lock-group
extension. \
In order to use custom lock groups, you must have a performance pack or
\
enterprise edition license. Contact sales@bea.com for details on \
upgrading your license.
But, I have found no code references to indicate that they exist. The
functionality sounds helpful. Was this function accidentally forgotten?
And, it seems that this missing LockGroup function may have ripple effects
to other functions, such as multiple version column mapping:
bad-col-lg-counts: Cannot synchronize mapping information: the number of \
version columns is not equal to the number of lock groups.
I don't see this message id (bad-col-lg-counts) used anywhere, so maybe this
"restriction" is no longer in place?
Thanks,
Kevin
Re: Status of LockGroups...
Posted by Kevin Sutter <kw...@gmail.com>.
Okay, guys, the manual looks good. As Marc pointed out, the network
activity for downloading the dependencies is horendous. Looking back at my
logs for the site build, I was having problems getting all of the necessary
dependencies before timeouts were expiring. I just did an [mvn clean
install site] and it all worked as expected. Thanks.
Kevin
On 9/13/06, Abe White <aw...@bea.com> wrote:
>
> > "mvn site" should build the docbook files, although it is a tad
> > slow and untested (and network-intensive, since it dynamically
> > downloads all the stylesheets).
>
>
> you have to run "mvn install" first.
> >>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
> _______________________________________________________________________
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
>
Re: Status of LockGroups...
Posted by Abe White <aw...@bea.com>.
> "mvn site" should build the docbook files, although it is a tad
> slow and untested (and network-intensive, since it dynamically
> downloads all the stylesheets).
you have to run "mvn install" first.
>>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Re: Status of LockGroups...
Posted by Marc Prud'hommeaux <mp...@apache.org>.
"mvn site" should build the docbook files, although it is a tad slow
and untested (and network-intensive, since it dynamically downloads
all the stylesheets).
On Sep 13, 2006, at 1:36 PM, Kevin Sutter wrote:
> Changes are done and committed. Updated the messages, docs, and
> code to
> remove references to LockGroups. I had some general problems with
> generating the manual. How does one go about generating our manuals?
>
> On 9/13/06, Abe White <aw...@bea.com> wrote:
>>
>> > I can do the changes, if there's no chance that these LockGroups
>> > will be
>> > included in the OpenJPA drop... :-(
>>
>> No chance.
>>
>> >>Register now for BEA World 2006 --- See http://www.bea.com/
>> beaworld<<
>> _____________________________________________________________________
>> __
>> Notice: This email message, together with any attachments, may
>> contain
>> information of BEA Systems, Inc., its subsidiaries and
>> affiliated
>> entities, that may be confidential, proprietary, copyrighted
>> and/or
>> legally privileged, and is intended solely for the use of the
>> individual
>> or entity named in this message. If you are not the intended
>> recipient,
>> and have received this message in error, please immediately return
>> this
>> by email and then delete it.
>>
Re: Status of LockGroups...
Posted by Kevin Sutter <kw...@gmail.com>.
Changes are done and committed. Updated the messages, docs, and code to
remove references to LockGroups. I had some general problems with
generating the manual. How does one go about generating our manuals?
On 9/13/06, Abe White <aw...@bea.com> wrote:
>
> > I can do the changes, if there's no chance that these LockGroups
> > will be
> > included in the OpenJPA drop... :-(
>
> No chance.
>
> >>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
> _______________________________________________________________________
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
>
Re: Status of LockGroups...
Posted by Abe White <aw...@bea.com>.
> I can do the changes, if there's no chance that these LockGroups
> will be
> included in the OpenJPA drop... :-(
No chance.
>>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Re: Status of LockGroups...
Posted by Kevin Sutter <kw...@gmail.com>.
I can do the changes, if there's no chance that these LockGroups will be
included in the OpenJPA drop... :-(
Kevin
On 9/13/06, Abe White <aw...@bea.com> wrote:
>
>
> > Are LockGroups supported by OpenJPA?
>
> They are not. Can you remove the bad doc and unused localization
> messages you found?
> >>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
> _______________________________________________________________________
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
>
Re: Status of LockGroups...
Posted by Abe White <aw...@bea.com>.
> Are LockGroups supported by OpenJPA?
They are not. Can you remove the bad doc and unused localization
messages you found?
>>Register now for BEA World 2006 --- See http://www.bea.com/beaworld<<
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.