You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Thijs Vonk (JIRA)" <ji...@apache.org> on 2009/02/05 12:21:59 UTC

[jira] Created: (WICKET-2081) Add optional support for "Setting Markup Head Elements" PLT.12.5.4

Add optional support for "Setting Markup Head Elements" PLT.12.5.4
------------------------------------------------------------------

                 Key: WICKET-2081
                 URL: https://issues.apache.org/jira/browse/WICKET-2081
             Project: Wicket
          Issue Type: Sub-task
            Reporter: Thijs Vonk




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-2081) Add optional support for "Setting Markup Head Elements" PLT.12.5.4

Posted by "Thijs Vonk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thijs Vonk updated WICKET-2081:
-------------------------------

    Attachment: WICKET-2081.patch

First draft.

Note that for testing purposes "markupHeadElementSupported" is set to true by default. 
This will break Wicket portlets if the portlet-container does not support this feature.

> Add optional support for "Setting Markup Head Elements" PLT.12.5.4
> ------------------------------------------------------------------
>
>                 Key: WICKET-2081
>                 URL: https://issues.apache.org/jira/browse/WICKET-2081
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>            Reporter: Thijs Vonk
>            Priority: Minor
>             Fix For: 1.5-M1
>
>         Attachments: WICKET-2081.patch
>
>
> Add support for PLT.12.5.4 Setting Markup Head Elements.
> Changing the EmbeddedPortletHeaderResponse to (in some cases) output Dom elements instead of strings to provide to the portal to put in the <head> section of the portal page.
> one of the problems that still exist is (if possible) filtering out double added references. As each Wicket portlet will add a reference to the Wicket javascript files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-2081) Add optional support for "Setting Markup Head Elements" PLT.12.5.4

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg updated WICKET-2081:
----------------------------------

    Fix Version/s: 1.5-M2
                       (was: 1.5-M1)

> Add optional support for "Setting Markup Head Elements" PLT.12.5.4
> ------------------------------------------------------------------
>
>                 Key: WICKET-2081
>                 URL: https://issues.apache.org/jira/browse/WICKET-2081
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>            Reporter: Thijs Vonk
>            Priority: Minor
>             Fix For: 1.5-M2
>
>         Attachments: WICKET-2081.patch
>
>
> Add support for PLT.12.5.4 Setting Markup Head Elements.
> Changing the EmbeddedPortletHeaderResponse to (in some cases) output Dom elements instead of strings to provide to the portal to put in the <head> section of the portal page.
> one of the problems that still exist is (if possible) filtering out double added references. As each Wicket portlet will add a reference to the Wicket javascript files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-2081) Add optional support for "Setting Markup Head Elements" PLT.12.5.4

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg updated WICKET-2081:
----------------------------------

    Fix Version/s: 1.5-M3
                       (was: 1.5-M2)

> Add optional support for "Setting Markup Head Elements" PLT.12.5.4
> ------------------------------------------------------------------
>
>                 Key: WICKET-2081
>                 URL: https://issues.apache.org/jira/browse/WICKET-2081
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>            Reporter: Thijs Vonk
>            Priority: Minor
>             Fix For: 1.5-M3
>
>         Attachments: WICKET-2081.patch
>
>
> Add support for PLT.12.5.4 Setting Markup Head Elements.
> Changing the EmbeddedPortletHeaderResponse to (in some cases) output Dom elements instead of strings to provide to the portal to put in the <head> section of the portal page.
> one of the problems that still exist is (if possible) filtering out double added references. As each Wicket portlet will add a reference to the Wicket javascript files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-2081) Add optional support for "Setting Markup Head Elements" PLT.12.5.4

Posted by "Thijs Vonk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thijs Vonk updated WICKET-2081:
-------------------------------

      Component/s: wicket
    Fix Version/s: 1.5-M1
         Priority: Minor  (was: Major)
      Description: 
Add support for PLT.12.5.4 Setting Markup Head Elements.

Changing the EmbeddedPortletHeaderResponse to (in some cases) output Dom elements instead of strings to provide to the portal to put in the <head> section of the portal page.

one of the problems that still exist is (if possible) filtering out double added references. As each Wicket portlet will add a reference to the Wicket javascript files.

> Add optional support for "Setting Markup Head Elements" PLT.12.5.4
> ------------------------------------------------------------------
>
>                 Key: WICKET-2081
>                 URL: https://issues.apache.org/jira/browse/WICKET-2081
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>            Reporter: Thijs Vonk
>            Priority: Minor
>             Fix For: 1.5-M1
>
>
> Add support for PLT.12.5.4 Setting Markup Head Elements.
> Changing the EmbeddedPortletHeaderResponse to (in some cases) output Dom elements instead of strings to provide to the portal to put in the <head> section of the portal page.
> one of the problems that still exist is (if possible) filtering out double added references. As each Wicket portlet will add a reference to the Wicket javascript files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WICKET-2081) Add optional support for "Setting Markup Head Elements" PLT.12.5.4

Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-2081.
-------------------------------------

    Resolution: Won't Fix

Closing as "Won't fix" because we decided to not support Portlets in Wicket 1.5

> Add optional support for "Setting Markup Head Elements" PLT.12.5.4
> ------------------------------------------------------------------
>
>                 Key: WICKET-2081
>                 URL: https://issues.apache.org/jira/browse/WICKET-2081
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>            Reporter: Thijs Vonk
>            Priority: Minor
>             Fix For: 1.5-M3
>
>         Attachments: WICKET-2081.patch
>
>
> Add support for PLT.12.5.4 Setting Markup Head Elements.
> Changing the EmbeddedPortletHeaderResponse to (in some cases) output Dom elements instead of strings to provide to the portal to put in the <head> section of the portal page.
> one of the problems that still exist is (if possible) filtering out double added references. As each Wicket portlet will add a reference to the Wicket javascript files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.