You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/08/13 17:56:44 UTC
[jira] Created: (SLING-611) Save OSGi event properties as JCR
properties
Save OSGi event properties as JCR properties
--------------------------------------------
Key: SLING-611
URL: https://issues.apache.org/jira/browse/SLING-611
Project: Sling
Issue Type: Improvement
Components: Event
Affects Versions: Extensions Event 2.0.2
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Extensions Event 2.0.4
Currently all OSGi event properties are saved in a single JCR property (as serialized java object)
If possible the event properties can directly be saved as JCR properties - only props who's name or type is not directly usable get saved as a serialized java object
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-611) Save OSGi event properties as JCR
properties
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622331#action_12622331 ]
Tobias Bocanegra commented on SLING-611:
----------------------------------------
> ... only props who's name or type ...
the name can be escaped. see http://jackrabbit.apache.org/api/1.4/org/apache/jackrabbit/util/ISO9075.html as a possible escaping.
> Save OSGi event properties as JCR properties
> --------------------------------------------
>
> Key: SLING-611
> URL: https://issues.apache.org/jira/browse/SLING-611
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Affects Versions: Extensions Event 2.0.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.0.4
>
>
> Currently all OSGi event properties are saved in a single JCR property (as serialized java object)
> If possible the event properties can directly be saved as JCR properties - only props who's name or type is not directly usable get saved as a serialized java object
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-611) Save OSGi event properties as JCR
properties
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-611.
----------------------------------
Resolution: Fixed
The approach is very easy:
if the name contains a ":" it's not saved as a property
if the value is long, calendar, string, boolean or double the property is saved
All other values are saved as a blob as the back conversion would not guarantee to have the same type
(Yes, we could store the types in addition and recreate them, but I think that's not worth the effort atm)
> Save OSGi event properties as JCR properties
> --------------------------------------------
>
> Key: SLING-611
> URL: https://issues.apache.org/jira/browse/SLING-611
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Affects Versions: Extensions Event 2.0.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.0.4
>
>
> Currently all OSGi event properties are saved in a single JCR property (as serialized java object)
> If possible the event properties can directly be saved as JCR properties - only props who's name or type is not directly usable get saved as a serialized java object
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-611) Save OSGi event properties as JCR
properties
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622461#action_12622461 ]
Carsten Ziegeler commented on SLING-611:
----------------------------------------
Thanks for the pointer - yes this solves the problem partially - the event property could use a namespace like syntax which does not use a known prefix from the repository, like
myspecialevent:property, so we might have to escape the colons as well.
> Save OSGi event properties as JCR properties
> --------------------------------------------
>
> Key: SLING-611
> URL: https://issues.apache.org/jira/browse/SLING-611
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Affects Versions: Extensions Event 2.0.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.0.4
>
>
> Currently all OSGi event properties are saved in a single JCR property (as serialized java object)
> If possible the event properties can directly be saved as JCR properties - only props who's name or type is not directly usable get saved as a serialized java object
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.