[jira] Resolved: (TOBAGO-704) Page state should be decoded in apply request values phase instead of update model phase

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-704.
--

Resolution: Fixed

> Page state should be decoded in apply request values phase instead of update 
> model phase
> 
>
> Key: TOBAGO-704
> URL: https://issues.apache.org/jira/browse/TOBAGO-704
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.18, 1.0.19, 1.1.0
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Fix For: 1.0.20
>
>


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

[jira] Resolved: (TOBAGO-707) Ajax paging of tabGroup should skip disabled tabs

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-707.
--

Resolution: Fixed

> Ajax paging of tabGroup should skip disabled tabs
> -
>
> Key: TOBAGO-707
> URL: https://issues.apache.org/jira/browse/TOBAGO-707
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Themes
>Affects Versions: 1.0.19
>    Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
>Priority: Minor
> Fix For: 1.0.20
>
>


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

[jira] Created: (TOBAGO-714) Target attribute for tc:toolBarCommand

[Bernd Bohmann (JIRA)]

Target attribute for tc:toolBarCommand
--

 Key: TOBAGO-714
 URL: https://issues.apache.org/jira/browse/TOBAGO-714
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.0.19
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.20, 1.1.0




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

[jira] Created: (TOBAGO-713) Possibility to render a drop-down in a TabGroup for selection of 'invisible' tabs (Eclipse-style)

[Bernd Bohmann (JIRA)]

Possibility to render a drop-down in a TabGroup for selection of 'invisible' 
tabs (Eclipse-style)
-

 Key: TOBAGO-713
 URL: https://issues.apache.org/jira/browse/TOBAGO-713
 Project: MyFaces Tobago
  Issue Type: New Feature
  Components: Themes
Reporter: Bernd Bohmann




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

Re: Async Lifecycle for JSF without patching JSF

[Bernd Bohmann]

Hello,

I just started an Async Lifecycle module based on the suggestion from
Greg Wilkins

http://wiki.glassfish.java.net/Wiki.jsp?page=AlternateAsyncProposalRebuttal

The module has been tested with MyFaces 1.2.4 and Sun RI 1.2_08 and the
async-jsf-example-webapp from the jetty 7.0.0pre3 version.

http://svn.codehaus.org/jetty/jetty/tags/jetty-7.0.0pre3/modules/examples/async-jsf-example-webapp/

Please look at the code

http://svn.apache.org/repos/asf/myfaces/commons/trunk/myfaces-async-lifecycle/src/main/java/org/apache/myfaces/commons/async/

The common Lifecycle and FacesContext code has been added to the
myfaces-commons-utils artifact.

Note the async Servlet API is not final.

Regards

Bernd


Greg Wilkins schrieb:
> Bernd Bohmann wrote:
>> Hello Greg,
>>
>> I just reviewed your patch for the Mojarra JSF implementation. I think
>> it should be possible to provide an extra artifact for JSF which
>> implements the async support for JSF without patching the
>> implementation. The extra artifact contains a FacesContextFactory and a
>> different Lifecyle for the async case. If you are interested I would try
>> to provide the code as a new module in MyFaces Commons.
> 
> 
> Bernd,
> 
> that would be excellent!  and well timed as well as the servlet-EG
> is in final deliberations about the async API proposals.
> 
> cheers
> 

[jira] Created: (TOBAGO-711) Onsubmit Attribute is missing in facelets ScriptHandler

[Bernd Bohmann (JIRA)]

Onsubmit Attribute  is missing in facelets ScriptHandler


 Key: TOBAGO-711
 URL: https://issues.apache.org/jira/browse/TOBAGO-711
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Facelets
Affects Versions: 1.0.19
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor
 Fix For: 1.0.20




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

New module in MyFaces Commons or add the code to util

[Bernd Bohmann]

Hello,

I would like to add some Wrapper Classes to MyFaces Commons
like FacesEventWrapper, FacesContextWrapper..
And I would like to add the Lifecyle PhaseExecutor stuff to Commons, too.

Any suggestions for the package names and artifact names?

Regards

Bernd

[RESULT] [VOTE] Release Tobago 1.0.19

[Bernd Bohmann]

The vote has passed with the following results:

+1
lofwyr (binding)
matzew (binding)
bommel (binding)

I will proceed with the next steps.

Regards

Bernd

Bernd Bohmann schrieb:
> Hello,
> 
> I would like to release Tobago 1.0.19
> 
> For a detail list please consult the release notes:
> 
> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313372
> 
> The version is available at the staging location and the
> revision number of the release is 700483 and tagged as tobago-1.0.19.
> 
> Staging distribution:
> 
> http://people.apache.org/~bommel/repo
> 
> Staging repository:
> 
> http://people.apache.org/~bommel/repo
> 
> 
> The Vote is open for 72h.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> 
> 
> 

[jira] Created: (TOBAGO-707) Ajax paging of tabGroup should skip disabled tabs

[Bernd Bohmann (JIRA)]

Ajax paging of tabGroup should skip disabled tabs
-

 Key: TOBAGO-707
 URL: https://issues.apache.org/jira/browse/TOBAGO-707
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Themes
Affects Versions: 1.0.19
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor
 Fix For: 1.0.20




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

Re: [VOTE] Release Tobago 1.0.19

[Bernd Bohmann]

Here is my

+1

Regards

Bernd

Matthias Wessendorf schrieb:
> +1
> 
> On Thu, Oct 2, 2008 at 5:50 PM, Udo Schnurpfeil <[EMAIL PROTECTED]> wrote:
>> Here is my
>>
>> +1
>>
>> I've updated the demo on: http://tobago.atanion.net/tobago-example-demo/
>>
>> Regards
>>
>> Udo
>>
>> Bernd Bohmann schrieb:
>>> Hello,
>>>
>>> I would like to release Tobago 1.0.19
>>>
>>> For a detail list please consult the release notes:
>>>
>>>
>>> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313372
>>>
>>> The version is available at the staging location and the
>>> revision number of the release is 700483 and tagged as tobago-1.0.19.
>>>
>>> Staging distribution:
>>>
>>> http://people.apache.org/~bommel/repo
>>>
>>> Staging repository:
>>>
>>> http://people.apache.org/~bommel/repo
>>>
>>>
>>> The Vote is open for 72h.
>>>
>>> [ ] +1
>>> [ ] +0
>>> [ ] -1
>>>
>>>
>>>
>>>
>>>
>>
> 
> 
> 

[jira] Created: (TOBAGO-706) Event list in UIViewRoot changed to request scope (only a test)

[Bernd Bohmann (JIRA)]

Event list in UIViewRoot changed to request scope (only a test) 


 Key: TOBAGO-706
 URL: https://issues.apache.org/jira/browse/TOBAGO-706
 Project: MyFaces Tobago
  Issue Type: Improvement
Affects Versions: 1.0.20
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann




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

[jira] Created: (TOBAGO-705) Label tag should allow body content

[Bernd Bohmann (JIRA)]

Label tag should allow body content
---

 Key: TOBAGO-705
 URL: https://issues.apache.org/jira/browse/TOBAGO-705
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.0.18
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann




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

[jira] Created: (TOBAGO-704) page state should be decoded in apply request values phase instead of update model phase

[Bernd Bohmann (JIRA)]

page state should be decoded in apply request values phase instead of update 
model phase


 Key: TOBAGO-704
 URL: https://issues.apache.org/jira/browse/TOBAGO-704
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.18, 1.0.19, 1.1.0
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.20




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

[VOTE] Release Tobago 1.0.19

[Bernd Bohmann]

Hello,

I would like to release Tobago 1.0.19

For a detail list please consult the release notes:

http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313372

The version is available at the staging location and the
revision number of the release is 700483 and tagged as tobago-1.0.19.

Staging distribution:

http://people.apache.org/~bommel/repo

Staging repository:

http://people.apache.org/~bommel/repo


The Vote is open for 72h.

[ ] +1
[ ] +0
[ ] -1

[jira] Resolved: (TOBAGO-701) By using a tx:selectBooleanCheckbox component that is readonly the command facet still works

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-701.
--

Resolution: Fixed

> By using a tx:selectBooleanCheckbox component that is readonly the command 
> facet still works
> 
>
> Key: TOBAGO-701
> URL: https://issues.apache.org/jira/browse/TOBAGO-701
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.18
>Reporter: Marcel Menze
>Assignee: Bernd Bohmann
> Fix For: 1.0.19
>
>
> By using a tx:selectBooleanCheckbox component that is readonly the command 
> facet still works

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

[jira] Resolved: (TOBAGO-176) Possibility to render a drop-down in a TabGroup for selection of 'invisible' tabs (Eclipse-style)

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-176.
--

Resolution: Fixed

merging to 1.1.x is still missing

> Possibility to render a drop-down in a TabGroup for selection of 'invisible' 
> tabs (Eclipse-style)
> -
>
> Key: TOBAGO-176
> URL: https://issues.apache.org/jira/browse/TOBAGO-176
> Project: MyFaces Tobago
>  Issue Type: New Feature
>  Components: Core, Themes
>Affects Versions: 1.0.8
> Environment: Any and all
>Reporter: Roland Asmann
>Assignee: Bernd Bohmann
>Priority: Minor
> Fix For: 1.0.19, 1.1.0
>
>
> It would be great to have the possibility to render a drop-down next to all 
> tabs in a TabGroup to use as an overview of currently invisible (but open) 
> tabs. Would be great if it could be realized as part of the component, eg 
> telling the TabGroup how many tabs it can show and any more that are opened 
> push some of the already open ones to the drop-down.
> If this can't be realized as one component, it should at least be possible to 
> reserve some space on the same 'line' as the tabs in the TabGroup to render a 
> drop-down (or a menu or something similar) so users can implement the above 
> functionality themselves.
> One hint from the mailing-list:
> I think this should be included in the TabGroupRenderer. -- Bernd Bohmann

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

[jira] Commented: (TRINIDAD-1220) Partial Lifecycle for Trinidad

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633689#action_12633689
 ] 

Bernd Bohmann commented on TRINIDAD-1220:
-

Hello Alf,

can you attach the example code, please.



> Partial Lifecycle for Trinidad
> --
>
> Key: TRINIDAD-1220
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1220
> Project: MyFaces Trinidad
>  Issue Type: Improvement
>  Components: Components
>Affects Versions: 1.2.9-core
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Attachments: TRINIDAD-1220-trinidad-impl.patch
>
>


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

[jira] Resolved: (TOBAGO-699) pom.xml uses deprecated syntax

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-699.
--

Resolution: Fixed

Thanks for the hint. Applied to 1.1.x and 1.0.x.

The trunk is currently in a alpha state. 
For a production app please use the 1.0.x branch or a release

> pom.xml uses deprecated syntax
> --
>
> Key: TOBAGO-699
> URL: https://issues.apache.org/jira/browse/TOBAGO-699
> Project: MyFaces Tobago
>  Issue Type: Task
>  Components: Build
>Affects Versions: 1.1.0
>Reporter: Paul Rivera
>    Assignee: Bernd Bohmann
>Priority: Trivial
> Fix For: 1.0.19, 1.1.0
>
> Attachments: tobago.patch
>
>
> ${version} is a deprecated maven property. It should be changed to 
> ${pom.version} or ${project.version}. 
> files using ${version}:
> example/tobago-example-assembly/pom.xml
> tobago-assembly/pom.xml

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

[jira] Commented: (TRINIDAD-1220) Partial Lifecycle for Trinidad

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633246#action_12633246
 ] 

Bernd Bohmann commented on TRINIDAD-1220:
-

I think it is the UIViewRoot. You can ignore the warning,


> Partial Lifecycle for Trinidad
> --
>
> Key: TRINIDAD-1220
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1220
> Project: MyFaces Trinidad
>  Issue Type: Improvement
>  Components: Components
>Affects Versions: 1.2.9-core
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Attachments: TRINIDAD-1220-trinidad-impl.patch
>
>


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

[jira] Commented: (TRINIDAD-1220) Partial Lifecycle for Trinidad

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TRINIDAD-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632771#action_12632771
 ] 

Bernd Bohmann commented on TRINIDAD-1220:
-

Have you applied the trinidad impl patch?

> Partial Lifecycle for Trinidad
> --
>
> Key: TRINIDAD-1220
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1220
> Project: MyFaces Trinidad
>  Issue Type: Improvement
>  Components: Components
>Affects Versions: 1.2.9-core
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Attachments: TRINIDAD-1220-trinidad-impl.patch
>
>


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

Re: JSR 314 Comment

[Bernd Bohmann]

Thanks Matthias,

where I can add a comment on the servlet 3.0 spec?

The OSGi spec supports adding and removing servlets:

http://www.osgi.org/javadoc/r4/org/osgi/service/http/HttpService.html

Regards

Bernd

Matthias Wessendorf schrieb:
> btw. in servlet 3.0 they should also add a remove(...) for Filters/Servelts.
> (for same reasons). Currently there is only a add() for these guys.
> 
> -M
> 
> On Thu, Sep 11, 2008 at 9:59 AM, Matthias Wessendorf <[EMAIL PROTECTED]> 
> wrote:
>> I did it.
>> It is funny that you aren't able to do so. I always thought the java
>> COMMUNITY process is actually *open*
>> ...
>>
>> -M
>>
>> On Thu, Sep 11, 2008 at 9:55 AM, Bernd Bohmann
>> <[EMAIL PROTECTED]> wrote:
>>> Hello,
>>>
>>> I would like to add a comment to
>>>
>>> https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=179
>>>
>>> Is anybody allowed to add a comment to this issue.
>>>
>>> I would like to see that the NavigationHandler API allow adding and
>>> removing of navigation cases as well.
>>>
>>> In a dynamic environment it would be nice to add and remove navigation
>>> cases. For example in a OSGi Container you can add and remove a JSF
>>> Application Bundle.
>>>
>>> Regards
>>>
>>> Bernd
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
> 
> 
> 

JSR 314 Comment

[Bernd Bohmann]

Hello,

I would like to add a comment to

https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=179

Is anybody allowed to add a comment to this issue.

I would like to see that the NavigationHandler API allow adding and
removing of navigation cases as well.

In a dynamic environment it would be nice to add and remove navigation
cases. For example in a OSGi Container you can add and remove a JSF
Application Bundle.

Regards

Bernd

Re: Partial Lifecycle for Trinidad

[Bernd Bohmann]

Hello,

has anybody take a look at it?

Regards

Bernd

Scott O'Bryan schrieb:
> I'll take a look at the trim changes Monday.
> 
> Sent from my iPhone
> 
> On Sep 6, 2008, at 9:53 AM, Bernd Bohmann <[EMAIL PROTECTED]>
> wrote:
> 
>>
>>
>> Bernd Bohmann schrieb:
>>>> Also, is there any real way we can take a look at the code before it's
>>>> committed?  Maybe move it to the sandbox first so people can take a
>>>> more
>>>> detailed look at it?
>>>
>>> I would prefer a commit and review policy. I think it should not part of
>>> the sandbox. The new artifact don't need api, imp... it's only a jar
>>> with a LifecycleFactory. I can add the trinidad-partial-lifecycle module
>>> under
>>>
>>> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/
>>>
>>> or
>>>
>>> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/trinidad-sandbox/
>>>
>>
>> For the changes in trindad-impl I would prefer a review and commit
>> policy, maybe there is a better option for the changes.
>>
>>
>> Regards
>>
>> Bernd
> 

[jira] Commented: (MYFACES-1956) Minor performance improvements for org.apache.myfaces.el, org.apache.myfaces.context and org.apache.myfaces.util

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629417#action_12629417
 ] 

Bernd Bohmann commented on MYFACES-1956:


Should not happend, but I will check my ide settings.

> Minor performance improvements for org.apache.myfaces.el, 
> org.apache.myfaces.context and org.apache.myfaces.util
> 
>
> Key: MYFACES-1956
> URL: https://issues.apache.org/jira/browse/MYFACES-1956
> Project: MyFaces Core
>  Issue Type: Improvement
>Affects Versions: 1.2.5-SNAPSHOT
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
>Priority: Minor
> Fix For: 1.2.5-SNAPSHOT
>
> Attachments: MyFaces-10-requests-1.2.4.nps, 
> MyFaces-10-requests-1.2.5-SNAPSHOT.nps, myfaces.el.convert-1.2.4.png, 
> myfaces.el.convert-1.2.5-SNAPSHOT.png, 
> myfaces.el.FacesCompositeELResolver-1.2.4.png, 
> myfaces.el.FacesCompositeELResolver-1.2.5-SNAPSHOT.png
>
>
> Fixed most of the findbugs errors in the performance category and apply many 
> pmd optimization rules
> Made many of the classes final.
> A method argument that is never assigned can be declared final. 
> A local variable assigned only once can be declared final 

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

Re: svn commit: r693059 [1/2] - in /myfaces/core/trunk_1.2.x/impl/src/main/java/org/apache/myfaces: application/ application/jsp/ context/portlet/ context/servlet/ convert/ el/ el/convert/ el/unified/

[Bernd Bohmann]

Hi Simon,

for performance data please look at

https://issues.apache.org/jira/browse/MYFACES-1956

I don't see any reason why anybody should extend classes from
myfaces-impl. I think jsf has enough extensions points. And if someone
need these impls, we should provide these parts in myfaces-commons.

Regards

Bernd

Simon Kitching schrieb:
> Hi Bernd,
> 
> [EMAIL PROTECTED] schrieb:
>> Author: bommel
>> Date: Mon Sep  8 04:42:28 2008
>> New Revision: 693059
>>
>> URL: http://svn.apache.org/viewvc?rev=693059&view=rev
>> Log:
>> (MYFACES-1956) Minor performance improvements for
>> org.apache.myfaces.el, org.apache.myfaces.context and
>> org.apache.myfaces.util ...
>>
>> Apply many of the findbugs and pmd performance rules
>>   
> 
> Changing classes and methods to be final will break any existing user
> code that subclasses it. Allowing users to subclass stuff inside the
> myfaces impl jar seems rather useful to me. Do you have some performance
> measurements that show this kind of lockdown of the core impl code is
> worthwhile? Or is there some reason why users would never want to
> subclass these packages?
> 
> Making a method-parameter final seems less problematic. I'm not quite
> sure what the benefit is though; I would have thought that a decent
> compiler would figure that out itself 99% of the time. Do you have any
> information on what gains we get from this?
> 
> Regards, Simon
> 
> 

[jira] Created: (MYFACES-1956) Minor performance improvements for org.apache.myfaces.el, org.apache.myfaces.context and org.apache.myfaces.util

[Bernd Bohmann (JIRA)]

Minor performance improvements for org.apache.myfaces.el, 
org.apache.myfaces.context and org.apache.myfaces.util


 Key: MYFACES-1956
 URL: https://issues.apache.org/jira/browse/MYFACES-1956
 Project: MyFaces Core
  Issue Type: Improvement
Affects Versions: 1.2.5-SNAPSHOT
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor


Fixed most of the findbugs errors in the performance category and many pmd 
optimization rules
Made many of the classes final.
A method argument that is never assigned can be declared final. 
A local variable assigned only once can be declared final 

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

Re: Partial Lifecycle for Trinidad

[Bernd Bohmann]

ok

Matthias Wessendorf schrieb:
> On Sat, Sep 6, 2008 at 8:50 AM, Bernd Bohmann <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> just created issue TRINIDAD-1220.
>>
>> Can I commit the module to
>>
>> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/trinidad-partial-lifecycle?
> 
> that is fine, to me...
> (please don't add it to the default build process ;-) )
> 
> -M
> 
>> The example patch for trinidad impl is attached to the issue.
>>
>> Regards
>>
>> Bernd
>>
>> Matthias Wessendorf schrieb:
>>> I spoke a bit with Bernd about this on the phone.
>>> I'd love to see this happen.
>>>
>>> Bernd, can you just create an artifact that we can review this ?
>>> Or is it possible that you create an issue in JIRA and you attach
>>> the patch and  lifecycle + factory ?
>>>
>>> -M
>>>
>>> On Sat, Sep 6, 2008 at 6:53 AM, Bernd Bohmann <[EMAIL PROTECTED]> wrote:
>>>> Bernd Bohmann schrieb:
>>>>>> Also, is there any real way we can take a look at the code before it's
>>>>>> committed?  Maybe move it to the sandbox first so people can take a more
>>>>>> detailed look at it?
>>>>> I would prefer a commit and review policy. I think it should not part of
>>>>> the sandbox. The new artifact don't need api, imp... it's only a jar
>>>>> with a LifecycleFactory. I can add the trinidad-partial-lifecycle module
>>>>> under
>>>>>
>>>>> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/
>>>>>
>>>>> or
>>>>>
>>>>> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/trinidad-sandbox/
>>>> For the changes in trindad-impl I would prefer a review and commit
>>>> policy, maybe there is a better option for the changes.
>>>>
>>>>
>>>> Regards
>>>>
>>>> Bernd
>>>>
>>>
>>>
> 
> 
> 

Re: Partial Lifecycle for Trinidad

[Bernd Bohmann]

Hello,

just created issue TRINIDAD-1220.

Can I commit the module to

http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/trinidad-partial-lifecycle?

The example patch for trinidad impl is attached to the issue.

Regards

Bernd

Matthias Wessendorf schrieb:
> I spoke a bit with Bernd about this on the phone.
> I'd love to see this happen.
> 
> Bernd, can you just create an artifact that we can review this ?
> Or is it possible that you create an issue in JIRA and you attach
> the patch and  lifecycle + factory ?
> 
> -M
> 
> On Sat, Sep 6, 2008 at 6:53 AM, Bernd Bohmann <[EMAIL PROTECTED]> wrote:
>>
>> Bernd Bohmann schrieb:
>>>> Also, is there any real way we can take a look at the code before it's
>>>> committed?  Maybe move it to the sandbox first so people can take a more
>>>> detailed look at it?
>>> I would prefer a commit and review policy. I think it should not part of
>>> the sandbox. The new artifact don't need api, imp... it's only a jar
>>> with a LifecycleFactory. I can add the trinidad-partial-lifecycle module
>>> under
>>>
>>> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/
>>>
>>> or
>>>
>>> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/trinidad-sandbox/
>> For the changes in trindad-impl I would prefer a review and commit
>> policy, maybe there is a better option for the changes.
>>
>>
>> Regards
>>
>> Bernd
>>
> 
> 
> 

[jira] Created: (TRINIDAD-1220) Partial Lifecycle for Trinidad

[Bernd Bohmann (JIRA)]

Partial Lifecycle for Trinidad
--

 Key: TRINIDAD-1220
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1220
 Project: MyFaces Trinidad
  Issue Type: Improvement
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann




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

Re: Partial Lifecycle for Trinidad

[Bernd Bohmann]

Bernd Bohmann schrieb:
>> Also, is there any real way we can take a look at the code before it's
>> committed?  Maybe move it to the sandbox first so people can take a more
>> detailed look at it?
> 
> I would prefer a commit and review policy. I think it should not part of
> the sandbox. The new artifact don't need api, imp... it's only a jar
> with a LifecycleFactory. I can add the trinidad-partial-lifecycle module
> under
> 
> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/
> 
> or
> 
> http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/trinidad-sandbox/

For the changes in trindad-impl I would prefer a review and commit
policy, maybe there is a better option for the changes.


Regards

Bernd

Re: Partial Lifecycle for Trinidad

[Bernd Bohmann]

Hello Scott,

Scott O'Bryan schrieb:
> Bernd,
> 
> So to get this straight, is this going to be an extra jar file that you
> add to the classpath and allows for partial lifecycle processing or is
> this a change to the Trinidad impl itself?
> 
It's an optional jar file. But for a working partial lifecycle some of
the renderer and javascript must be changed a little bit. The changes
don't effect the old unoptimized lifecycle.

> If the latter, I think we need to be very careful about changing the
> unoptimized lifecycle until people have a chance to wrap their heads
> around it.  If the former, then I would be willing to take a look, I had
> some similar ideas recently and think this can only benifit the project.

Certainly it should be reviewed by more people. I don't know all
internals of trindad.
> 
> Also, is there any real way we can take a look at the code before it's
> committed?  Maybe move it to the sandbox first so people can take a more
> detailed look at it?

I would prefer a commit and review policy. I think it should not part of
the sandbox. The new artifact don't need api, imp... it's only a jar
with a LifecycleFactory. I can add the trinidad-partial-lifecycle module
under

http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/

or

http://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/trinidad-sandbox/

> 
> Also I don't undersand your todo's..  I have been off for a month with a
> new child so I suppose it's possible I'm missing something.

Without the code you can't understand the todo's.
The list is only a summery of the todo's in the code.
>

Regards

Bernd

Partial Lifecycle for Trinidad

[Bernd Bohmann]

Hello,

I just started with a partial lifecycle module for trinidad.
The partial lifecyle is currently an own artifact. The artifact
overrides the default lifecyle and supports partial processDecodes,
processValidators, processUpdates and rendering if the request parameter
partialTarget is present.

If no objections I will commit the trindad-partial-lifecycle module and
create an issue with the attached trinidad-impl diff for discussion.

Regards

Bernd

Following todo's:

Is partialTarget a valid choice for the parameter name?
partialRequest from inside Tree or Table
source inside a partialTarget
decode SubForms?
SubForms
Messages
NavigationTree
broadcast Events UIViewRoot has no public method
writeState is performed by patched FormRenderer
...

[RESULT] [VOTE] Release Tobago 1.0.18

[Bernd Bohmann]

The vote has passed with the following votes:

+1
lofwyr (binding)
matzew (binding)
bommel (binding)
weber (binding)

I will proceed with the next steps.

Regards

Bernd

Bernd Bohmann schrieb:
> Hello,
> 
> I would like to release Tobago 1.0.18
> 
> For a detail list please consult the release notes:
> 
> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313150
> 
> The version is available at the staging location and the
> revision number of the release is 688030 and tagged as tobago-1.0.18.
> 
> Staging distribution:
> 
> http://people.apache.org/~bommel/repo
> 
> Staging repository:
> 
> http://people.apache.org/~bommel/repo
> 
> 
> The Vote is open for 72h.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> 
> 

Re: [VOTE] Release Tobago 1.0.18

[Bernd Bohmann]

+1

Regards

Bernd

Bernd Bohmann schrieb:
> Hello,
> 
> I would like to release Tobago 1.0.18
> 
> For a detail list please consult the release notes:
> 
> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313150
> 
> The version is available at the staging location and the
> revision number of the release is 688030 and tagged as tobago-1.0.18.
> 
> Staging distribution:
> 
> http://people.apache.org/~bommel/repo
> 
> Staging repository:
> 
> http://people.apache.org/~bommel/repo
> 
> 
> The Vote is open for 72h.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> 
> 

[VOTE] Release Tobago 1.0.18

[Bernd Bohmann]

Hello,

I would like to release Tobago 1.0.18

For a detail list please consult the release notes:

http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313150

The version is available at the staging location and the
revision number of the release is 688030 and tagged as tobago-1.0.18.

Staging distribution:

http://people.apache.org/~bommel/repo

Staging repository:

http://people.apache.org/~bommel/repo


The Vote is open for 72h.

[ ] +1
[ ] +0
[ ] -1

Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)

[Bernd Bohmann]

Thanks Manfred,

maybe we should open a feature request at Atlassian.

Regards

Bernd

Manfred Geiler schrieb:
> Ok, re-enabled the "fix version" on the edit screen.
> --Manfred
> 
> On Thu, Aug 21, 2008 at 10:50 AM, Matthias Wessendorf <[EMAIL PROTECTED]> 
> wrote:
>> On Thu, Aug 21, 2008 at 10:42 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
>>> Hi,
>>>
>>> isn't the fixVersion field needed for unresolved issues to prepare the 
>>> roadmap?
>> yes. I think the main point is, that actually bug-filers abuse the field.
>> They understand it as a "wish list", like "you have to fix my bug in
>> version 'yesterday'" :)
>>
>> -Matthias
>>
>>>
>>> Regards,
>>>Volker
>>>
>>> 2008/8/21 Manfred Geiler <[EMAIL PROTECTED]>:
>>>> The "Fix version" field is still there on the "Resolve Issue" page!
>>>> That is where it belongs to. Right?
>>>>
>>>> But: I see that there are 964 issues (in all MyFaces projects) with
>>>> Status "Resolved" that have no "Fix Version". Which is weird!
>>>>
>>>> What I COULD do is (re)enable the "fix version" on the Edit Screen.
>>>> But I CANNOT restrict it to committers only. There is no way in Jira
>>>> AFAIK.
>>>>
>>>> What I suggest:
>>>> - Leave it that way. Fix versions normally set during resolve workflow.
>>>> - Fix missing fix versions by doing bulk operations ("Fix version" is
>>>> editable there)
>>>>
>>>> Thoughts?
>>>>
>>>> --Manfred
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Aug 21, 2008 at 10:11 AM, Bernd Bohmann
>>>> <[EMAIL PROTECTED]> wrote:
>>>>> Hello Manfred,
>>>>>
>>>>> how can I edit the fix version field, now?
>>>>>
>>>>> I would like to prepare the tobago-1.0.18 release.
>>>>>
>>>>> Can you revert the MyFaces Screen configuration for Tobago.
>>>>>
>>>>> Regards
>>>>>
>>>>> Bernd
>>>>>
>>>>> Manfred Geiler schrieb:
>>>>>> The Jira permissions settings cannot be adjusted on field level.
>>>>>> As a workaround I added a new "MyFaces Screen" configuration to Jira.
>>>>>> With this configuration the "Fix version" field should no longer show
>>>>>> up on the "Edit" screen.
>>>>>> I activated this scheme for Trinidad.
>>>>>> Please check it out. If ok, I will activate this scheme for all other
>>>>>> MyFaces projects as well.
>>>>>>
>>>>>> --Manfred
>>>>>>
>>>>>>
>>>>>> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]> 
>>>>>> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> we had the discussion already in the past.
>>>>>>> I'd love to see that the fix-version/s is not! editable by filers.
>>>>>>>
>>>>>>> Greetings,
>>>>>>> Matthias
>>>>>>>
>>>>>>>
>>>>>>> -- Forwarded message --
>>>>>>> From: Rottstock, Sven <[EMAIL PROTECTED]>
>>>>>>> Date: Tue, Aug 5, 2008 at 10:35 AM
>>>>>>> Subject: [Trinidad] Missing issue in 1.0.8
>>>>>>> To: dev@myfaces.apache.org
>>>>>>>
>>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>> i have seen that the patch of TRINIDAD-1010 was not included in the
>>>>>>> 1.0.8 release but was listed in the release notes. Is there anything
>>>>>>> wrong with it or was the patch only forgotten to submit?
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Sven
>>>>>>>
>>>>>>>
>>>
>>>
>>> --
>>> inexso - information exchange solutions GmbH
>>> Bismarckstraße 13 | 26122 Oldenburg
>>> Tel.: +49 441 4082 356 |
>>> FAX: +49 441 4082 355 | www.inexso.de
>>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> Need JSF and Web 2.0?
>> http://code.google.com/p/facesgoodies
>>
>> further stuff:
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> mail: matzew-at-apache-dot-org
> 

Re: Jira configuration ? (was Fwd: [Trinidad] Missing issue in 1.0.8)

[Bernd Bohmann]

Hello Manfred,

how can I edit the fix version field, now?

I would like to prepare the tobago-1.0.18 release.

Can you revert the MyFaces Screen configuration for Tobago.

Regards

Bernd

Manfred Geiler schrieb:
> The Jira permissions settings cannot be adjusted on field level.
> As a workaround I added a new "MyFaces Screen" configuration to Jira.
> With this configuration the "Fix version" field should no longer show
> up on the "Edit" screen.
> I activated this scheme for Trinidad.
> Please check it out. If ok, I will activate this scheme for all other
> MyFaces projects as well.
> 
> --Manfred
> 
> 
> On Tue, Aug 5, 2008 at 10:27 PM, Matthias Wessendorf <[EMAIL PROTECTED]> 
> wrote:
>> Hi,
>>
>> we had the discussion already in the past.
>> I'd love to see that the fix-version/s is not! editable by filers.
>>
>> Greetings,
>> Matthias
>>
>>
>> -- Forwarded message --
>> From: Rottstock, Sven <[EMAIL PROTECTED]>
>> Date: Tue, Aug 5, 2008 at 10:35 AM
>> Subject: [Trinidad] Missing issue in 1.0.8
>> To: dev@myfaces.apache.org
>>
>>
>> Hi Devs,
>>
>> i have seen that the patch of TRINIDAD-1010 was not included in the
>> 1.0.8 release but was listed in the release notes. Is there anything
>> wrong with it or was the patch only forgotten to submit?
>>
>> Regards,
>>
>> Sven
>>
>>
> 

Re: Continuum environment upgrade

[Bernd Bohmann]

+1 for option (1)

Bernd

Simon Kitching schrieb:
> Hi All,
> 
> I managed to get continuum-1.1 installed and running on
> myfaces.zones.apache.org, and also to get the user accounts loaded into
> the new instance.
> 
> However I just cannot get the existing build configuration to load. The
> load appears to go ok, but continuum just fails to restart afterwards.
> 
> So the options are:
> (1) go with new installation, and recreate the project config
> (2) move to using the central server at vmbuild.apache.org (which will
> mean creating all new user accounts, as well as manually recreating the
> project config)
> (3) leave myfaces on continuum-1.1-beta-2 forever
> (4) someone else can have a try
> 
> Personally, I'm happy with (1). Adding the projects again is only an
> hour's work or so.
> 
> I think that we work our install hard enough to justify using a separate
> server rather than a central one.
> 
> Opinions?
> 
> Regards,
> Simon
> 
> 

[jira] Created: (TOBAGO-693) Allow setting the converter with tc:attribute in facelets, similar setting the action or actionlistener

[Bernd Bohmann (JIRA)]

Allow setting the converter with tc:attribute in facelets, similar setting the 
action or actionlistener
---

 Key: TOBAGO-693
 URL: https://issues.apache.org/jira/browse/TOBAGO-693
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Facelets
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0




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

[jira] Created: (TOBAGO-692) Support for modal css style for popup

[Bernd Bohmann (JIRA)]

Support for modal css style for popup 
--

 Key: TOBAGO-692
 URL: https://issues.apache.org/jira/browse/TOBAGO-692
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Themes
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0


A modal popup should provide a tobago-popup-modal style

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

[jira] Created: (TOBAGO-691) nonmodal popup blocks the page

[Bernd Bohmann (JIRA)]

nonmodal popup blocks the page 
---

 Key: TOBAGO-691
 URL: https://issues.apache.org/jira/browse/TOBAGO-691
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Themes
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0




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

[jira] Created: (TOBAGO-690) Markup attribute for Label Extension tags doesn't work

[Bernd Bohmann (JIRA)]

Markup attribute for Label Extension tags doesn't work
--

 Key: TOBAGO-690
 URL: https://issues.apache.org/jira/browse/TOBAGO-690
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Facelets
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0


If you set the markup attribute on tx tags the attribute isn't copied to the 
underlying label

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

[jira] Commented: (TOBAGO-683) Sheet header resizer is not rendered correct in FF3

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618752#action_12618752
 ] 

Bernd Bohmann commented on TOBAGO-683:
--

just checked in a fix 
tested on firefox 2,3 ie7 for 1.0.18

A version with more changes for 1.1.0 is still untested. I will commit the 
change later 

> Sheet header resizer is not rendered correct in FF3
> ---
>
> Key: TOBAGO-683
> URL: https://issues.apache.org/jira/browse/TOBAGO-683
> Project: MyFaces Tobago
>  Issue Type: Bug
>Affects Versions: 1.0.17
> Environment: Mozilla Firefox 3.0
>Reporter: Volker Weber
>Assignee: Bernd Bohmann
> Fix For: 1.0.18, 1.1.0
>
>


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

[jira] Created: (TOBAGO-689) Extension tag for tc:separator

[Bernd Bohmann (JIRA)]

Extension tag for tc:separator
--

 Key: TOBAGO-689
 URL: https://issues.apache.org/jira/browse/TOBAGO-689
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core, Facelets
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0


Support for 

 

instead of 


   
  
   


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

[jira] Commented: (TOBAGO-688) Support for new protocol vfszip: introduced by JBoss 5.0.0

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614854#action_12614854
 ] 

Bernd Bohmann commented on TOBAGO-688:
--

Can you send a list of the content for the directory 
vfszip:/home/stefan/as/jboss-5.0.0.CR1/server/devel/deploy/myapp.ear.
Or is vfszip:/home/stefan/as/jboss-5.0.0.CR1/server/devel/deploy/myapp.ear a 
file?

> Support for new protocol vfszip: introduced by JBoss 5.0.0
> --
>
> Key: TOBAGO-688
> URL: https://issues.apache.org/jira/browse/TOBAGO-688
> Project: MyFaces Tobago
>  Issue Type: Bug
>Affects Versions: 1.1.0
> Environment: JBoss AS 5.0.0.CR1, openSuse 11.0 amd64, Java sun sdk 
> 1.6.0_06
>Reporter: Stefan Hedtfeld
>Assignee: Bernd Bohmann
> Fix For: 1.0.18, 1.1.0
>
> Attachments: ResourceLocator.java.diff
>
>
> I'm using tobago-1.1.0-SNAPSHOT on JBoss 5.0.0.CR1. Deploying my application 
> failed due to an exception in ResourceLocator because JBoss introduced a new 
> protocol vfszip: for accessing archives. It gives a warning "Unknown protocol 
> 'vfszip:/home/stefan/as/jboss-5.0.0.CR1/server/devel/deploy/myapp.ear/tobago-theme-speyside-1.1.0-SNAPSHOT.jar/META-INF/tobago-theme.xml'"
>  and then fails when creating a File instance without the file: protocol.
> I tried several ways to access the file correctly, the only way seems to be 
> to handle this like an archive but going up to directories. I've attached a 
> diff to give you an impression - I'm not sure if it is the correct approach 
> to handle this in tobago as I would think if JBoss introduces a new protocol 
> then this should not impact tobago.

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

Re: code style for new commons modules?

[Bernd Bohmann]

Hello,

+1 for the myfaces-tobago code style.

The the myfaces-tobago code style is primarily the sun code style.
Some addtional requirements are:
tabWith is 2,
need Braces ...


Regards

Bernd

Volker Weber schrieb:
> Hi,
> 
> +1 for the code style used in myfaces-tobago ;-)
> 
> Can someone describe the differences between sun and myfaces code styles?
> 
> 
> Regards,
> Volker
> 
> 2008/7/12 simon <[EMAIL PROTECTED]>:
>> Hi,
>>
>> Should the new commons modules use the traditional MyFaces code style,
>> the Sun code style?
>>
>> Right now, it is a mix with some files in one style, and some files in
>> another (probably about 65% Sun style).
>>
>> Regards,
>> Simon
>>
>>
> 
> 
> 

Re: commons logging again

[Bernd Bohmann]

Hello Werner,

I would like to replace commons-logging with slf4j:-)

Regards

Bernd

Werner Punz schrieb:
> Hello everyone, we have been using commons-logging the past years.
> I am not sure if it is a good idea,
> first of all java has a decent logging api, which would allow us to
> eliminate the logging dependency.
> Secondly,I have not looked into the code yet, but there are a load
> of references that commons logging has problems due to messing around
> with the classloader.
> Projects like Tapestry already have moved away towards SLF4J which
> apparently is better.
> 
> Whats your opinion should we keep the commons logging
> references?
> 
> Werner
> 
> 

[jira] Resolved: (TOBAGO-680) Allow relative id of the popup in popupReferenceTag

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-680.
--

Resolution: Fixed

> Allow relative id of the popup in popupReferenceTag
> ---
>
> Key: TOBAGO-680
> URL: https://issues.apache.org/jira/browse/TOBAGO-680
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Core, Facelets
>    Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
> Fix For: 1.0.18, 1.1.0
>
>


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

Re: cleaning up whitespace in source files

[Bernd Bohmann]

+1 for b

Regards

Bernd

Matthias Wessendorf schrieb:
> On Wed, Jul 2, 2008 at 7:28 PM, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
>> Hi All,
>>
>> In the new checkstyle rules file I enabled checks for tab characters, as the
>> myfaces convention is (AFAIK) to use 4 spaces, not tabs. However the
>> checkstyle report points out a lot of files containing tabs.
>>
>> It's no big deal, but do we want to:
>> (a) disable the checkstyle rule and ignore tabs or
>> (b) fix them?
> 
> +1 for (b)
> 
> -M
> 
>> Tabs are a minor nuisance when viewing the source as some tools render 4
>> spaces, some 8.
>>
>> I've written a simple shellscript that can clean this up very easily, and am
>> happy to do so. The script also removes trailing whitespace from lines, of
>> which we also appear to have quite a lot.
>>
>> But doing this will create some large commit messages and make comparing
>> files with past versions noisier. It can also cause svn conflicts if people
>> have modified files they have not yet committed, unless they run the cleanup
>> script against their own working dir before doing svn update.
>>
>> So, option (a) or (b)?
>>
>> Regards, Simon
>>
>>
> 
> 
> 

[jira] Created: (TOBAGO-687) Readonly support for tc:selectOneRadio

[Bernd Bohmann (JIRA)]

Readonly support for tc:selectOneRadio
--

 Key: TOBAGO-687
 URL: https://issues.apache.org/jira/browse/TOBAGO-687
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Themes
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0




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

[jira] Created: (TOBAGO-685) Caches in ResourceManagerImpl should be Thread save

[Bernd Bohmann (JIRA)]

Caches in ResourceManagerImpl should be Thread save
---

 Key: TOBAGO-685
 URL: https://issues.apache.org/jira/browse/TOBAGO-685
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.18, 1.1.0
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann




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

[jira] Commented: (TOBAGO-682) Facelets, page is not rendered correct, it toggles from ok - wrong - ok - wrong... by executing an actionListener

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607917#action_12607917
 ] 

Bernd Bohmann commented on TOBAGO-682:
--

Can you attach the page, please?

> Facelets, page is not rendered correct, it toggles from ok - wrong - ok - 
> wrong... by executing an actionListener
> -
>
> Key: TOBAGO-682
> URL: https://issues.apache.org/jira/browse/TOBAGO-682
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Facelets
>Affects Versions: 1.0.18
> Environment: Facelets 1.1.14, MyFaces 1.1.6 snap (08.01.2008), Tobago 
> 1.0.18 snap (13.06.2008) 
>Reporter: Guido Dubois
> Attachments: form_err.png, form_err2.png, form_ok.png
>
>
> If I start the site, I get the right rendered result like in picture (1). But 
> the following warnings will be logged.
> 02:43:18,927 INFO  [PageRendererBase] actionPosition='10px,115px,20px,12px'
> 02:43:19,130 ERROR [STDERR] 14.06.2008 02:43:19 
> com.sun.facelets.impl.DefaultFacelet refresh
> INFO: 
> Facelet[/file:/C:/Programme/jboss-4.2.2.GA/server/default/tmp/deploy/tmp2320gut_prodis3EAR.ear-contents/gut_prodis3Client-exp.war/WEB-INF/lib/tobago-facelets-1.0.18-SNAPSHOT.jar!/META-INF/in.xml]
>  was modified @ 02:43:19, flushing component applied @ 02:43:08
> 02:43:19,130 ERROR [STDERR] 14.06.2008 02:43:19 
> com.sun.facelets.impl.DefaultFacelet refresh
> INFO: 
> Facelet[/file:/C:/Programme/jboss-4.2.2.GA/server/default/tmp/deploy/tmp2320gut_prodis3EAR.ear-contents/gut_prodis3Client-exp.war/WEB-INF/lib/tobago-facelets-1.0.18-SNAPSHOT.jar!/META-INF/in.xml]
>  was modified @ 02:43:19, flushing component applied @ 02:43:08
> 02:43:19,130 WARN  [GridLayoutRenderer] Unable to calculate Height for token 
> '1*'! using 'fixed' , component:page:_id77 is Panel
> 02:43:19,130 WARN  [GridLayoutRenderer] Unable to calculate Height for token 
> '1*'! using 'fixed' , component:page:_id80 is Panel
> 02:43:19,130 WARN  [GridLayoutRenderer] Unable to calculate Height for token 
> '1*'! using 'fixed' , component:page:_id77 is Panel
> 02:43:19,130 WARN  [GridLayoutRenderer] Unable to calculate Height for token 
> '1*'! using 'fixed' , component:page:_id80 is Panel
> 02:43:19,146 INFO  [PageRenderer] get clientDebugSeverity = 2;hide
> 02:43:19,287 INFO  [DebugPhaseListener] Total response time : 375 milliseconds
> 
> Then I click a flag on the left side - there will only be executed an 
> actionListener to switch the language - and I will get a wrong rendered site 
> like in pictute (2) with the following log info
> 02:43:58,604 INFO  [PageRendererBase] actionPosition='10px,115px,20px,12px'
> 02:43:58,713 ERROR [STDERR] 14.06.2008 02:43:58 
> com.sun.facelets.impl.DefaultFacelet refresh
> INFO: 
> Facelet[/file:/C:/Programme/jboss-4.2.2.GA/server/default/tmp/deploy/tmp2320gut_prodis3EAR.ear-contents/gut_prodis3Client-exp.war/WEB-INF/lib/tobago-facelets-1.0.18-SNAPSHOT.jar!/META-INF/in.xml]
>  was modified @ 02:43:58, flushing component applied @ 02:43:21
> 02:43:58,713 ERROR [STDERR] 14.06.2008 02:43:58 
> com.sun.facelets.impl.DefaultFacelet refresh
> INFO: 
> Facelet[/file:/C:/Programme/jboss-4.2.2.GA/server/default/tmp/deploy/tmp2320gut_prodis3EAR.ear-contents/gut_prodis3Client-exp.war/WEB-INF/lib/tobago-facelets-1.0.18-SNAPSHOT.jar!/META-INF/in.xml]
>  was modified @ 02:43:58, flushing component applied @ 02:43:21
> 02:43:58,713 ERROR [STDERR] 14.06.2008 02:43:58 
> com.sun.facelets.impl.DefaultFacelet refresh
> INFO: 
> Facelet[/file:/C:/Programme/jboss-4.2.2.GA/server/default/tmp/deploy/tmp2320gut_prodis3EAR.ear-contents/gut_prodis3Client-exp.war/WEB-INF/lib/tobago-facelets-1.0.18-SNAPSHOT.jar!/META-INF/in.xml]
>  was modified @ 02:43:58, flushing component applied @ 02:43:21
> 02:43:58,713 ERROR [STDERR] 14.06.2008 02:43:58 
> com.sun.facelets.impl.DefaultFacelet refresh
> INFO: 
> Facelet[/file:/C:/Programme/jboss-4.2.2.GA/server/default/tmp/deploy/tmp2320gut_prodis3EAR.ear-contents/gut_prodis3Client-exp.war/WEB-INF/lib/tobago-facelets-1.0.18-SNAPSHOT.jar!/META-INF/in.xml]
>  was modified @ 02:43:58, flushing component applied @ 02:43:21
> 02:43:58,745 INFO  [PageRenderer] get clientDebugSeverity = 2;hide
> 02:43:58,776 INFO  [DebugPhaseListener] Total response time : 188 milliseconds
> 
> If I click the falg again, I get the right site again. It toggles by clicken 
> right - wrong - right - wrong
> ++

[jira] Created: (TOBAGO-680) Allow relative id of the popup in popupReferenceTag

[Bernd Bohmann (JIRA)]

Allow relative id of the popup in popupReferenceTag
---

 Key: TOBAGO-680
 URL: https://issues.apache.org/jira/browse/TOBAGO-680
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core, Facelets
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0




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

[jira] Created: (TOBAGO-676) Avoid using attribute Map for menuAcceleratorKeys

[Bernd Bohmann (JIRA)]

Avoid using attribute Map for menuAcceleratorKeys
-

 Key: TOBAGO-676
 URL: https://issues.apache.org/jira/browse/TOBAGO-676
 Project: MyFaces Tobago
  Issue Type: Improvement
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor
 Fix For: 1.0.18




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

[jira] Created: (TOBAGO-675) A redisplayed popup blocks the page

[Bernd Bohmann (JIRA)]

A redisplayed popup blocks the page
---

 Key: TOBAGO-675
 URL: https://issues.apache.org/jira/browse/TOBAGO-675
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Themes
Affects Versions: 1.0.17
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.18, 1.1.0




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

Re: [VOTE] myfaces-extensions as a new myfaces sub-project

[Bernd Bohmann]

+1

Scott O'Bryan schrieb:
> +1
> 
> Matthias Wessendorf wrote:
>> +1
>>
>> On Mon, Jun 2, 2008 at 9:13 AM, Volker Weber <[EMAIL PROTECTED]> wrote:
>>  
>>> +1
>>>
>>>
>>> Regards,
>>>Volker
>>>
>>> 2008/6/2 Gerhard Petracek <[EMAIL PROTECTED]>:
>>>
 hello,

 we discussed whether or not we should start a new myfaces sub-project
 (details at: [1] and [2]).

 name:
 myfaces-extensions

 description:
 place for small innovative projects (which are beyond the current "std.
 mechanisms" of jsf)
 currently these small projects are: aspect-el, sev-en and scripting

 so - after the positive response let's vote!
 (there will be a separated discussion + vote concerning the names.)

 ---

 [ ] +1 for: myfaces-extensions should become a myfaces sub-project
 [ ] +0
 [ ] -1 for: myfaces-extensions shouldn't become a myfaces sub-project
 ---


 regards,
 gerhard

 [1]
 http://www.nabble.com/-PROPOSAL--myfaces-extensions-to17466179.html#a17466179

 [2]
 http://www.nabble.com/Re%3A--PROPOSAL--myfaces-extensions-p17474665.html


 -- 

 http://www.irian.at

 Your JSF powerhouse -
 JSF Consulting, Development and
 Courses in English and German

 Professional Support for Apache MyFaces
   
>>>
>>> -- 
>>> inexso - information exchange solutions GmbH
>>> Bismarckstraße 13 | 26122 Oldenburg
>>> Tel.: +49 441 4082 356 |
>>> FAX: +49 441 4082 355 | www.inexso.de
>>>
>>> 
>>
>>
>>
>>   
> 
> 

[RESULT] [VOTE] Release Tobago 1.0.17

[Bernd Bohmann]

The vote has passed with the following results:


+1
lofwyr (binding)
weber (binding)
idus
bommel (binding)

I will proceed with the next steps.

Regards

Bernd

Bernd Bohmann schrieb:
> Hello,
> 
> I would like to release Tobago 1.0.17,
> 
> For a detail list please consult the release notes:
> 
> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313084
> 
> The version is available at the staging location and the
> revision number of the release is 656789 and tagged as tobago-1.0.17.
> 
> Staging distribution:
> 
> http://people.apache.org/~bommel/repo
> 
> Staging repository:
> 
> http://people.apache.org/~bommel/repo
> 
> 
> The Vote is open for 72h.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> 

Re: [VOTE] Release Tobago 1.0.17

[Bernd Bohmann]

Here is my

+1

Bernd

Arvid Hülsebus schrieb:
> +1
> 
> Regards
> Arvid
> 
> Bernd Bohmann wrote:
>> Hello,
>>
>> I would like to release Tobago 1.0.17,
>>
>> For a detail list please consult the release notes:
>>
>> http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313084
>>
>>
>> The version is available at the staging location and the
>> revision number of the release is 656789 and tagged as tobago-1.0.17.
>>
>> Staging distribution:
>>
>> http://people.apache.org/~bommel/repo
>>
>> Staging repository:
>>
>> http://people.apache.org/~bommel/repo
>>
>>
>> The Vote is open for 72h.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>>
>>   
> 

[VOTE] Release Tobago 1.0.17

[Bernd Bohmann]

Hello,

I would like to release Tobago 1.0.17,

For a detail list please consult the release notes:

http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273&styleName=Html&version=12313084

The version is available at the staging location and the
revision number of the release is 656789 and tagged as tobago-1.0.17.

Staging distribution:

http://people.apache.org/~bommel/repo

Staging repository:

http://people.apache.org/~bommel/repo


The Vote is open for 72h.

[ ] +1
[ ] +0
[ ] -1

[jira] Resolved: (TOBAGO-546) selectOneChoice should support coloring and images

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-546.
--

Resolution: Fixed

> selectOneChoice should support coloring and images
> --
>
> Key: TOBAGO-546
> URL: https://issues.apache.org/jira/browse/TOBAGO-546
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Core, Themes
>Affects Versions: 1.0.12, 1.0.16
>Reporter: Rainer Rohloff
>    Assignee: Bernd Bohmann
> Fix For: 1.0.17, 1.0.13
>
>
> Example:
> 
> 
> option.information, select.information {
>   background-position:left middle;
>   background-repeat:no-repeat;
>   padding-left:17px;
>   background-image: url(./information.gif);
>   color: yellow;
>   vertical-align:middle;
> }
> option.hinweis, select.hinweis {
>   background-position:left middle;
>   background-repeat:no-repeat;
>   padding-left:17px;
>   background-image: url(./hinweis.gif);
>   color:blue;
>   vertical-align:middle;
> }
> 
> 
> 
>   Eintrag 1
>   Eintrag 2
>   Eintrag 3
>   Eintrag 4
>   Eintrag 5
> 
> 
> 
> The API from SelectItem must then support markup:
> public SelectItem(Object value,
>   String label,
>   String description,
>   String image,
>   String markup)
> if "image" is set, then  can be rendered as 
>   Eintrag 3
> restrictions:
> * MS IE does not rendert the pictures - however the different colors.

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

[jira] Created: (TOBAGO-667) Subform support for toolbar

[Bernd Bohmann (JIRA)]

Subform support for toolbar
---

 Key: TOBAGO-667
 URL: https://issues.apache.org/jira/browse/TOBAGO-667
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core, Themes
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor
 Fix For: 1.1.0




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

[jira] Reopened: (TOBAGO-632) PanelRenderer should write style attribute

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann reopened TOBAGO-632:
--


Revert for 1.0.17 

> PanelRenderer should write style attribute
> --
>
> Key: TOBAGO-632
> URL: https://issues.apache.org/jira/browse/TOBAGO-632
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Themes
>Reporter: Volker Weber
>    Assignee: Bernd Bohmann
>Priority: Minor
> Fix For: 1.1.0
>
>
> tc:panel needs the width and height values to enable styling via markup

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

[jira] Resolved: (TOBAGO-666) Selection of pageable sheet doesn't work

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-666.
--

Resolution: Fixed

> Selection of pageable sheet doesn't work
> 
>
> Key: TOBAGO-666
> URL: https://issues.apache.org/jira/browse/TOBAGO-666
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Themes
>Affects Versions: 1.0.16
>Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Fix For: 1.0.17
>
>


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

[jira] Reopened: (TOBAGO-546) selectOneChoice should support coloring and images

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann reopened TOBAGO-546:
--


> selectOneChoice should support coloring and images
> --
>
> Key: TOBAGO-546
> URL: https://issues.apache.org/jira/browse/TOBAGO-546
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Core, Themes
>Affects Versions: 1.0.12
>Reporter: Rainer Rohloff
>    Assignee: Bernd Bohmann
> Fix For: 1.0.13
>
>
> Example:
> 
> 
> option.information, select.information {
>   background-position:left middle;
>   background-repeat:no-repeat;
>   padding-left:17px;
>   background-image: url(./information.gif);
>   color: yellow;
>   vertical-align:middle;
> }
> option.hinweis, select.hinweis {
>   background-position:left middle;
>   background-repeat:no-repeat;
>   padding-left:17px;
>   background-image: url(./hinweis.gif);
>   color:blue;
>   vertical-align:middle;
> }
> 
> 
> 
>   Eintrag 1
>   Eintrag 2
>   Eintrag 3
>   Eintrag 4
>   Eintrag 5
> 
> 
> 
> The API from SelectItem must then support markup:
> public SelectItem(Object value,
>   String label,
>   String description,
>   String image,
>   String markup)
> if "image" is set, then  can be rendered as 
>   Eintrag 3
> restrictions:
> * MS IE does not rendert the pictures - however the different colors.

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

[jira] Created: (TOBAGO-666) Selection of pageable sheet doesn't work

[Bernd Bohmann (JIRA)]

Selection of pageable sheet doesn't work


 Key: TOBAGO-666
 URL: https://issues.apache.org/jira/browse/TOBAGO-666
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Themes
Affects Versions: 1.0.16
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.17




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

[jira] Created: (TOBAGO-665) Move onComponentCreated to Renderer

[Bernd Bohmann (JIRA)]

Move onComponentCreated to Renderer
---

 Key: TOBAGO-665
 URL: https://issues.apache.org/jira/browse/TOBAGO-665
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core, Themes
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.1.0




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

[jira] Created: (TOBAGO-664) Avoid buffering of the request or request parts as much as possible

[Bernd Bohmann (JIRA)]

Avoid buffering of the request or request parts as much as possible
---

 Key: TOBAGO-664
 URL: https://issues.apache.org/jira/browse/TOBAGO-664
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core, Themes
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.1.0




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

[jira] Resolved: (TOBAGO-663) Button: defaultCommand doesn't call onsubmit functions.

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-663.
--

Resolution: Fixed

> Button: defaultCommand doesn't call onsubmit functions.
> ---
>
> Key: TOBAGO-663
> URL: https://issues.apache.org/jira/browse/TOBAGO-663
> Project: MyFaces Tobago
>  Issue Type: Bug
>Affects Versions: 1.0.16
>Reporter: Udo Schnurpfeil
>Assignee: Udo Schnurpfeil
> Fix For: 1.0.17, 1.1.0
>
>


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

[jira] Resolved: (TOBAGO-661) Add immediate update check for UIReload

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-661.
--

Resolution: Fixed

> Add immediate update check for UIReload
> ---
>
> Key: TOBAGO-661
> URL: https://issues.apache.org/jira/browse/TOBAGO-661
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.0.16
>    Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
> Fix For: 1.0.17, 1.1.0
>
>


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

[jira] Resolved: (TOBAGO-647) Setting the converter of the timeInput in the datePicker depending on the supplied date and time pattern

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-647.
--

Resolution: Fixed

> Setting the converter of the timeInput in the datePicker depending on the 
> supplied date and time pattern 
> -
>
> Key: TOBAGO-647
> URL: https://issues.apache.org/jira/browse/TOBAGO-647
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Themes
>Affects Versions: 1.0.16
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
>Priority: Minor
> Fix For: 1.0.17, 1.1.0
>
>


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

[jira] Resolved: (TOBAGO-662) Use LOG.isInfoEnabled() for LOG.info()

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-662.
--

Resolution: Fixed

> Use LOG.isInfoEnabled() for LOG.info()
> --
>
> Key: TOBAGO-662
> URL: https://issues.apache.org/jira/browse/TOBAGO-662
> Project: MyFaces Tobago
>  Issue Type: Improvement
>Affects Versions: 1.0.16
>    Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
> Fix For: 1.0.17, 1.1.0
>
>


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

[jira] Resolved: (TOBAGO-660) Reload facet doesn't work since TOBAGO-312

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-660.
--

Resolution: Fixed

> Reload facet doesn't work since TOBAGO-312
> --
>
> Key: TOBAGO-660
> URL: https://issues.apache.org/jira/browse/TOBAGO-660
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.11, 1.0.12, 1.0.13, 1.0.14, 1.0.15, 1.0.16
>Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Fix For: 1.0.17
>
>


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

[jira] Resolved: (TOBAGO-646) Allow to configure an unsorted image for sorted columns in the sheet

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-646.
--

Resolution: Fixed

> Allow to configure an unsorted image for sorted columns in the sheet
> 
>
> Key: TOBAGO-646
> URL: https://issues.apache.org/jira/browse/TOBAGO-646
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Themes
>Affects Versions: 1.0.16
>    Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
>Priority: Minor
> Fix For: 1.0.17, 1.1.0
>
>


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

Re: Exporter new syntax discussion

[Bernd Bohmann]

+1 for the new syntax

Glauco P. Gomes schrieb:
> +1
> 
> I'm using the old component in one project (with the old sintax), but I 
> prefer 
> the new sintax.
> 
> Glauco P. Gomes
> 
> Cagatay Civici escreveu:
>> +1 for the newer one.
>>
>> On Thu, May 8, 2008 at 9:52 PM, Hazem Saleh <[EMAIL PROTECTED] 
>> > wrote:
>>
>> Hi Gerald,
>>
>> No special reason, I just asked people who use this component and they
>> disliked the new syntax.
>>
>>
>> On Thu, May 8, 2008 at 9:29 PM, Gerald Müllan <[EMAIL PROTECTED]
>> > wrote:
>>
>> Hi,
>>
>> i would prefer the new syntax since it seems to be more natural to 
>> me.
>>
>> Similar to an updateActionListener; the command component fires the
>> listener embedded inside.
>>
>> So, +1
>>
>> Any special reason why breaking the common sense?
>>
>> cheers,
>>
>> Gerald
>>
>> On Thu, May 8, 2008 at 8:01 PM, Hazem Saleh <[EMAIL PROTECTED]
>> > wrote:
>> > Hi Team,
>> >
>> > After I started modifying of the Exporter component syntax,
>> >
>> > To be like this :
>> > 
>> > > >   fileType="XLS"/>
>> >  
>> >
>> > Some guys didnot like this new syntax, and they preferred the
>> current one :
>> > 
>> > 
>> > 
>> >
>> > I need your input regarding this.
>> > (+1) for supporting the new syntax.
>> > (-1) for supporting the old syntax.
>> >
>> > Thanks!
>> >
>> > --
>> > Hazem Ahmed Saleh Ahmed
>> > http://www.jroller.com/page/HazemBlog
>>
>>
>>
>> --
>> http://www.irian.at
>>
>> Your JSF powerhouse -
>> JSF Consulting, Development and
>> Courses in English and German
>>
>> Professional Support for Apache MyFaces
>>
>>
>>
>>
>> -- 
>> Hazem Ahmed Saleh Ahmed
>> http://www.jroller.com/page/HazemBlog
>>
>>
> 

[jira] Created: (TOBAGO-662) Use LOG.isInfoEnable() for LOG.info()

[Bernd Bohmann (JIRA)]

Use LOG.isInfoEnable() for LOG.info()
-

 Key: TOBAGO-662
 URL: https://issues.apache.org/jira/browse/TOBAGO-662
 Project: MyFaces Tobago
  Issue Type: Improvement
Affects Versions: 1.0.16
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.17, 1.1.0




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

[jira] Created: (TOBAGO-661) Add immediate update check for UIReload

[Bernd Bohmann (JIRA)]

Add immediate update check for UIReload
---

 Key: TOBAGO-661
 URL: https://issues.apache.org/jira/browse/TOBAGO-661
 Project: MyFaces Tobago
  Issue Type: Improvement
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.0.17, 1.1.0




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

[jira] Created: (TOBAGO-660) Reload facet doesn't work since TOBAGO-312

[Bernd Bohmann (JIRA)]

Reload facet doesn't work since TOBAGO-312
--

 Key: TOBAGO-660
 URL: https://issues.apache.org/jira/browse/TOBAGO-660
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.16, 1.0.15, 1.0.14, 1.0.13, 1.0.12, 1.0.11
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann




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

[jira] Reopened: (TOBAGO-628) Setting rendererType on TobagoMenuExtensionHandler for facelets (tx:menuRadio and tx:menuCheckbox)

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann reopened TOBAGO-628:
--


> Setting rendererType on TobagoMenuExtensionHandler for facelets (tx:menuRadio 
> and tx:menuCheckbox)
> --
>
> Key: TOBAGO-628
> URL: https://issues.apache.org/jira/browse/TOBAGO-628
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Facelets
>Affects Versions: 1.0.15
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Fix For: 1.0.17, 1.1.0
>
>


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

[jira] Created: (TOBAGO-658) JSF 1.2 compability

[Bernd Bohmann (JIRA)]

JSF 1.2 compability
---

 Key: TOBAGO-658
 URL: https://issues.apache.org/jira/browse/TOBAGO-658
 Project: MyFaces Tobago
  Issue Type: Improvement
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.1.0




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

[jira] Commented: (TOBAGO-657) not running at all

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592747#action_12592747
 ] 

Bernd Bohmann commented on TOBAGO-657:
--

Can you attach the webapp as an attachment to the issue.
I assume you are using tomcat 6?

Such kind of questions should asked on the user list.

http://myfaces.apache.org/mail-lists.html

> not running at all
> --
>
> Key: TOBAGO-657
> URL: https://issues.apache.org/jira/browse/TOBAGO-657
> Project: MyFaces Tobago
>  Issue Type: Bug
>Reporter: adam
>
> Hey Guys .. I'm new with Tobago and i make small example to test my knowledge 
> and when i press the button nothing run plz can any one help me and tell me 
> why not running?
> I attached all files that u will need to see it 
> Waiting for ur replay as soon as possible
> plz any one help me on my first application 
> faces-config.xml:
> 
>  "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
> "http://java.sun.com/dtd/web-facesconfig_1_1.dtd";>
> 
>   
>   
>   goClass
>   
>   com.GoClass
>   
>   session
>   
>   
>   
>   index
>   
>   /index.jsp
>   
>   success
>   
>   /success.jsp
>   
>   
> 
> tobago-config.xml : 
> 
>  "-//The Apache Software Foundation//DTD Tobago Config 1.0//EN" 
> "tobago-config_1_0.dtd">
> 
>   
> speyside
> scarborough
> richmond
> charlotteville
>   
>   tobago-resource
>   true
> 
> web.xml : 
> 
>xmlns="http://java.sun.com/xml/ns/j2ee";
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee 
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";>
>   TestJSF
>   
>   
>   multipartFormdataFilter
>   
>   
> org.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter
>   
>   
>   
>   Set the size limit for uploaded files. Default 
> value is
>   1 MB. Format: 10 = 10 bytes 10k = 10 KB 10m = 
> 10 MB 1g =
>   1 GB
>   
>   uploadMaxFileSize
>   20m
>   
>   
>   
>   
>   multipartFormdataFilter
>   /faces/*
>   
>   
>   
>   
>   
> org.apache.myfaces.tobago.webapp.TobagoServletContextListener
>   
>   
>   
>   Faces Servlet
>   javax.faces.webapp.FacesServlet
>   1
>   
>   
>   Faces Servlet
>   /faces/*
>   
>   
>   index.html
>   index.htm
>   index.jsp
>   default.html
>   default.htm
>   default.jsp
>   
> 
> index.jsp: 
> <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f"%>
> <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h"%>
> <%@ taglib uri="http://myfaces.apache.org/tobago/component"; prefix="tc"%>
> <%@ taglib uri="http://myfaces.apache.org/tobago/extension"; prefix="tx"%>
> 
>   
>   
>   
>   
>   
>action="#{goClass.go}">
>   
>   
> 
> success.jsp:
> <%@ page language="java" contentType="text/html; charset=ISO-8859-1"
> pageEncoding="ISO-8859-1"%>
>  "http://www.w3.org/TR/html4/loose.dtd";>
> 
> 
> 
> Insert title here
> 
> 
> Success
> 
> 
> tell me where is the error i use appach server version 6
> Thanks & Regards 
> Adam

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

[jira] Commented: (TOBAGO-634) javascript bug makes does not work inside a

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592642#action_12592642
 ] 

Bernd Bohmann commented on TOBAGO-634:
--

Can you provide an example, please?

> javascript bug makes  does not work inside a  
> -
>
> Key: TOBAGO-634
> URL: https://issues.apache.org/jira/browse/TOBAGO-634
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.0.12, 1.0.13, 1.0.14, 1.0.15
> Environment: Firefox and MSIE
>Reporter: Diego Vieira Vivo
>Priority: Blocker
>
> I have a search page   that has a TC:button search and a  with 
> tc:links inside tc:columns
> When I access the page by the first time, the list of items is empty, so 
> tc:sheet shows 0 rows.  That's  expected
> When I click the search button then a findBean.findAll is performed and the 
> list is filled of items and the tc:sheet displays them. Again that's  expected
> But when i click on tc:link its call Tobago.submitAction and pass throught it 
> and nothing happens.
> after call Tobago.form.submit(),inside  Tobago.submitAction , the page is 
> reloaded. As i could see, it just like if i clicked in a # link.
> there was envem a call to server it stopped on the browser. 
> Note: All the beans are request scoped
> In a second test i initialize the list before the first time the page is 
> accessed, doing this the every thing works fine and there was no tc:link 
> problem
> So I realize that by the first time, when i filled before open the page, the 
> Tobago initialized all the lines of the tc:sheet,
> If i load the list after page is opened it does some kind of partial render 
> and does not reinitialize tc:sheet, so when i click in a link and it calls 
> Tobago.submitAction and  it can't get the action and when tobago.form.submit 
> is called it doesn t call the server and fallback to 
> that reload the page.

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

[jira] Created: (TOBAGO-656) Move to the merged apt-maven-plugin from codehaus

[Bernd Bohmann (JIRA)]

Move to the merged apt-maven-plugin from codehaus 
--

 Key: TOBAGO-656
 URL: https://issues.apache.org/jira/browse/TOBAGO-656
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Build
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor
 Fix For: 1.1.0


The tobago maven-apt-plugin and the codehaus apt-maven-plugin has been merged 
by Mark Hobson, Thanks

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

[jira] Created: (TOBAGO-655) Create a prepareRender Phase

[Bernd Bohmann (JIRA)]

Create a prepareRender Phase  
--

 Key: TOBAGO-655
 URL: https://issues.apache.org/jira/browse/TOBAGO-655
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core, Facelets, Themes
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.1.0


Calculation of layout and adding resources to the Page should moved to this 
Phase. 
The PageRenderer invoke this Phase on all Components/Renderer 

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

[jira] Commented: (MYFACES-1825) duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds()

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591225#action_12591225
 ] 

Bernd Bohmann commented on MYFACES-1825:


fixed 
too many idea frames open :-)

> duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds() 
> -
>
> Key: MYFACES-1825
> URL: https://issues.apache.org/jira/browse/MYFACES-1825
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 1.1.5
>Reporter: gaston
>    Assignee: Bernd Bohmann
> Fix For:  1.1.6-SNAPSHOT, 1.2.3-SNAPSHOT
>
>
> Some duplicate id are not detected in my MyFaces(1.1.5)/Facelets(1.1.12) 
> based application.
> I think there's a bug in MyFaces's detection of duplicate ids in 
> JspStateManagerImpl.checkForDuplicateIds() : 
> this code seems to be wrong :
> boolean namingContainer = component instanceof NamingContainer;
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }
> It should be :
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> boolean namingContainer = kid instanceof NamingContainer;
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }

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

[jira] Resolved: (MYFACES-1825) duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds()

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYFACES-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved MYFACES-1825.


Resolution: Fixed

> duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds() 
> -
>
> Key: MYFACES-1825
> URL: https://issues.apache.org/jira/browse/MYFACES-1825
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 1.1.5
>Reporter: gaston
>    Assignee: Bernd Bohmann
> Fix For:  1.1.6-SNAPSHOT, 1.2.3-SNAPSHOT
>
>
> Some duplicate id are not detected in my MyFaces(1.1.5)/Facelets(1.1.12) 
> based application.
> I think there's a bug in MyFaces's detection of duplicate ids in 
> JspStateManagerImpl.checkForDuplicateIds() : 
> this code seems to be wrong :
> boolean namingContainer = component instanceof NamingContainer;
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }
> It should be :
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> boolean namingContainer = kid instanceof NamingContainer;
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }

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

Re: [VOTE] sev-en as a new myfaces sub-project

[Bernd Bohmann]

-1 as a new sub-project
+1 included in commons

Regards

Bernd

Andrew Robinson schrieb:
> +0.5 to the code
> -0.9 as a new top level project. I really would prefer to see this in
> commons or orchestra as the MyFaces project is already confusing at
> first to users due to the number of top level projects.
> 
> Also, what is up with the name? It doesn't seem to relate to what it does.
> 
> Also has there been any thought on how this will play with existing
> Hibernate applications and how compatible it is if the bean validation
> framework JSR goes through as something pretty similar to what
> Hibernate already has?
> 
> -Andrew
> 
> On Sun, Apr 20, 2008 at 5:29 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote:
>> +1
>>
>> regards
>>
>> Leonardo Uribe
>>
>>
>>
>> On Sun, Apr 20, 2008 at 4:21 PM, Gerhard Petracek
>> <[EMAIL PROTECTED]> wrote:
>>> hello cagatay,
>>>
>>> you would still benefit in the cases you mentioned, if there would be an
>> optional cross-component client-side validation support.
>>> -> in such a case we wouldn't reinvent the wheel.
>>> + complex client-side validation would be independent of the component lib
>> you are using.
>>> however, client-side sev-en validation isn't implemented at the moment
>>> (and it isn't clear, if there will be such a feature. there will be a
>> separated discussion about such topics).
>>> it was just a question in view of your orchestra comment.
>>> -> so let's just continue the vote. (thank you for attending the vote - i
>> noticed: your position hasn't changed so far.)
>>>
>>>
>>>
>>> regards,
>>> gerhard
>>>
>>>
>>>
>>>
>>> 2008/4/20, Cagatay Civici <[EMAIL PROTECTED]>:
 Hi,


> in the near future i'll think about client side validation support.
 Sorry but no:) This is what I'm talking about actually, every subproject
>> has the potential of reinventing the wheel and overlap with already
>> implemented features in other myfaces subprojects.
 Trinidad has it;

>> http://www.irian.at/trinidad-demo/faces/convertValidate/clientConvert.jspx
 Tomahawk Sandbox has it;
 http://www.irian.at/myfaces-sandbox/clientValidationWithStandardForm.jsf

 Regards,

 Cagatay



 On Sun, Apr 20, 2008 at 10:45 PM, Gerhard Petracek
>> <[EMAIL PROTECTED]> wrote:
> hello cagatay,
>
> in the near future i'll think about client side validation support.
> -> does this change your opinion?
>
> regards,
> gerhard
>
>
>
>
> 2008/4/20, Cagatay Civici <[EMAIL PROTECTED]>:
>
>
>
>> Hi,
>>
>> My mind hasn't changed since the last discussion so it's still -1
>> for a stand-alone project because in my opinion every goodie, extension
>> etc...) that doesn't render anything should join orchestra.
>> We might end up with a subproject hell that's hard to maintain if we
>> create a subproject for each jsf extension.
>> Orchestra core15 module is a nice place for sev-en.
>>
>> Cagatay
>>
>>
>>
>> On Sun, Apr 20, 2008 at 10:07 PM, Werner Punz
>> <[EMAIL PROTECTED]> wrote:
>>> Ok Gerhard my apologies then if all of this is discussed out
>>> then a clear +1
>>> from my side.
>>>
>>> Werner
>>>
>>>
>>> Gerhard Petracek schrieb:
>>>
 hello werner,

 thank you for your additional hint.
 however, we already discussed this topic and there are several
>> arguments against the integration.
 this vote is just about sev-en as a stand-alone sub-project of
>> myfaces.
 (aspect-el is a different topic. so let's have a separated
>> vote.)
 regards,
 gerhard



 2008/4/20, Werner Punz <[EMAIL PROTECTED]
>> >:



+1 but one addition

since we already have an extension api project
wouldnt it be better to be integrated into orchestra
I think since orchestra is not a scope project although
its main area is scoping that sev-en should belong in there.
Think about that, I think orchestra might be the perfect
>> place
for things like sev-en and/or aspect-el


Werner


Gerhard Petracek schrieb:

hello,

as requested i published the source code of the sev-en
>> preview
some days ago (details at: [1]).

we discussed whether or not we should start a new myfaces
sub-project.

so let's vote!
(there will be a separated discussion + vote concerning
>> the name.)

>> ---
[ ] +1 for: sev-en should become a myfaces sub-project
[ ] +0
[ ] -1 for: sev-en shouldn't becom

Re: Exporter comes finally to the scene :)

[Bernd Bohmann]

Hello Hazem,

I would prefer matthias suggestion.

If the exporter is inside a command it should be easier to use the
exporter in a different renderkit.

Regards

Bernd

Hazem Saleh schrieb:
> Hi Matzew,
> I followed the previous pattern of the excelExport component.
> So IMO, I think it is not odd for the component users.
> 
> On Fri, Apr 18, 2008 at 7:41 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
> wrote:
> 
>> On Fri, Apr 18, 2008 at 7:02 PM, Hazem Saleh <[EMAIL PROTECTED]>
>> wrote:
>>> Hi Matzew,
>>> What is the problem with the previous syntax :-
>>>
>>> 
>>> 
>>>  
>> I thought that the exporter would be an ActionListener.
>> Therefore embedding it inside an ActionSource(2) component
>> would make sense.
>>
>> I think it is odd, the nest the button inside a comp, to do the export.
>> Nesting the exporter inside the button makes more sense, since
>> the button performs the action. So IMO it should be ActionListener.
>>
>> -M
>>
>>
>>
>>>
>>>
>>> On Fri, Apr 18, 2008 at 6:57 PM, Matthias Wessendorf <[EMAIL PROTECTED]>
>>> wrote:
 Hi,

 I would  instead of:

 

 

 expect something like:

 

 




 On Fri, Apr 18, 2008 at 6:49 PM, Hazem Saleh <[EMAIL PROTECTED]>
>>> wrote:
> Hi Team,
> Generated file is now depending on the mime type :) .
>
>  Here is an example of usage)
>  
>  
>  
> Thanks all for your suggestions.
>
>
>
> On Fri, Apr 18, 2008 at 5:45 AM, Hazem Saleh <[EMAIL PROTECTED]>
>>> wrote:
>> Hi Team,
>> Iam pleased to tell you that I integrated both the excelExport and
>> the
> pdfExport components into
>> one single component called (exporter).
>>
>> Till now, it exports the contents of DataTables to EXCEL or PDF
>> files.
>> Here is an example of usage)
>> 
>> 
>> 
>>
>> Here is the patch URL:
>> https://issues.apache.org/jira/browse/TOMAHAWK-1231
>>
>> Thanks all very much.
>> --
>> Hazem Ahmed Saleh Ahmed
>> http://www.jroller.com/page/HazemBlog
>
>
> --
> Hazem Ahmed Saleh Ahmed
> http://www.jroller.com/page/HazemBlog


 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 mail: matzew-at-apache-dot-org

>>>
>>>
>>> --
>>>
>>> Hazem Ahmed Saleh Ahmed
>>> http://www.jroller.com/page/HazemBlog
>>
>>
>> --
>> Matthias Wessendorf
>>
>> further stuff:
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> mail: matzew-at-apache-dot-org
>>
> 
> 
> 

[jira] Created: (TOBAGO-653) Create a own JsonResponseWriter for dojo ajax requests

[Bernd Bohmann (JIRA)]

Create a own JsonResponseWriter for dojo ajax requests
--

 Key: TOBAGO-653
 URL: https://issues.apache.org/jira/browse/TOBAGO-653
 Project: MyFaces Tobago
  Issue Type: Sub-task
  Components: Core
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor
 Fix For: 1.1.0


It would be nice if the response writer supports separating the html and 
javascript response

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

[jira] Commented: (TOBAGO-652) Move tobago-menu.css and tobago-sheet.css content to style.css

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/TOBAGO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590556#action_12590556
 ] 

Bernd Bohmann commented on TOBAGO-652:
--

This would be the next possible step, but I would like to resolve TOBAGO-419 
for 1.1

> Move tobago-menu.css and tobago-sheet.css content to style.css
> --
>
> Key: TOBAGO-652
> URL: https://issues.apache.org/jira/browse/TOBAGO-652
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Themes
>Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
> Fix For: 1.1.0
>
>


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

[jira] Resolved: (TOBAGO-419) Sheets disappear on a tab in IE

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-419.
--

Resolution: Fixed

> Sheets disappear on a tab in IE
> ---
>
> Key: TOBAGO-419
> URL: https://issues.apache.org/jira/browse/TOBAGO-419
> Project: MyFaces Tobago
>  Issue Type: Bug
>  Components: Themes
>Affects Versions: 1.0.11
> Environment: Internet Explorer 6 and 7
>Reporter: Helmut Swaczinna
>Assignee: Bernd Bohmann
> Fix For: 1.1.0
>
>
> When there're more than one sheet on one tab in tabGroup with 
> switchType="reloadTab"
> all sheets disappear when switching to the tab the first time.
> Example:
> 
>   
> 
>   
> 
>   
>   
> 
>   
>columns="1*;1*"/>
>   
>columns="1*;1*"
> showHeader="true"
> showRowRange="none"
> showPageRange="none"
> showDirectLinks="none"
> first="0"
> selectable="none"
> var="row"
> value="#{controller.list1}">
> 
>value="#{row.column1}"/>
> 
> 
>value="#{row.column2}"/>
> 
>   
>columns="1*;1*"
> showHeader="true"
> showRowRange="none"
> showPageRange="none"
> showDirectLinks="none"
> first="0"
> selectable="none"
> var="row"
> value="#{controller.list2}">
> 
>value="#{row.column1}"/>
> 
> 
>value="#{row.column2}"/>
> 
>   
> 
>   
> 
>   
> 

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

[jira] Resolved: (TOBAGO-652) Move tobago-menu.css and tobago-sheet.css content to style.css

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-652.
--

Resolution: Fixed

> Move tobago-menu.css and tobago-sheet.css content to style.css
> --
>
> Key: TOBAGO-652
> URL: https://issues.apache.org/jira/browse/TOBAGO-652
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Themes
>    Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
> Fix For: 1.1.0
>
>


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

[jira] Created: (TOBAGO-652) Move tobago-menu.css and tobago-sheet.css content to style.css

[Bernd Bohmann (JIRA)]

Move tobago-menu.css and tobago-sheet.css content to style.css
--

 Key: TOBAGO-652
 URL: https://issues.apache.org/jira/browse/TOBAGO-652
 Project: MyFaces Tobago
  Issue Type: Improvement
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.1.0




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

[jira] Resolved: (TOBAGO-621) Avoid empty class in option element of tc:selectXXX

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TOBAGO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved TOBAGO-621.
--

Resolution: Fixed

> Avoid empty class in option element of tc:selectXXX
> ---
>
> Key: TOBAGO-621
> URL: https://issues.apache.org/jira/browse/TOBAGO-621
> Project: MyFaces Tobago
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 1.0.15
>    Reporter: Bernd Bohmann
>    Assignee: Bernd Bohmann
>Priority: Minor
> Fix For: 1.1.0
>
>


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

Re: [Tobago] Merging maven-apt-plugin with Codehaus'

[Bernd Bohmann]

Hello Mark,

I found no issues with 1.0-alpha-2-SNAPSHOT and the tobago build.
When you will release the 1.0-alpha-2-SNAPSHOT version?

Regards

Bernd

Bernd Bohmann schrieb:
> Hello Mark,
> 
> I changed a local tobago version to use the apt-maven-plugin.
> I think everything is fine with the new plugin. In a few days I will
> commit the changed build to trunk.
> 
> Regard
> 
> Bernd
> 
> 
> 
> Mark Hobson schrieb:
>> Just to let you know, the Codehaus apt-maven-plugin has graduated out
>> of the sandbox and changed version.  It is now located at:
>>
>> http://svn.codehaus.org/mojo/trunk/mojo/apt-maven-plugin/
>>
>> And the version is now 1.0-alpha-2-SNAPSHOT, which is deployed here:
>>
>> http://snapshots.repository.codehaus.org/org/codehaus/mojo/apt-maven-plugin/1.0-alpha-2-SNAPSHOT/
>>
>> Did you have a chance to try the plugin with the Tobago build over
>> ApacheCon?  I'd be interested in any feedback before 1.0-alpha-2 is
>> released.
>>
>> Cheers,
>>
>> Mark
>>
>> On 04/04/2008, Mark Hobson <[EMAIL PROTECTED]> wrote:
>>> Great, I'll looking forward to hearing back from you then.
>>>
>>>  Cheers,
>>>
>>>
>>>  Mark
>>>
>>>
>>>  On 04/04/2008, Bernd Bohmann <[EMAIL PROTECTED]> wrote:
>>>  > Hello Mark,
>>>  >
>>>  >  during the ApacheCon Europe next week I can spend some time to test the
>>>  >  plugin with the tobago build.
>>>  >
>>>  >  Regards
>>>  >
>>>  >
>>>  >
>>>  >  Bernd
>>>  >
>>>  >
>>>  >
>>>
> 

[jira] Created: (TOBAGO-651) Own Renderer for cell

[Bernd Bohmann (JIRA)]

Own Renderer for cell
-

 Key: TOBAGO-651
 URL: https://issues.apache.org/jira/browse/TOBAGO-651
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Themes
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.1.0




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

[jira] Resolved: (MYFACES-1866) Avoid possible NullPointerException and NumberFormatException in JspStateManagerImpl.getServerStateId

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYFACES-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann resolved MYFACES-1866.


Resolution: Fixed

> Avoid possible NullPointerException and NumberFormatException in 
> JspStateManagerImpl.getServerStateId
> -
>
> Key: MYFACES-1866
> URL: https://issues.apache.org/jira/browse/MYFACES-1866
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-252
>Affects Versions: 1.2.2
>    Reporter: Bernd Bohmann
>Assignee: Bernd Bohmann
> Fix For: 1.2.3-SNAPSHOT
>
>
> java.lang.NullPointerException
>   at 
> org.apache.myfaces.application.jsp.JspStateManagerImpl.getServerStateId(JspStateManagerImpl.java:218)
>   at 
> org.apache.myfaces.application.jsp.JspStateManagerImpl.restoreView(JspStateManagerImpl.java:295)
>   at 
> org.apache.myfaces.application.jsp.JspViewHandlerImpl.restoreView(JspViewHandlerImpl.java:505)
>   at 
> org.apache.myfaces.tobago.application.ViewHandlerImpl.restoreView(ViewHandlerImpl.java:98)
>   at 
> org.apache.myfaces.tobago.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:108)
>   at 
> org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.executePhase(TobagoLifecycle.java:102)
>   at 
> org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.execute(TobagoLifecycle.java:72)
>   at javax.faces.webapp.FacesServlet.service(FacesServlet.java:148)
>   at 
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>   at 
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>   at 
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>   at 
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>   at 
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
>   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>   at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
>   at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
>   at 
> org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:767)
>   at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:47)
>   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>   at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
>   at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
>   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>   at 
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>   at 
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>   at 
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>   at 
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>   at 
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
>   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>   at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
>   at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
>   at 
> org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:463)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>   at 
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>   at 
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
>   at 
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>   at 
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>   at 
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
>   at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
>   at 
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
>   at 
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>   at org.mortbay.jetty.Server.handle(Serv

[jira] Created: (MYFACES-1866) Avoid possible NullPointerException and NumberFormatException in JspStateManagerImpl.getServerStateId

[Bernd Bohmann (JIRA)]

Avoid possible NullPointerException and NumberFormatException in 
JspStateManagerImpl.getServerStateId
-

 Key: MYFACES-1866
 URL: https://issues.apache.org/jira/browse/MYFACES-1866
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-252
Affects Versions: 1.2.2
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
 Fix For: 1.2.3-SNAPSHOT


java.lang.NullPointerException
at 
org.apache.myfaces.application.jsp.JspStateManagerImpl.getServerStateId(JspStateManagerImpl.java:218)
at 
org.apache.myfaces.application.jsp.JspStateManagerImpl.restoreView(JspStateManagerImpl.java:295)
at 
org.apache.myfaces.application.jsp.JspViewHandlerImpl.restoreView(JspViewHandlerImpl.java:505)
at 
org.apache.myfaces.tobago.application.ViewHandlerImpl.restoreView(ViewHandlerImpl.java:98)
at 
org.apache.myfaces.tobago.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:108)
at 
org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.executePhase(TobagoLifecycle.java:102)
at 
org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.execute(TobagoLifecycle.java:72)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:148)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
at 
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:767)
at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:47)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:285)
at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
at 
org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:463)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:828)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at 
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at 
org.mortbay.thread.BoundedThreadPool$PoolThread.run

[jira] Commented: (MYFACES-1825) duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds()

[Bernd Bohmann (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590417#action_12590417
 ] 

Bernd Bohmann commented on MYFACES-1825:


I think it should be:

Iterator it = component.getFacetsAndChildren();
if (component instanceof NamingContainer)
{
  ids = new HashSet();
}
while (it.hasNext())
{
  UIComponent kid = (UIComponent) it.next();
  checkForDuplicateIds(context, kid, ids);
}

If you agree I will commit this change.

> duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds() 
> -
>
> Key: MYFACES-1825
> URL: https://issues.apache.org/jira/browse/MYFACES-1825
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 1.1.5
>Reporter: gaston
>Assignee: Leonardo Uribe
> Fix For:  1.1.6-SNAPSHOT, 1.2.3-SNAPSHOT
>
>
> Some duplicate id are not detected in my MyFaces(1.1.5)/Facelets(1.1.12) 
> based application.
> I think there's a bug in MyFaces's detection of duplicate ids in 
> JspStateManagerImpl.checkForDuplicateIds() : 
> this code seems to be wrong :
> boolean namingContainer = component instanceof NamingContainer;
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }
> It should be :
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> boolean namingContainer = kid instanceof NamingContainer;
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }

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

[jira] Reopened: (MYFACES-1825) duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds()

[Bernd Bohmann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYFACES-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Bohmann reopened MYFACES-1825:



> duplicate ids not detected in JspStateManagerImpl.checkForDuplicateIds() 
> -
>
> Key: MYFACES-1825
> URL: https://issues.apache.org/jira/browse/MYFACES-1825
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 1.1.5
>Reporter: gaston
>Assignee: Leonardo Uribe
> Fix For:  1.1.6-SNAPSHOT, 1.2.3-SNAPSHOT
>
>
> Some duplicate id are not detected in my MyFaces(1.1.5)/Facelets(1.1.12) 
> based application.
> I think there's a bug in MyFaces's detection of duplicate ids in 
> JspStateManagerImpl.checkForDuplicateIds() : 
> this code seems to be wrong :
> boolean namingContainer = component instanceof NamingContainer;
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }
> It should be :
> while (it.hasNext()) {
> UIComponent kid = (UIComponent) it.next();
> boolean namingContainer = kid instanceof NamingContainer;
> if (namingContainer) {
> checkForDuplicateIds(context, kid, new HashSet());
> }
> else {
> checkForDuplicateIds(context, kid, ids);
> }
> }

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

[jira] Created: (TOBAGO-650) Support for validatorMessage, requiredMessage, converterMessage and label attribute for EditableValueHolder

[Bernd Bohmann (JIRA)]

Support for validatorMessage, requiredMessage, converterMessage and label 
attribute for EditableValueHolder
---

 Key: TOBAGO-650
 URL: https://issues.apache.org/jira/browse/TOBAGO-650
 Project: MyFaces Tobago
  Issue Type: Improvement
  Components: Core
Reporter: Bernd Bohmann
Assignee: Bernd Bohmann
Priority: Minor
 Fix For: 1.1.0




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