[
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.
