[jira] [Commented] (JSPWIKI-120) Separate rendering engine from core

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JSPWIKI-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038544#comment-17038544 ] 

ASF subversion and git services commented on JSPWIKI-120:
---------------------------------------------------------

Commit 0d178df16c4cfae7030d1d884d9b943e06f07520 in jspwiki's branch refs/heads/master from juanpablo
[ https://gitbox.apache.org/repos/asf?p=jspwiki.git;h=0d178df ]

JSPWIKI-120: finally, extract Engine interface from WikiEngine

also first step towards public api - JSPWIKI-303


> Separate rendering engine from core
> -----------------------------------
>
>                 Key: JSPWIKI-120
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-120
>             Project: JSPWiki
>          Issue Type: New Feature
>          Components: Core & storage
>            Reporter: Janne Jalkanen
>            Priority: Major
>             Fix For: 3.0
>
>
> Quite a few people have shown up recently on the mailing list and have expressed a wish to separate the rendering engine from the core itself, so that they wouldn't need so much baggage with the engine.
> Unfortunately, this is quite difficult, as the rendering engine does rely on quite a few bits from the WikiEngine instance, for example URL generation and checking whether a page/attachment exists or not, as well as settings.
> However, these things could be enumerated and isolated to a RenderingContext interface.  Then, anyone who would like to get their own engine would need to implement this interface.
> It may mean that WikiEngine and WikiContext might need to become interfaces as well.  However, that might not be such a bad thing, as it would give a more stable developer API.  Then we would have a three-layered architecture, where one layer (WikiEngine) takes care of static stuff, WikiContext contains per-request data, and RenderingContext provides the bits and pieces which are part of HTML generation.
> At any rate, this requires more thinking.  Probably not going to happen before 3.0 anyway.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)