[magnolia-dev] [JIRA] Created: (MAGNOLIA-2264) Second activation throws an error

Second activation throws an error
---------------------------------

                 Key: MAGNOLIA-2264
                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2264
             Project: Magnolia
          Issue Type: Bug
    Affects Versions: 3.6 RC1
         Environment: Mac OSX 10.5.4
            Reporter: Tom Wespi
            Assignee: Gregory Joseph

Delete  /config/modules/adminInterface/commands/website to remove the workflow

Create a new page
Activate the page
Activate again

Message received from subscriber: failed to resolve path  relative to /: empty path on magnoliaPublic8080
	at info.magnolia.module.exchangetransactional.TransactionalSyndicator.activate(TransactionalSyndicator.java:127)
	at info.magnolia.module.exchangesimple.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:285)
	at info.magnolia.module.exchangesimple.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:247)
	at info.magnolia.module.admininterface.commands.ActivationCommand.execute(ActivationCommand.java:101)
	at info.magnolia.commands.MgnlCommand.executePooledOrSynchronized(MgnlCommand.java:173)
	at info.magnolia.commands.MgnlCommand.execute(MgnlCommand.java:160)
	at info.magnolia.cms.servlets.CommandBasedMVCServletHandler.execute(CommandBasedMVCServletHandler.java:99)
	at info.magnolia.cms.servlets.MVCServlet.doPost(MVCServlet.java:124)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	at info.magnolia.cms.filters.ServletDispatchingFilter.doFilter(ServletDispatchingFilter.java:143)
(Continue reading)

[magnolia-dev] [JIRA] Issue Comment Edited: (MAGNOLIA-1928) Add support for repo-only modules


    [
http://jira.magnolia.info/browse/MAGNOLIA-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555#action_16555
] 

gjoseph edited comment on MAGNOLIA-1928 at 7/15/08 6:34 PM:
-------------------------------------------------------------------

related: any module should be observed such that adding a {{paragraphs}} or other observed nodes will
register this new node with the relevant ObservedManager. -> see MAGNOLIA-2265

      was (Author: gjoseph):
    related: any module should be observed such that adding a {{paragraphs}} or other observed nodes will
register this new node with the relevant ObservedManager.

> Add support for repo-only modules
> ---------------------------------
>
>                 Key: MAGNOLIA-1928
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1928
>             Project: Magnolia
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.5
>            Reporter: Gregory Joseph
>            Assignee: Gregory Joseph
>             Fix For: Green
>
>
> Currently, only modules found through a module descriptor are loaded/initialized. We should provide
(Continue reading)

[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2265) Observe module nodes to automatically register new nodes in appropriate components


     [
http://jira.magnolia.info/browse/MAGNOLIA-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Joseph reassigned MAGNOLIA-2265:
----------------------------------------

    Assignee: Gregory Joseph  (was: Philipp Bracher)

> Observe module nodes to automatically register new nodes in appropriate components
> ----------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2265
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2265
>             Project: Magnolia
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 3.6
>            Reporter: Gregory Joseph
>            Assignee: Gregory Joseph
>             Fix For: Green
>
>
> A restart is currently required if one wants to add, for example, paragraph in her own module, when the
{{/modules/mymodule/paragraph}} did not exist yet. Observing all modules node (isDeep=false) and
registering children node with the appropriate ObservedManager could solve this.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)


Gmane