You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Chris Colman (JIRA)" <ji...@apache.org> on 2010/05/20 00:53:55 UTC

[jira] Created: (WICKET-2882) Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1

Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1
---------------------------------------------------------------------------------------------------------

                 Key: WICKET-2882
                 URL: https://issues.apache.org/jira/browse/WICKET-2882
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.4.8, 1.4.7, 1.4.6, 1.4.5, 1.4.4, 1.4.3, 1.4.2
         Environment: Tomcat 6.x, Java 6, Windows or Linux
            Reporter: Chris Colman
         Attachments: enclosurebug.zip

We have been using an IComponentResolver implementation for a long time to allow the inclusion of certain panels to be determined by the markup. Some panels are included inside enclosures and some are not. Both cases worked fine in wicket 1.4.1 but in versions 1.4.2 and later a 'Tag expected' error occurs if the component is wrapped inside a wicket enclosure.

A quickstart example has been included to demonstrate the problem.

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


[jira] Commented: (WICKET-2882) Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885039#action_12885039 ] 

Hudson commented on WICKET-2882:
--------------------------------

Integrated in Apache Wicket 1.5.x #127 (See [http://hudson.zones.apache.org/hudson/job/Apache%20Wicket%201.5.x/127/])
    fixed WICKET-2882: IComponentResolver usage with Enclosure
Issue: WICKET-2882


> Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2882
>                 URL: https://issues.apache.org/jira/browse/WICKET-2882
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8
>         Environment: Tomcat 6.x, Java 6, Windows or Linux
>            Reporter: Chris Colman
>            Assignee: Jeremy Thomerson
>             Fix For: 1.4.10
>
>         Attachments: enclosurebug.zip
>
>
> We have been using an IComponentResolver implementation for a long time to allow the inclusion of certain panels to be determined by the markup. Some panels are included inside enclosures and some are not. Both cases worked fine in wicket 1.4.1 but in versions 1.4.2 and later a 'Tag expected' error occurs if the component is wrapped inside a wicket enclosure.
> A quickstart example has been included to demonstrate the problem.

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


[jira] Updated: (WICKET-2882) Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1

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

Chris Colman updated WICKET-2882:
---------------------------------

    Attachment: enclosurebug.zip

Quickstart to reproduce the problem.

> Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2882
>                 URL: https://issues.apache.org/jira/browse/WICKET-2882
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8
>         Environment: Tomcat 6.x, Java 6, Windows or Linux
>            Reporter: Chris Colman
>         Attachments: enclosurebug.zip
>
>
> We have been using an IComponentResolver implementation for a long time to allow the inclusion of certain panels to be determined by the markup. Some panels are included inside enclosures and some are not. Both cases worked fine in wicket 1.4.1 but in versions 1.4.2 and later a 'Tag expected' error occurs if the component is wrapped inside a wicket enclosure.
> A quickstart example has been included to demonstrate the problem.

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


[jira] Commented: (WICKET-2882) Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870912#action_12870912 ] 

Hudson commented on WICKET-2882:
--------------------------------

Integrated in Apache Wicket 1.5.x #65 (See [http://hudson.zones.apache.org/hudson/job/Apache%20Wicket%201.5.x/65/])
    

> Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2882
>                 URL: https://issues.apache.org/jira/browse/WICKET-2882
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8
>         Environment: Tomcat 6.x, Java 6, Windows or Linux
>            Reporter: Chris Colman
>            Assignee: Jeremy Thomerson
>             Fix For: 1.4.10
>
>         Attachments: enclosurebug.zip
>
>
> We have been using an IComponentResolver implementation for a long time to allow the inclusion of certain panels to be determined by the markup. Some panels are included inside enclosures and some are not. Both cases worked fine in wicket 1.4.1 but in versions 1.4.2 and later a 'Tag expected' error occurs if the component is wrapped inside a wicket enclosure.
> A quickstart example has been included to demonstrate the problem.

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


[jira] Resolved: (WICKET-2882) Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1

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

Jeremy Thomerson resolved WICKET-2882.
--------------------------------------

         Assignee: Jeremy Thomerson
    Fix Version/s: 1.4.10
       Resolution: Fixed

> Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2882
>                 URL: https://issues.apache.org/jira/browse/WICKET-2882
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8
>         Environment: Tomcat 6.x, Java 6, Windows or Linux
>            Reporter: Chris Colman
>            Assignee: Jeremy Thomerson
>             Fix For: 1.4.10
>
>         Attachments: enclosurebug.zip
>
>
> We have been using an IComponentResolver implementation for a long time to allow the inclusion of certain panels to be determined by the markup. Some panels are included inside enclosures and some are not. Both cases worked fine in wicket 1.4.1 but in versions 1.4.2 and later a 'Tag expected' error occurs if the component is wrapped inside a wicket enclosure.
> A quickstart example has been included to demonstrate the problem.

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


[jira] Commented: (WICKET-2882) Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1

Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885052#action_12885052 ] 

Juergen Donnerstag commented on WICKET-2882:
--------------------------------------------

verifed in 1.5 (trunk) => working correctly

> Dynamically adding component via an IComponentResolver fails within an enclosure for versions after 1.4.1
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2882
>                 URL: https://issues.apache.org/jira/browse/WICKET-2882
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8
>         Environment: Tomcat 6.x, Java 6, Windows or Linux
>            Reporter: Chris Colman
>            Assignee: Jeremy Thomerson
>             Fix For: 1.4.10
>
>         Attachments: enclosurebug.zip
>
>
> We have been using an IComponentResolver implementation for a long time to allow the inclusion of certain panels to be determined by the markup. Some panels are included inside enclosures and some are not. Both cases worked fine in wicket 1.4.1 but in versions 1.4.2 and later a 'Tag expected' error occurs if the component is wrapped inside a wicket enclosure.
> A quickstart example has been included to demonstrate the problem.

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