headers
Andrea K. | 1 Feb 2007 09:38
Picon
Favicon

Versioning


Hi all,
a question about versioning system. 
It can be used in this way? I explain:

- save a versionable node with a base version and label it as public
- save a second version labelling it stage
- save a third version labelling it draft

I can direct access a version to retrieve and modify its properties?

I want to use it as a very simple workflow.

Any idea, suggestion or patterns to follow to implement a simple workflow
over nodes?

Thanks in advance.
Bye, Andrea.
--

-- 
View this message in context: http://www.nabble.com/Versioning-tf3153610.html#a8744732
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Permalink | Reply | 5 comments |
headers
Andrea K. | 1 Feb 2007 09:57
Picon
Favicon

Binary Search


Hi,
what is the right way to save binary data (documents, etc..) in a node (es:
setproperty("document", ...Stream..)) and integrate it in the fulltext
search? It can be used in this way or fulltext search is working only on
standalone nt:resources?

thanks again.

Andrea.
--

-- 
View this message in context: http://www.nabble.com/Binary-Search-tf3153666.html#a8744925
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Permalink | Reply | 1 comment |
headers
Java Prog | 1 Feb 2007 10:07
Picon

Re: java.lang.OutOfMemoryError: Java heap space

I have managed to put more than 100mb file to Jackrabbit (remotely) -
with default memory configuration. I have use Derby Db, and Derby
persistence manager. It took some time but  worked (however, other
work was impossible due to single connection to th database).

Can you specify your configuration, and put slightly more line of stacktrace?

On 1/31/07, Michal Hybler <m.hybler <at> email.cz> wrote:
>
> I have tried to send 10Mb file to jackrabbit repository and this exception
> has been thrown
>
> org.apache.jackrabbit.rmi.client.RemoteRepositoryException: Error occurred
> in server thread; nested exception is:
>         java.lang.OutOfMemoryError: Java heap space: Error occurred in server
> thread; nested exception is:
>         java.lang.OutOfMemoryError: Java heap space
>         ........
> If I tried it with smaller file(about 5 Mb) it was working good.
>
> I have tried to set JVM memory greater (512Mb) by command "java -Xmx512Mb"
> but nothing changed.
> Does someone have experiences with it?
> Thanks for help
> Michal Hybler
> --
> View this message in context: http://www.nabble.com/java.lang.OutOfMemoryError%3A-Java-heap-space-tf3147963.html#a8726755
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>
(Continue reading)

Permalink | Reply | 10 comments |
headers
Tobias Bocanegra | 1 Feb 2007 10:40
Favicon
Gravatar

Re: java.lang.OutOfMemoryError: Java heap space

> I have tried to set JVM memory greater (512Mb) by command "java -Xmx512Mb"

maybe because the syntax is wrong: it's just -Xmx512m  (not Mb).
regards, toby

On 1/31/07, Michal Hybler <m.hybler <at> email.cz> wrote:
>
> I have tried to send 10Mb file to jackrabbit repository and this exception
> has been thrown
>
> org.apache.jackrabbit.rmi.client.RemoteRepositoryException: Error occurred
> in server thread; nested exception is:
>         java.lang.OutOfMemoryError: Java heap space: Error occurred in server
> thread; nested exception is:
>         java.lang.OutOfMemoryError: Java heap space
>         ........
> If I tried it with smaller file(about 5 Mb) it was working good.
>
> I have tried to set JVM memory greater (512Mb) by command "java -Xmx512Mb"
> but nothing changed.
> Does someone have experiences with it?
> Thanks for help
> Michal Hybler
> --
> View this message in context: http://www.nabble.com/java.lang.OutOfMemoryError%3A-Java-heap-space-tf3147963.html#a8726755
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tobias Bocanegra | 1 Feb 2007 10:41
Favicon
Gravatar

Re: Versioning

no, once a version is created it's immutable.
usually you create different workspaces for this.

regards, toby

On 2/1/07, Andrea K. <akregar <at> alteanet.it> wrote:
>
> Hi all,
> a question about versioning system.
> It can be used in this way? I explain:
>
> - save a versionable node with a base version and label it as public
> - save a second version labelling it stage
> - save a third version labelling it draft
>
> I can direct access a version to retrieve and modify its properties?
>
> I want to use it as a very simple workflow.
>
> Any idea, suggestion or patterns to follow to implement a simple workflow
> over nodes?
>
> Thanks in advance.
> Bye, Andrea.
> --
> View this message in context: http://www.nabble.com/Versioning-tf3153610.html#a8744732
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Robert Gacki | 1 Feb 2007 10:46
Picon

AW: java.lang.OutOfMemoryError: Java heap space

He has a typo in his java arguments:
"java -Xmx512Mb" -> the "Mb" is wrong.

Michal, try "java -Xmx512m -Xms512m" instead.

-----Ursprüngliche Nachricht-----
Von: Java Prog [mailto:javaprimer <at> gmail.com] 
Gesendet: Donnerstag, 1. Februar 2007 10:08
An: users <at> jackrabbit.apache.org
Betreff: Re: java.lang.OutOfMemoryError: Java heap space

I have managed to put more than 100mb file to Jackrabbit (remotely) -
with default memory configuration. I have use Derby Db, and Derby
persistence manager. It took some time but  worked (however, other
work was impossible due to single connection to th database).

Can you specify your configuration, and put slightly more line of
stacktrace?

On 1/31/07, Michal Hybler <m.hybler <at> email.cz> wrote:
>
> I have tried to send 10Mb file to jackrabbit repository and this exception
> has been thrown
>
> org.apache.jackrabbit.rmi.client.RemoteRepositoryException: Error occurred
> in server thread; nested exception is:
>         java.lang.OutOfMemoryError: Java heap space: Error occurred in
server
> thread; nested exception is:
>         java.lang.OutOfMemoryError: Java heap space
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrea K. | 1 Feb 2007 11:05
Picon
Favicon

Re: Versioning


If I delete the old 'draft' version from history and save a new version
labelled 'draft' with new data? 
The idea is to have 3 versions in the history of a specific node.
Can I do this? 

thanks.

Tobias Bocanegra wrote:
> 
> no, once a version is created it's immutable.
> usually you create different workspaces for this.
> 
> regards, toby
> 
> On 2/1/07, Andrea K. <akregar <at> alteanet.it> wrote:
>>
>> Hi all,
>> a question about versioning system.
>> It can be used in this way? I explain:
>>
>> - save a versionable node with a base version and label it as public
>> - save a second version labelling it stage
>> - save a third version labelling it draft
>>
>> I can direct access a version to retrieve and modify its properties?
>>
>> I want to use it as a very simple workflow.
>>
>> Any idea, suggestion or patterns to follow to implement a simple workflow
(Continue reading)

Permalink | Reply | 3 comments |
headers
Tobias Bocanegra | 1 Feb 2007 11:11
Favicon
Gravatar

Re: Versioning

but then you can concurrently edit on the 'working nodes'.
the best is to create 3 workspaces 'public', 'draft', 'stage'. and if
you want to promote a change, just update the node in the respective
workspace.

regards, toby

On 2/1/07, Andrea K. <akregar <at> alteanet.it> wrote:
>
> If I delete the old 'draft' version from history and save a new version
> labelled 'draft' with new data?
> The idea is to have 3 versions in the history of a specific node.
> Can I do this?
>
> thanks.
>
>
> Tobias Bocanegra wrote:
> >
> > no, once a version is created it's immutable.
> > usually you create different workspaces for this.
> >
> > regards, toby
> >
> > On 2/1/07, Andrea K. <akregar <at> alteanet.it> wrote:
> >>
> >> Hi all,
> >> a question about versioning system.
> >> It can be used in this way? I explain:
> >>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Andrea K. | 1 Feb 2007 11:24
Picon
Favicon

Re: Versioning


so, basically, what is the best way to do this in a single workspace?

thanks.

Tobias Bocanegra wrote:
> 
> but then you can concurrently edit on the 'working nodes'.
> the best is to create 3 workspaces 'public', 'draft', 'stage'. and if
> you want to promote a change, just update the node in the respective
> workspace.
> 
> regards, toby
> 
> On 2/1/07, Andrea K. <akregar <at> alteanet.it> wrote:
>>
>> If I delete the old 'draft' version from history and save a new version
>> labelled 'draft' with new data?
>> The idea is to have 3 versions in the history of a specific node.
>> Can I do this?
>>
>> thanks.
>>
>>
>> Tobias Bocanegra wrote:
>> >
>> > no, once a version is created it's immutable.
>> > usually you create different workspaces for this.
>> >
>> > regards, toby
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Nuescheler | 1 Feb 2007 11:55
Picon

Re: Versioning

hi andrea,

> so, basically, what is the best way to do this in a single workspace?
this is exactly what workspaces are designed for.
so the single best way to do what you would like to achieve in a content
repository is to have multiple workspaces "draft", "stage" and "public".

there is no good way to do that with a single workspace since you would
be emulating functionality provided by the repository in your own application
code. there are numerous bad ways though, to simulate your usecase in a single
workspace.

is there an issue with using multiple workspaces?

<not-entirely-serious>
to me this conversation sounds similar to:
Q: I want to have multiple updates to a relational database table
committed in an atomic fashion, how do i do that?
A: Use the built-in transactions!
Q: ...but how do i do it without transactions?
A: why would you?
</not-entirely-serious>

regards,
david
Permalink | Reply | 0 comments |

Gmane