You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by Murray Altheim <mu...@altheim.com> on 2007/10/23 05:35:03 UTC

Issues register for JSPWiki metadata support?

Janne,

Just wondering, since you seem to have alluded to potential planning
for upcoming support for WikiPage metadata in future versions of
JSPWiki, if you have any existing requirements or designs that you'd
be willing to share, or if there's an existing place where we might
lodge what might be requirements on metadata functionality?

As an example, the current page attributes are delivered as a Java
Map. Because Maps uses unique keys this would eliminate the ability
to be able to store properties that have the same name. With Dublin
Core metadata there's generally (in common usage) the idea that
there may be multiple DC.creator entries for an given resources (e.g.,
documents written by more than one author), and certainly more than
one DC.contributor (when there are multiple contributors, which
would certainly be the case with wiki pages). The limitation of Map
is currently stinging me...

If there's a place (perhaps a page on JSPWiki, or a document somewhere)
where we might begin to put together a set of requirements, this might
help when the design starts getting fleshed out.

Thanks,

Murray

...........................................................................
Murray Altheim <murray07 at altheim.com>                           ===  = =
http://www.altheim.com/murray/                                     = =  ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk               = =  = =

       Boundless wind and moon - the eye within eyes,
       Inexhaustible heaven and earth - the light beyond light,
       The willow dark, the flower bright - ten thousand houses,
       Knock at any door - there's one who will respond.
                                       -- The Blue Cliff Record

Re: Issues register for JSPWiki metadata support?

Posted by Janne Jalkanen <ja...@iki.fi>.
> Apache-commons is also one of two implementations that Stripes uses,  
> so that's good too from a future-proofing standpoint. When we get to  
> JSPWiki 3, there won't be a need to even code to Apache-commons  
> directly -- the file attachment will "appear" in your form's  
> ActionBean as a FileBean.

Except that we'll want to keep the upload progress bar, so we'll need
to hook into the update mechanism of Fileupload... Which I don't think
Stripes enables directly.

/Janne

Re: Issues register for JSPWiki metadata support?

Posted by Andrew Jaquith <an...@mac.com>.
Apache-commons is also one of two implementations that Stripes uses,  
so that's good too from a future-proofing standpoint. When we get to  
JSPWiki 3, there won't be a need to even code to Apache-commons  
directly -- the file attachment will "appear" in your form's  
ActionBean as a FileBean.

But I digress. Thumbs up on the Apache library.

On Oct 24, 2007, at 2:02 AM, Janne Jalkanen <Ja...@ecyrd.com>  
wrote:

>> we could also replace non APL compatible libraries  
>> (multipartrequest and
>> jwebunit) with compatible ones.
>
> I think it's a question of must, not could :-).
>
> Multipartrequest is easy, we can just use apache commons  
> fileupload.  It doesn't come with a ton of dependencies anymore  
> (which was the reason why we originally chose the multipartrequest).
>
>> I was going to begin with jmeter equivalent
>> tests of jwebunit but I've encoutered several problems last weeks  
>> (going to
>> barcelona, computer died, etc).
>
> I can see that going to barcelona would be a problem ;-).  I'm btw  
> going to be in Bilbao on the 14th. if anybody wants to meet up.   
> I'll also be in Hamburg on 12-13th.
>
> /Janne

Re: Issues register for JSPWiki metadata support?

Posted by Janne Jalkanen <Ja...@ecyrd.com>.
> we could also replace non APL compatible libraries  
> (multipartrequest and
> jwebunit) with compatible ones.

I think it's a question of must, not could :-).

Multipartrequest is easy, we can just use apache commons fileupload.   
It doesn't come with a ton of dependencies anymore (which was the  
reason why we originally chose the multipartrequest).

> I was going to begin with jmeter equivalent
> tests of jwebunit but I've encoutered several problems last weeks  
> (going to
> barcelona, computer died, etc).

I can see that going to barcelona would be a problem ;-).  I'm btw  
going to be in Bilbao on the 14th. if anybody wants to meet up.  I'll  
also be in Hamburg on 12-13th.

/Janne

Re: Issues register for JSPWiki metadata support?

Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Hi!

we could also replace non APL compatible libraries (multipartrequest and
jwebunit) with compatible ones. I was going to begin with jmeter equivalent
tests of jwebunit but I've encoutered several problems last weeks (going to
barcelona, computer died, etc).

Regards,
JP

2007/10/23, Janne Jalkanen <ja...@iki.fi>:
>
>
> The plan currently is to release 2.8, which is essentially a 2.6 with
> labels changed to Apache (and minor bugfixes), and then land your
> Stripes stuff in the trunk as a basis for 3.0 work.
>
> The question is, do you all think this plan is still valid?
>
> /Janne
>

Re: Issues register for JSPWiki metadata support?

Posted by Janne Jalkanen <ja...@iki.fi>.
> Janne - I haven't had as much time as I'd like to work ok JSPWiki  
> lately, but when I am able to pop up for air, where should I commit my  
> Stripes build? Pretty much all of the core class work is done,  
> although the front-end classes (ActionBeans and JSPs) need work.

There's an ARJ_BRANCH on cvs.jspwiki.org, just waiting for you :-)

One option would of course be to put it on svn.apache.org, but I fear
that that might create a lot of confusion with would-be developers.

The plan currently is to release 2.8, which is essentially a 2.6 with
labels changed to Apache (and minor bugfixes), and then land your
Stripes stuff in the trunk as a basis for 3.0 work.

The question is, do you all think this plan is still valid?

/Janne

Re: Issues register for JSPWiki metadata support?

Posted by Andrew Jaquith <an...@mac.com>.
Janne - I haven't had as much time as I'd like to work ok JSPWiki  
lately, but when I am able to pop up for air, where should I commit my  
Stripes build? Pretty much all of the core class work is done,  
although the front-end classes (ActionBeans and JSPs) need work.

On Oct 23, 2007, at 4:39 AM, Janne Jalkanen <ja...@iki.fi>  
wrote:

>> I completely agree, but we also need a lower-level API that the  
>> higher-
>> level (JSP-170 level) API is a subset of, a simple API for file  
>> system
>> providers and for implementations that simply don't need the  
>> complexity
>> of JSR-170 (either from an installation, implementation or footprint
>> standpoint), a simple API that still has metadata support. Not sure  
>> how
>> to do that, but it IMO probably should be a requirement unless we're
>> going to let JSPWiki become a heavyweight-only application. I kinda  
>> like
>> the ability to just use a simple file system provider sometimes  
>> (and in
>> fact, ended up adding a file backend my XNodeStore a long time after
>> implementing a Xindice, Exist, and finally BerkeleyDB DB backends).  
>> Also,
>> for a lot of ISPs (mine, forinstance), it may be difficult to  
>> manage a
>> DB-based backend, even completely embedded. I like being able to  
>> simply
>> copy that 'pages' directory between version upgrades.
>
> These are two different things.  JSR-170 is the API that should be
> visible to the rest of JSPWiki.  Of course, the API should be
> pluggable, that is, you can put in Jackrabbit or what-have-you as the
> JCR implementation.
>
> Jackrabbit will happily use also file storage, or you can even use
> something like HSQLDB, which stores all data as files, making managing
> them very easy.
>
> However, having said that, I do also see a need for something simple
> to ship with our product.  Jackrabbit is a full-featured JSR-170
> implementation with all the possible bells and whistles (of which we
> don't need most), and it's pretty big and needs external libraries as
> well.  The file storage is also rather obscure, so direct file
> management the way that people are currently doing would be a bit
> complicated.
>
> Therefore, I started a small JSR-170 -implementation project called
> "Priha".  It's not meant to be JSR-170 -compliant, but should fulfil
> all of our use cases, while retaining a very simple-to-use provider
> SPI, similar to the current JSPWiki PageProvider.  It also needs few
> external libraries (it tries to use Java 5 built-in stuff as much as
> possible), and is pretty fast.  I thought it would be cool to ship it
> as part of JSPWiki 3, and provide some nice migration path.  Then the
> people who need serious enterprise grade performance can use something
> else, and people who are happy with just a simple implementation can
> use whatever is built-in.
>
> It already works to quite a large degree.  If you want to start
> hacking away at it, you can check it out from cvs.jspwiki.org under
> the module name "Priha".  At this stage I'd be happy to get some
> co-contributors on it :-)
>
> (By the way, in a completely unrelated matter, Java 5 + Hibernate +
> Stripes is a very cool combo.  Using Stripes would make JSPWiki a
> *lot* simpler in the future.)
>
> /Janne

Re: Issues register for JSPWiki metadata support?

Posted by Murray Altheim <mu...@altheim.com>.
Janne Jalkanen wrote:
>> I would be happy to take a look, and potentially work on it as well,
>> but for some reason I'm not currently able to get CVS to work, not
>> sure if it's my end or the CVS server is down. I'll try again tomorrow
>> from work.
> 
> It should be working, but just in case, I kicked the cvsd...

No change at my end, but it's likely me. I just upgraded to Ubuntu
Gutsy Gibbon (now there's a mouthful) and my laptop started freezing
unpredictably, so I've gone back to Fiesty Fawn. In all the confusion
I think my CVS installation got busted. I'll have to tackle this
tomorrow... but I *am* interested.

Murray

...........................................................................
Murray Altheim <murray07 at altheim.com>                           ===  = =
http://www.altheim.com/murray/                                     = =  ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk               = =  = =

       Boundless wind and moon - the eye within eyes,
       Inexhaustible heaven and earth - the light beyond light,
       The willow dark, the flower bright - ten thousand houses,
       Knock at any door - there's one who will respond.
                                       -- The Blue Cliff Record

Re: Issues register for JSPWiki metadata support?

Posted by Janne Jalkanen <ja...@iki.fi>.
> I would be happy to take a look, and potentially work on it as well,
> but for some reason I'm not currently able to get CVS to work, not
> sure if it's my end or the CVS server is down. I'll try again tomorrow
> from work.

It should be working, but just in case, I kicked the cvsd...

/Janne

Re: Issues register for JSPWiki metadata support?

Posted by Murray Altheim <mu...@altheim.com>.
Janne Jalkanen wrote:
[...]
> Therefore, I started a small JSR-170 -implementation project called
> "Priha".  It's not meant to be JSR-170 -compliant, but should fulfil
> all of our use cases, while retaining a very simple-to-use provider
> SPI, similar to the current JSPWiki PageProvider.  It also needs few
> external libraries (it tries to use Java 5 built-in stuff as much as
> possible), and is pretty fast.  I thought it would be cool to ship it
> as part of JSPWiki 3, and provide some nice migration path.  Then the
> people who need serious enterprise grade performance can use something
> else, and people who are happy with just a simple implementation can
> use whatever is built-in.

Sounds like exactly what I was trying to describe (poorly).

> It already works to quite a large degree.  If you want to start
> hacking away at it, you can check it out from cvs.jspwiki.org under
> the module name "Priha".  At this stage I'd be happy to get some
> co-contributors on it :-)

I would be happy to take a look, and potentially work on it as well,
but for some reason I'm not currently able to get CVS to work, not
sure if it's my end or the CVS server is down. I'll try again tomorrow
from work.

Thanks much!

Murray

...........................................................................
Murray Altheim <murray07 at altheim.com>                           ===  = =
http://www.altheim.com/murray/                                     = =  ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk               = =  = =

       Boundless wind and moon - the eye within eyes,
       Inexhaustible heaven and earth - the light beyond light,
       The willow dark, the flower bright - ten thousand houses,
       Knock at any door - there's one who will respond.
                                       -- The Blue Cliff Record

Re: Issues register for JSPWiki metadata support?

Posted by Janne Jalkanen <ja...@iki.fi>.
> I completely agree, but we also need a lower-level API that the higher-
> level (JSP-170 level) API is a subset of, a simple API for file system
> providers and for implementations that simply don't need the complexity
> of JSR-170 (either from an installation, implementation or footprint
> standpoint), a simple API that still has metadata support. Not sure how
> to do that, but it IMO probably should be a requirement unless we're
> going to let JSPWiki become a heavyweight-only application. I kinda like
> the ability to just use a simple file system provider sometimes (and in
> fact, ended up adding a file backend my XNodeStore a long time after
> implementing a Xindice, Exist, and finally BerkeleyDB DB backends). Also,
> for a lot of ISPs (mine, forinstance), it may be difficult to manage a
> DB-based backend, even completely embedded. I like being able to simply
> copy that 'pages' directory between version upgrades.

These are two different things.  JSR-170 is the API that should be
visible to the rest of JSPWiki.  Of course, the API should be
pluggable, that is, you can put in Jackrabbit or what-have-you as the
JCR implementation.

Jackrabbit will happily use also file storage, or you can even use
something like HSQLDB, which stores all data as files, making managing
them very easy.

However, having said that, I do also see a need for something simple
to ship with our product.  Jackrabbit is a full-featured JSR-170
implementation with all the possible bells and whistles (of which we
don't need most), and it's pretty big and needs external libraries as
well.  The file storage is also rather obscure, so direct file
management the way that people are currently doing would be a bit
complicated.

Therefore, I started a small JSR-170 -implementation project called
"Priha".  It's not meant to be JSR-170 -compliant, but should fulfil
all of our use cases, while retaining a very simple-to-use provider
SPI, similar to the current JSPWiki PageProvider.  It also needs few
external libraries (it tries to use Java 5 built-in stuff as much as
possible), and is pretty fast.  I thought it would be cool to ship it
as part of JSPWiki 3, and provide some nice migration path.  Then the
people who need serious enterprise grade performance can use something
else, and people who are happy with just a simple implementation can
use whatever is built-in.

It already works to quite a large degree.  If you want to start
hacking away at it, you can check it out from cvs.jspwiki.org under
the module name "Priha".  At this stage I'd be happy to get some
co-contributors on it :-)

(By the way, in a completely unrelated matter, Java 5 + Hibernate +
Stripes is a very cool combo.  Using Stripes would make JSPWiki a
*lot* simpler in the future.)

/Janne

Re: Issues register for JSPWiki metadata support?

Posted by Murray Altheim <mu...@altheim.com>.
Janne Jalkanen wrote:
> 
> Well, I seem to recall I tasked you a few months ago to start working on 
> one ;-)

Heh, I guess I just need a call to action. :-o

> I'd really rather stop making up our own backends, and move to an 
> industry standard solution such as JSR-170.  It has a very rich metadata 
> model (in which even the page content is just metadata).  If we want, we 
> can then build our own light-weight JSR-170 implementation (it's not 
> hard, if you don't aim for full TCK compatibility) which is compatible 
> with existing repositories.

I completely agree, but we also need a lower-level API that the higher-
level (JSP-170 level) API is a subset of, a simple API for file system
providers and for implementations that simply don't need the complexity
of JSR-170 (either from an installation, implementation or footprint
standpoint), a simple API that still has metadata support. Not sure how
to do that, but it IMO probably should be a requirement unless we're
going to let JSPWiki become a heavyweight-only application. I kinda like
the ability to just use a simple file system provider sometimes (and in
fact, ended up adding a file backend my XNodeStore a long time after
implementing a Xindice, Exist, and finally BerkeleyDB DB backends). Also,
for a lot of ISPs (mine, forinstance), it may be difficult to manage a
DB-based backend, even completely embedded. I like being able to simply
copy that 'pages' directory between version upgrades.

[not sure how lucid that last paragraph was but I'm short of time to
go back and edit it.]

Okay, will begin investigating this with more attention...

Murray

...........................................................................
Murray Altheim <murray07 at altheim.com>                           ===  = =
http://www.altheim.com/murray/                                     = =  ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk               = =  = =

       Boundless wind and moon - the eye within eyes,
       Inexhaustible heaven and earth - the light beyond light,
       The willow dark, the flower bright - ten thousand houses,
       Knock at any door - there's one who will respond.
                                       -- The Blue Cliff Record

Re: Issues register for JSPWiki metadata support?

Posted by Janne Jalkanen <Ja...@ecyrd.com>.
Well, I seem to recall I tasked you a few months ago to start working  
on one ;-)

I'd really rather stop making up our own backends, and move to an  
industry standard solution such as JSR-170.  It has a very rich  
metadata model (in which even the page content is just metadata).  If  
we want, we can then build our own light-weight JSR-170  
implementation (it's not hard, if you don't aim for full TCK  
compatibility) which is compatible with existing repositories.

/Janne

On 23 Oct 2007, at 06:35, Murray Altheim wrote:

> Janne,
>
> Just wondering, since you seem to have alluded to potential planning
> for upcoming support for WikiPage metadata in future versions of
> JSPWiki, if you have any existing requirements or designs that you'd
> be willing to share, or if there's an existing place where we might
> lodge what might be requirements on metadata functionality?
>
> As an example, the current page attributes are delivered as a Java
> Map. Because Maps uses unique keys this would eliminate the ability
> to be able to store properties that have the same name. With Dublin
> Core metadata there's generally (in common usage) the idea that
> there may be multiple DC.creator entries for an given resources (e.g.,
> documents written by more than one author), and certainly more than
> one DC.contributor (when there are multiple contributors, which
> would certainly be the case with wiki pages). The limitation of Map
> is currently stinging me...
>
> If there's a place (perhaps a page on JSPWiki, or a document  
> somewhere)
> where we might begin to put together a set of requirements, this might
> help when the design starts getting fleshed out.
>
> Thanks,
>
> Murray
>
> ...................................................................... 
> .....
> Murray Altheim <murray07 at altheim.com>                            
> ===  = =
> http://www.altheim.com/murray/                                      
> = =  ===
> SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk                
> = =  = =
>
>       Boundless wind and moon - the eye within eyes,
>       Inexhaustible heaven and earth - the light beyond light,
>       The willow dark, the flower bright - ten thousand houses,
>       Knock at any door - there's one who will respond.
>                                       -- The Blue Cliff Record