You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2006/10/04 18:25:17 UTC

Re: is it time to move thedefault pub to uuids?

Jürgen Ragaller schrieb:
> 
> Am Sep 30, 2006 um 17:58 schrieb Jörn Nettingsmeier:
> 
>> hi everyone!
>>
>>
>> i wonder: should we move the default publication to uuid storage?
>>
>> we will lose a test case for the migration target, but it seems quite
>> odd to me that our example publication is in a deprecated format that
>> will not even work out-of-the-box.
> 
> What came to my mind regarding this:
> 
> Wouldn't it be better to integrate the migration target into the build?
> 
> Otherwise the exact same uuids will be found in the default publications
> of many users all over the planet (not exactly the purpose of uuids...).

Good point.

Maybe an even cleaner way would be to

- implement XML import/export (use site structure as directory
  structure, similar to the old content storage)

- provide the default content as "exported XML"

Then the user could import the initial content and new UUIDs would
be generated.

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: is it time to move thedefault pub to uuids?

Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann schrieb:
> Doug Chestnut schrieb:
>>
>> Andreas Hartmann wrote:
>>> Doug Chestnut schrieb:
>>>
>>> [...]
>>>
>>>
>>>>> Maybe an even cleaner way would be to
>>>>>
>>>>> - implement XML import/export (use site structure as directory
>>>>>  structure, similar to the old content storage)
> 
> This raises the issue of exporting/importing internal links.
> We'd have to convert UUID-based links to path-based links,
> but I guess this should be possible.

I moved the content dir to example-content and added an
importExampleContent usecase.

When the user enters the default pub for the first time,
she is promted either to import the example content or
create her own pages.

It was the quickest solution I found, but if you don't
like it, feel free to change or discuss.

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: is it time to move thedefault pub to uuids?

Posted by Andreas Hartmann <an...@apache.org>.
Doug Chestnut schrieb:
> 
> 
> Andreas Hartmann wrote:
>> Doug Chestnut schrieb:
>>
>> [...]
>>
>>
>>>> Maybe an even cleaner way would be to
>>>>
>>>> - implement XML import/export (use site structure as directory
>>>>  structure, similar to the old content storage)

This raises the issue of exporting/importing internal links.
We'd have to convert UUID-based links to path-based links,
but I guess this should be possible.

-- Andreas

>>>>
>>>> - provide the default content as "exported XML"
>>>>
>>>> Then the user could import the initial content and new UUIDs would
>>>> be generated.
>>>
>>> This would be a nice feature anyway.  Perhaps this could be handled via
>>> webDAV?
>>
>>
>> Good idea, that sounds like the most straightforward way.
>> Is there a WebDAV client library which can be called from Ant?
>> I wouldn't like to require to install a WebDAV client to import
>> the default content ...
> It looks like vfs from jakarta commons might be up to the task:
> http://jakarta.apache.org/commons/vfs/anttasks.html
> 
> --Doug
>>
>> -- Andreas
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: dev-help@lenya.apache.org
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: is it time to move thedefault pub to uuids?

Posted by Doug Chestnut <dh...@virginia.edu>.

Andreas Hartmann wrote:
> Doug Chestnut schrieb:
> 
> [...]
> 
> 
>>>Maybe an even cleaner way would be to
>>>
>>>- implement XML import/export (use site structure as directory
>>>  structure, similar to the old content storage)
>>>
>>>- provide the default content as "exported XML"
>>>
>>>Then the user could import the initial content and new UUIDs would
>>>be generated.
>>
>>This would be a nice feature anyway.  Perhaps this could be handled via
>>webDAV?
> 
> 
> Good idea, that sounds like the most straightforward way.
> Is there a WebDAV client library which can be called from Ant?
> I wouldn't like to require to install a WebDAV client to import
> the default content ...
It looks like vfs from jakarta commons might be up to the task:
http://jakarta.apache.org/commons/vfs/anttasks.html

--Doug
> 
> -- Andreas
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: is it time to move thedefault pub to uuids?

Posted by Doug Chestnut <dh...@virginia.edu>.

Andreas Hartmann wrote:
> Doug Chestnut schrieb:
> 
> [...]
> 
> 
>>>Maybe an even cleaner way would be to
>>>
>>>- implement XML import/export (use site structure as directory
>>>  structure, similar to the old content storage)
>>>
>>>- provide the default content as "exported XML"
>>>
>>>Then the user could import the initial content and new UUIDs would
>>>be generated.
>>
>>This would be a nice feature anyway.  Perhaps this could be handled via
>>webDAV?
> 
> 
> Good idea, that sounds like the most straightforward way.
> Is there a WebDAV client library which can be called from Ant?
> I wouldn't like to require to install a WebDAV client to import
> the default content ...
I don't think we would need a full webDAV client.  Just a simple http 
PUT and GET (inport/export) would do.  We wouldn't need to even do a 
propfind, as we could use the api to get a listing for export.

--Doug

> 
> -- Andreas
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: is it time to move thedefault pub to uuids?

Posted by Andreas Hartmann <an...@apache.org>.
Doug Chestnut schrieb:

[...]

>> Maybe an even cleaner way would be to
>>
>> - implement XML import/export (use site structure as directory
>>   structure, similar to the old content storage)
>>
>> - provide the default content as "exported XML"
>>
>> Then the user could import the initial content and new UUIDs would
>> be generated.
> This would be a nice feature anyway.  Perhaps this could be handled via
> webDAV?

Good idea, that sounds like the most straightforward way.
Is there a WebDAV client library which can be called from Ant?
I wouldn't like to require to install a WebDAV client to import
the default content ...

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: is it time to move thedefault pub to uuids?

Posted by Doug Chestnut <dh...@virginia.edu>.

Andreas Hartmann wrote:
> Jürgen Ragaller schrieb:
> 
>>Am Sep 30, 2006 um 17:58 schrieb Jörn Nettingsmeier:
>>
>>
>>>hi everyone!
>>>
>>>
>>>i wonder: should we move the default publication to uuid storage?
>>>
>>>we will lose a test case for the migration target, but it seems quite
>>>odd to me that our example publication is in a deprecated format that
>>>will not even work out-of-the-box.
>>
>>What came to my mind regarding this:
>>
>>Wouldn't it be better to integrate the migration target into the build?
>>
>>Otherwise the exact same uuids will be found in the default publications
>>of many users all over the planet (not exactly the purpose of uuids...).
> 
> 
> Good point.
> 
> Maybe an even cleaner way would be to
> 
> - implement XML import/export (use site structure as directory
>   structure, similar to the old content storage)
> 
> - provide the default content as "exported XML"
> 
> Then the user could import the initial content and new UUIDs would
> be generated.
This would be a nice feature anyway.  Perhaps this could be handled via 
webDAV?  I have been meaning to fix propfind to work with the new uuid 
site structure (Last time I looked it was broken).

--Doug

> 
> -- Andreas
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org