You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David DeWolf (JIRA)" <ji...@apache.org> on 2006/12/04 04:58:21 UTC
[jira] Created: (PLUTO-274) Save page configuration
Save page configuration
-----------------------
Key: PLUTO-274
URL: http://issues.apache.org/jira/browse/PLUTO-274
Project: Pluto
Issue Type: New Feature
Components: portlets-admin
Reporter: David DeWolf
Priority: Minor
Fix For: Current CVS
Portlet Admin portlets currently store the page configuration (added portlets/removed portlets) in cache. It'd be nice to persist these in a simple location.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-274) Save page configuration
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David DeWolf updated PLUTO-274:
-------------------------------
Fix Version/s: (was: 1.1.1)
1.2.0
No database. Properties or xml file only. I'm not convinced we need this in 1.1.x. I'm going to move out to 1.2.0 and we'll consider jaxb.
> Save page configuration
> -----------------------
>
> Key: PLUTO-274
> URL: https://issues.apache.org/jira/browse/PLUTO-274
> Project: Pluto
> Issue Type: New Feature
> Components: portlets-admin
> Reporter: David DeWolf
> Priority: Minor
> Fix For: 1.2.0
>
>
> Portlet Admin portlets currently store the page configuration (added portlets/removed portlets) in cache. It'd be nice to persist these in a simple location.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (PLUTO-274) Save page configuration
Posted by "David H. DeWolf" <dd...@apache.org>.
Correct, I'd be for a pluggable interface, but only implementing in
pluto with a simple mechanism. . .like file based.
D
Elliot Metsger wrote:
> The implementation would be pluggable (? - this is a question) which
> could allow for more sophisticated persistence implementations that rely
> on a db.
>
> David H. DeWolf wrote:
>> We've been down that path once and decided to scrap it. Let's discuss
>> this on the list if this is the approach you want to take. I'm
>> leaning towards something a little simpler.
>>
>> Craig Doremus (JIRA) wrote:
>>> [
>>> http://issues.apache.org/jira/browse/PLUTO-274?page=comments#action_12455363
>>> ] Craig Doremus commented on PLUTO-274:
>>> -------------------------------------
>>>
>>> We really should use a database for this and Derby seems like the
>>> best candidate especially since it's suppose to be part of Java 6. We
>>> can use it for portlet preference and user attribute persistence too.
>>> Jens Fisher is supposably working on a Derby implementation of
>>> portlet preference persistence (see PLUTO-122).
>>>
>>>> Save page configuration
>>>> -----------------------
>>>>
>>>> Key: PLUTO-274
>>>> URL: http://issues.apache.org/jira/browse/PLUTO-274
>>>> Project: Pluto
>>>> Issue Type: New Feature
>>>> Components: portlets-admin
>>>> Reporter: David DeWolf
>>>> Priority: Minor
>>>> Fix For: Current CVS
>>>>
>>>>
>>>> Portlet Admin portlets currently store the page configuration (added
>>>> portlets/removed portlets) in cache. It'd be nice to persist these
>>>> in a simple location.
>>>
>
>
Re: [jira] Commented: (PLUTO-274) Save page configuration
Posted by Elliot Metsger <em...@jhu.edu>.
The implementation would be pluggable (? - this is a question) which
could allow for more sophisticated persistence implementations that rely
on a db.
David H. DeWolf wrote:
> We've been down that path once and decided to scrap it. Let's discuss
> this on the list if this is the approach you want to take. I'm leaning
> towards something a little simpler.
>
> Craig Doremus (JIRA) wrote:
>> [
>> http://issues.apache.org/jira/browse/PLUTO-274?page=comments#action_12455363
>> ] Craig Doremus commented on PLUTO-274:
>> -------------------------------------
>>
>> We really should use a database for this and Derby seems like the best
>> candidate especially since it's suppose to be part of Java 6. We can
>> use it for portlet preference and user attribute persistence too. Jens
>> Fisher is supposably working on a Derby implementation of portlet
>> preference persistence (see PLUTO-122).
>>
>>> Save page configuration
>>> -----------------------
>>>
>>> Key: PLUTO-274
>>> URL: http://issues.apache.org/jira/browse/PLUTO-274
>>> Project: Pluto
>>> Issue Type: New Feature
>>> Components: portlets-admin
>>> Reporter: David DeWolf
>>> Priority: Minor
>>> Fix For: Current CVS
>>>
>>>
>>> Portlet Admin portlets currently store the page configuration (added
>>> portlets/removed portlets) in cache. It'd be nice to persist these in
>>> a simple location.
>>
Re: [jira] Commented: (PLUTO-274) Save page configuration
Posted by "David H. DeWolf" <dd...@apache.org>.
We've been down that path once and decided to scrap it. Let's discuss
this on the list if this is the approach you want to take. I'm leaning
towards something a little simpler.
Craig Doremus (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/PLUTO-274?page=comments#action_12455363 ]
>
> Craig Doremus commented on PLUTO-274:
> -------------------------------------
>
> We really should use a database for this and Derby seems like the best candidate especially since it's suppose to be part of Java 6. We can use it for portlet preference and user attribute persistence too. Jens Fisher is supposably working on a Derby implementation of portlet preference persistence (see PLUTO-122).
>
>> Save page configuration
>> -----------------------
>>
>> Key: PLUTO-274
>> URL: http://issues.apache.org/jira/browse/PLUTO-274
>> Project: Pluto
>> Issue Type: New Feature
>> Components: portlets-admin
>> Reporter: David DeWolf
>> Priority: Minor
>> Fix For: Current CVS
>>
>>
>> Portlet Admin portlets currently store the page configuration (added portlets/removed portlets) in cache. It'd be nice to persist these in a simple location.
>
[jira] Commented: (PLUTO-274) Save page configuration
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-274?page=comments#action_12455363 ]
Craig Doremus commented on PLUTO-274:
-------------------------------------
We really should use a database for this and Derby seems like the best candidate especially since it's suppose to be part of Java 6. We can use it for portlet preference and user attribute persistence too. Jens Fisher is supposably working on a Derby implementation of portlet preference persistence (see PLUTO-122).
> Save page configuration
> -----------------------
>
> Key: PLUTO-274
> URL: http://issues.apache.org/jira/browse/PLUTO-274
> Project: Pluto
> Issue Type: New Feature
> Components: portlets-admin
> Reporter: David DeWolf
> Priority: Minor
> Fix For: Current CVS
>
>
> Portlet Admin portlets currently store the page configuration (added portlets/removed portlets) in cache. It'd be nice to persist these in a simple location.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (PLUTO-274) Save page configuration
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David DeWolf updated PLUTO-274:
-------------------------------
Fix Version/s: (was: Current CVS)
1.1.1
> Save page configuration
> -----------------------
>
> Key: PLUTO-274
> URL: https://issues.apache.org/jira/browse/PLUTO-274
> Project: Pluto
> Issue Type: New Feature
> Components: portlets-admin
> Reporter: David DeWolf
> Priority: Minor
> Fix For: 1.1.1
>
>
> Portlet Admin portlets currently store the page configuration (added portlets/removed portlets) in cache. It'd be nice to persist these in a simple location.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.