[ANNOUNCE] MyFaces Trinidad 2.2.1 released

2017-07-27 Thread Bernd Bohmann
The Apache MyFaces team is pleased to announce the release of MyFaces
Trinidad 2.2.1.

MyFaces Trinidad is a JavaServer(tm) Faces component library compatible
with JSF 2.2

Apache MyFaces Trinidad is available in both binary and source
distributions and there are examples available as well:

* http://myfaces.apache.org/trinidad/download.html

Apache MyFaces Trinidad is available in the central Maven repository under
Group ID "org.apache.myfaces.trinidad"

Release Notes - MyFaces Trinidad - Version 2.2.1

** Bug
* [TRINIDAD-2554] - Avoid duplicated trinidad-assembly artifacts
* [TRINIDAD-2555] - java.lang.NullPointerException in
SimpleSelectOneRenderer with
javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL enabled
* [TRINIDAD-2556] -
UIXComponentBase|UIXEditableValue#processValidators|Decodes|Updates,
CoreRenderer#encodeAllChildren and UIXComponent#visitTree  doesn't support
component expression in rendered attribute
* [TRINIDAD-2557] - writeDoctype is not implemented in PPRResponseWriter
* [TRINIDAD-2558] - NPE with partialStateSaving off and viewCache off
and myface core in restore View

Regards

Bernd


[ANNOUNCE] MyFaces Trinidad 2.1.4 released

2017-07-27 Thread Bernd Bohmann
The Apache MyFaces team is pleased to announce the release of MyFaces
Trinidad 2.1.4.

MyFaces Trinidad is a JavaServer(tm) Faces component library compatible
with JSF 2.1

Apache MyFaces Trinidad is available in both binary and source
distributions and there are examples available as well:

* http://myfaces.apache.org/trinidad/download.html

Apache MyFaces Trinidad is available in the central Maven repository under
Group ID "org.apache.myfaces.trinidad"

Release Notes - MyFaces Trinidad - Version 2.1.4

** Bug
* [TRINIDAD-2554] - Avoid duplicated trinidad-assembly artifacts
* [TRINIDAD-2555] - java.lang.NullPointerException in
SimpleSelectOneRenderer with
javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL enabled
* [TRINIDAD-2556] -
UIXComponentBase|UIXEditableValue#processValidators|Decodes|Updates,
CoreRenderer#encodeAllChildren and UIXComponent#visitTree  doesn't support
component expression in rendered attribute
* [TRINIDAD-2558] - NPE with partialStateSaving off and viewCache off
and myface core in restore View

Regards

Bernd


[ANNOUNCE] MyFaces Trinidad 2.1.3 released

2017-07-21 Thread Bernd Bohmann
The Apache MyFaces team is pleased to announce the release of MyFaces
Trinidad 2.1.3.

MyFaces Trinidad is a JavaServer(tm) Faces component library compatible
with JSF 2.1

Apache MyFaces Trinidad is available in both binary and source
distributions and there are examples available as well:

* http://myfaces.apache.org/trinidad/download.html

Apache MyFaces Trinidad is available in the central Maven repository under
Group ID "org.apache.myfaces.trinidad"

Release Notes - MyFaces Trinidad - Version 2.1.3

** Bug
* [TRINIDAD-1091] - Internet Explorer 6 displays "This page contains
both secure and nonsecure items" message when user tries to open a
lightweight dialog box when using SSL
* [TRINIDAD-2339] - Trinidad on Jboss AS 6. Cannot deploy application
because of syntax error in tld
* [TRINIDAD-2434] - Usage of Class.getMethod in
TreeRenderer.retrieveGetNodeTypeMethod is a critical performance issue
* [TRINIDAD-2450] - ClassCastException @
UIXEditableValue.shouldValidateEmptyFields
* [TRINIDAD-2465] - Memory Leak on redeploy
* [TRINIDAD-2508] - JSF 2.2 @MultipartConfig on FacesServlet breaks
Trinidad file upload
* [TRINIDAD-2534] - JSF Page Navigation is not working while
partialSubmit="true" on Commandbutton or commandlink.
* [TRINIDAD-2543] - Modal dialog doesn't mask the Parent Window on
Chrome browsers
* [TRINIDAD-2545] - Update of view state in partial response not
working (JSF 2.2)
* [TRINIDAD-2546] - f:ajax listener not called
* [TRINIDAD-2549] - ViewRootCaching of trinidad conflicts with jsf >=
2,2

** Improvement
* [TRINIDAD-2539] - Make Trinidad 2.1 compatible with JSF 2.2
* [TRINIDAD-2547] - ClientBehavior doesn't get rendered on all commands
* [TRINIDAD-2548] - Missing Client-Side-State-Saving Secrets
initialization if trinidad runs in oracle jsf ri

Regards

Bernd


[ANNOUNCE] MyFaces Trinidad 2.2.0 released

2017-07-21 Thread Bernd Bohmann
The Apache MyFaces team is pleased to announce the release of MyFaces
Trinidad 2.2.0.

MyFaces Trinidad is a JavaServer(tm) Faces component library compatible
with JSF 2.2

Apache MyFaces Trinidad is available in both binary and source
distributions and there are examples available as well:

* http://myfaces.apache.org/trinidad/download.html

Apache MyFaces Trinidad is available in the central Maven repository under
Group ID "org.apache.myfaces.trinidad"

Release Notes - MyFaces Trinidad - Version 2.2.0

** Sub-task
* [TRINIDAD-2551] - Add Pass-through attributes support

** Improvement
* [TRINIDAD-2550] - Create a Trinidad 2.2.x version with more jsf 2.2
features

NOTE: 2.2.0 contains all fixes from 2.1.3 as well

Regards

Bernd


Re: [Trinidad] Table pagination not showing up

2017-07-14 Thread Bernd Bohmann
Hello

without more details. I would suggest following:
Please set a breakpoint inside DesktopTableRenderer.renderControlBar and
check why the navigation bar is not rendered.

Regards

Bernd

On Tue, Jul 11, 2017 at 5:24 PM, PETITIOT, LUCAS 
wrote:

> I can’t see anything wrong in the server console, is there any way to
> enable more thorough debug messages ?
>
> Here’s what it looks like: http://imgur.com/a/qFKsm . I have also noticed
> that table banding doesn’t seem to work either... Is there some setting in
> web.xml or something I need to configure to get this to work?
>
> I’m using 2.1.2, but I have tried with 2.2.0 as well. My table is as
> follows:
>
>  first="0">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  value="#{alarm.organisation}"/>
> 
> 
> 
> 
> 
> 
>  timeStyle="medium"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> Thanks
>
> _
> From: PETITIOT, LUCAS
> Sent: Monday, July 10, 2017 5:29 PM
> To: 'MyFaces Discussion'
> Subject: [Trinidad] Table pagination not showing up
>
>
> Hello,
> I’m trying to get the Table component to show the pagination as can be
> seen here http://example.irian.at/trinidad-components-showcase/
> component-demo/table-Pagination
> I have set rows=”25”, I have also tried with another number, the table
> does show 25 entries but the pagination bar at the top doesn’t show
>
> Anybody have the same problem?
>
> Thanks
>
> Ce message et toutes les pièces jointes (ci-après le "message") sont
> établis à l’intention exclusive des destinataires désignés. Il contient des
> informations confidentielles et pouvant être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de détruire le message. Toute utilisation de
> ce message non conforme à sa destination, toute diffusion ou toute
> publication, totale ou partielle, est interdite, sauf autorisation expresse
> de l’émetteur. L'internet ne garantissant pas l'intégrité de ce message
> lors de son acheminement, Atos (et ses filiales) décline(nt) toute
> responsabilité au titre de son contenu. Bien que ce message ait fait
> l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne peut
> garantir l’absence totale de logiciels malveillants dans son contenu et ne
> pourrait être tenu pour responsable des dommages engendrés par la
> transmission de l’un d’eux.
>
> This message and any attachments (the "message") are intended solely for
> the addressee(s). It contains confidential information, that may be
> privileged. If you receive this message in error, please notify the sender
> immediately and delete the message. Any use of the message in violation of
> its purpose, any dissemination or disclosure, either wholly or partially is
> strictly prohibited, unless it has been explicitly authorized by the
> sender. As its integrity cannot be secured on the internet, Atos and its
> subsidiaries decline any liability for the content of this message.
> Although the sender endeavors to maintain a computer virus-free network,
> the sender does not warrant that this transmission is virus-free and will
> not be liable for any damages resulting from any virus transmitted.
>


Re: Trinidad 2.1.3 release plan

2017-04-25 Thread Bernd Bohmann
Only a few days until i will start with the release of 2.1.3-core:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661=12339845

and 2.2.0-core:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310661=12340363

Regards

Bernd

On Sun, Apr 9, 2017 at 7:12 PM, Bernd Bohmann <bernd.bohm...@googlemail.com>
wrote:

> Here is the jira 2.1.3 version link
>
> https://issues.apache.org/jira/browse/TRINIDAD/fixforversion/12339845/?
> selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
>
> Regards
>
> Bernd
>
> On Sun, Apr 9, 2017 at 6:56 PM, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>> Hello
>>
>> and some feedback on the current Trinidad 2.1.3-SNAPSHOT would be nice.
>>
>> Regards
>>
>> Bernd
>>
>> On Sun, Apr 9, 2017 at 11:55 AM, Dennis Kieselhorst <d...@apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> as posted on Twitter yesterday: We are planning Apache MyFaces Trinidad
>>> release 2.1.3. Any issues you'd like to see in there? Please let us know!
>>> Patches appreciated.
>>>
>>> Cheers
>>> Dennis
>>>
>>
>>
>


Re: Trinidad 2.1.3 release plan

2017-04-09 Thread Bernd Bohmann
Here is the jira 2.1.3 version link

https://issues.apache.org/jira/browse/TRINIDAD/fixforversion/12339845/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel

Regards

Bernd

On Sun, Apr 9, 2017 at 6:56 PM, Bernd Bohmann <bernd.bohm...@googlemail.com>
wrote:

> Hello
>
> and some feedback on the current Trinidad 2.1.3-SNAPSHOT would be nice.
>
> Regards
>
> Bernd
>
> On Sun, Apr 9, 2017 at 11:55 AM, Dennis Kieselhorst <d...@apache.org>
> wrote:
>
>> Hi,
>>
>> as posted on Twitter yesterday: We are planning Apache MyFaces Trinidad
>> release 2.1.3. Any issues you'd like to see in there? Please let us know!
>> Patches appreciated.
>>
>> Cheers
>> Dennis
>>
>
>


Re: Trinidad 2.1.3 release plan

2017-04-09 Thread Bernd Bohmann
Hello

and some feedback on the current Trinidad 2.1.3-SNAPSHOT would be nice.

Regards

Bernd

On Sun, Apr 9, 2017 at 11:55 AM, Dennis Kieselhorst  wrote:

> Hi,
>
> as posted on Twitter yesterday: We are planning Apache MyFaces Trinidad
> release 2.1.3. Any issues you'd like to see in there? Please let us know!
> Patches appreciated.
>
> Cheers
> Dennis
>


Re: [Tobago] PageRendererBase warning

2011-06-21 Thread Bernd Bohmann
Hello Hani,

can you create an issue. I think we can change this behavior.

Regards

Bernd

On Tue, Jun 21, 2011 at 1:31 PM, Abushammala, Hani (EXTERN: conceptQ)
extern.hani.abushamma...@volkswagen.de wrote:
 Any other Idea?

 Regards,
 Hani

 -Ursprüngliche Nachricht-
 Von: Helmut Swaczinna [mailto:myfa...@wlp-systems.de]
 Gesendet: Mittwoch, 8. Juni 2011 10:32
 An: MyFaces Discussion
 Betreff: Re: [Tobago] PageRendererBase warning

 Hi Hani,

 now I'm able to reproduce this warning. Thanks for the info. But I'm not able 
 to
 find a workaround for this problem. Because it doesn't seem to be a serious
 problem, I will try to configure log4j to prevent this warning.

 Regards,
 Helmut

 Am 06.06.2011 11:51, schrieb Abushammala, Hani (EXTERN: conceptQ):
 Hi Helmut,


 In the item list we have defined 26 items and the warning comes out by 
 selecting the below items after scrolling down in the selectOneChoice. It 
 seems like a rendering problem of selectOneChoice with many values under FF.

 Regards,
 Hani

 -Ursprüngliche Nachricht-
 Von: Abushammala, Hani (EXTERN: conceptQ) 
 [mailto:extern.hani.abushamma...@volkswagen.de]
 Gesendet: Montag, 6. Juni 2011 10:03
 An: MyFaces Discussion
 Betreff: AW: [Tobago] PageRendererBase warning

 Hi Helmut,

 In the controller class we have defined some countries and cities in the 
 item list. After selecting some items (e.g Southafrica) to call an action we 
 became this warning.

 Regards,
 Hani

 -Ursprüngliche Nachricht-
 Von: Helmut Swaczinna [mailto:myfa...@wlp-systems.de]
 Gesendet: Mittwoch, 1. Juni 2011 17:45
 An: MyFaces Discussion
 Betreff: Re: [Tobago] PageRendererBase warning

 Hi Hani,

 I'm still not able to reproduce it with your code and FF 3.6.17. What 
 exactly do
 you mean with by selecting the same items to performe an action?

 Regards,
 Helmut

 Am 01.06.2011 13:07, schrieb Abushammala, Hani (EXTERN: conceptQ):
 Hi Helmut,

 I`ve got this warning with FF 4.0.1 and 3.6.17.

 Regards,
 Hani

 -Ursprüngliche Nachricht-
 Von: Helmut Swaczinna [mailto:myfa...@wlp-systems.de]
 Gesendet: Mittwoch, 1. Juni 2011 12:49
 An: MyFaces Discussion
 Betreff: Re: [Tobago] PageRendererBase warning

 Hi Hani,

 with which browser version do you get this warning exactly? Only with FF 
 4.0.1?

 Regards,
 Helmut

 Am 01.06.2011 12:07, schrieb Abushammala, Hani (EXTERN: conceptQ):

 Hi,

 We could reproduce the warning by selecting the same items to performe an 
 action.

 Test page:

 %@ 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%

 f:view
        tc:page id=statusbar

            tc:panel
                f:facet name=layout
                    tc:gridLayout rows=20px;* columns=222px;* 
 margin=0 cellspacing=0 /
                /f:facet

                tc:panel
                    f:facet name=layout
                        tc:gridLayout rows=* columns=160px;* /
                    /f:facet

                    tc:selectOneChoice id=selector
                                        value=#{controller.selectedItem}
                        f:facet name=change
                            tc:command id=changeAction 
 action=#{controller.doSomething}  /
                        /f:facet
                        tc:selectItems value=#{controller.items} /
                    /tc:selectOneChoice
                    tc:panel /
                /tc:panel

                tc:panel /

                tc:cell spanX=2 /

            /tc:panel
        /tc:page
 /f:view



 Regards,
 Hani

 -Ursprüngliche Nachricht-
 Von: Helmut Swaczinna [mailto:myfa...@wlp-systems.de]
 Gesendet: Dienstag, 31. Mai 2011 16:31
 An: MyFaces Discussion
 Betreff: Re: [Tobago] PageRendererBase warning

 Hi,

 I found this warning often in our customers log file too, but I wasn't 
 able to
 reproduce it myself. I had a look in tobago.js and found this code:

 getAbsoluteLeft: function(element) {
         var left = 0;
         var parent = false;
         while (element    element.offsetParent) {
           left += element.offsetLeft;
           left -= element.scrollLeft;
           if (parent    element.currentStyle) {  // IE only
             left += element.currentStyle.borderLeftWidth.replace(/\D/g, 
 ) - 0;
           }
           element = element.offsetParent;
           parent = true;
         }
         return left;
       }

 I'm not sure, if it's correct for all browsers and if the page content is 
 scrolled.

 Regards,
 Helmut

 Am 31.05.2011 15:51, schrieb Abushammala, Hani (EXTERN: conceptQ):
 Hello,

 Sometimes we got a warning from PageRendererBase class while calling an
 action. In contrast to firefox, internet explorer don`t produce this
 warning.
 I found out, that by decoding the requested page the request parametr
 actionPositionString contains negative pixel values.
 I don`t know what that means and why.

 Log:
 

Re: [tobago] problem with selectBooleanCheckbox

2011-04-27 Thread Bernd Bohmann
Hello Hani,

maybe
-moz-appearance: none !important;
-moz-border-bottom-colors: red;
-moz-border-left-colors: red;
-moz-border-right-colors: red;
-moz-border-top-colors: red;
helps but i never try it

http://support.mozilla.com/sv-SE/questions/774427
https://developer.mozilla.org/en/CSS/-moz-appearance

Regards

Bernd

On Tue, Apr 26, 2011 at 12:56 PM, Abushammala, Hani (EXTERN: conceptQ)
extern.hani.abushamma...@volkswagen.de wrote:
 Hello,

 I have the following problem. Firefox can't display style features for
 check boxes after adding a markup to selectBooleanCheckbox. In contrast
 to firefox, internet explorer displays the style effects.
 I have tried differents style properties like 'border', 'background' and
 'background-color', but it doesn't works.

 Any suggestions?


 Tabago Version: 1.0. 30
 MyFaces: 1.1.7
 FireFox : 4.0
 IE: 6.0


 Regards,
 Hani





Re: JSF application very slow with HTTPS

2011-04-12 Thread Bernd Bohmann
Hello,

maybe it is a richfaces issue see:

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

Regards

Bernd

On Mon, Apr 11, 2011 at 6:42 PM, Mike Kienenberger mkien...@gmail.com wrote:
 Yes, I know that this method has drawbacks, but it's still a good
 alternative in this case as he knows what methods are involved, and he
 has access to the source code so he can change it at the
 htmlTableRenderer.encodeInnerHtml. Data method.

 Not everyone wants to try to set up and learn YourKit, nor evaluate
 it or buy it or any of the other serious profilers.

 If you've already got a profiler installed and are familiar with it,
 go with that.  :)  This is a quick-and-dirty solution that's often
 worked for me.   I've got the eclipse profiler installed, and I've had
 YourKit installed before, but this is often the simplest path for me.

 You can have the results back from this in the time it takes to 1)
 download the h2database jar and drop it into your project, 2) change
 the code, 3) recompile the app, 4) run it.

 On Mon, Apr 11, 2011 at 12:31 PM, Mark Struberg strub...@yahoo.de wrote:
 yea, but most of the time you

 a) don't exactly know what you r looking for
 b) don't like to change your code
 c) will get the the lifecycle wrappers back as 'most expensive' methods...

 LieGrue,
 strub

 --- On Mon, 4/11/11, Mike Kienenberger mkien...@gmail.com wrote:

 From: Mike Kienenberger mkien...@gmail.com
 Subject: Re: JSF application very slow with HTTPS
 To: MyFaces Discussion users@myfaces.apache.org
 Cc: Mark Struberg strub...@yahoo.de
 Date: Monday, April 11, 2011, 4:27 PM
 Or you can go with something a lot
 simpler and start with the free
 profiler provided in the H2Database jar.

 import org.h2.util;
 ...
 Profiler profiler = new Profiler();
 profiler.startCollecting();
 // application code
 System.out.println(profiler.getTop(3));

 http://www.h2database.com/html/performance.html#application_profiling

 For my own use, I've pulled out the three relevant classes
 and removed
 the unnecessary methods if you don't want to grab the
 entire package,
 although that's really trivial to do as well.
 It's about 350 lines
 of code total.

 On Mon, Apr 11, 2011 at 12:12 PM, Mark Struberg strub...@yahoo.de
 wrote:
  Ah sorry, have overread that:
  The time is spent in
  htmlTableRenderer.encodeInnerHtml
 
  I'd start the application with YourKit profiler and do
 some profiling.
 
  You can get a free yourkit test license (14 days I
 think) for evaluation.
 
  LieGrue,
  strub
 
  --- On Mon, 4/11/11, Michael Heinen mhn4...@googlemail.com
 wrote:
 
  From: Michael Heinen mhn4...@googlemail.com
  Subject: Re: JSF application very slow with HTTPS
  To: MyFaces Discussion users@myfaces.apache.org
  Date: Monday, April 11, 2011, 3:45 PM
    Fat? Well there is a lot of EL
  in this table, nearly in all cells,
  e.g. for column widths, values, styles etc.
  The EL is always hitting backing beans, some with
  additional map access.
 
  But the real problem is the poor HTTPS performance
 compared
  to HTTP.
  It should not be caused by the app and also not by
 JSF or
  Tomcat of course.
  There should be a little overhead for additional
  handshaking, but not
  for the rendering!
  Could this be caused by a buffering whereever?
 
  Mark (or anybody else), did you compare your app
 with http
  and https?
  Just wondering whether this is a problem only in
 my app.
 
  Regards,
  Michael
 
 
 
  Am 11.04.2011 17:27, schrieb Mark Struberg:
   Btw another question: 1s local response time?
 How fat
  is this page?
  
   We have a really big page in production with
 1400
  lines in a dataTable - and it renders in 450
 ms...
  
   How many back-and-forth requests do you see
 if you
  open firebug?
   Do you have some EL involved which isn't
 hitting the
  backing bean but directly goes into the database?
 Something
  in this direction...
  
   LieGrue,
   strub
  
   --- On Mon, 4/11/11, Mike Kienenbergermkien...@gmail.com
  wrote:
  
   From: Mike Kienenbergermkien...@gmail.com
   Subject: Re: JSF application very slow
 with HTTPS
   To: MyFaces Discussionusers@myfaces.apache.org
   Cc: Michael Heinenmhn4...@googlemail.com
   Date: Monday, April 11, 2011, 2:20 PM
   I also use
   jetty-6.1.22.   My environment is
  almost
   identical to
   yours, give or take a minor version
 number.
  
   On Mon, Apr 11, 2011 at 7:49 AM, Michael
  Heinenmhn4...@googlemail.com
   wrote:
     Hi,
  
   My JSF application is very slow via
 HTTPS.
   Some parts are 15 times slower
 compared to
  HTTP
  
   I measured the response times of the
 xhtml
  requests
   with Fiddler (locally
   and over network)
  
   Result for a very large page (512 KB)
 with a
  big
   datatable without ajax
   usage:
   --  local access with HTTP:  1 sec
   --  local access with HTTPS: 15-16
 sec
  
   Other pages are factor 2-4 slower,
 with or
  without
   ajax.
   The time is spent in
   htmlTableRenderer.encodeInnerHtml. Data
 is of
  course
   available, there is no 

[ANNOUNCE] Apache MyFaces Tobago 1.0.33

2011-02-16 Thread Bernd Bohmann
The Apache MyFaces team is pleased to announce the release of Apache
MyFaces Tobago 1.0.33.
Apache MyFaces Tobago is a renderkit for JSF and runs with MyFaces Core.

Please check the release notes at
http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12315586
for a full list of the changes in version 1.0.33.

For more information about Apache Tobago, please visit
http://myfaces.apache.org/tobago/.

Have fun,
-The MyFaces team


Re: [TRINIDAD] Downloading Trinidad 1.2.13

2011-02-10 Thread Bernd Bohmann
Hello,

older releases are available in the archive

http://archive.apache.org/dist/myfaces/binaries/

Regards

Bernd

On Thu, Feb 10, 2011 at 12:02 PM, Gururaj, Sandeep
sandeep.guru...@in.pega.com wrote:
 I am not sure if I posted my earlier mail correctly. Hence, resending
 the same.



 ~Sandeep





 From: Gururaj, Sandeep
 Sent: Thursday, February 03, 2011 7:49 PM
 To: 'users@myfaces.apache.org'
 Subject: [TRINIDAD] Downloading Trinidad 1.2.13





 Hi,



 I would like to download Trinidad 1.2.13. However, the Download page
 http://myfaces.apache.org/trinidad/download.html only lists 1.2.14
 http://myfaces.apache.org/trinidad/download.html%20only%20lists%201.2.1
 4 . I was able to see v1.2.13 on this page last month but the same is
 not available this time. Could one of you point me to the URL where I
 can download the archived versions?



 Thanks

 ~Sandeep






Re: [Tobago] Problem with sheet styles and tabGroup (still no answer)

2010-11-16 Thread Bernd Bohmann
Hello Helmut,

I think this is a known llmitation of 1.0.x. This should be solved in 1.5.x see:

https://issues.apache.org/jira/browse/TOBAGO-332

In 1.0.x the Script and the Style tag, are no components just tags.

Maybe volker has a workaround?

Regards

Bernd

On Tue, Nov 16, 2010 at 12:04 PM, Helmut Swaczinna
myfa...@wlp-systems.de wrote:
 Hello,

 I want to change the appearing of a tc:sheet on a specfic page. So I
 overloaded the style classes for tobago-sheet in my page:

    tc:style
      .tobago-sheet-content-odd {
        background-color: #BBCCDD;
      }
      .tobago-sheet-content-even {
        background-color: #BBCCDD;
      }
      .tobago-sheet-body-div {
        background-color: #BBCCDD;
      }
    /tc:style

 This works fine in general. But the sheet is on a tab of a tabGroup. When I
 switch to another tab (Ajax reloading), do a page reload on this tab and
 switch back to the tab with the sheet, the style classes are not applied.
 The sheet appears in the standard look.

 I'm using Tobago 1.0.31 and MyFaces 1.1.5 with Faclets. I've tested this
 with FF 3.6 and IE 7.

 Regards
 Helmut



Re: [Tobago] update model value with tc:hidden

2010-11-08 Thread Bernd Bohmann
Hello Hani,

I'm thinking about a way how to extend the rendered region in a case
of a sheet ajax request.
Can you add an issue for this, please.

And can you explain why you need to update the hidden field?

Regards

Bernd

On Fri, Nov 5, 2010 at 1:59 PM, Abushammala, Hani (EXTERN: conceptQ)
extern.hani.abushamma...@volkswagen.de wrote:
 Hello All,

 What is the recommended way to update model value in a hidden element by
 an ajax request in Tobago?

 I have noticed that only by invoking an action and not by an ajax
 request (e.g. sorting or paging in the sheet) the bounded value in a
 hidden element will be updated.

 Thanks in advanced.

 Regards,
 Hani



[ANNOUNCE] Apache MyFaces Tobago 1.0.29

2010-09-24 Thread Bernd Bohmann
The Apache MyFaces team is pleased to announce the release of Apache
MyFaces Tobago 1.0.29.
Apache MyFaces Tobago is a renderkit for JSF and runs with MyFaces Core.

MyFaces Tobago 1.0.29 is available in both binary and source distributions.

  * http://myfaces.apache.org/tobago/download.html

MyFaces Tobago is also available in the central Maven repository under
Group ID org.apache.myfaces.tobago.

Please check the release notes at
http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12315262
for a full list of the changes in version 1.0.29.


For more information about Apache MyFaces Tobago, please visit
http://myfaces.apache.org/tobago/.

Have fun,
 -The MyFaces team


Re: [Tobago] Script error - tx:date

2009-12-17 Thread Bernd Bohmann
Hello Alf,

can you test the latest nighly build of 1.0.24.
The continuum server has not updated the nightly build automatically.

Regards

Bernd

2009/12/11 Alf Felis alf.fe...@gmx.de:
 Uups,

 wrong header... my fault :)


 The question again:

 --

 Hi all,

 I noticed an error using tx:date with IE 6.0 (FF works fine) in Version
 myfaces-tobago-1.0.24-SNAPSHOT-dist.zip (from today).

 I figured out that IE7 has a problem too, but IE8 seems to have no problem 
 with the datepicker.

 Using this testpage

 -
 %@ taglib uri=http://myfaces.apache.org/tobago/component; prefix=tc% %@ 
 taglib uri=http://myfaces.apache.org/tobago/extension; prefix=tx% %@ 
 taglib uri=http://java.sun.com/jsf/core; prefix=f%

 f:view
  tc:page
    tx:date value= label=Testdate /
  /tc:page
 /f:view

 -

 shows the following javascript error (in german) when clicking the datepicker:

 -
 Es ist ein Laufzeitfehler aufgetreten. Soll der Debugmodus gestartet werden?

 Zeile: 1044 Fehler: Das Steuerelement kann den Focus nicht erhalten, da 
 dieses unsichtbar oder nicht aktiviert ist oder keinen Focus zulنكt.

 -

 After approving the error dialog and pressing ok/cancel in the datepicker, 
 the date will be set and everything seems to be ok.

 Tobago version myfaces-tobago-1.0.23-dist.zip works perfectly in this case :)

 Best regards

 Alf

 --
 Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
 sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser



Re: [Tobago] Error using paging (tc:sheet) in IE

2009-09-11 Thread Bernd Bohmann
Hello Alf,

just added a fix for this.

Can you test it with the latest nightly build of 1.0.24-SNAPSHOT, please.

http://people.apache.org/builds/myfaces/nightly/

Regards

Bernd

On Thu, Sep 10, 2009 at 6:45 PM, Volker Weber v.we...@inexso.de wrote:
 Hi Alf,

 I think this is the above bug, or a similar one.

 The IE submits a request on enter in the only one textfield and
 executes the onKeydown code which makes an ajax request.

 If there are more textfields the IE did not submit on enter and the
 only submit is from the onKeydown code.

 I checked a solution with return false in the eventHandler (also on
 keyup and keypress) but this did not solve this Problem.


 Maybe a tc:in somewhere out of sight ( in a layout cell with 0px ? )
 could solve this.


 Regards,
    Volker


 2009/9/10 Alf Felis alf.fe...@gmx.de:
 Hi Marcus,

 I'm not sure if this is the problem. Maybe I'm wrong, but I noticed that IE 
 sends two requests to the server if I start paging... FF only sends one 
 request. See below.

 The problem is not, that submitting the page doesn't post the parameter at 
 all. Or I have misunderstood the IE bug description :)

 I think the second request overwrites the first one.
 Because the second request has an empty value for parameter 
 _idJsp0::form-action it seems to be a simple reload without changing the 
 displayed row.

 First:  _idJsp0::form-action: _idJsp0:_idJsp1:ToRow
 Second: _idJsp0::form-action: 

 Hope that helps :)

 Regards

 Alf


 The examples below show the requested URIs with the parameters set (if any).

 Here the example (IE go from row 1 to row 50):
 --
 URI: /Tobago/org/apache/myfaces/tobago/renderkit/html/standard/blank.html
 URI: /Tobago/faces/TobagoTest.jsp
 Parameters:
 _idJsp0:_idJsp1::scrollPosition:
 _idJsp0::form-action: _idJsp0:_idJsp1:ToRow
 _idJsp0:_idJsp1::widths: ,381,
 jsf_tree: 1
 _idJsp0::context-path: /Tobago
 _idJsp0::action-position: 33px,286px,25px,14px
 jsf_viewid: /TobagoTest.jsp
 _idJsp0:_idJsp1::selected: ,
 affectedAjaxComponent: _idJsp0:_idJsp1
 _idJsp0:_idJsp1:ToRow::value: 50
 _:
 URI: /Tobago/faces/TobagoTest.jsp
 Parameters:
 _idJsp0:_idJsp1::scrollPosition:
 _idJsp0::form-action:
 _idJsp0:_idJsp1::widths: ,381,
 _idJsp0::context-path: /Tobago
 jsf_tree: 1
 _idJsp0::action-position: 33px,286px,25px,14px
 jsf_viewid: /TobagoTest.jsp
 _idJsp0:_idJsp1::selected: ,
 _idJsp0:_idJsp1:ToRow::value: 50
 _idJsp0::form-clientDimension: 1074;893
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/style/style.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/scarborough/msie/style/style.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/standard/style/style.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/msie/style/style.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/style/tobago-sheet.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/scarborough/msie/style/tobago-sheet.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/standard/style/tobago-sheet.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/msie/style/tobago-sheet.css
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/prototype.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/standard/msie/script/tobago.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/theme-config.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/script/theme-config.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/standard/script/theme-config.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/tobago-sheet.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/script/tobago-sheet.js
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/standard/image/sheetFirstDisabled.gif
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/standard/image/sheetPrevDisabled.gif
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/standard/image/sheetNext.gif
 URI: 
 /Tobago/org/apache/myfaces/tobago/renderkit/html/speyside/standard/image/sheetLast.gif

 *
 The same with FF:
 -

 URI: /Tobago/faces/TobagoTest.jsp
 Parameters:
 _idJsp0:_idJsp1::scrollPosition:
 _idJsp0::form-action: _idJsp0:_idJsp1:ToRow
 _idJsp0:_idJsp1::widths: ,379,
 jsf_tree: 9
 _idJsp0::context-path: /Tobago
 _idJsp0::action-position: 0px,0px,0px,0px
 jsf_viewid: /TobagoTest.jsp
 _idJsp0:_idJsp1::selected: ,
 affectedAjaxComponent: _idJsp0:_idJsp1
 _idJsp0:_idJsp1:ToRow::value: 50
 _:



 -Ursprüngliche Nachricht-
 Von: Marcus Kröger marcus.kroe...@googlemail.com
 Gesendet: 10.09.09 

Re: [Tobago] Error using paging (tc:sheet) in IE

2009-09-08 Thread Bernd Bohmann
Hello Alf,

just tested with http://myfaces.apache.org/tobago/demo.html in IE6 but
Linux. Found no issue.

Can you test the sheet with the online demo, please.

Please clear all caches in IE.

Regards

Bernd

On Tue, Sep 8, 2009 at 5:58 PM, Alf Felisalf.fe...@gmx.de wrote:
 Hello,

 I'm new to Tobago and I have a problem with sheet paging in IE (FF works!). I 
 think its a bug... possibly its my fault (IE settings?).

 Tabago Version: 1.0.22
 MyFaces: 1.1.6
 IE Version: 6

 When I type a row number to jump to and press enter, I notice, that the 
 server gets multiple requests.

 One of the requests from IE seems to be wrong... the parameter 
 _idJsp0::form-action, which contains the _idJsp0:_idJsp3:ToRow entry in 
 the first request, is empty! This request seems to be the problem.

 It seems that first the browser shows the correct result (jump to the row; 
 only visible for short) and than reloads the page and jumps back to the old 
 view.

 I already opened a Bug report in JIRA: TOBAGO-788
 But no answer so far :(


 Thanks for your help :)

 Alf


 My simple testpage:

 %@ taglib uri=http://myfaces.apache.org/tobago/component; prefix=tc%
 %@ taglib uri=http://java.sun.com/jsf/core; prefix=f%

 f:view
 tc:page width=400 height=300
 tc:sheet var=var
 value=#{tobagoTestBean.data}
 showPageRange=right
 showRowRange=left
 rows=25
 tc:column label=Col
 tc:out value=#{var} /
 /tc:column
 /tc:sheet
 /tc:page
 /f:view

 The test bean only provides a list of 100 strings.

 --
 Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
 sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser



Re: [Tobago] getting started

2009-02-13 Thread Bernd Bohmann
Hello Daphna,

can you send the list of WEB-INF/lib please.

Maybe a compatibilty issue between some JSF libs.

Please don't mix myfaces-api and myfaces-impl with the SUN JSF Impl.

Regards

Bernd


Daphna Deutsch schrieb:
 Hello,
 
  
 
 I’m trying to add Tobago to my project, so I can use its JSF components.
 
 Please see the attached file.
 
  
 
 Thanks,
 
 Daphna Deutsch
 
  
 



Re: [tobago] ResourceLocator and JBoss 5.0 vfszip protocol running on windows

2009-01-12 Thread Bernd Bohmann
Hello Stefan,

thanks for your efforts in testing tobago with JBoss 5.0.0.
Can you create an issue with the patch applied, please.

Regards

Bernd

Stefan Hedtfeld schrieb:
 Hi,
 
 I'm working with tobago 1.1.0 SNAPSHOT and run in a problem deploying my
 application on JBoss 5.0.0.GA on a windows machine. The problem arises
 when the theme jars are scanned for the obago config as JBoss 5
 introduced a new protocol vfszip: - I already fixed for a Linux
 environment. The weird thing (for me) is that the URL class cannot
 handle the backslash itself - so I added a line replacing backslashes by
 slashes in case of File's separator char is backslash itself.
 
 If you are interested a appended the patch file - you might want to
 remove the logging, feel free.
 
 Regards,
 
 Stefan.


Re: [tobago] Binding for tc:menuBar

2008-12-30 Thread Bernd Bohmann
Hello Stefan,

for 1.1.0-SNAPSHOT it should be

org.apache.myfaces.tobago.component.UIMenuBar

http://myfaces.apache.org/tobago/tobago-core/tlddoc/tc/menuBar.html

for 1.0.x it should be

javax.faces.component.UIPanel

http://myfaces.apache.org/tobago/tobago-core/tlddoc-1.0.20/tc/menuBar.html

Regards

Bernd

Stefan Hedtfeld schrieb:
 Hi,
 
 I'm using tobago 1.1.0-SNAPSHOT and I would like to use a tc.menuBar
 with a binding  - meaning I would like to provide the menu data by a
 backing bean. What type / class is expected to be returned for this
 binding?
 
 Regards,
 
 Stefan.
 


Re: JSF servlet request in action method or navigation rule to get binary servlet data?

2008-12-10 Thread Bernd Bohmann
Hello Andreas,

is your action immediate=true ?

Regards

Bernd

Andreas Niemeyer schrieb:
 yippi :)
 
 Thank you all!
 
 Regards,
 Andreas
 
 Richard Yee schrieb:
 Try using divelement.style.display=none

 Regards,

 Richard


 On Wed, Dec 10, 2008 at 6:27 AM, Andreas Niemeyer
 [EMAIL PROTECTED] wrote:
 Hi,

 It works.

 The only problem is the left space from the invisible div tag.


 Regards,
 Andreas



 div id=error_messages style=color: darkred;visibility: visible 
t:messages id=error_messages showDetail=true
 showSummary=false
 /
 /div

 
 h:commandButton id=reportbutton
 onclick=clearMessages('error_messages')
 value=#{msgs.CreateReportButton}
 action=#{pdfreport.createPDFReport} /



 JavaScript:

 function clearMessages(aMessagesID) {
var divelement = document.getElementById(aMessagesID);
divelement.style.visibility='hidden';
 }


 Andreas Niemeyer schrieb:
 Hello Helmut,

 Good proposal to handle this about JavaScript before send the form.
 I'll
 give it a trial.

 Kind regards,
 Andreas


 Helmut Swaczinna schrieb:
 Hello Andreas,

 I don't think Tobago or JSF can clear the messages for you. But you
 can
 clear the messages on the page  yourself  with
 some javascript before the action for the PDF generation gets
 submitted.

 For example:

 ...
 action=controller.createPDF
 onclick=clearMessagesAndSubmit('@autoId')
 ...

 function clearMessagesAndSubmit(actionId) {
  // Find messages and clear them
  Var message = document.getElenemtById('page:message');
  message.value = ;
  Tobago.submitAction(actionId, false);
 }

 I haven't tried this, but I think it should work.

 Regards
 Helmut

 - Original Message - From: Andreas Niemeyer
 [EMAIL PROTECTED]
 To: users@myfaces.apache.org
 Sent: Wednesday, December 10, 2008 11:11 AM
 Subject: Re: JSF servlet request in action method or navigation
 rule to
 get binary servlet data?


 Hello Bernd,

 Yes, I did.

 There seems to be no way to get previous messages away due I don't
 get
 the page reloaded.

 I'll open a new thread and try to describe in more detail the
 requirements.


 Thank you.

 Regards,
 Andreas



 Bernd Bohmann schrieb:
 Hello Andreas,

 are you calling
 FacesContext.getCurrentInstance().responseComplete() ?

 Regards

 Bernd


 Andreas Niemeyer schrieb:
 Hello Bernd,

 Thank you for response.

 Unfortunatly I have to use this servlet as a pdf dynamic provider.

 The redirect works fine so far, but another thing happened.

 Due some validation rules in the same method, a previous custom
 FacesMessage stays displayed and only after a page reload it goes
 away.

 Have someone an idea?

 Regards,
 Andreas



 Bernd Bohmann schrieb:
 Hello Andreas,

 maybe this help:

 http://wiki.apache.org/myfaces/Sending_Files

 You don't need a Servlet for sending binary data from jsf.

 The magic is the responseComplete() method.

 Please look at the Section

 2.1.3 Faces Request Generates Non-Faces Response

 of the jsf 1.1 spec.

 Regards

 Bernd

 Andreas Niemeyer schrieb:
 Hi,

 I would like to send form data from a JSF page for a servlet
 request
 with a navigation rule.

 The servlet returns a content type of application/pdf and is
 running
 in a context path.

 If I call it from within a action method, it works with following
 code:

 public String createPDFReport() {
 ...
  FacesContext context = FacesContext.getCurrentInstance();
  ExternalContext ext = context.getExternalContext();

  String vServletPath = /context_path/pdf-test;
  ext.redirect(ext.encodeResourceURL(vServletPath));

  ...
  return call_servlet;
 }


 My context is a portal, I'm using the JSF portal bridge.


 The web.xml looks like:

 ...
 servlet
  servlet-namepdf-test/servlet-name
 servlet-classcom.xxx.PDFTest/servlet-class
  load-on-startup20/load-on-startup
 /servlet...

 I would like to avoid to send a redirect and would prefer to
 create
 a
 navigation rule in the faces-config, but it fails with an
 exception
 arised from my GenericPortlet

 ...

 public class JSFGenericPortlet
extends org.apache.myfaces.portlet.MyFacesGenericPortlet {
 ...
 public void render(RenderRequest req, RenderResponse res)
throws IOException, PortletException {
 ...
 super.render(req, res);
 }
 ...
 }

 javax.portlet.PortletException: String index out of range: -1
at

 org.apache.myfaces.portlet.MyFacesGenericPortlet.handleExceptionFromLifecycle(MyFacesGenericPortlet.java:310)



at

 org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:502)



at

 org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:323)



at
 javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
at
 javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
at

 com.gutzmann.portlets.JSFGenericPortlet.render(JSFGenericPortlet.java:73)




 The navigation rule looks like:

navigation-rule
from-view-id/pages/view.xhtml/from-view-id

Re: [Tobago] Problem with NonFacesRequestServlet (correction)

2008-12-09 Thread Bernd Bohmann
Hello Helmut,

I asume you are using facelets?
Which JSF Implementation are you using?
In a internal project I switched from myfaces impl to sun ri because of
this issue.

Regards

Bernd

Helmut Swaczinna schrieb:
 Hi,
 
 I just tried to use the NonFacesRequestServlet but I got a problem I can't
 solve. The servlet is
 called and the initial page is displayed as expexted. But when I execute an
 action on the page
 the URL is prepended with the servlet name and cannot be resolved:
 
 This is the initial URL wich calls the NonFacesRequestServlet
 
 http://localhost:8080/MyWebapp/OpenMediaRequest.jsf?titel=abc
 
 When I execute an action the URL is
 
 http://localhost:8080/MyWebapp/OpenMediaRequest.jsf/edit.xml;jsessionid=59135BB960B04D4B759D5ECFAB6074FA
 
 
 This is my web.xml
 
  context-param
param-namejavax.faces.DEFAULT_SUFFIX/param-name
param-value.xml/param-value
  /context-param
 
  servlet
servlet-nameFacesServlet/servlet-name
servlet-classjavax.faces.webapp.FacesServlet/servlet-class
load-on-startup3/load-on-startup
  /servlet
 
  servlet
servlet-nameOpenMediaRequestServlet/servlet-name
   
 servlet-classde.wlps.ndr.workflow.beitragsid.webapp.web.OpenMediaRequestServlet/servlet-class
 
load-on-startup1/load-on-startup
  /servlet
 
  servlet-mapping
servlet-nameFacesServlet/servlet-name
url-pattern*.jsf/url-pattern
  /servlet-mapping
 
  servlet-mapping
servlet-nameOpenMediaRequestServlet/servlet-name
url-pattern/OpenMediaRequest.jsf/url-pattern
  /servlet-mapping
 
 and my faces-config.xml
 
  navigation-rule
navigation-case
  from-outcomeedit/from-outcome
  to-view-id/edit.xml/to-view-id
/navigation-case
  /navigation-rule
 
 This is the NonFacesRequestServlet
 
 public class OpenMediaRequestServlet extends NonFacesRequestServlet {
 
  private static final Log LOG =
 LogFactory.getLog(OpenMediaRequestServlet.class);
 
  public String invokeApplication(FacesContext facesContext) {
 
String titel =
 (String)facesContext.getExternalContext().getRequestParameterMap().get(titel);
 
LOG.info(invokeApplication: titel=' + titel + ');
 
return edit;
  }
 
 }
 
 
 Did I something wrong? I don't think so. I'm using Tobago 1.013. Please
 help!
 
 Regards
 Helmut
 
 
 
 
 
 


Re: JSF servlet request in action method or navigation rule to get binary servlet data?

2008-12-09 Thread Bernd Bohmann
Hello Andreas,

maybe this help:

http://wiki.apache.org/myfaces/Sending_Files

You don't need a Servlet for sending binary data from jsf.

The magic is the responseComplete() method.

Please look at the Section

2.1.3 Faces Request Generates Non-Faces Response

of the jsf 1.1 spec.

Regards

Bernd

Andreas Niemeyer schrieb:
 Hi,
 
 I would like to send form data from a JSF page for a servlet request
 with a navigation rule.
 
 The servlet returns a content type of application/pdf and is running
 in a context path.
 
 If I call it from within a action method, it works with following code:
 
 public String createPDFReport() {
 ...
  FacesContext context = FacesContext.getCurrentInstance();
  ExternalContext ext = context.getExternalContext();
 
  String vServletPath = /context_path/pdf-test;
  ext.redirect(ext.encodeResourceURL(vServletPath));
 
  ...
  return call_servlet;
 }
 
 
 My context is a portal, I'm using the JSF portal bridge.
 
 
 The web.xml looks like:
 
 ...
 servlet
  servlet-namepdf-test/servlet-name   
  servlet-classcom.xxx.PDFTest/servlet-class
  load-on-startup20/load-on-startup
 /servlet
 ...
 
 I would like to avoid to send a redirect and would prefer to create a
 navigation rule in the faces-config, but it fails with an exception
 arised from my GenericPortlet
 
 ...
 
 public class JSFGenericPortlet
 extends org.apache.myfaces.portlet.MyFacesGenericPortlet {
 ...
 public void render(RenderRequest req, RenderResponse res)
 throws IOException, PortletException {
 ...
 super.render(req, res);
 }
 ...
 }
 
 javax.portlet.PortletException: String index out of range: -1
 at
 org.apache.myfaces.portlet.MyFacesGenericPortlet.handleExceptionFromLifecycle(MyFacesGenericPortlet.java:310)
 
 at
 org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:502)
 
 at
 org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:323)
 
 at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
 at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
 at
 com.gutzmann.portlets.JSFGenericPortlet.render(JSFGenericPortlet.java:73)
 
 
 The navigation rule looks like:
 
 navigation-rule
 from-view-id/pages/view.xhtml/from-view-id
 navigation-case
 from-outcomecall_servlet/from-outcome
 to-view-id/pdf-test//to-view-id
 /navigation-case
 /navigation-rule
 
 I tried also `to-view-id/context_path/pdf-test//to-view-id' - same
 exception.
 
 
 
 What is the best practice to do such redirect / servlet calls?
 
 
 If request parameter should be changed, how would it work in the action
 method?
 
 
 Many thanks fro some help!
 
 
 Regards,
 Andreas
 
 
 
 
 
 


Re: JSF servlet request in action method or navigation rule to get binary servlet data?

2008-12-09 Thread Bernd Bohmann
Hello Andreas,

are you calling FacesContext.getCurrentInstance().responseComplete() ?

Regards

Bernd


Andreas Niemeyer schrieb:
 Hello Bernd,
 
 Thank you for response.
 
 Unfortunatly I have to use this servlet as a pdf dynamic provider.
 
 The redirect works fine so far, but another thing happened.
 
 Due some validation rules in the same method, a previous custom
 FacesMessage stays displayed and only after a page reload it goes away.
 
 Have someone an idea?
 
 Regards,
 Andreas
 
 
 
 Bernd Bohmann schrieb:
 Hello Andreas,

 maybe this help:

 http://wiki.apache.org/myfaces/Sending_Files

 You don't need a Servlet for sending binary data from jsf.

 The magic is the responseComplete() method.

 Please look at the Section

 2.1.3 Faces Request Generates Non-Faces Response

 of the jsf 1.1 spec.

 Regards

 Bernd

 Andreas Niemeyer schrieb:
 Hi,

 I would like to send form data from a JSF page for a servlet request
 with a navigation rule.

 The servlet returns a content type of application/pdf and is running
 in a context path.

 If I call it from within a action method, it works with following code:

 public String createPDFReport() {
 ...
  FacesContext context = FacesContext.getCurrentInstance();
  ExternalContext ext = context.getExternalContext();

  String vServletPath = /context_path/pdf-test;
  ext.redirect(ext.encodeResourceURL(vServletPath));

  ...
  return call_servlet;
 }


 My context is a portal, I'm using the JSF portal bridge.


 The web.xml looks like:

 ...
 servlet
  servlet-namepdf-test/servlet-name  
  servlet-classcom.xxx.PDFTest/servlet-class
  load-on-startup20/load-on-startup
 /servlet...

 I would like to avoid to send a redirect and would prefer to create a
 navigation rule in the faces-config, but it fails with an exception
 arised from my GenericPortlet

 ...

 public class JSFGenericPortlet
 extends org.apache.myfaces.portlet.MyFacesGenericPortlet {
 ...
 public void render(RenderRequest req, RenderResponse res)
 throws IOException, PortletException {
 ...
 super.render(req, res);
 }
 ...
 }

 javax.portlet.PortletException: String index out of range: -1
 at
 org.apache.myfaces.portlet.MyFacesGenericPortlet.handleExceptionFromLifecycle(MyFacesGenericPortlet.java:310)


 at
 org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:502)


 at
 org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:323)


 at
 javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
 at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
 at
 com.gutzmann.portlets.JSFGenericPortlet.render(JSFGenericPortlet.java:73)



 The navigation rule looks like:

 navigation-rule
 from-view-id/pages/view.xhtml/from-view-id
 navigation-case
 from-outcomecall_servlet/from-outcome
 to-view-id/pdf-test//to-view-id
 /navigation-case
 /navigation-rule

 I tried also `to-view-id/context_path/pdf-test//to-view-id' - same
 exception.



 What is the best practice to do such redirect / servlet calls?


 If request parameter should be changed, how would it work in the action
 method?


 Many thanks fro some help!


 Regards,
 Andreas







 
 


Re: [Tobago] navigation issue

2008-12-04 Thread Bernd Bohmann
Hello Mario,

I don't see any reason why this shouldn't work.

Can you send the complete page, please.

Is your page containing a tc:page?

Regards

Bernd

Mario Schröder schrieb:
 Hi,
 
 I wrote a simple app whith a single bean and two pages, one to enter some 
 text and another page to display the result. I used MyFaces 1.1.5 and Tobago 
 1.0.12 and 1.0.20. My sample works with myfaces but not with Tobago. Tobago 
 displays always the same page. I thought the cause is that my bean returns 
 the wrong navigation rule, so I tried a static rule, unfortunetly it doesn't 
 help. The same navigation rule applies to the myfaces sample, and there it 
 works.
 I'm getting slightly mad. Who can help me and show me what am I doing wrong?
 
 Here are the important pieces of my code:
 
 faces-config.xml:
 ...
 managed-bean
   managed-bean-namebean/managed-bean-name
   managed-bean-classtest.TextBean/managed-bean-class
   managed-bean-scopesession/managed-bean-scope
   managed-property
   property-nametext/property-name
   valueTest/value
   /managed-property
 /managed-bean
 
 navigation-rule
   navigation-case
   from-outcomeshow/from-outcome
   to-view-id/result.jsp/to-view-id
   /navigation-case
 /navigation-rule
 ...
 
 The myfaces page:
 ...
 f:view
 h1h:outputText value=MyFaces //h1
 h:form
 h:inputText value=#{bean.text} /
 h:commandButton action=#{bean.nextAction} value=submit /
 /h:form
 /f:view
 ...
 
 The Tobago page:
 ...
 tc:box label=Address
 f:facet name=layout
 tc:gridLayout rows=fixed;fixed/
 /f:facet
 tc:form
 tx:in label=First Name value=#{bean.text}/
 
 tc:button action=#{bean.nextAction} label=save /
 /tc:form
 /tc:box
 ...
 
 And the nextAction()-Method of my bean:
 ...
 public String nextAction(){
   return show;
 }
 ...
 
 I appreciate any hints or help.
 
 Pt! Schon vom neuen WEB.DE MultiMessenger gehört? 
 Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123
 
 


Re: [Tobago] navigation issue

2008-12-04 Thread Bernd Bohmann
Hello Mario,

please add a tc:messages tag to your page.

Regards

Bernd

Bernd Bohmann schrieb:
 Hello Mario,
 
 I don't see any reason why this shouldn't work.
 
 Can you send the complete page, please.
 
 Is your page containing a tc:page?
 
 Regards
 
 Bernd
 
 Mario Schröder schrieb:
 Hi,

 I wrote a simple app whith a single bean and two pages, one to enter some 
 text and another page to display the result. I used MyFaces 1.1.5 and Tobago 
 1.0.12 and 1.0.20. My sample works with myfaces but not with Tobago. Tobago 
 displays always the same page. I thought the cause is that my bean returns 
 the wrong navigation rule, so I tried a static rule, unfortunetly it doesn't 
 help. The same navigation rule applies to the myfaces sample, and there it 
 works.
 I'm getting slightly mad. Who can help me and show me what am I doing wrong?

 Here are the important pieces of my code:

 faces-config.xml:
 ...
 managed-bean
  managed-bean-namebean/managed-bean-name
  managed-bean-classtest.TextBean/managed-bean-class
  managed-bean-scopesession/managed-bean-scope
  managed-property
  property-nametext/property-name
  valueTest/value
  /managed-property
 /managed-bean

 navigation-rule
  navigation-case
  from-outcomeshow/from-outcome
  to-view-id/result.jsp/to-view-id
  /navigation-case
 /navigation-rule
 ...

 The myfaces page:
 ...
 f:view
 h1h:outputText value=MyFaces //h1
 h:form
 h:inputText value=#{bean.text} /
 h:commandButton action=#{bean.nextAction} value=submit 
 /
 /h:form
 /f:view
 ...

 The Tobago page:
 ...
 tc:box label=Address
 f:facet name=layout
 tc:gridLayout rows=fixed;fixed/
 /f:facet
 tc:form
 tx:in label=First Name value=#{bean.text}/

 tc:button action=#{bean.nextAction} label=save /
 /tc:form
 /tc:box
 ...

 And the nextAction()-Method of my bean:
 ...
 public String nextAction(){
  return show;
 }
 ...

 I appreciate any hints or help.
 
 Pt! Schon vom neuen WEB.DE MultiMessenger gehört? 
 Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123


 


Re: Correction: [TOBAGO] tc.gridlayout does not work inside a sheets column

2008-11-22 Thread Bernd Bohmann
Hello Groovie,

a column should only contain one child.
Please try it with a surrounding panel.

tc:column id=... align=top
  tc:panel
f:facet name=layout
  tc:gridLayout rows=*;*/
/f:facet
tc:panel width=400px rendered=#{itm.type == 'View1'}
  f:facet name=layout
tc:gridLayout columns=50%;50%/
  /f:facet

 tc: /

 tc: /
/tc:panel
tc:panel rendered=#{itm.type == 'View2'}
/tc:panel
  /tc:panel
/tc:column

The sheet issued a warning about More or less than 1 child in column! 

I think we should extend this warning in the case of more than one child
in column.

See https://issues.apache.org/jira/browse/TOBAGO-728

Regards

Bernd


Groovie schrieb:
 Hy there,
 
 the workaround for this issue is to assign a 
 with-value to the column or the first 
 panel element.
 
 
 tc:sheet  columns=25px;1*  
 
   tc:column id=... align=top 
 tc:selectBooleanCheckbox id=...  value=.. / 
   /tc:column 
 
   tc:column id=... align=top 
  tc:panel width=400px rendered=#{itm.type == 'View1'} 
f:facet name=layout 
   tc:gridLayout columns=50%;50%/ 
/f:facet 
 
 tc: /
 
 tc: /
  /tc:panel 
 
 It looks like, that the tc:column does not have any useful
 information concerning its dimension. Maybe its is also 
 a kind of sequence problem. Perhaps, the tc:sheet is
 not completly rendered, when the panel starts asking
 the column tag, how fat he is ;-)
 
 Maybe a Tobago Developer has an explanation for this ?!?!
 
 
 Groovie
 
 
 


Re: Correction: [TOBAGO] tc.gridlayout does not work inside a sheets column

2008-11-20 Thread Bernd Bohmann
Hello Groovie,

i will look at this issue tonight or tomorrow.

Regards

Bernd

Groovie schrieb:
 Hy there,
 
 the workaround for this issue is to assign a 
 with-value to the column or the first 
 panel element.
 
 
 tc:sheet  columns=25px;1*  
 
   tc:column id=... align=top 
 tc:selectBooleanCheckbox id=...  value=.. / 
   /tc:column 
 
   tc:column id=... align=top 
  tc:panel width=400px rendered=#{itm.type == 'View1'} 
f:facet name=layout 
   tc:gridLayout columns=50%;50%/ 
/f:facet 
 
 tc: /
 
 tc: /
  /tc:panel 
 
 It looks like, that the tc:column does not have any useful
 information concerning its dimension. Maybe its is also 
 a kind of sequence problem. Perhaps, the tc:sheet is
 not completly rendered, when the panel starts asking
 the column tag, how fat he is ;-)
 
 Maybe a Tobago Developer has an explanation for this ?!?!
 
 
 Groovie
 
 
 


Re: [tobago] and facelets: using composition

2008-11-10 Thread Bernd Bohmann
Hello Stefan,

the transient property is for the state saving.

http://java.sun.com/javaee/javaserverfaces/1.1_01/docs/api/javax/faces/component/StateHolder.html#isTransient()

You can skip the comments with following context-param

context-param
param-namefacelets.SKIP_COMMENTS/param-name
param-valuetrue/param-value
  /context-param

Just added a section about facelets to the Tobago faq.

An other note:
Your facelets should not contain any body or html tags or DOCTYPE
declaration. Tobago writes these tags to the html page.

Regards

Bernd

Stefan Hedtfeld schrieb:
 Hi Bernd,
 
 as far as I'm concerned this change fixes my original layout problems.
 
 I'm still not sure if the root of the problem is somewhere else. Why do
 you get the comments as children, anyway? And I'm not sure if the
 transient property is the correct one to decide if the child component
 should be ignored.
 
 I haven't filed a bug so far, shall I do this and attach the fix to it?
 
 Regards,
 
 Stefan.
 
 Stefan Hedtfeld schrieb:
 Hi Bernd,

 I guess I found a problem in LayoutUtil (not sure if the root of the
 problem is another one). When adding the children the lines containing
 comments are considered components. If you skip these (using
 child.isTransient()) the layout seems to be correct (I will have to
 test with a more complex example).

 See the attached diff for LayoutUtil.

 Regards,

 Stefan.

 
 


Re: Problem with the My Faces Wagon Plugin

2008-11-04 Thread Bernd Bohmann
Hello Praveen,

can you use a relative inputDirectory target/gbi_backups.
And can you send the debug output
mvn -X

Regards

Bernd

Durbha, Praveen (GE Healthcare) schrieb:
 Hi,
  
 I am having a problem using the Wagon Plugin as described here
  
 http://myfaces.apache.org/wagon-maven-plugin/deploy-mojo.html
 blocked::http://myfaces.apache.org/wagon-maven-plugin/deploy-mojo.html
 
  
 I have the plugin set up as below in my pom.xml file and I am expecting
 the files in the inputDirectory gbi_backups to be FTPed on to a remote
 server gbi-test..but it does not happen..
  
 Any ideas ?
  
 Thanks
  
!-- Wagon Maven Plugin to deploy files into remote server --
 plugin
  groupIdorg.apache.myfaces.maven/groupId
  artifactIdwagon-maven-plugin/artifactId
  configuration
   idgbi-test.am.med.ge.com/id
  
 inputDirectoryC:/dev/views/gbi_view/cbs_hlp/target/gbi_backups/inputD
 irectory
   urlftp://gbi-test/url
  /configuration
 /plugin
 


Re: [tobago] and facelets: using composition

2008-11-01 Thread Bernd Bohmann
Hello Stefan,

can you attach an example page, please.

I will ask Udo for some information about the new layout management in
Tobago. Maybe the Unit-Tests in

core/src/test/java/org/apache/myfaces/tobago/layout/grid

provides some information.

Regards

Bernd

Stefan Hedtfeld schrieb:
 Hi,
 
 providing information about width and height - which are set to the
 default values 1024 and 768 in my case - leads to the next error: an
 index out of bounds exception when calling the solve() method on the
 vertical EquationManager in LayoutContext.layout(). I can fix this in
 EquationManager (copying the data array to the resulting array with
 regard to the data array length). But this still doesn't help. At least
 there are no exceptions in the logs anymore :)
 
 As the LayoutContext seems to be quite new maybe there are some
 implementation gaps left? If so - and if anyone is willing to provide
 information about the concept or idea of the layouting mechanism - I
 would like to help filling the gaps.
 
 Regards,
 
 Stefan.
 
 Stefan Hedtfeld schrieb:
 Hi,

 when I change the getConstraints mehtod to create a constraints
 instance (like in UIInputBase) the next NullPointerException arises
 when accessing width and height - thought there is an (this$0)
 instance which contains the information (as strings).

 I'll take a look at this when I have some more time - if you have any
 hint how to proceed I'd be happy!

 Regards,

 Stefan.

 Stefan Hedtfeld schrieb:
 Hi,

 I've updated to revision 708014. Before the warnings about the
 unbalanced layout appear in the logs now a NullPointerException is
 printed in LayoutContext line 49. The field container returns null
 for container.getConstraints().

 Maybe I have to add some configuration so the new LayoutContext will
 work with the container?

 Regards,

 Stefan.

 Bernd Bohmann schrieb:
 Hello Stefan,

 the 1.1.x trunk is a little bit buggy now. We try to refactor the
 layouting and many other parts of Tobago. I can look at your issue at
 the weekend.

 Regards

 Bernd

 Stefan Hedtfeld schrieb:
  
 Hi,

 I'm switching from using jsp to faclets and am currently working on a
 prototype using tobago-1.1.0-SNAPSHOT and sun RI 1.2 on JBoss. I
 started
 with a layout which worked for jsps, and began to migrate it to
 facelets. As this didn't work as expected I tried to simplify the
 layout
 and finally came to a point where I only have three parts in my
 layout:
 a header, the body (content) and a footer. But I still get weird rows
 with 0px height and columns with 0px width in the resulting html.

 Here is some code:

 app/home.xhtml:

  ui:composition template=/templates/master.xhtml
tc:loadBundle basename=bundle var=mainBundle /
ui:define name=title#{mainBundle.pageTitle}/ui:define
ui:define name=body
  tx:date id=test label=Label/
/ui:define
  /ui:composition

 templates/master.xhtml:

  f:view locale=#{clientConfiguration.locale}
tc:loadBundle basename=bundle var=mainBundle /
tc:page label=#{mainBundle.pageTitle} id=masterpage
 width=800
 height=600

  f:facet name=layout
tc:gridLayout border=1 margin=1px columns=*
 rows=fixed;fixed;*;fixed  /
  /f:facet

  !-- row 0 --
  tc:link action=app/home immediate=true
  image=image/logo_tiny.gif /

  !-- row 1 --
  ui:insert name=body
ui:include src=/templates/body.xhtml/
  /ui:insert
  !-- row 2 --
  tc:cell/

  !-- row 3 --
  tc:out value=#{mainBundle.copyrightNote}/

/tc:page
  /f:view

 templates/header.xhtml

  f:subview id=header
tc:loadBundle basename=bundle var=mainBundle /
tc:link action=app/home immediate=true
image=image/logo_tiny.gif /
  /f:subview

 (footer is similar to header so I skip this one).

 The result is (excerpt only :))

 table border=1 class=tobago-gridLayout-default
 style=height:600px;
 width:800px;  cellspacing=0 cellpadding=0 summary=
  
 colgroup
 col width=796
 /colgrouptr
 td class=tobago-gridLayout-cell-td style=width: 796px; height:
 0px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-row
 tobago-gridLayout-first-column style=width: 796px; height: 0px;

   
  !-- row 0 --/div/td/trtr
  
 td class=tobago-gridLayout-cell-td style=width: 796px; height:
 25px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-column
 style=width: 796px; height: 25px;
 a href=javascript:; onclick=Tobago.submitAction(this,
 'masterpage:j_id4', true); class=tobago-link-default
 id=masterpage:j_id4 name=masterpage:j_id4
 img
 src=/seam-template/tobago-resource/html/standard/standard/image/logo_tiny.gif

 border=0 alt=
 /a/div/td/trtr
 td class=tobago-gridLayout-cell-td style=width: 796px; height:
 108px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-column
 style=width: 796px; height: 108px;

   
 I get the following warnings in the log (as far as I know row is used
 for both row and column in the output):

 22:21:06,164 WARN  [GridLayoutRenderer

Re: [tobago] and facelets: using composition

2008-10-24 Thread Bernd Bohmann
Hello Stefan,

the 1.1.x trunk is a little bit buggy now. We try to refactor the
layouting and many other parts of Tobago. I can look at your issue at
the weekend.

Regards

Bernd

Stefan Hedtfeld schrieb:
 Hi,
 
 I'm switching from using jsp to faclets and am currently working on a
 prototype using tobago-1.1.0-SNAPSHOT and sun RI 1.2 on JBoss. I started
 with a layout which worked for jsps, and began to migrate it to
 facelets. As this didn't work as expected I tried to simplify the layout
 and finally came to a point where I only have three parts in my layout:
 a header, the body (content) and a footer. But I still get weird rows
 with 0px height and columns with 0px width in the resulting html.
 
 Here is some code:
 
 app/home.xhtml:
 
  ui:composition template=/templates/master.xhtml
tc:loadBundle basename=bundle var=mainBundle /
ui:define name=title#{mainBundle.pageTitle}/ui:define
ui:define name=body
  tx:date id=test label=Label/
/ui:define
  /ui:composition
 
 templates/master.xhtml:
 
  f:view locale=#{clientConfiguration.locale}
tc:loadBundle basename=bundle var=mainBundle /
tc:page label=#{mainBundle.pageTitle} id=masterpage width=800
 height=600
 
  f:facet name=layout
tc:gridLayout border=1 margin=1px columns=*
 rows=fixed;fixed;*;fixed  /
  /f:facet
 
  !-- row 0 --
  tc:link action=app/home immediate=true
  image=image/logo_tiny.gif /
 
  !-- row 1 --
  ui:insert name=body
ui:include src=/templates/body.xhtml/
  /ui:insert
  !-- row 2 --
  tc:cell/
 
  !-- row 3 --
  tc:out value=#{mainBundle.copyrightNote}/
 
/tc:page
  /f:view
 
 templates/header.xhtml
 
  f:subview id=header
tc:loadBundle basename=bundle var=mainBundle /
tc:link action=app/home immediate=true
image=image/logo_tiny.gif /
  /f:subview
 
 (footer is similar to header so I skip this one).
 
 The result is (excerpt only :))
 
 table border=1 class=tobago-gridLayout-default style=height:600px;
 width:800px;  cellspacing=0 cellpadding=0 summary=
 colgroup
 col width=796
 /colgrouptr
 td class=tobago-gridLayout-cell-td style=width: 796px; height: 0px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-row
 tobago-gridLayout-first-column style=width: 796px; height: 0px;

 
  !-- row 0 --/div/td/trtr
 td class=tobago-gridLayout-cell-td style=width: 796px; height: 25px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-column
 style=width: 796px; height: 25px;
 a href=javascript:; onclick=Tobago.submitAction(this,
 'masterpage:j_id4', true); class=tobago-link-default
 id=masterpage:j_id4 name=masterpage:j_id4
 img
 src=/seam-template/tobago-resource/html/standard/standard/image/logo_tiny.gif
 border=0 alt=
 /a/div/td/trtr
 td class=tobago-gridLayout-cell-td style=width: 796px; height:
 108px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-column
 style=width: 796px; height: 108px;

 
 
 I get the following warnings in the log (as far as I know row is used
 for both row and column in the output):
 
 22:21:06,164 WARN  [GridLayoutRenderer] Unbalanced layout: rows.size()=8
 !=layoutTokens.length=4 rowLayout='fixed;fixed;1*;fixed;'
 (clientId='masterpage:j_id2')
 22:21:06,213 WARN  [GridLayoutRenderer] Unable to calculate Height for
 token '1*'! using 'fixed' , component:masterpage:j_id6 is Panel
 22:21:06,308 WARN  [GridLayoutRenderer] Unable to calculate Height for
 token '1*'! using 'fixed' , component:masterpage:j_id6 is Panel
 2
 
 Has anyone used tobago and facelets for this kind of composite layout?
 How do I avoid these 0px wide columns / high rows? (You can imagine the
 more complex the layout the more weird the result ...)
 
 Any hints welcome!
 
 Best regards,
 
 Stefan.
 


Re: Print version of Myfaces library

2008-10-09 Thread Bernd Bohmann
Hello,

two options

maven way
pom = getClass().getClassLoader().getResourceAsStream(
META-INF/maven/org.apache.myfaces.core/myfaces-impl/pom.properties);
Properties properties = new Properties();
properties.load(pom);
version = properties.getProperty(version);


or java manifest way

Package myPackage = myPackage =
Package.getPackage(org.apache.myfaces.renderkit);
version = myPackage.getImplementationVersion();

Regards

Bernd



Matthias Wessendorf schrieb:
 afaik there is no implicit #{myfaces} bean, that has infos like that.
 would be interesting, though.
 
 can you file a jira ticket on that ?
 
 -M
 
 On Wed, Oct 8, 2008 at 4:50 PM,  [EMAIL PROTECTED] wrote:
 Hi,

 is it possible to get Myfaces version from jsf page/java code?

 Perhaps something similar to #{a4j.version}?

 --
 Jiri Pejchal


 
 
 


Re: [Tobago] Render a drop-down in a TabGroup

2008-10-08 Thread Bernd Bohmann
Hello Salvador,

this feature should be enabled by default. But the description of the
feature is not complete. The description should be TabNavigationBar for
TabGroup. The drop-down menu requires more changes and hase been moved
to an other issue.

Regards

Bernd

Bravo Villegas Salvador Francisco schrieb:
 Hi All,
 
  
 
 I see this new feature in the notes of the new release.
 
 But my question is, If somebody knows how can I implement this feature
 in a project.
 
  
 
 New Feature
 
 [TOBAGO-176] - Possibility to render a drop-down in a TabGroup for
 selection of 'invisible' tabs (Eclipse-style) 
 
  
 
 http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273
 styleName=Htmlversion=12313372
 http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231027
 3styleName=Htmlversion=12313372 
 
  
 
 Regards,
 
 Salvador Bravo.
 
 


Re: [Tobago] core compilation problems

2008-09-11 Thread Bernd Bohmann
Hello Salvador,

maybe a complete checkout of 1.0.17 would be easier.

svn co
http://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.17/
tobago-1.0.17

Regards

Bernd



Bravo Villegas Salvador Francisco schrieb:
 Hi Bernd
 
 The version is the 1.0.17
 
 -Mensaje original-
 De: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Enviado el: Jueves, 11 de Septiembre de 2008 12:48 a.m.
 Para: MyFaces Discussion
 Asunto: Re: [Tobago] core compilation problems
 
 Hello Salvador,
 
 which version of tobago are you trying to compile?
 
 Regards
 
 Bernd
 
 Bravo Villegas Salvador Francisco schrieb:
 Hi All,

  

 Im trying to compile the source of the Tobago Core, but I'm having
 troubles with the importing the packages
 org.apache.myfaces.tobago.apt.annotation.*

  

 I have the tobago-tool-apt-1.0.8.jar, but It look like the version is
 not the correct.

 Anybody knows which one is the version that I need to use??

  

 Regards

 Salvador B.


 



Re: [Tobago] core compilation problems

2008-09-11 Thread Bernd Bohmann
Hello Salvador,

please check the url it should be:
http://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.17

maybe a proxy problem please check your subversion configuration and you
can try the https link

https://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.17

If this doesn't help I will put a tar.gz of a fresh checkout on

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

Regards

Bernd


Bravo Villegas Salvador Francisco schrieb:
 SVN
 Send me an error.
 svn: OPTIONS de 
 'http://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.17': Could 
 not read status line: Se ha forzado la interrupción de una conexión existente 
 por el host remoto.
  (http://svn.apache.org)
 
 -Mensaje original-
 De: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Enviado el: Jueves, 11 de Septiembre de 2008 11:45 a.m.
 Para: MyFaces Discussion
 Asunto: Re: [Tobago] core compilation problems
 
 Hello Salvador,
 
 maybe a complete checkout of 1.0.17 would be easier.
 
 svn co
 http://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.17/
 tobago-1.0.17
 
 Regards
 
 Bernd
 
 
 
 Bravo Villegas Salvador Francisco schrieb:
 Hi Bernd

 The version is the 1.0.17

 -Mensaje original-
 De: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Enviado el: Jueves, 11 de Septiembre de 2008 12:48 a.m.
 Para: MyFaces Discussion
 Asunto: Re: [Tobago] core compilation problems

 Hello Salvador,

 which version of tobago are you trying to compile?

 Regards

 Bernd

 Bravo Villegas Salvador Francisco schrieb:
 Hi All,

  

 Im trying to compile the source of the Tobago Core, but I'm having
 troubles with the importing the packages
 org.apache.myfaces.tobago.apt.annotation.*

  

 I have the tobago-tool-apt-1.0.8.jar, but It look like the version is
 not the correct.

 Anybody knows which one is the version that I need to use??

  

 Regards

 Salvador B.


 
 


Re: [Trinidad] Strange subform behavior

2008-09-10 Thread Bernd Bohmann
Hello Walter,

only the submitted form invokes the PROCESS_VALIDATIONS Phase and
UPDATE_MODEL_VALUES Phase for his childs. If you want to display the new
values from the ValueBindings for all components you should return an
outcome. If you don't return an outcome the current view is displayed again.

Regards

Bernd

Walter Mourão schrieb:
 Hi Volker,
 
 I think the question is not if it was submitted or not but if all the
 visible references (inputText, outputText or everything else) of a property
 instance show its current value when the view is rendered.
 
 Regards,
 
 Walter Mourão
 http://waltermourao.com.br
 http://arcadian.com.br
 http://oriens.com.br
 
 
 
 On Wed, Sep 10, 2008 at 2:12 PM, Volker Weber [EMAIL PROTECTED] wrote:
 
 Hi,

 why would you expect a not submited subform should loose changes made
 on the client (the submitted value)?

 This is exact the behavior i would expect. And BTW how the tobago subform
 works.


 Regards,
Volker

 2008/9/10 Andrew Robinson [EMAIL PROTECTED]:
 Okay, I know the problem:

 The Subform allows the decode phase of all the children, regardless of
 what was clicked on. If an event was queued inside of the subform, but
 not during the apply phase, the form is considered submitted. Only
 the submitted form will be validated  updated.

 Now, UIXInput (and UIInput) render the submitted value as the current
 value if it is set. Therefore:

 1) subform 1 is submitted
 2) subform 1  2 are decoded, storing the submitted value ( for the
 inputText in the 2nd subform)
 3) subform 1 is validated
 4) subform 1 is updated
 5) render subform 1, inputText renders the value attribute
 6) render subform 2, inputText renders the submittedValue attribute
 (blank string  - )

 So to me this looks like a design flaw of the subform component. IMO,
 I would file a bug. Fixing it based on looking at the current design
 could be a pain in the rear. I wonder how the Tomahawk subform handles
 the same situation?

 As a workaround, you would have to find all components under
 non-submitted subforms that implement EditableValueHolder and set
 their submitted value to null.

 -Andrew

 On Wed, Sep 10, 2008 at 8:03 AM, Walter Mourão [EMAIL PROTECTED]
 wrote:
 Actually it looks like the issue isn't related with PPR. I just tested
 without PPR (see code below)  and had the same result:

 ?xml version=1.0 encoding=iso-8859-1 standalone=yes ?
 jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0
   xmlns:f=http://java.sun.com/jsf/core;
   xmlns:tr=http://myfaces.apache.org/trinidad; 
   jsp:directive.page contentType=text/html;charset=utf-8/
   f:view
 tr:document title=Apache Trinidad Blank Demo
tr:form
 tr:subform id=sub1
 tr:panelPage
   tr:outputText value=#{helloWorldBacking.name} /
   tr:inputText label=Your name id=input1
 value=#{helloWorldBacking.name} required=true/
   tr:commandButton id=button1 text=press me
 action=#{helloWorldBacking.send}/
 /tr:panelPage
 /tr:subform
 tr:subform id=sub2
 tr:panelPage
   tr:outputText value=#{helloWorldBacking.name} /
   tr:inputText label=Your name id=input1
 value=#{helloWorldBacking.name} required=true/
   tr:commandButton id=button1 text=press me
 action=#{helloWorldBacking.send}/
 /tr:panelPage
/tr:subform
/tr:form
 /tr:document
   /f:view
 /jsp:root


 Walter Mourão
 http://waltermourao.com.br
 http://arcadian.com.br
 http://oriens.com.br



 On Wed, Sep 10, 2008 at 10:13 AM, Andrew Robinson
 [EMAIL PROTECTED] wrote:
 Looks like you need to add partialTriggers to the components you want
 to update / refresh

 -A

 On Wed, Sep 10, 2008 at 4:50 AM, Walter Mourão 
 [EMAIL PROTECTED]
 wrote:
 Sorry the bump, but I'm in a dead end... Does anybody know a
 workaround
 ?


 Walter Mourão
 http://waltermourao.com.br
 http://arcadian.com.br
 http://oriens.com.br



 On Sun, Sep 7, 2008 at 8:22 AM, Walter Mourão 
 [EMAIL PROTECTED]
 wrote:
 Hi folks,
 I'm dealing with a strange behavior when using subforms and I
 reproduced
 it using the trinidad-blank example (from 1.0.9, but I found the
 problem
 first with 1.0.5).
 When executing an action from subform 1, only the inputs of the
 subform
 1
 are refreshed and show the new value. Besides that, when I added a
 tr:outputText to the subform, pointing to the same backing bean
 property, it
 shows the new value, so the tr:inputText and tr:outputText (of the
 subform
 2) shows differente values...

 To reproduce using the trinidad-blank example:
 1 - change HelloWorldBacking.send to:
   public String send()
   {
 _name = _name.toUpperCase();

 return null;
   }

 2 - add the file two_subforms.jspx with the content:
 ?xml version=1.0 encoding=iso-8859-1 standalone=yes ?
 jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=2.0
   xmlns:f=http://java.sun.com/jsf/core;
   xmlns:tr=http://myfaces.apache.org/trinidad; 
   

Re: [Tobago] core compilation problems

2008-09-10 Thread Bernd Bohmann
Hello Salvador,

which version of tobago are you trying to compile?

Regards

Bernd

Bravo Villegas Salvador Francisco schrieb:
 Hi All,
 
  
 
 Im trying to compile the source of the Tobago Core, but I'm having
 troubles with the importing the packages
 org.apache.myfaces.tobago.apt.annotation.*
 
  
 
 I have the tobago-tool-apt-1.0.8.jar, but It look like the version is
 not the correct.
 
 Anybody knows which one is the version that I need to use??
 
  
 
 Regards
 
 Salvador B.
 
 


Re: [tobago] something makes my menus need near 20s to reload

2008-08-26 Thread Bernd Bohmann
Hello Zied,

can you send an example page, please?

Regards

Bernd

Zied Hamdi schrieb:
 Sorry, I forgot to say that upgrading to the last stable build doesn't fix
 the problem.
 
 Regards
 Zied
 
 2008/8/26 Zied Hamdi [EMAIL PROTECTED]
 
  Hi all (especially Volker and Bernd whom I didn't report anything for a
 while ;-)

 I had an intervention for a customer these last 4 months. For that Time my
 computer continued to live as a simple home computer (installing
 uninstalling and trying softs). Now that I'm back to my app I notice the
 tobago menus take nearly 20 seconds to reloads: for all that time the whole
 browser hangs on. I tried to begin on a clean environment by rebuilding on a
 new developement envirenoment but the problem persists: my menu isn't really
 complex: it has some 5 root level items with one submenu for each. I'd like
 to know what is the reason for this problem because if I encouter the same
 on a custumer computer I will have no answer.

 If anyone experience the same problems please let me know.

 Thanks and regards,
 --
 Zied Hamdi
 www.into-i.fr
 (previously in 2003)
 zatreex.sf.net

 
 
 


Re: [Tobago] Handling of url protocol vfszip: in JBoss 5.0.0.CR1

2008-07-18 Thread Bernd Bohmann
Thanks Stefan,

can you open an issue, please.

http://myfaces.apache.org/tobago/issue-tracking.html

Regards

Bernd

Stefan Hedtfeld schrieb:
 And here comes the attachment ... :)
 
 Stefan Hedtfeld schrieb:
 Hi,

 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.

 Any thoughts about this?

 Regards,

 Stefan.

 


Re: [Tobago] NullPointerException on first request on JBoss 5.0.0.RC1

2008-07-10 Thread Bernd Bohmann
Hello Stefan,

I think Tobago hasn't been initialized.

I would expect something like this in the log file:
2008-07-10 21:00:21 INFO  -
org.apache.myfaces.tobago.webapp.TobagoServletContextListener:40 - ***
contextInitialized ***

Maybe you can add

listener
listener-classorg.apache.myfaces.tobago.webapp.TobagoServletContextListener/listener-class
/listener

 to your web.xml

Or a ViewRoot is missing

Regards

Bernd

Stefan Hedtfeld schrieb:
 Hi,
 
 I try to get tobago running on JBoss 5.0.0.RC1. I create my ear
 containing the web application, some of my on libs and external libs
 (using maven2) and deployment works fine. But during the first request I
 get a NullPointerException in TobagoResourceBundle.handleGetObject (see
 below). It seems to me that something is not setup correctly. As JBoss
 is bundled with the JSF RI I had to solve some problems before getting
 this far, so I guess I simply missed something here. Any ideas?
 
 2008-07-09 20:19:47,083 ERROR
 [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces
 Servlet]] (http-127.0.0.1-8080-2:) Servlet.service() for servlet Faces
 Servlet threw exception
 java.lang.NullPointerException
at
 org.apache.myfaces.tobago.context.TobagoResourceBundle.handleGetObject(TobagoResourceBundle.java:44)
 
at java.util.ResourceBundle.getObject(ResourceBundle.java:378)
at java.util.ResourceBundle.getString(ResourceBundle.java:344)
at
 com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:162)
at
 com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:133)
at
 com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:351)
 
at
 com.sun.faces.application.ApplicationImpl.newThing(ApplicationImpl.java:1029)
 
at
 com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:550)
 
at
 com.sun.faces.application.ViewHandlerImpl.createView(ViewHandlerImpl.java:332)
 
at
 org.apache.myfaces.tobago.application.ViewHandlerImpl.createView(ViewHandlerImpl.java:57)
 
at
 com.sun.facelets.FaceletViewHandler.createView(FaceletViewHandler.java:799)
at
 org.apache.myfaces.tobago.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:110)
 
at
 org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.executePhase(TobagoLifecycle.java:105)
 
at
 org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.execute(TobagoLifecycle.java:79)
 
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 
at
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
 
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 
at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
 
at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:183)
 
at
 org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
 
at
 org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)
 
at
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)
 
at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 
at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 
at
 org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
 
at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 
at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:325)
at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at
 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
 
at
 org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
 
 
 Regards,
 
 Stefan.
 


Re: [Tobago] Rendering problems

2008-07-10 Thread Bernd Bohmann
Hallo Salvador,

can you send an example page.

Regards

Bernd

Bravo Villegas Salvador Francisco schrieb:
 Hi all,
 
  
 
 We made an application with Tomahawk, and we have some pages with
 automatic creation of components with an XML.
 
 We use HtmlPanelGrid objects, to Guild this.
 
  
 
 But we want to upgrade the app, to Tobago, and the pages with this
 components do not render this objects.
 
  
 
 Any idea?
 
  
 
 Regards
 
  
 
 Salvador.
 
 


Re: [Tobago] NullPointerException on first request on JBoss 5.0.0.RC1

2008-07-10 Thread Bernd Bohmann
Hello Stefan,

just tested with 1.2_08-b06-FCS and facelets 1.1.14.

It's works.

In some of the examples you can test the JSF RI 1.2 with the property

-Djsf=ri12

for example

in example/demo/

mvn -Djsf=ri12 clean package jetty:run-exploded

The 1.1 trunk has only alpha state. Can you test it with the 1.0.17 or
the 1.0.18-SNAPSHOT version.

Regards

Bernd



Stefan Hedtfeld schrieb:
 Hi,
 
 here is some more information. The key which is going to be looked up is
 com.sun.faces.CANT_INSTANTIATE_CLASS, and while trying to access the
 view root the following WARNing is logged out:
 
 JSF1004: Cannot instantiate component of type javax.faces.ViewRoot
 
 The JSF implementation shipped with JBoss 5.0 is the following (taken
 from the manifest file):
 
 Implementation-Title: Sun Microsystems JavaServer Faces Implementation
 Specification-Vendor: JBoss (http://www.jboss.org/)
 Specification-Version: 1.2MR1
 Implementation-Vendor-Id: com.sun
 Extension-Name: com.sun.faces
 Implementation-Version: 1.2_08-b06-FCS
 Implementation-Vendor: Sun Microsystems, Inc.
 Implementation-URL: http://www.jboss.org/
 
 Anyone having experience in running tobago with JSF RI 1.2?
 
 Regards,
 
 Stefan.
 
 Stefan Hedtfeld schrieb:
 Hi,

 I try to get tobago running on JBoss 5.0.0.RC1. I create my ear
 containing the web application, some of my on libs and external libs
 (using maven2) and deployment works fine. But during the first request
 I get a NullPointerException in TobagoResourceBundle.handleGetObject
 (see below). It seems to me that something is not setup correctly. As
 JBoss is bundled with the JSF RI I had to solve some problems before
 getting this far, so I guess I simply missed something here. Any ideas?

 2008-07-09 20:19:47,083 ERROR
 [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces
 Servlet]] (http-127.0.0.1-8080-2:) Servlet.service() for servlet Faces
 Servlet threw exception
 java.lang.NullPointerException
at
 org.apache.myfaces.tobago.context.TobagoResourceBundle.handleGetObject(TobagoResourceBundle.java:44)

at java.util.ResourceBundle.getObject(ResourceBundle.java:378)
at java.util.ResourceBundle.getString(ResourceBundle.java:344)
at
 com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:162)
at
 com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:133)
at
 com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:351)

at
 com.sun.faces.application.ApplicationImpl.newThing(ApplicationImpl.java:1029)

at
 com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:550)

at
 com.sun.faces.application.ViewHandlerImpl.createView(ViewHandlerImpl.java:332)

at
 org.apache.myfaces.tobago.application.ViewHandlerImpl.createView(ViewHandlerImpl.java:57)

at
 com.sun.facelets.FaceletViewHandler.createView(FaceletViewHandler.java:799)

at
 org.apache.myfaces.tobago.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:110)

at
 org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.executePhase(TobagoLifecycle.java:105)

at
 org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.execute(TobagoLifecycle.java:79)

at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)

at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:183)

at
 org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)

at
 org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)

at
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)

at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at
 org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)

at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:325)

at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)

at
 

Re: [TOBAGO] Build Error apt failed in tobago-components

2008-06-16 Thread Bernd Bohmann
Hello Kai,

the tobago trunk build uses the apt plugin from mojo.codehaus.org. This
plugin assumes that the apt executable is in the path available. Please
add JAVA_HOME/bin to your path. I will check if this can be fixed in the
plugin. A note the trunk is only in a alpha state. If you need a stable
release please check out the 1.0.x branch

http://svn.apache.org/repos/asf/myfaces/tobago/branches/tobago-1.0.x/

Regards

Bernd



[EMAIL PROTECTED] schrieb:
 Hi everyone,
 
 i get the following error in maven build process with a clean svn update and
 mvn -P all-modules clean install call.
 
 Somebody also have the same problem or is this an open issue?
 
 Thank you for helping, kai.
 
 [WARNING] Note: Replacing:
 org.apache.myfaces.tobago.taglib.component.BoxTagDecl
 aration - org.apache.myfaces.tobago.internal.taglib.BoxTag
 [WARNING] Note: Replacing:
 org.apache.myfaces.tobago.taglib.component.TabTagDecl
 aration - org.apache.myfaces.tobago.internal.taglib.TabTag
 [WARNING] Note: Create DOM
 [WARNING] Note: Write to file org.apache.myfaces.tobago.taglib.component
 tobago.
 tld
 [WARNING] Note: Some input files use or override a deprecated API.
 [WARNING] Note: Recompile with -Xlint:deprecation for details.
 [WARNING] 1 warning
 [INFO] [apt:process {execution: tobago-components}]
 [INFO] Processing 352 source files to
 D:\DEV\tobago\1.0.Source\core\target\gener
 ated-component
 [WARNING] Der Befehl apt ist entweder falsch geschrieben oder
 [WARNING] konnte nicht gefunden werden.
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Apt failed
 [INFO]
 
 [INFO] Trace
 org.apache.maven.lifecycle.LifecycleExecutionException: Apt failed
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
 ultLifecycleExecutor.java:583)
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
 fecycle(DefaultLifecycleExecutor.java:499)
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
 ltLifecycleExecutor.java:478)
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
 dleFailures(DefaultLifecycleExecutor.java:330)
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
 ts(DefaultLifecycleExecutor.java:291)
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
 fecycleExecutor.java:142)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
 java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Apt failed
 at
 org.codehaus.mojo.apt.AbstractAptMojo.executeApt(AbstractAptMojo.java
 :377)
 at
 org.codehaus.mojo.apt.AbstractAptMojo.executeImpl(AbstractAptMojo.jav
 a:262)
 at
 org.codehaus.mojo.apt.AbstractAptMojo.execute(AbstractAptMojo.java:23
 9)
 at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
 nManager.java:451)
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
 ultLifecycleExecutor.java:558)
 ... 16 more
 [INFO]
 
 [INFO] Total time: 16 seconds
 [INFO] Finished at: Mon Jun 16 13:38:09 CEST 2008
 [INFO] Final Memory: 22M/51M
 [INFO]
 
 


ApacheCon Europe 2008

2008-04-08 Thread Bernd Bohmann
Hello,

we Udo Schnurpfeil (lofwyr) and my self just arrived in Amsterdam.
You can meet us at the Hackathon when you are interested to discuss
about Tobago and of cause MyFaces.

Regards

Udo and Bernd







Re: [Tobago] Can't build from current sources

2008-03-19 Thread Bernd Bohmann
Hello Helmut,

tobago-core has split into tobago-core, tobago-taglib-extension(tx) and
tobago-jsf-compat.

tobago-jsf-compat manages the differences between jsf 1.1 and jsf 1.2.
At the end of the road maybe tobago 1.1 is jsf 1.1 and jsf 1.2 compatible.

Regards

Bernd


Helmut Swaczinna schrieb:
 Hello Bernd,
 
 I've done so. Building is ok. But now I can't even deploy my test app:
 
 2008-03-19 11:56:32
 ContainerBackgroundProcessor[StandardEngine[Catalina]] ERROR -
 org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/tob
 ago-test]:3731 - Exception sending context initialized event to listener
 instance of class org.apache.myfaces.webapp.StartupServletContextListener
 java.lang.NoClassDefFoundError:
 org/apache/myfaces/tobago/compat/InvokeOnComponent
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at
 org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1779)
 
at
 org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:866)
 
at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1319)
 
at
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
 
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
at java.lang.Class.getConstructor0(Class.java:2671)
at java.lang.Class.getConstructor(Class.java:1629)
at
 org.apache.myfaces.config.FacesConfigurator.getApplicationObject(FacesConfigurator.java:677)
 
 ...
 
 
 The tobago-example-demo can be deployed and works partially. There're
 are some exceptions.
 
 I'll give up testing with 1.1.0 for now. Maybe I'll try it again in some
 weeks.
 (I've done all this only because I wanted to test the patch for
 TOBAGO-325 with 1.1.0. So it still stays untestet.)
 
 Regards
 
 Helmut
 
 
 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Tuesday, March 18, 2008 10:32 PM
 Subject: Re: [Tobago] Can't build from current sources
 
 
 Hello Helmut,

 found some missing uncommited files.

 Please perform a svn up and a mvn -P all-modules clean install.

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hello Bernd,

 do you mean Are the class files for components and tags generated
 now?. Yes, they are.

 But my test app doesn't run at all with 1.1.0:

 java.lang.ClassCastException:
 org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.PageRenderer


at
 org.apache.myfaces.tobago.renderkit.AbstractLayoutableRendererBaseWrapper.getLayoutableRenderer(AbstractLayoutableRendererBaseWrapper.java:


 70)
at
 org.apache.myfaces.tobago.renderkit.AbstractLayoutableRendererBaseWrapper.getComponentExtraWidth(AbstractLayoutableRendererBaseWrapper.java


 :42)
at
 org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.layoutSpace(HtmlRendererUtil.java:359)


at
 org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.layoutWidth(HtmlRendererUtil.java:313)


at
 org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.prepareRender(HtmlRendererUtil.java:97)


at
 org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.PageRenderer.encodeEnd(PageRenderer.java:113)


at
 org.apache.myfaces.tobago.renderkit.AbstractRendererBaseWrapper.encodeEnd(AbstractRendererBaseWrapper.java:80)


at
 javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)

 ...

 This exception occurs immediately on every page.

 Regards

 Helmut


 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Tuesday, March 18, 2008 6:06 PM
 Subject: Re: [Tobago] Can't build from current sources


 Hello Helmut,

 the package-info.java contains the information for generating the tlds.
 package-info.java can be excluded for tobago-components and
 tobago-faces-config.

 Are the components and tags generated now?

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hello Bernd,

 I added

 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude




 to the tobago-components execution. So there's no error in
 tobago-components but it's then in tobago-faces-config.
 So I added

 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude



 excludeorg/apache/myfaces/tobago/taglib/extension/package-info.java/exclude




 to tobago-faces-config. Then it builds.

 But excluding the package-infos is only a workaround not the
 solution to
 the problem, right?

 Regards

 Helmut


 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces

Re: [Tobago] Can't build from current sources

2008-03-18 Thread Bernd Bohmann
Hello Helmut,

the package-info.java contains the information for generating the tlds.
package-info.java can be excluded for tobago-components and
tobago-faces-config.

Are the components and tags generated now?

Regards

Bernd

Helmut Swaczinna schrieb:
 Hello Bernd,
 
 I added
 
 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude
 
 
 to the tobago-components execution. So there's no error in
 tobago-components but it's then in tobago-faces-config.
 So I added
 
 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude
 
 excludeorg/apache/myfaces/tobago/taglib/extension/package-info.java/exclude
 
 
 to tobago-faces-config. Then it builds.
 
 But excluding the package-infos is only a workaround not the solution to
 the problem, right?
 
 Regards
 
 Helmut
 
 
 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 8:57 PM
 Subject: Re: [Tobago] Can't build from current sources
 
 
 Hello Helmut,

 i think this is a problem with jdk 1.5, windows and the annotation
 processing tool. Please add
 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude


 to the excludes section of the tobago-components execution.

 I think Arvid tries the build with jdk 1.6, but it should work with jdk
 1.5, too.

 Can you try the suggestion, please.

 Regards

 Bernd



 Helmut Swaczinna schrieb:
 Hello Bernd,

 execution id tobago-components is called but leads to an error:

 [INFO] [apt:execute {execution: tobago-components}]
 [ERROR]
 C:/Projekte/jsf/tobago-new/core/src/main/java/org/apache/myfaces/tobago/taglib/component/pac


 kage-info.java:9: package annotations should be in file
 package-info.java
fileName = tobago.tld, displayName = Tobago Components) package
 org.apache.myfaces.tobago.ta
 glib.component;

 This is the content of package-info.java:

 @org.apache.myfaces.tobago.apt.annotation.Taglib(
shortName = tc, uri = http://myfaces.apache.org/tobago/component;,
listener =
 org.apache.myfaces.tobago.webapp.TobagoServletContextListener,
fileName = tobago.tld, displayName = Tobago Components) package
 org.apache.myfaces.tobago.taglib.component;

 I think the problem is in tobago-tlds:

 [INFO] [apt:execute {execution: tobago-tlds}]
 C:\Projekte\jsf\tobago-new\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\SelectManyC


 heckboxExtensionTag.java:40: cannot find symbol
 symbol  : class SelectManyCheckboxTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.SelectManyCheckboxTag;
 ^
 ...

 Regards
 Helmut

 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 6:39 PM
 Subject: Re: [Tobago] Can't build from current sources


 Hello Helmut,

 we test a fresh build on arvids windows machine.
 Can you check why the execution of the maven-apt-plugin with the
 execution id tobago-components is not called?

 Just tried a sucessful fresh build from source on my linux machine.
 The build of tobago-core on the continuum server is sucessful, too
 (solaris-x86.)

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hello Bernd,

 it still does not build. I've done a svn update and a mvn clean
 install
 but get the same result.

 C:\Projekte\jsf\tobago-src\tools\svn-win32-1.4.2\bin\svn update
 U
 theme\scarborough\src\main\java\org\apache\myfaces\tobago\renderkit\html\scarborough\standard\t



 ag\GridLayoutRenderer.java
 U
 core\src\main\java\org\apache\myfaces\tobago\taglib\component\MenuSelectOneTagDeclaration.java



 U
 core\src\main\java\org\apache\myfaces\tobago\taglib\component\MenuSelectBooleanTagDeclaration.j



 ava
 U
 core\src\main\java\org\apache\myfaces\tobago\webapp\TobagoMultipartFormdataFilter.java



 U
 extension\facelets\src\main\java\org\apache\myfaces\tobago\facelets\TobagoComponentHandler.java




 U
 extension\facelets\src\main\java\org\apache\myfaces\tobago\facelets\extension\TobagoLabelExtens



 ionHandler.java
 Aktualisiert zu Revision 637965.

 C:\Projekte\jsf\tobago-src\tools\maven-2.0.7\bin\mvn clean install
 ...

 Did you already checked in your changes?

 Regards

 Helmut


 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 4:21 PM
 Subject: Re: [Tobago] Can't build from current sources


 Hello Helmut,

 can you try again with a mvn clean install. Arvid and me just sort
 out
 some issues with windows.

 I changed the build to generate more components and tags from the
 annotation metadata.

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hi,

 just checkedout the current (1.1.x) sources but get lots of errors
 when
 building with mvn install in the main directory:

 C:\Projekte\jsf\tobago-src\tools\maven-2.0.7\bin\mvn

Re: [Tobago] Can't build from current sources

2008-03-18 Thread Bernd Bohmann
Hello Helmut,

found some missing uncommited files.

Please perform a svn up and a mvn -P all-modules clean install.

Regards

Bernd

Helmut Swaczinna schrieb:
 Hello Bernd,
 
 do you mean Are the class files for components and tags generated
 now?. Yes, they are.
 
 But my test app doesn't run at all with 1.1.0:
 
 java.lang.ClassCastException:
 org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.PageRenderer
 
at
 org.apache.myfaces.tobago.renderkit.AbstractLayoutableRendererBaseWrapper.getLayoutableRenderer(AbstractLayoutableRendererBaseWrapper.java:
 
 70)
at
 org.apache.myfaces.tobago.renderkit.AbstractLayoutableRendererBaseWrapper.getComponentExtraWidth(AbstractLayoutableRendererBaseWrapper.java
 
 :42)
at
 org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.layoutSpace(HtmlRendererUtil.java:359)
 
at
 org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.layoutWidth(HtmlRendererUtil.java:313)
 
at
 org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.prepareRender(HtmlRendererUtil.java:97)
 
at
 org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.PageRenderer.encodeEnd(PageRenderer.java:113)
 
at
 org.apache.myfaces.tobago.renderkit.AbstractRendererBaseWrapper.encodeEnd(AbstractRendererBaseWrapper.java:80)
 
at
 javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539)
 ...
 
 This exception occurs immediately on every page.
 
 Regards
 
 Helmut
 
 
 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Tuesday, March 18, 2008 6:06 PM
 Subject: Re: [Tobago] Can't build from current sources
 
 
 Hello Helmut,

 the package-info.java contains the information for generating the tlds.
 package-info.java can be excluded for tobago-components and
 tobago-faces-config.

 Are the components and tags generated now?

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hello Bernd,

 I added

 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude



 to the tobago-components execution. So there's no error in
 tobago-components but it's then in tobago-faces-config.
 So I added

 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude


 excludeorg/apache/myfaces/tobago/taglib/extension/package-info.java/exclude



 to tobago-faces-config. Then it builds.

 But excluding the package-infos is only a workaround not the solution to
 the problem, right?

 Regards

 Helmut


 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 8:57 PM
 Subject: Re: [Tobago] Can't build from current sources


 Hello Helmut,

 i think this is a problem with jdk 1.5, windows and the annotation
 processing tool. Please add
 excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude



 to the excludes section of the tobago-components execution.

 I think Arvid tries the build with jdk 1.6, but it should work with jdk
 1.5, too.

 Can you try the suggestion, please.

 Regards

 Bernd



 Helmut Swaczinna schrieb:
 Hello Bernd,

 execution id tobago-components is called but leads to an error:

 [INFO] [apt:execute {execution: tobago-components}]
 [ERROR]
 C:/Projekte/jsf/tobago-new/core/src/main/java/org/apache/myfaces/tobago/taglib/component/pac



 kage-info.java:9: package annotations should be in file
 package-info.java
fileName = tobago.tld, displayName = Tobago Components) package
 org.apache.myfaces.tobago.ta
 glib.component;

 This is the content of package-info.java:

 @org.apache.myfaces.tobago.apt.annotation.Taglib(
shortName = tc, uri =
 http://myfaces.apache.org/tobago/component;,
listener =
 org.apache.myfaces.tobago.webapp.TobagoServletContextListener,
fileName = tobago.tld, displayName = Tobago Components) package
 org.apache.myfaces.tobago.taglib.component;

 I think the problem is in tobago-tlds:

 [INFO] [apt:execute {execution: tobago-tlds}]
 C:\Projekte\jsf\tobago-new\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\SelectManyC



 heckboxExtensionTag.java:40: cannot find symbol
 symbol  : class SelectManyCheckboxTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import
 org.apache.myfaces.tobago.internal.taglib.SelectManyCheckboxTag;
 ^
 ...

 Regards
 Helmut

 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 6:39 PM
 Subject: Re: [Tobago] Can't build from current sources


 Hello Helmut,

 we test a fresh build on arvids windows machine.
 Can you check why the execution of the maven-apt-plugin with the
 execution id tobago-components is not called?

 Just tried a sucessful fresh build from source on my linux machine.
 The build of tobago-core on the continuum server is sucessful, too
 (solaris

Re: [Tobago] Can't build from current sources

2008-03-17 Thread Bernd Bohmann
Hello Helmut,

can you try again with a mvn clean install. Arvid and me just sort out
some issues with windows.

I changed the build to generate more components and tags from the
annotation metadata.

Regards

Bernd

Helmut Swaczinna schrieb:
 Hi,
 
 just checkedout the current (1.1.x) sources but get lots of errors when
 building with mvn install in the main directory:
 
 C:\Projekte\jsf\tobago-src\tools\maven-2.0.7\bin\mvn install
 [INFO] Scanning for projects...
 Downloading:
 http://repo1.maven.org/maven2/org/apache/myfaces/myfaces/5/myfaces-5.pom
 28K downloaded
 [INFO] Reactor build order:
 [INFO]   Apache Tobago
 [INFO]   Tobago Tool
 [INFO]   Maven Apt Plugin
 [INFO]   Maven Tobago Theme Plugin
 [INFO]   Tobago Annotation
 [INFO]   Tobago Apt
 [INFO]   Tobago Core
 [INFO]   Tobago Themes
 [INFO]   Theme Standard
 [INFO]   Theme Scarborough
 [INFO]   Theme Speyside
 [INFO]   Theme Richmond
 [INFO]   Theme Charlotteville
 [INFO]
 
 
 [INFO] Building Apache Tobago
 [INFO]task-segment: [install]
 [INFO]
 
 
 ...
 no errors until now
 ...
 [INFO]
 
 
 [INFO] Building Tobago Core
 [INFO]task-segment: [install]
 [INFO]
 
 
 [INFO] [resources:resources]
 [INFO] Using default encoding to copy filtered resources.
 [INFO] [compiler:compile]
 [INFO] Compiling 438 source files to
 C:\Projekte\jsf\tobago-src\core\target\classes
 [INFO] [apt:execute {execution: tobago-tlds}]
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\SelectOneC
 
 oiceExtensionTag.java:22: cannot find symbol
 symbol  : class SelectOneChoiceTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.SelectOneChoiceTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\LabelExten
 
 ionTag.java:25: cannot find symbol
 symbol  : class GridLayoutTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.GridLayoutTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\LabelExten
 
 ionTag.java:26: cannot find symbol
 symbol  : class LabelTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.LabelTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\LabelExten
 
 ionTag.java:27: cannot find symbol
 symbol  : class PanelTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.PanelTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\SelectOneC
 
 oiceExtensionTag.java:76: cannot find symbol
 symbol  : class SelectOneChoiceTag
 location: class
 org.apache.myfaces.tobago.taglib.extension.SelectOneChoiceExtensionTag
  private SelectOneChoiceTag selectOneChoiceTag;
  ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\LabelExten
 
 ionTag.java:54: cannot find symbol
 symbol  : class PanelTag
 location: class
 org.apache.myfaces.tobago.taglib.extension.LabelExtensionTag
  private PanelTag panelTag;
  ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\FileExtens
 
 onTag.java:22: cannot find symbol
 symbol  : class FileTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.FileTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\FileExtens
 
 onTag.java:73: cannot find symbol
 symbol  : class FileTag
 location: class org.apache.myfaces.tobago.taglib.extension.FileExtensionTag
  private FileTag fileTag;
  ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\InExtensio
 
 Tag.java:22: cannot find symbol
 symbol  : class InTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.InTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\InExtensio
 
 Tag.java:89: cannot find symbol
 symbol  : class InTag
 location: class org.apache.myfaces.tobago.taglib.extension.InExtensionTag
  private InTag inTag;
  ^
 

Re: [Tobago] Can't build from current sources

2008-03-17 Thread Bernd Bohmann
Hello Helmut,

we test a fresh build on arvids windows machine.
Can you check why the execution of the maven-apt-plugin with the
execution id tobago-components is not called?

Just tried a sucessful fresh build from source on my linux machine.
The build of tobago-core on the continuum server is sucessful, too
(solaris-x86.)

Regards

Bernd

Helmut Swaczinna schrieb:
 Hello Bernd,
 
 it still does not build. I've done a svn update and a mvn clean install
 but get the same result.
 
 C:\Projekte\jsf\tobago-src\tools\svn-win32-1.4.2\bin\svn update
 U
 theme\scarborough\src\main\java\org\apache\myfaces\tobago\renderkit\html\scarborough\standard\t
 
 ag\GridLayoutRenderer.java
 U
 core\src\main\java\org\apache\myfaces\tobago\taglib\component\MenuSelectOneTagDeclaration.java
 
 U
 core\src\main\java\org\apache\myfaces\tobago\taglib\component\MenuSelectBooleanTagDeclaration.j
 
 ava
 U
 core\src\main\java\org\apache\myfaces\tobago\webapp\TobagoMultipartFormdataFilter.java
 
 U
 extension\facelets\src\main\java\org\apache\myfaces\tobago\facelets\TobagoComponentHandler.java
 
 
 U
 extension\facelets\src\main\java\org\apache\myfaces\tobago\facelets\extension\TobagoLabelExtens
 
 ionHandler.java
 Aktualisiert zu Revision 637965.
 
 C:\Projekte\jsf\tobago-src\tools\maven-2.0.7\bin\mvn clean install
 ...
 
 Did you already checked in your changes?
 
 Regards
 
 Helmut
 
 
 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 4:21 PM
 Subject: Re: [Tobago] Can't build from current sources
 
 
 Hello Helmut,

 can you try again with a mvn clean install. Arvid and me just sort out
 some issues with windows.

 I changed the build to generate more components and tags from the
 annotation metadata.

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hi,

 just checkedout the current (1.1.x) sources but get lots of errors when
 building with mvn install in the main directory:

 C:\Projekte\jsf\tobago-src\tools\maven-2.0.7\bin\mvn install
 [INFO] Scanning for projects...
 Downloading:
 http://repo1.maven.org/maven2/org/apache/myfaces/myfaces/5/myfaces-5.pom
 28K downloaded
 [INFO] Reactor build order:
 [INFO]   Apache Tobago
 [INFO]   Tobago Tool
 [INFO]   Maven Apt Plugin
 [INFO]   Maven Tobago Theme Plugin
 [INFO]   Tobago Annotation
 [INFO]   Tobago Apt
 [INFO]   Tobago Core
 [INFO]   Tobago Themes
 [INFO]   Theme Standard
 [INFO]   Theme Scarborough
 [INFO]   Theme Speyside
 [INFO]   Theme Richmond
 [INFO]   Theme Charlotteville
 [INFO]
 


 [INFO] Building Apache Tobago
 [INFO]task-segment: [install]
 [INFO]
 


 ...
 no errors until now
 ...
 [INFO]
 


 [INFO] Building Tobago Core
 [INFO]task-segment: [install]
 [INFO]
 


 [INFO] [resources:resources]
 [INFO] Using default encoding to copy filtered resources.
 [INFO] [compiler:compile]
 [INFO] Compiling 438 source files to
 C:\Projekte\jsf\tobago-src\core\target\classes
 [INFO] [apt:execute {execution: tobago-tlds}]
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\SelectOneC


 oiceExtensionTag.java:22: cannot find symbol
 symbol  : class SelectOneChoiceTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.SelectOneChoiceTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\LabelExten


 ionTag.java:25: cannot find symbol
 symbol  : class GridLayoutTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.GridLayoutTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\LabelExten


 ionTag.java:26: cannot find symbol
 symbol  : class LabelTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.LabelTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\LabelExten


 ionTag.java:27: cannot find symbol
 symbol  : class PanelTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.PanelTag;
 ^
 C:\Projekte\jsf\tobago-src\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\SelectOneC


 oiceExtensionTag.java:76: cannot find symbol
 symbol  : class SelectOneChoiceTag
 location: class
 org.apache.myfaces.tobago.taglib.extension.SelectOneChoiceExtensionTag
  private SelectOneChoiceTag

Re: [Tobago] Can't build from current sources

2008-03-17 Thread Bernd Bohmann
Hello Helmut,

i think this is a problem with jdk 1.5, windows and the annotation
processing tool. Please add
excludeorg/apache/myfaces/tobago/taglib/component/package-info.java/exclude

to the excludes section of the tobago-components execution.

I think Arvid tries the build with jdk 1.6, but it should work with jdk
1.5, too.

Can you try the suggestion, please.

Regards

Bernd



Helmut Swaczinna schrieb:
 Hello Bernd,
 
 execution id tobago-components is called but leads to an error:
 
 [INFO] [apt:execute {execution: tobago-components}]
 [ERROR]
 C:/Projekte/jsf/tobago-new/core/src/main/java/org/apache/myfaces/tobago/taglib/component/pac
 
 kage-info.java:9: package annotations should be in file package-info.java
fileName = tobago.tld, displayName = Tobago Components) package
 org.apache.myfaces.tobago.ta
 glib.component;
 
 This is the content of package-info.java:
 
 @org.apache.myfaces.tobago.apt.annotation.Taglib(
shortName = tc, uri = http://myfaces.apache.org/tobago/component;,
listener =
 org.apache.myfaces.tobago.webapp.TobagoServletContextListener,
fileName = tobago.tld, displayName = Tobago Components) package
 org.apache.myfaces.tobago.taglib.component;
 
 I think the problem is in tobago-tlds:
 
 [INFO] [apt:execute {execution: tobago-tlds}]
 C:\Projekte\jsf\tobago-new\core\src\main\java\org\apache\myfaces\tobago\taglib\extension\SelectManyC
 
 heckboxExtensionTag.java:40: cannot find symbol
 symbol  : class SelectManyCheckboxTag
 location: package org.apache.myfaces.tobago.internal.taglib
 import org.apache.myfaces.tobago.internal.taglib.SelectManyCheckboxTag;
 ^
 ...
 
 Regards
 Helmut
 
 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 6:39 PM
 Subject: Re: [Tobago] Can't build from current sources
 
 
 Hello Helmut,

 we test a fresh build on arvids windows machine.
 Can you check why the execution of the maven-apt-plugin with the
 execution id tobago-components is not called?

 Just tried a sucessful fresh build from source on my linux machine.
 The build of tobago-core on the continuum server is sucessful, too
 (solaris-x86.)

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hello Bernd,

 it still does not build. I've done a svn update and a mvn clean install
 but get the same result.

 C:\Projekte\jsf\tobago-src\tools\svn-win32-1.4.2\bin\svn update
 U
 theme\scarborough\src\main\java\org\apache\myfaces\tobago\renderkit\html\scarborough\standard\t


 ag\GridLayoutRenderer.java
 U
 core\src\main\java\org\apache\myfaces\tobago\taglib\component\MenuSelectOneTagDeclaration.java


 U
 core\src\main\java\org\apache\myfaces\tobago\taglib\component\MenuSelectBooleanTagDeclaration.j


 ava
 U
 core\src\main\java\org\apache\myfaces\tobago\webapp\TobagoMultipartFormdataFilter.java


 U
 extension\facelets\src\main\java\org\apache\myfaces\tobago\facelets\TobagoComponentHandler.java



 U
 extension\facelets\src\main\java\org\apache\myfaces\tobago\facelets\extension\TobagoLabelExtens


 ionHandler.java
 Aktualisiert zu Revision 637965.

 C:\Projekte\jsf\tobago-src\tools\maven-2.0.7\bin\mvn clean install
 ...

 Did you already checked in your changes?

 Regards

 Helmut


 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Monday, March 17, 2008 4:21 PM
 Subject: Re: [Tobago] Can't build from current sources


 Hello Helmut,

 can you try again with a mvn clean install. Arvid and me just sort out
 some issues with windows.

 I changed the build to generate more components and tags from the
 annotation metadata.

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hi,

 just checkedout the current (1.1.x) sources but get lots of errors
 when
 building with mvn install in the main directory:

 C:\Projekte\jsf\tobago-src\tools\maven-2.0.7\bin\mvn install
 [INFO] Scanning for projects...
 Downloading:
 http://repo1.maven.org/maven2/org/apache/myfaces/myfaces/5/myfaces-5.pom

 28K downloaded
 [INFO] Reactor build order:
 [INFO]   Apache Tobago
 [INFO]   Tobago Tool
 [INFO]   Maven Apt Plugin
 [INFO]   Maven Tobago Theme Plugin
 [INFO]   Tobago Annotation
 [INFO]   Tobago Apt
 [INFO]   Tobago Core
 [INFO]   Tobago Themes
 [INFO]   Theme Standard
 [INFO]   Theme Scarborough
 [INFO]   Theme Speyside
 [INFO]   Theme Richmond
 [INFO]   Theme Charlotteville
 [INFO]
 



 [INFO] Building Apache Tobago
 [INFO]task-segment: [install]
 [INFO]
 



 ...
 no errors until now
 ...
 [INFO]
 



 [INFO] Building Tobago Core
 [INFO]task-segment: [install]
 [INFO]
 



 [INFO

Re: maven-apt-plugin

2008-02-23 Thread Bernd Bohmann
Hello Josh,

the plugin did not support plugin dependencies. See:

https://issues.apache.org/jira/browse/TOBAGO-130

Regards

Bernd




Josh Suereth schrieb:
 Not sure if this is the right place to be sending this, but I was wondering
 why the following doesn't work:
 
 build
 finalNameTestWar/finalName
 plugins
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-compiler-plugin/artifactId
 configuration
 compilerVersion1.5/compilerVersion
 /configuration
 /plugin
 plugin
 groupIdorg.apache.myfaces.tobago/groupId
 artifactIdmaven-apt-plugin/artifactId
 version1.0.15/version
 configuration
   nocompiletrue/nocompile
   factorytest.MyAnnotationProcessorFactory/factory
   forkfalse/fork
 /configuration
 dependencies
   dependency
 groupIdMyAptProcessor/groupId
 artifactIdMyAptProcessor/artifactId
 version1.0-SNAPSHOT/version
   /dependency
 /dependencies
 /plugin
 /plugins
 /build
 
 
 
 If I move the dependency outside the plugin directory, and make it for the
 whole project then it works.   I'd rather not make my Annotation processor
 be a dependency for the whole project as it just generates some config files
 based on annotations.   Any ideas?
 
 Thanks,
 -Josh Suereth
 



Re: [tobago] Seam integration

2008-02-05 Thread Bernd Bohmann
Hello,

the tobago-example-seam is only a simple blank web app for now.
I would like to sort out all compatibility issues in tobago.

Patches und suggestions for reasonable content in the
tobago-example-seam module are wellcome.

Regards

Bernd

Zied Hamdi schrieb:
 Hi Stojan,
 
 Sorry I didn't look at the svn lastly (at my first mail there wasn't any).
 So the project is in progress I guess (since there's no official post about
 it), it'll be a big event for the tobago community I think. Thanks for your
 posts.
 
 Regards,
 Zied
 
 
 2008/2/5, Stojan Peshov [EMAIL PROTECTED]:
 I was actually talking about tobago seam example found here:
 http://svn.apache.org/repos/asf/myfaces/tobago/trunk/example/seam

 All I did was checkout the code and opened it with NetBeans as a Maven
 project (maven plugin for netbeans is required)

 At first build was not successful, but after changing the update snapshots
 parameter for the idapache.snapshots/id
 build was successful. You can do this in the main pom file in the tobago
 trunk:
 http://svn.apache.org/repos/asf/myfaces/tobago/trunk/pom.xml

 After all this, the only problem was deployment to the Tomcat, but I
 already explained this in the previous mail...

 I really don't know what to send to Bernd since the code is already at
 svn...
 Bernd you can write me if you want some more help.

 Regards,
 Stojan


 On Feb 5, 2008 11:26 AM, Zied Hamdi [EMAIL PROTECTED] wrote:

 Hi Stojan,

 Can you send this working version to Bernd so everyone can benefit of
 it. (a blanc project would be a no head ake starting point for everyone).

 Regards,
 Zied


 
 


Re: [tobago] Seam integration

2008-01-28 Thread Bernd Bohmann
/ajax4jsf.taglib.xml

 11:15:20,171 ERROR [STDERR] 23 janv. 2008 11:15:20
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit

 INFO: Added Library from:
 jar:file:/D:/jbdevstudio/jboss-eap/jboss-as/server/default/deploy/IntoServices-
 ear.ear/IntoServices.war/WEB-INF/lib/richfaces-
 ui.jar!/META-INF/rich.taglib.xml

 11:15:20,187 ERROR [STDERR] 23 janv. 2008 11:15:20
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit

 INFO: Added Library from:
 jar:file:/D:/jbdevstudio/jboss-eap/jboss-as/server/default/deploy/IntoServices-
 ear.ear/IntoServices.war/WEB-INF/lib/richfaces-
 ui.jar!/META-INF/richfaces.taglib.xml

 11:15:20,187 ERROR [STDERR] 23 janv. 2008 11:15:20
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit

 INFO: Added Library from:
 jar:file:/D:/jbdevstudio/jboss-eap/jboss-as/server/default/deploy/IntoServices-
 ear.ear/IntoServices.war/WEB-INF/lib/tomahawk-
 facelets-1.1.6.jar!/META-INF/tomahawk-sandbox.taglib.xml

 11:15:20,203 ERROR [STDERR] 23 janv. 2008 11:15:20
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit

 INFO: Added Library from:
 jar:file:/D:/jbdevstudio/jboss-eap/jboss-as/server/default/deploy/IntoServices-
 ear.ear/IntoServices.war/WEB-INF/lib/tomahawk-
 facelets-1.1.6.jar!/META-INF/tomahawk.taglib.xml

 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.PRETTY_HTML' found, using default value true

 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true

 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using
 default value true

 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.CONFIG_REFRESH_PERIOD' found, using default value 2


 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.DETECT_JAVASCRIPT' found, using default value false


 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.AUTO_SCROLL' found, using default value false

 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value
 org.apache.myfaces.renderkit.html.util.DefaultAddResource

 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value
 /faces/myFacesExtensionResource

 11:15:20,296 INFO   [MyfacesConfig] No context init parameter '
 org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value
 true

 11:15:20,296 INFO   [MyfacesConfig] Starting up Tomahawk on the
 RI-JSF-Implementation.





 2008/1/22, Bernd Bohmann [EMAIL PROTECTED]:
 Hello Zied,

 richfaces has it's own ViewHandlerImpl. Until 1.1.0-SNAPSHOT tobago
 depends on this own ViewHandlerImpl. Now tobago doesn't require a
 own
 ViewHandlerImpl (I hope). Maybe we backport this change to a 1.0.15
 version.

 Please can you remove the richfaces lib from the WEB-INF/lib folder
 or
 use the 1.1.0-SNAPSHOT version of tobago until we backport this fix.


 Regards

 Bernd

 Zied Hamdi schrieb:
 Hi Bernd,

 I've tried to estimate the cost of moving to rich faces (to avoid
 unexpected
 secondary effects with Tobago), it's too much for my app in its
 state today.
 So I'm back to Tobago :-).

 Did you say you were able to run tobago on Seam (if the view is
 not the
 RichFaces implementation) ?

 I'm actually facing the same problem as before: my page is
 extremey basic. I
 verified the view root is tobago's view.


 f:view xmlns:f=http://java.sun.com/jsf/core 

   xmlns:tc= http://myfaces.apache.org/tobago/component;

   tc:page

 tc:out value=ok /

   /tc:page

 /f:view

 I don't understand where the rich faces view handler takes place
 in this
 schema. (it was the case in the previous example where I had
 tobago inside
 rich faces panels, but now the view is pure tobago...)

 Any idea please?

 Regards,
 Zied

 --
 Zied Hamdi
 www.into-i.fr
 (previously in 2003)
 zatreex.sf.net



 --
 Zied Hamdi
 www.into-i.fr
 (previously in 2003)
 zatreex.sf.net

 
 
 


Re: [Tobago] Error with field validation

2008-01-24 Thread Bernd Bohmann
Hello,

can you send list of WEB-INF/lib, please.

Regards

Bernd

florimodo schrieb:
 Hi,
 
 when I am submitting a form with empty required fields - I get a
 ClassCastException, no messages are displayed on the page. It seems that
 I got something to do with my resources, but I have no clue where to look..
 
 The exception is
 
 java.lang.ClassCastException:
 org.apache.myfaces.tobago.context.ResourceManagerImpl
at
 org.apache.myfaces.tobago.context.ResourceManagerFactory.getResourceManager(ResourceManagerFactory.java:39)
 
at
 org.apache.myfaces.tobago.context.TobagoResourceBundle.handleGetObject(TobagoResourceBundle.java:42)
 
at java.util.ResourceBundle.getObject(ResourceBundle.java:319)
at java.util.ResourceBundle.getString(ResourceBundle.java:285)
at
 javax.faces.component._MessageUtils.getBundleString(_MessageUtils.java:155)
at javax.faces.component._MessageUtils.getMessage(_MessageUtils.java:92)
at
 javax.faces.component._MessageUtils.addErrorMessage(_MessageUtils.java:52)
at javax.faces.component.UIInput.validateValue(UIInput.java:306)
at javax.faces.component.UIInput.validate(UIInput.java:354)
at javax.faces.component.UIInput.processValidators(UIInput.java:184)
at
 javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:627)
 
at
 javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:627)
 
at
 javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:627)
 
at
 javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:627)
 
at
 javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:627)
 
at
 org.apache.myfaces.tobago.component.UIForm.processValidators(UIForm.java:71)
 
at
 javax.faces.component.UIComponentBase.processValidators(UIComponentBase.java:627)
 
at
 javax.faces.component.UIViewRoot.processValidators(UIViewRoot.java:149)
at
 org.apache.myfaces.tobago.component.UIViewRoot.processValidators(UIViewRoot.java:194)
 
at
 org.apache.myfaces.tobago.lifecycle.ProcessValidationsExecutor.execute(ProcessValidationsExecutor.java:57)
 
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:139)
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
 
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 
at
 org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
 
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 
at
 org.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter.doFilter(TobagoMultipartFormdataFilter.java:130)
 
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 
at
 qme.media.publishing.ui.servlets.SecurityFilter.doFilter(SecurityFilter.java:54)
 
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 
at
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
 
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 
at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
 
at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 
at
 org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
 
at
 org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
 
at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 
at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 
at
 org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
 
at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 
at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
 org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 
at
 

Re: [tobago] Seam integration

2008-01-22 Thread Bernd Bohmann
,

 Did I understand the issue? is it to fix compatibilty of Tobago with other
 jsf implementations like rich faces?

 Regards,
 Zied

 2008/1/18, Bernd Bohmann [EMAIL PROTECTED]:
 Hello Zied,

 I think tobago should compatible with seam or a other webbeans
 implementation. The own ViewHandler from richfaces is the cause of the
 error.

 I have change the tobago code to reflect this.

 https://issues.apache.org/jira/browse/TOBAGO-600

 The next nighlty build of 1.1.0 should include this fix. Maybe we
 backport this change to a 1.0.15 release. I would not like to include
 this change in the 1.0.14 release, which will be released in a few days.

 The current 1.1.0-SNAPSHOT is not stable.

 Regards

 Bernd

 Zied Hamdi schrieb:
 Hi Bernd,

 I posted it to
 http://dl.free.fr/nMcECNoTg/20080117-105000NonworkingTobagointegration.zip
 .
 It will be valid for 30 days.

 I would like to insist on the presence of Seam in the next coming
 applications architecture (it resolves a lot of JSF everyday
 problems). Seen
 it's granted to work with RichFaces, all developers will opt for it,
 and if
 Tobago is not compatible with Seam or RichFaces, it will be abandoned
 by all
 this big community. This is naturally a personal opinion.

 Regards,
 Zied


 2008/1/17, Bernd Bohmann  [EMAIL PROTECTED]:
 Hello Zied,

 can you send me the test project, please.

 I will try to debug the project.

 Regards

 Bernd

 Zied Hamdi schrieb:
 Hi,

 I'm trying to run a seam-tobago testing project.

 I have the following exception, and i can't find why it happens. I
 started
 from a working seam project then i added the Tobago conf (that i
 took
 from
 my existing working tobago project). I'm under JBoss 4.2 so the sun
 JSF
 implementation.

 Notice there's nothing confidential in my project: I can send it to
 you
 as
 an empty testing project.


 16:42:32,265 ERROR [STDERR] 16 janv. 2008 16:42:32
 com.sun.facelets.FaceletViewHandler *handleRenderException*

 GRAVE: Error Rendering View[/home.xhtml]

 *java.util.NoSuchElementException*

   at java.util.StringTokenizer.nextToken(*StringTokenizer.java
 :332*)
   at
 org.apache.myfaces.tobago.context.ResourceManagerImpl.getPaths
 (*
 ResourceManagerImpl.java:180*)

   at
 org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(*
 ResourceManagerImpl.java :341*)

   at
 org.apache.myfaces.tobago.renderkit.TobagoRenderKit.getRenderer
 (*
 TobagoRenderKit.java:64*)

   at javax.faces.component.UIComponentBase.getRenderer (*
 UIComponentBase.java:1206*)

   at javax.faces.component.UIComponentBase.encodeBegin(*
 UIComponentBase.java:786*)

   at javax.faces.component.UIComponent.encodeAll(*
 UIComponent.java
 :884*)
   at javax.faces.component.UIComponent.encodeAll(*
 UIComponent.java
 :892*)
   at com.sun.facelets.FaceletViewHandler.renderView (*
 FaceletViewHandler.java:592*)

   at org.ajax4jsf.application.ViewHandlerWrapper.renderView(*
 ViewHandlerWrapper.java:108*)

   at org.ajax4jsf.application.AjaxViewHandler.renderView(*
 AjaxViewHandler.java:243*)

   at
 org.apache.myfaces.tobago.lifecycle.RenderResponseExecutor.execute(
 *RenderResponseExecutor.java:56*)

   at org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.render
 (*
 TobagoLifecycle.java:141*)

   at javax.faces.webapp.FacesServlet.service(*FacesServlet.java
 :245*)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(*
 ApplicationFilterChain.java :290*)

   at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
 ApplicationFilterChain.java:206*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:83*)

   at org.jboss.seam.web.MultipartFilter.doFilter(*
 MultipartFilter.java
 :85*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter
 (*
 SeamFilter.java:69*)

   at org.jboss.seam.web.ExceptionFilter.doFilter(*
 ExceptionFilter.java
 :64*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter
 (*
 SeamFilter.java:69*)

   at org.jboss.seam.web.RedirectFilter.doFilter (*
 RedirectFilter.java
 :44*
 )

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter
 (*
 SeamFilter.java:69*)

   at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(*
 BaseXMLFilter.java
 :141*)

   at org.ajax4jsf.webapp.BaseFilter.doFilter(*BaseFilter.java
 :281*)
   at org.jboss.seam.web.Ajax4jsfFilter.doFilter(*
 Ajax4jsfFilter.java
 :60*
 )

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.web.LoggingFilter.doFilter(*
 LoggingFilter.java
 :58*)
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(*
 HotDeployFilter.java:68*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.servlet.SeamFilter.doFilter

Re: [tobago] Seam integration

2008-01-18 Thread Bernd Bohmann
Hello Zied,

I think tobago should compatible with seam or a other webbeans
implementation. The own ViewHandler from richfaces is the cause of the
error.

I have change the tobago code to reflect this.

https://issues.apache.org/jira/browse/TOBAGO-600

The next nighlty build of 1.1.0 should include this fix. Maybe we
backport this change to a 1.0.15 release. I would not like to include
this change in the 1.0.14 release, which will be released in a few days.

The current 1.1.0-SNAPSHOT is not stable.

Regards

Bernd

Zied Hamdi schrieb:
 Hi Bernd,
 
 I posted it to
 http://dl.free.fr/nMcECNoTg/20080117-105000NonworkingTobagointegration.zip .
 It will be valid for 30 days.
 
 I would like to insist on the presence of Seam in the next coming
 applications architecture (it resolves a lot of JSF everyday problems). Seen
 it's granted to work with RichFaces, all developers will opt for it, and if
 Tobago is not compatible with Seam or RichFaces, it will be abandoned by all
 this big community. This is naturally a personal opinion.
 
 Regards,
 Zied
 
 
 2008/1/17, Bernd Bohmann [EMAIL PROTECTED]:
 Hello Zied,

 can you send me the test project, please.

 I will try to debug the project.

 Regards

 Bernd

 Zied Hamdi schrieb:
 Hi,

 I'm trying to run a seam-tobago testing project.

 I have the following exception, and i can't find why it happens. I
 started
 from a working seam project then i added the Tobago conf (that i took
 from
 my existing working tobago project). I'm under JBoss 4.2 so the sun JSF
 implementation.

 Notice there's nothing confidential in my project: I can send it to you
 as
 an empty testing project.


 16:42:32,265 ERROR [STDERR] 16 janv. 2008 16:42:32
 com.sun.facelets.FaceletViewHandler *handleRenderException*

 GRAVE: Error Rendering View[/home.xhtml]

 *java.util.NoSuchElementException*

   at java.util.StringTokenizer.nextToken(*StringTokenizer.java:332*)

   at org.apache.myfaces.tobago.context.ResourceManagerImpl.getPaths
 (*
 ResourceManagerImpl.java:180*)

   at
 org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(*
 ResourceManagerImpl.java:341*)

   at org.apache.myfaces.tobago.renderkit.TobagoRenderKit.getRenderer
 (*
 TobagoRenderKit.java:64*)

   at javax.faces.component.UIComponentBase.getRenderer(*
 UIComponentBase.java:1206*)

   at javax.faces.component.UIComponentBase.encodeBegin(*
 UIComponentBase.java:786*)

   at javax.faces.component.UIComponent.encodeAll(*UIComponent.java
 :884*)
   at javax.faces.component.UIComponent.encodeAll(*UIComponent.java
 :892*)
   at com.sun.facelets.FaceletViewHandler.renderView(*
 FaceletViewHandler.java:592*)

   at org.ajax4jsf.application.ViewHandlerWrapper.renderView(*
 ViewHandlerWrapper.java:108*)

   at org.ajax4jsf.application.AjaxViewHandler.renderView(*
 AjaxViewHandler.java:243*)

   at
 org.apache.myfaces.tobago.lifecycle.RenderResponseExecutor.execute(
 *RenderResponseExecutor.java:56*)

   at org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.render(*
 TobagoLifecycle.java:141*)

   at javax.faces.webapp.FacesServlet.service(*FacesServlet.java
 :245*)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(*
 ApplicationFilterChain.java:290*)

   at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
 ApplicationFilterChain.java:206*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:83*)

   at org.jboss.seam.web.MultipartFilter.doFilter(*
 MultipartFilter.java
 :85*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.web.ExceptionFilter.doFilter(*
 ExceptionFilter.java
 :64*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.web.RedirectFilter.doFilter(*RedirectFilter.java
 :44*
 )

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(*
 BaseXMLFilter.java
 :141*)

   at org.ajax4jsf.webapp.BaseFilter.doFilter(*BaseFilter.java:281*)

   at org.jboss.seam.web.Ajax4jsfFilter.doFilter(*Ajax4jsfFilter.java
 :60*
 )

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.web.LoggingFilter.doFilter(*LoggingFilter.java
 :58*)
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(*
 HotDeployFilter.java:68*)

   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)

   at org.jboss.seam.servlet.SeamFilter.doFilter(*SeamFilter.java
 :158*)
   at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(*
 ApplicationFilterChain.java:235*)

   at org.apache.catalina.core.ApplicationFilterChain.doFilter

Re: [Tobago] How to checkout 1.0.* sources

2008-01-18 Thread Bernd Bohmann
Hello Helmut,

http://svn.apache.org/repos/asf/myfaces/tobago/branches/tobago-1.0.x/

for the 1.0.x branch

and

http://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.13/

for the 1.0.13 release.


Regards

Bernd

Helmut Swaczinna schrieb:
 Hi,
 
 I'm not very familar with svn and the organization of the Tobago svn
 repository. So apologize my question:
 
 How do I check out the source of a specific release (e.g. 1.0.13) or the
 latest sources of the 1.0.* branch?
 With svn checkout http://svn.apache.org/repos/asf/myfaces/tobago/trunk I
 get the latest 1.1.0 sources.
 
 Regards
 Helmut
 


Re: [tobago] Seam integration

2008-01-16 Thread Bernd Bohmann
Hello Zied,

can you send me the test project, please.

I will try to debug the project.

Regards

Bernd

Zied Hamdi schrieb:
 Hi,
 
 I'm trying to run a seam-tobago testing project.
 
 I have the following exception, and i can't find why it happens. I started
 from a working seam project then i added the Tobago conf (that i took from
 my existing working tobago project). I'm under JBoss 4.2 so the sun JSF
 implementation.
 
 Notice there's nothing confidential in my project: I can send it to you as
 an empty testing project.
 
 
 16:42:32,265 ERROR [STDERR] 16 janv. 2008 16:42:32
 com.sun.facelets.FaceletViewHandler *handleRenderException*
 
 GRAVE: Error Rendering View[/home.xhtml]
 
 *java.util.NoSuchElementException*
 
   at java.util.StringTokenizer.nextToken(*StringTokenizer.java:332*)
 
   at org.apache.myfaces.tobago.context.ResourceManagerImpl.getPaths(*
 ResourceManagerImpl.java:180*)
 
   at org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(*
 ResourceManagerImpl.java:341*)
 
   at org.apache.myfaces.tobago.renderkit.TobagoRenderKit.getRenderer(*
 TobagoRenderKit.java:64*)
 
   at javax.faces.component.UIComponentBase.getRenderer(*
 UIComponentBase.java:1206*)
 
   at javax.faces.component.UIComponentBase.encodeBegin(*
 UIComponentBase.java:786*)
 
   at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:884*)
 
   at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:892*)
 
   at com.sun.facelets.FaceletViewHandler.renderView(*
 FaceletViewHandler.java:592*)
 
   at org.ajax4jsf.application.ViewHandlerWrapper.renderView(*
 ViewHandlerWrapper.java:108*)
 
   at org.ajax4jsf.application.AjaxViewHandler.renderView(*
 AjaxViewHandler.java:243*)
 
   at org.apache.myfaces.tobago.lifecycle.RenderResponseExecutor.execute(
 *RenderResponseExecutor.java:56*)
 
   at org.apache.myfaces.tobago.lifecycle.TobagoLifecycle.render(*
 TobagoLifecycle.java:141*)
 
   at javax.faces.webapp.FacesServlet.service(*FacesServlet.java:245*)
 
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(*
 ApplicationFilterChain.java:290*)
 
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
 ApplicationFilterChain.java:206*)
 
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:83*)
 
   at org.jboss.seam.web.MultipartFilter.doFilter(*MultipartFilter.java
 :85*)
 
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)
 
   at org.jboss.seam.web.ExceptionFilter.doFilter(*ExceptionFilter.java
 :64*)
 
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)
 
   at org.jboss.seam.web.RedirectFilter.doFilter(*RedirectFilter.java:44*
 )
 
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)
 
   at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(*BaseXMLFilter.java
 :141*)
 
   at org.ajax4jsf.webapp.BaseFilter.doFilter(*BaseFilter.java:281*)
 
   at org.jboss.seam.web.Ajax4jsfFilter.doFilter(*Ajax4jsfFilter.java:60*
 )
 
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)
 
   at org.jboss.seam.web.LoggingFilter.doFilter(*LoggingFilter.java:58*)
 
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)
 
   at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(*
 HotDeployFilter.java:68*)
 
   at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(*
 SeamFilter.java:69*)
 
   at org.jboss.seam.servlet.SeamFilter.doFilter(*SeamFilter.java:158*)
 
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(*
 ApplicationFilterChain.java:235*)
 
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
 ApplicationFilterChain.java:206*)
 
   at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(*
 ReplyHeaderFilter.java:96*)
 
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(*
 ApplicationFilterChain.java:235*)
 
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
 ApplicationFilterChain.java:206*)
 
   at org.apache.catalina.core.StandardWrapperValve.invoke(*
 StandardWrapperValve.java:230*)
 
   at org.apache.catalina.core.StandardContextValve.invoke(*
 StandardContextValve.java:175*)
 
   at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(*
 SecurityAssociationValve.java:179*)
 
   at org.apache.catalina.authenticator.AuthenticatorBase.invoke(*
 AuthenticatorBase.java:433*)
 
   at org.jboss.web.tomcat.security.JaccContextValve.invoke(*
 JaccContextValve.java:84*)
 
   at org.apache.catalina.core.StandardHostValve.invoke(*
 StandardHostValve.java:128*)
 
   at org.apache.catalina.valves.ErrorReportValve.invoke(*
 ErrorReportValve.java:104*)
 
   at 

Re: [tobago] is ti seam compatible?

2008-01-14 Thread Bernd Bohmann
Hello Zied,

unfortunatley I have not the time to setup a seam tobago test project.

Tobago should support client and server side state saving with or
without ajax requests. I would like to help everyone who tries to setup
a tobago seam example. Spring Web Flow, Apache Orchestra and Apache
Shale Dialog are on my wishlist too.

Regards

Bernd

Zied Hamdi schrieb:
 Hi,
 
 Rereading my mail, I've discovered it isn't very comprehensive. The question
 was: is Tobago compatible with Seam.
 
 Did anyone try to integrate Tobago with Rich Faces?
 
 I think the fact that Seam, Rich Faces, JBoss, and Hibernate are developped
 under the same group is a handicap for other JSF products. Mainly because
 Seam is really the next generation web framework so it has lots of good
 ideas to simplify developement and maintainance. I think that being out of
 the movement is a big risk for any JSF implementation to be eliminated just
 because it costs 'comparatively' a lot more to develop with.
 
 What do you think about it?
 
 Regards,
 Zied
 
 2008/1/11, Zied Hamdi [EMAIL PROTECTED]:
 Hi,

 I'm learning Seam to use it in my Tobao project. I've found some posts
 like
 http://lists.jboss.org/pipermail/jboss-user/2006-August/007561.html
 or
 http://www.mail-archive.com/users@myfaces.apache.org/msg28872.html

 But all are too old to be considered as the answer. Did some changes arise
 from that period?

 Regards,
 --
 Zied Hamdi
 www.into-i.fr

 
 
 


Re: [Tobago] tc:columnEvent TOBAGO-553

2008-01-14 Thread Bernd Bohmann
Hello Helmut,

please add a new jira issue and link the issue to TOBAGO-553.

I would like to add you to the contributors section of the tobago pom.
Can I use your email address?

Regards

Bernd

Helmut Swaczinna schrieb:
 Hello Bernd,
 
 please reopen TOBAGO-553. Or should I add new jira issues for the
 comments I added?
 
 Regards
 Helmut
 


Re: [Tobago] tc:columnEvent

2008-01-07 Thread Bernd Bohmann
Hello Helmut,

the current snapshot is unstable. In a few days i will change the
version of the trunk to 1.1.0-SNAPSHOT. Please try it with the 1.0.13
release. Maybe we will backport some changes to a 1.0.14 version.

tc:columnEvent supports action and actionListener until now.

Regards

Bernd

Helmut Swaczinna schrieb:
 Hi Bernd,
 
 I stil can't get it work at all. Nothing happens when I click or
 doubleclick on a row. I tried both events and
 I tried an action and an onclick command. This is my code:
 
 f:view
  tc:page id=sheetPage width=800px height=200px
tc:panel id=panel
  f:facet name=layout
tc:gridLayout columns=*;*/
  /f:facet
 
  tc:sheet id=testTable
columns=80px;80px
showHeader=true
showRowRange=none
showPageRange=none
showDirectLinks=none
first=0I
selectable=none
state=#{controller.sheetState}
var=row
value=#{controller.list1}
tc:columnEvent event=dblclick 
  tc:command
onclick=alert('Hallo')/
/tc:columnEvent
tc:column label=Column 1
  tc:out id=column1
value=#{row.column1}/
/tc:column
tc:column label=Column 2
  tc:out id=column2
value=#{row.column2}/
/tc:column
  /tc:sheet
 
  tc:panel id=panel2
f:facet name=layout
  tc:gridLayout rows=fixed;*/
/f:facet
tc:in value=#{controller.value2}/
tc:hidden id=selection value=#{controller.value}/
  /tc:panel
 
/tc:panel
  /tc:page
 /f:view
 
 There's no alert statement in the generated HTML code, so I think the
 sheet renderer ignores the columnEvent
 tag. The only thing I see is the hand coursor when I position the
 mouse over the sheet.
 
 I'm using the 1.0.14 snapshot from 19/12/2007.
 
 Regards
 Helmut
 
 
 - Original Message - From: Bernd Bohmann
 [EMAIL PROTECTED]
 To: MyFaces Discussion users@myfaces.apache.org
 Sent: Friday, January 04, 2008 5:20 PM
 Subject: Re: [Tobago] tc:columnEvent
 
 
 Hello Helmut,

 please look at tobago-example-addressbook list.jsp.

 Regards

 Bernd

 Helmut Swaczinna schrieb:
 Hi,

 I'm looking for a working example for tc:columnEvent usage. Can't get it
 work.

 Regards
 Helmut


 
 


Re: [tobago] tc:time disable att doesn't work

2008-01-07 Thread Bernd Bohmann
Hello Zied,

See:
https://issues.apache.org/jira/browse/TOBAGO-583

Maybe we will backport this issue to a 1.0.14 release.

Regards

Bernd

Zied Hamdi schrieb:
 Hi,
 
 I'm unable to disable a tc:time is it a misuse?
 
 Regards,
 Zied
 


Re: [Tobago] tc:columnEvent

2008-01-04 Thread Bernd Bohmann
Hello Helmut,

please look at tobago-example-addressbook list.jsp.

Regards

Bernd

Helmut Swaczinna schrieb:
 Hi,
 
 I'm looking for a working example for tc:columnEvent usage. Can't get it
 work.
 
 Regards
 Helmut
 


[ANNOUNCE] Apache Tobago 1.0.13

2007-12-29 Thread Bernd Bohmann
The Apache MyFaces team is pleased to announce the release of Apache
Tobago 1.0.13.
Apache Tobago is a renderkit for JSF and runs with MyFaces Core.

Changes
---

Please check the release notes at
http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310273styleName=Htmlversion=12312766
for a full list of the changes in version 1.0.13.

For more information about Apache Tobago, please visit
http://myfaces.apache.org/tobago/.

Have fun,
-The MyFaces team


Re: [Tobago] Default sorting by the second column in tc:sheet

2007-12-29 Thread Bernd Bohmann
Hello Marcin,

maybe you can sort the List or Array after creating it.
I don't know a way to sort a column on a page load.

Regards

Bernd

Marcin Zajaczkowski schrieb:
 Hi,
 
 
 Maybe my problem is a trivial one, but I was unable to find an answer.
 I would like to have a table (sheet) sort by the second column by
 default (on a page load).
 I've seen setSortedColumnId() method in SheetState class which could be
 somehow useful, but maybe there is an easier way to set key column
 directly in JSP?
 
 
 Thanks for help
 Marcin
 
 


Re: [Tobago] tx:date and onchange

2007-12-16 Thread Bernd Bohmann
Hello Michael,

this is on my wish list, too.

Can you add an issue for this, please.

The tile should be: 'Adding facet onchange support to tc:date' or
something else.

Regards

Bernd

Michał 'Gandalf' Stawicki schrieb:
 hello,
 
 I wish to launch some action upon selecting date from datapicker. I
 have already tried setting onchange attribute, facet onchange and
 adding onchange event to date's input field. All of this have failed.
 
 Does anyone know how to achieve this?
 
 regards,
 michael
 


Re: [Tobago] Class attribute not rendered for input fields

2007-12-14 Thread Bernd Bohmann
Hello Florian,

can you add an issue for this, please.

https://issues.apache.org/jira/browse/TOBAGO

We should keep this issue in mind.

Regards

Bernd

florimodo schrieb:
 Bernd,
 
 I fixed the issue! I removed the jars in my WEB-INF/lib dir one by
 another, and the problem was not tomahawk (which works fine), but the
 shale-* libs!
 
 Thanks,
 Florian
 
 
 florimodo schrieb:
 Hello Bernd,

 I have already tried that, it didn't help...
 It even happened that the class attribute wasn't rendered at all, e.g.

 tx:in
 id=username
 label=Benutzername
 tabIndex=1
 value=#{sessionBean.username}
 required=true /

 renders

 input type=text name=page:username id=page:username value= 
 tabindex=1

 Regards,
 Florian

 Bernd Bohmann schrieb:
 Hello Florian,

 can you remove the tomahawk and tomahawk-sandbox jar from the
 WEB-INF/lib, please.

 Regards

 Bernd

 Regards

 florimodo schrieb:
   
 Bernd,

 the content is as follows:

 activation.jar
 avalon-framework-4.1.3.jar
 commons-beanutils-1.7.0.jar
 commons-chain-1.1.jar
 commons-codec-1.3.jar
 commons-collections-3.1.jar
 commons-digester-1.7.jar
 commons-el-1.0.jar
 commons-email-1.0.jar
 commons-fileupload-1.0.jar
 commons-io-1.1.jar
 commons-lang-2.1.jar
 commons-validator-1.3.0.jar
 jstl-1.1.0.jar
 mail.jar
 oro-2.0.8.jar
 ostermillerutils_1_06_00.jar
 shale-core-1.0.3.jar
 standard-1.1.2.jar
 tobago-core-1.0.12.jar
 tobago-theme-charlotteville-1.0.12.jar
 tobago-theme-hdi-1.0.0.jar
 tobago-theme-richmond-1.0.12.jar
 tobago-theme-scarborough-1.0.12.jar
 tobago-theme-speyside-1.0.12.jar
 tobago-theme-standard-1.0.12.jar
 tobago-theme-talanx-1.0.1.jar
 tomahawk-1.1.7-SNAPSHOT.jar
 tomahawk-sandbox-1.1.6-SNAPSHOT.jar

 Thanks,
 Florian

 Bernd Bohmann schrieb:
 
 Hello Florian,

 can you list the content of the WEB-INF/lib dir?

 Regards

 Bernd

 florimodo schrieb:
   
   
 Hi,

 I have used the Tobago demo application as a blueprint and modified it
 for my own purposes. Everything is fine, except no class attributes are
 rendered for text and textarea input fields.

 Example tag:

 tx:in id=username label=Benutzername tabIndex=1
 value=#{sessionBean.username} required=true /

 Rendered code would look like this:

 a class=tobago-label-default tobago-label-required
 
 
 label id=page:_idJsp11 for=page:username 
 class=tobago-label-default tobago-label-required
 Benutzername/label/a/div/div/tdtd 
 class=tobago-gridLayout-cell-td style=width: 52px; height: 20px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-row 
 style=width: 52px; height: 20px;
 input type=text name=page:username id=page:username 
 value=fieber tabindex=1 class=

   
   
 -- The class attribute is empty!
 This only applies for text and textarea fields - all other inputs, divs,
 tables, etc are fine!

 Things I have already tried (none of which helped):
 - I have removed my own theme (based on speyside)
 - I have removed tomahwak, as I've learned that Tobago doesn't work with
 Tomahawk properly

 The only error I get on the console is:

 org.apache.myfaces.tobago.renderkit.TobagoRenderKit: This method isn't
 implemeted yet, and should not be called: addRenderer


 I am desperate - any ideas are appreciated.
 Thanks in advance,

 Florian



 
 
   
   
 
   
 
 


Re: [Tobago] Class attribute not rendered for input fields

2007-12-13 Thread Bernd Bohmann
Hello Florian,

can you remove the tomahawk and tomahawk-sandbox jar from the
WEB-INF/lib, please.

Regards

Bernd

Regards

florimodo schrieb:
 Bernd,
 
 the content is as follows:
 
 activation.jar
 avalon-framework-4.1.3.jar
 commons-beanutils-1.7.0.jar
 commons-chain-1.1.jar
 commons-codec-1.3.jar
 commons-collections-3.1.jar
 commons-digester-1.7.jar
 commons-el-1.0.jar
 commons-email-1.0.jar
 commons-fileupload-1.0.jar
 commons-io-1.1.jar
 commons-lang-2.1.jar
 commons-validator-1.3.0.jar
 jstl-1.1.0.jar
 mail.jar
 oro-2.0.8.jar
 ostermillerutils_1_06_00.jar
 shale-core-1.0.3.jar
 standard-1.1.2.jar
 tobago-core-1.0.12.jar
 tobago-theme-charlotteville-1.0.12.jar
 tobago-theme-hdi-1.0.0.jar
 tobago-theme-richmond-1.0.12.jar
 tobago-theme-scarborough-1.0.12.jar
 tobago-theme-speyside-1.0.12.jar
 tobago-theme-standard-1.0.12.jar
 tobago-theme-talanx-1.0.1.jar
 tomahawk-1.1.7-SNAPSHOT.jar
 tomahawk-sandbox-1.1.6-SNAPSHOT.jar
 
 Thanks,
 Florian
 
 Bernd Bohmann schrieb:
 Hello Florian,

 can you list the content of the WEB-INF/lib dir?

 Regards

 Bernd

 florimodo schrieb:
   
 Hi,

 I have used the Tobago demo application as a blueprint and modified it
 for my own purposes. Everything is fine, except no class attributes are
 rendered for text and textarea input fields.

 Example tag:

 tx:in id=username label=Benutzername tabIndex=1
 value=#{sessionBean.username} required=true /

 Rendered code would look like this:

 a class=tobago-label-default tobago-label-required
 
 label id=page:_idJsp11 for=page:username class=tobago-label-default 
 tobago-label-required
 Benutzername/label/a/div/div/tdtd 
 class=tobago-gridLayout-cell-td style=width: 52px; height: 20px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-row 
 style=width: 52px; height: 20px;
 input type=text name=page:username id=page:username value=fieber 
 tabindex=1 class=

   
 -- The class attribute is empty!
 This only applies for text and textarea fields - all other inputs, divs,
 tables, etc are fine!

 Things I have already tried (none of which helped):
 - I have removed my own theme (based on speyside)
 - I have removed tomahwak, as I've learned that Tobago doesn't work with
 Tomahawk properly

 The only error I get on the console is:

 org.apache.myfaces.tobago.renderkit.TobagoRenderKit: This method isn't
 implemeted yet, and should not be called: addRenderer


 I am desperate - any ideas are appreciated.
 Thanks in advance,

 Florian



 
   
 
 


Re: [Tobago] Class attribute not rendered for input fields

2007-12-12 Thread Bernd Bohmann
Hello Florian,

can you list the content of the WEB-INF/lib dir?

Regards

Bernd

florimodo schrieb:
 Hi,
 
 I have used the Tobago demo application as a blueprint and modified it
 for my own purposes. Everything is fine, except no class attributes are
 rendered for text and textarea input fields.
 
 Example tag:
 
 tx:in id=username label=Benutzername tabIndex=1
 value=#{sessionBean.username} required=true /
 
 Rendered code would look like this:
 
 a class=tobago-label-default tobago-label-required
 label id=page:_idJsp11 for=page:username class=tobago-label-default 
 tobago-label-required
 Benutzername/label/a/div/div/tdtd 
 class=tobago-gridLayout-cell-td style=width: 52px; height: 20px;
 div class=tobago-gridLayout-default tobago-gridLayout-first-row 
 style=width: 52px; height: 20px;
 input type=text name=page:username id=page:username value=fieber 
 tabindex=1 class=

 
 -- The class attribute is empty!
 This only applies for text and textarea fields - all other inputs, divs,
 tables, etc are fine!
 
 Things I have already tried (none of which helped):
 - I have removed my own theme (based on speyside)
 - I have removed tomahwak, as I've learned that Tobago doesn't work with
 Tomahawk properly
 
 The only error I get on the console is:
 
 org.apache.myfaces.tobago.renderkit.TobagoRenderKit: This method isn't
 implemeted yet, and should not be called: addRenderer
 
 
 I am desperate - any ideas are appreciated.
 Thanks in advance,
 
 Florian
 
 
 


Re: [Tobago] Problems with IE6

2007-11-30 Thread Bernd Bohmann
Hello Carsten,

thanks for your hint :-)

Regards

Bernd

[EMAIL PROTECTED] schrieb:
 Hello Bernd,
 
 our problems are resolved. After searching for about two weeks the
 firewall team has discovered the rules responsible for our Page cannot
 be loaded error.
 
 But good to know that the next Tobago version hasn't the JavaScript code
 in the post buffer.
 
 Regards
 Carsten Manshusen
 
 
  
 
 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-
 
 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, November 29, 2007 4:10 PM
 To: MyFaces Discussion
 Subject: Re: [Tobago] Problems with IE6
 
 Hello Carsten,
 
 in one or two weeks.
 
 Regards
 
 Bernd
 
 [EMAIL PROTECTED] schrieb:
 Hello Bernd,

 when will ne next Tobago version 1.0.13 be released?

 My next try is to upgrade our app from Tobago 1.0.10 to 1.0.12.

 Regards
 Carsten


  

 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-

 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, November 28, 2007 7:19 PM
 To: MyFaces Discussion
 Subject: Re: [Tobago] Problems with IE6

 Hello Carsten,

 I think the size of the submit should not be a problem.
 The IE includes the content of the button.

 The javascript in the submit should not be a problem.
 But the javacript content should not included i will fix this.

 See:

 https://issues.apache.org/jira/browse/TOBAGO-559

 Can you send a test page for your problem, please.

 Can you update to a more recent version of tobago?

 Regards

 Bernd

 [EMAIL PROTECTED] schrieb:
 Hello Bernd,

 we have testet it with the Tobago demo app on our server and the demo
 app works.

 It seems that we have a problem with the post bodies in our tobago
 app.
 In Firefox (here our app works) the size is 973 bytes and in IE6
 (here
 our app doesn't work) the size is 1320 bytes

 Buffer Firefox: 


 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+fl
 ight+schedules.+OAL+flight+and+booking%0D%0A++confirmati
 on+is+required+before+shipment+is+reconfirmed+to+the+LCAG+customer.page
 %3AsprDlg%3A_idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPo
 sition=page%3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-client
 Dimension=1280%3B864HTTP/1.1 200 OK

 Buffer IE:


 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3Aclearbutton=C%3CU%3El%3C%2FU%3Eear%0D%0A%3CSCRIPT+t
 ype%3Dtext%2Fjavascript%3E%0A%3C%21--%0Anew+Tobago.ScriptLoader%28%0A+++
 +%5B%5D%2C+%0A++%22new+Tobago.AcceleratorKey%28function%28%29+%7
 BTobago.clickOnElement%28%27page%3AsprDlg%3Aclearbutton%27%29%3B%7D%2C+%
 5C%22l%5C%22%29%3B%22%0A%29%3B%0A%2F%2F+--%3E%0A%3C%2FSCRIPT%3Epage%3As
 prDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+flight+schedule
 s.+OAL+flight+and+booking%0D%0A++confirmation+is+require
 d+before+shipment+is+reconfirmed+to+the+LCAG+customer.page%3AsprDlg%3A_
 idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPosition=page%
 3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-clientDimension=127
 6%3B896HTTP/1.1 200 OK

 Is this correct or is ther a problem in our application with the post
 buffer? Is it correct to have JavaScript in the post buffer?

 Regards,
 Carsten



  

 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-

 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, November 27, 2007 6:28 PM

Re: [Tobago] Problems with IE6

2007-11-29 Thread Bernd Bohmann
Hello Carsten,

in one or two weeks.

Regards

Bernd

[EMAIL PROTECTED] schrieb:
 Hello Bernd,
 
 when will ne next Tobago version 1.0.13 be released?
 
 My next try is to upgrade our app from Tobago 1.0.10 to 1.0.12.
 
 Regards
 Carsten
 
 
  
 
 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-
 
 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, November 28, 2007 7:19 PM
 To: MyFaces Discussion
 Subject: Re: [Tobago] Problems with IE6
 
 Hello Carsten,
 
 I think the size of the submit should not be a problem.
 The IE includes the content of the button.
 
 The javascript in the submit should not be a problem.
 But the javacript content should not included i will fix this.
 
 See:
 
 https://issues.apache.org/jira/browse/TOBAGO-559
 
 Can you send a test page for your problem, please.
 
 Can you update to a more recent version of tobago?
 
 Regards
 
 Bernd
 
 [EMAIL PROTECTED] schrieb:
 Hello Bernd,

 we have testet it with the Tobago demo app on our server and the demo
 app works.

 It seems that we have a problem with the post bodies in our tobago
 app.
 In Firefox (here our app works) the size is 973 bytes and in IE6 (here
 our app doesn't work) the size is 1320 bytes

 Buffer Firefox: 


 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+fl
 ight+schedules.+OAL+flight+and+booking%0D%0A++confirmati
 on+is+required+before+shipment+is+reconfirmed+to+the+LCAG+customer.page
 %3AsprDlg%3A_idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPo
 sition=page%3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-client
 Dimension=1280%3B864HTTP/1.1 200 OK

 Buffer IE:


 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3Aclearbutton=C%3CU%3El%3C%2FU%3Eear%0D%0A%3CSCRIPT+t
 ype%3Dtext%2Fjavascript%3E%0A%3C%21--%0Anew+Tobago.ScriptLoader%28%0A+++
 +%5B%5D%2C+%0A++%22new+Tobago.AcceleratorKey%28function%28%29+%7
 BTobago.clickOnElement%28%27page%3AsprDlg%3Aclearbutton%27%29%3B%7D%2C+%
 5C%22l%5C%22%29%3B%22%0A%29%3B%0A%2F%2F+--%3E%0A%3C%2FSCRIPT%3Epage%3As
 prDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+flight+schedule
 s.+OAL+flight+and+booking%0D%0A++confirmation+is+require
 d+before+shipment+is+reconfirmed+to+the+LCAG+customer.page%3AsprDlg%3A_
 idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPosition=page%
 3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-clientDimension=127
 6%3B896HTTP/1.1 200 OK

 Is this correct or is ther a problem in our application with the post
 buffer? Is it correct to have JavaScript in the post buffer?

 Regards,
 Carsten



  

 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-

 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, November 27, 2007 6:28 PM
 To: MyFaces Discussion
 Subject: Re: [Tobago] Problems with IE6

 Hello Carsten,

 can you test it with the tobago example demo?

 Regards

 Bernd

 [EMAIL PROTECTED] schrieb:
 Hi,

 we have Problems with a Tobago-Application (Tobago Version 1.0.10)
 under
 Internet Explorer 6 SP 2. When the Application submits form data via
 post a Page not found error occurs. The destination page is the
 page
 with the form itself, so the submit should be a simple reload. Under
 Firefox everything works fine. Does anyone else have these problems
 too?
 Best regards,
 Carsten Manshusen
  

 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd

Re: [Tobago] Problems with IE6

2007-11-29 Thread Bernd Bohmann
Hello Carsten,

i don't think the javascript cause the error. But you can try the fix
with the nightly build.

http://people.apache.org/builds/myfaces/nightly/

Regards

Bernd

[EMAIL PROTECTED] schrieb:
 Hello Bernd,
 
 I've updated our app to Tobago version 1.0.12 and the Page cannot be
 loaded error in IE6 still occurs.  Can you tell me, when version 1.0.13
 with the JavaScript fix will be released? As an attachement you'll find
 our main JSF-Application-File.
 
 Regards,
 Carsten
 
 
  
 
 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-
 
 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, November 28, 2007 7:19 PM
 To: MyFaces Discussion
 Subject: Re: [Tobago] Problems with IE6
 
 Hello Carsten,
 
 I think the size of the submit should not be a problem.
 The IE includes the content of the button.
 
 The javascript in the submit should not be a problem.
 But the javacript content should not included i will fix this.
 
 See:
 
 https://issues.apache.org/jira/browse/TOBAGO-559
 
 Can you send a test page for your problem, please.
 
 Can you update to a more recent version of tobago?
 
 Regards
 
 Bernd
 
 [EMAIL PROTECTED] schrieb:
 Hello Bernd,

 we have testet it with the Tobago demo app on our server and the demo
 app works.

 It seems that we have a problem with the post bodies in our tobago
 app.
 In Firefox (here our app works) the size is 973 bytes and in IE6 (here
 our app doesn't work) the size is 1320 bytes

 Buffer Firefox: 


 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+fl
 ight+schedules.+OAL+flight+and+booking%0D%0A++confirmati
 on+is+required+before+shipment+is+reconfirmed+to+the+LCAG+customer.page
 %3AsprDlg%3A_idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPo
 sition=page%3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-client
 Dimension=1280%3B864HTTP/1.1 200 OK

 Buffer IE:


 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3Aclearbutton=C%3CU%3El%3C%2FU%3Eear%0D%0A%3CSCRIPT+t
 ype%3Dtext%2Fjavascript%3E%0A%3C%21--%0Anew+Tobago.ScriptLoader%28%0A+++
 +%5B%5D%2C+%0A++%22new+Tobago.AcceleratorKey%28function%28%29+%7
 BTobago.clickOnElement%28%27page%3AsprDlg%3Aclearbutton%27%29%3B%7D%2C+%
 5C%22l%5C%22%29%3B%22%0A%29%3B%0A%2F%2F+--%3E%0A%3C%2FSCRIPT%3Epage%3As
 prDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+flight+schedule
 s.+OAL+flight+and+booking%0D%0A++confirmation+is+require
 d+before+shipment+is+reconfirmed+to+the+LCAG+customer.page%3AsprDlg%3A_
 idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPosition=page%
 3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-clientDimension=127
 6%3B896HTTP/1.1 200 OK

 Is this correct or is ther a problem in our application with the post
 buffer? Is it correct to have JavaScript in the post buffer?

 Regards,
 Carsten



  

 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-

 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, November 27, 2007 6:28 PM
 To: MyFaces Discussion
 Subject: Re: [Tobago] Problems with IE6

 Hello Carsten,

 can you test it with the tobago example demo?

 Regards

 Bernd

 [EMAIL PROTECTED] schrieb:
 Hi,

 we have Problems with a Tobago-Application (Tobago Version 1.0.10)
 under
 Internet Explorer 6 SP 2. When the Application submits form data via
 post a Page not found error occurs. The destination page is the
 page
 with the form itself, so the submit should be a simple reload. Under
 Firefox everything works fine. Does anyone else have

Re: [Tobago] Problems with IE6

2007-11-28 Thread Bernd Bohmann
Hello Carsten,

I think the size of the submit should not be a problem.
The IE includes the content of the button.

The javascript in the submit should not be a problem.
But the javacript content should not included i will fix this.

See:

https://issues.apache.org/jira/browse/TOBAGO-559

Can you send a test page for your problem, please.

Can you update to a more recent version of tobago?

Regards

Bernd

[EMAIL PROTECTED] schrieb:
 Hello Bernd,
 
 we have testet it with the Tobago demo app on our server and the demo
 app works.
 
 It seems that we have a problem with the post bodies in our tobago app.
 In Firefox (here our app works) the size is 973 bytes and in IE6 (here
 our app doesn't work) the size is 1320 bytes
 
 Buffer Firefox: 
 
 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+fl
 ight+schedules.+OAL+flight+and+booking%0D%0A++confirmati
 on+is+required+before+shipment+is+reconfirmed+to+the+LCAG+customer.page
 %3AsprDlg%3A_idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPo
 sition=page%3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-client
 Dimension=1280%3B864HTTP/1.1 200 OK
 
 Buffer IE:
 
 page%3A%3Aform-action=page%3AsprDlg%3Aclearbuttonpage%3AsprDlg%3Acarrie
 r1=page%3AsprDlg%3Aorig1=page%3AsprDlg%3Adest1=page%3AsprDlg%3Acarrie
 r2=page%3AsprDlg%3Aorig2=page%3AsprDlg%3Adest2=page%3AsprDlg%3Acarrie
 r3=page%3AsprDlg%3Aorig3=page%3AsprDlg%3Adest3=page%3AsprDlg%3Acarrie
 r4=page%3AsprDlg%3Aorig4=page%3AsprDlg%3Adest4=page%3AsprDlg%3Aprod_c
 ode=page%3AsprDlg%3Aissuer=1page%3AsprDlg%3Aoalissuer=page%3AsprDlg%3
 Achrgwgt=0.0page%3AsprDlg%3Achrgcode=1page%3AsprDlg%3Aissuedate=28.11.
 2007page%3AsprDlg%3Acurrency=EURpage%3AsprDlg%3Aissuedate_pickerDimens
 ion=page%3AsprDlg%3Aclearbutton=C%3CU%3El%3C%2FU%3Eear%0D%0A%3CSCRIPT+t
 ype%3Dtext%2Fjavascript%3E%0A%3C%21--%0Anew+Tobago.ScriptLoader%28%0A+++
 +%5B%5D%2C+%0A++%22new+Tobago.AcceleratorKey%28function%28%29+%7
 BTobago.clickOnElement%28%27page%3AsprDlg%3Aclearbutton%27%29%3B%7D%2C+%
 5C%22l%5C%22%29%3B%22%0A%29%3B%0A%2F%2F+--%3E%0A%3C%2FSCRIPT%3Epage%3As
 prDlg%3A_idJsp64=Attention%3A+This+tool+has+no+access+to+flight+schedule
 s.+OAL+flight+and+booking%0D%0A++confirmation+is+require
 d+before+shipment+is+reconfirmed+to+the+LCAG+customer.page%3AsprDlg%3A_
 idJsp73%3A%3Awidths=page%3AsprDlg%3A_idJsp73%3A%3AscrollPosition=page%
 3AsprDlg%3A_idJsp73%3A%3Aselected=%2Cpage%3A%3Aform-clientDimension=127
 6%3B896HTTP/1.1 200 OK
 
 Is this correct or is ther a problem in our application with the post
 buffer? Is it correct to have JavaScript in the post buffer?
 
 Regards,
 Carsten
 
 
 
  
 
 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 -Original Message-
 
 From: Bernd Bohmann [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, November 27, 2007 6:28 PM
 To: MyFaces Discussion
 Subject: Re: [Tobago] Problems with IE6
 
 Hello Carsten,
 
 can you test it with the tobago example demo?
 
 Regards
 
 Bernd
 
 [EMAIL PROTECTED] schrieb:
 Hi,

 we have Problems with a Tobago-Application (Tobago Version 1.0.10)
 under
 Internet Explorer 6 SP 2. When the Application submits form data via
 post a Page not found error occurs. The destination page is the page
 with the form itself, so the submit should be a simple reload. Under
 Firefox everything works fine. Does anyone else have these problems
 too?
 Best regards,
 Carsten Manshusen
  

 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel

 


Re: [Tobago] Problems with IE6

2007-11-27 Thread Bernd Bohmann
Hello Carsten,

can you test it with the tobago example demo?

Regards

Bernd

[EMAIL PROTECTED] schrieb:
 Hi,
 
 we have Problems with a Tobago-Application (Tobago Version 1.0.10) under
 Internet Explorer 6 SP 2. When the Application submits form data via
 post a Page not found error occurs. The destination page is the page
 with the form itself, so the submit should be a simple reload. Under
 Firefox everything works fine. Does anyone else have these problems too?
 
 Best regards,
 Carsten Manshusen
  
 
 Sitz der Gesellschaft / Corporate Headquarters:
 Lufthansa Systems AS GmbH, Norderstedt
 Registereintragung / Registration:
 Amtsgericht Norderstedt 3688NO
  
 Geschaeftsfuehrung/ Management:
 Bernd Appel
 


Re: Tobago: Validationproblem

2007-11-18 Thread Bernd Bohmann
Hello Mario,

if you get a 'Value is not a valid option' Validation Error I know two
reasons.

1. The default TimeZone for DateConverter is GMT.

2. The UISelectOne Component validate the converted Value with the list
of SelectItems values. The values of the SelectItems should be a Date.

Just added a SelectOneChoice date example to tobago-example-test

http://svn.apache.org/repos/asf/myfaces/tobago/trunk/example/test/src/main/webapp/selectOneChoice.jsp

http://svn.apache.org/viewvc?rev=596080view=rev

Regards


Bernd



Schröder schrieb:
 Hi everybody,
 
  
 
 I'm having a tc:selectOnceChoce-component that contains a list of years as 
 string. I'd like to set a select year in the bean as a Date-Object by using a 
 converter. The converter runs without an error but the Tobago-Framework 
 throws a ValidationException. 
 
 In the log I find this message: 2007-11-16 15:10:17 ERROR - 
 org.apache.myfaces.tobago.context.ResourceManagerImpl:292 - Path not found, 
 and no fallback. Using empty string.
 
  
 
 I tried to fix the problem with my own Validator, but I still get the same 
 Problem. When I use a string instead of a date in the bean it works. But I 
 don't want a String since this will cause problems somewhere else. 
 
 What can I do? Who can help me?
 
  
 
 Partial source code:
 
  
 
 ...
 
 tc:selectOneChoice value=#{controller.currentMedia.yearOfPubl} id=year
 
   disabled=#{not controller.editor} 
 
 f:converter converterId=books.YearListConverter /
 
 f:selectItems value=#{controller.yearList} /
 
 /tc:selectOneChoice
 
  
 
  
 
 This is the bean with the date:
 
 ...
 
 @Entity
 
 public class Book extends Hardware {
 
 private static final long serialVersionUID = 
 -176678560262298L;
 
  
 
 private URL url;
 
 private Date yaerOfPubl;
 
  
 
 /** Creates a new instance of Book */
 
 public Book() {
 
 super();
 
 }
 
  
 
 public URL getUrl() {
 
 return url;
 
 }
 
  
 
 public void setUrl(URL url) {
 
 this.url = url;
 
 }
 
  
 
 @Temporal(value = TemporalType.DATE)
 
 public Date getYearOfPubl() {
 
 return yaerOfPubl;
 
 }
 
  
 
 public void setYearOfPubl(Date yearOfPubl) {
 
 this.yaerOfPubl = yearOfPubl;
 
 }
 
 }
 
 ...
 
  
 
  
 
 Regards,
 
 Mario
 
 
 
  
 
 


Re: [Tobago] Thousands of warnings/errors with current 1.0.13 snapshot

2007-11-06 Thread Bernd Bohmann
Hello Helmut,

should be fixed now, thanks.

Regards

Bernd

Helmut Swaczinna schrieb:
 Hi,
 
 after upgrading to current 1.0.13 snapshot I get thousands of messages
 in the log like these:
 
 11-06 11:22:48,890 ERROR GENA-WAPP [http-8080-Processor19]
 ResourceManagerImpl Don't find any RendererClass for ColumnRenderer.
 Please check you c
 onfiguration.
 11-06 11:22:48,906 WARN  GENA-WAPP [http-8080-Processor19]
 HtmlRenderKitImpl Unsupported component-family/renderer-type:
 javax.faces.Column/Column
 
 11-06 11:22:48,906 ERROR GENA-WAPP [http-8080-Processor19]
 TobagoRenderKit The class which was found by the ResourceManager cannot
 be found or ins
 tantiated: classname='Column'
 11-06 11:22:48,906 INFO  GENA-WAPP [http-8080-Processor19] [/gena]
 No Renderer found for component {Component-Path : [Class:
 org.apache.myfaces.to
 bago.component.UIViewRoot,ViewId: /overview.jsp][Class:
 org.apache.myfaces.tobago.component.UIPage,Id: overviewPage][Class:
 org.apache.myfaces.tobago.
 component.UIPanel,Id: panel][Class:
 org.apache.myfaces.tobago.component.UIPanel,Id: mainPanel][Class:
 org.apache.myfaces.tobago.component.UICell,Id: _
 idJsp140][Class: javax.faces.component.UINamingContainer,Id:
 resultView][Class: org.apache.myfaces.tobago.component.UIPanel,Id:
 panel][Class: org.apac
 he.myfaces.tobago.component.UIData,Id: resultSheet][Class:
 org.apache.myfaces.tobago.component.UIColumn,Id:
 prodisProjektnummerColumn]} (component-fam
 ily=javax.faces.Column, renderer-type=Column)
 11-06 11:22:48,906 WARN  GENA-WAPP [http-8080-Processor19]
 UIComponentBase No Renderer found for component {Component-Path :
 [Class: org.apache.my
 faces.tobago.component.UIViewRoot,ViewId: /overview.jsp][Class:
 org.apache.myfaces.tobago.component.UIPage,Id: overviewPage][Class:
 org.apache.myfaces
 .tobago.component.UIPanel,Id: panel][Class:
 org.apache.myfaces.tobago.component.UIPanel,Id: mainPanel][Class:
 org.apache.myfaces.tobago.component.UICe
 ll,Id: _idJsp140][Class: javax.faces.component.UINamingContainer,Id:
 resultView][Class: org.apache.myfaces.tobago.component.UIPanel,Id:
 panel][Class:
 org.apache.myfaces.tobago.component.UIData,Id: resultSheet][Class:
 org.apache.myfaces.tobago.component.UIColumn,Id:
 prodisProjektnummerColumn]} (compo
 nent-family=javax.faces.Column, renderer-type=Column)
 
 
 Before, I had none these messages.
 
 Regards
 Helmut
 


Re: [tobago] Tag vs. component with facelets

2007-10-06 Thread Bernd Bohmann
= categoriesTree

  value =#{contractCtrl.categoriesRoot}

  state =#{contractCtrl.treeState}

  showIcons =true

  mutable =true

  nameReference =userObject.embedded.namehttp://userobject.embedded.name/
 

   f:actionListener type =
fr.into.services.controller.CategoryEditionListener /

   f:facet name =treeNodeCommand 

 tc:command actionListener =#{contractCtrl.selectCategory}

   c:if test =#{not empty ajaxScope} 

 tc:attribute

 name =renderedPartially

 value =#{ajaxScope} /



  / c:if

/ tc:command

  / f:facet



/ tc:tree




2007/10/4, Bernd Bohmann [EMAIL PROTECTED]:

Hello Zied,

maybe two Commands with the rendered attribute would be a better choice.

Regards

Bernd



Zied Hamdi wrote:

Hi,

I have a little problem with runtime vs build-time tags:

I have a component page categories.xhtml containing the snippet:

  c:if test=#{not empty ajaxScope}

tc:attribute

 name=renderedPartially

 value=#{ajaxScope} /

  /c:if




included by a page as follows:

 ui:include

src=/contract/categories.xhtml

   ui:param

 name=ajaxScope

 value=:page:mainInfoTabPanel

/

 /ui:include



The c:if evaluates correctly at build time and adds the attribute to

its

parent. But it seems tc:attribute evaluates at runtime: it finds null.
Having two varibales one runtime and one build time with the same

value is a

little barbar.

Anyone knows how to resolve this? Any idea is welcome.

Regards,
Zied




--
Zied Hamdi
zatreex.sourceforge.net







Re: [Tobago] tc:message tag does not work with IE

2007-10-05 Thread Bernd Bohmann

Hello Helmut,

please add a jira issue. I will provide a fix, soon.

Regards

Bernd

Helmut Swaczinna wrote:

Hi,

I encoutered some problems with the tc:messages tag with the IE. First, 
there's a layout problem, so
the message can not be seen, and second, the message is rendered twice. 
With Firefox everything is ok.


Here's the JSP code:

f:view
 tc:page id=inputPage width=200px height=200px
   tc:panel id=inputPanel
 f:facet name=layout
   tc:gridLayout
 rows=fixed;fixed;fixed;*/
 /f:facet
 tc:selectOneChoice id=in
   required=true
   value=#{controller.value}
   tc:selectItem itemLabel= itemValue=/
   tc:selectItem itemLabel=xx itemValue=xx/
 /tc:selectOneChoice
 tc:message for=in/
 tc:button label=submit/
 tc:cell/
   /tc:panel
 /tc:page
/f:view

This is the generated HTML code for IE:
...
select name=inputPage:in id=inputPage:in style=width:200px; 
height:21px;  class=tobago-selectOneChoice-default 
tobago-selectOneChoice-error tobago-selectOneChoice-required 
title=Eine Auswahl wird benötigt!

option value=
/optionoption value=xx
xx/option/select/div/td/trtr
td class=tobago-gridLayout-cell-td style=width: 200px; height: 6px;
div class=tobago-gridLayout-default tobago-gridLayout-first-column 
style=width: 200px; height: 6px;

span class=tobago-validation-message style=width:200px; height:1px; 
label for=inputPage:in title=Eine Auswahl wird benötigt!
Eine Auswahl wird benötigt!Eine Auswahl wird benötigt!/label

...

You can see, that the height of the message is 1px and the message text 
is duplicted.


This is the generated HTML code for Firefox:
...
select name=inputPage:in id=inputPage:in style=width:200px; 
height:18px;  class=tobago-selectOneChoice-default 
tobago-selectOneChoice-error tobago-selectOneChoice-required 
title=Eine Auswahl wird benötigt!

option value=
/optionoption value=xx
xx/option/select/div/td/trtr
td class=tobago-gridLayout-cell-td style=width: 200px; height: 25px;
div class=tobago-gridLayout-default tobago-gridLayout-first-column 
style=width: 200px; height: 25px;
span class=tobago-validation-message style=width:200px; 
height:20px; 

label for=inputPage:in title=Eine Auswahl wird benötigt!
Eine Auswahl wird benötigt!/label

...


Regards,
   Helmut



Re: still the same exception

2007-10-04 Thread Bernd Bohmann

Hello Zied,

can you send the page, please.

Regards

Bernd

Zied Hamdi wrote:

Hi,

The action doesn't execute, it's normal I didn't specify the action as an EL
(shame on me), but I still have the exception.

Regards,
Zied

2007/10/3, Zied Hamdi [EMAIL PROTECTED]:

Hi,

I still have the same (assertion) exception but this time my link doesn't
work, and I can't go out of it :-(.

The code seems unable to find the component by its id even if I can see it
in the view tree...

The code that produces it works elsewhere, here no action and no action
listener is called :
(otherwise there's a minor visual bug in the richmond style: when a row is
selected, its color is the same as links so no text is visible anymore)

 tc:sheet

  xmlns= http://www.w3.org/1999/xhtml;

  xmlns:jsp= http://java.sun.com/JSP/Page;

  xmlns:tc= http://myfaces.apache.org/tobago/component;

  xmlns:tx= http://myfaces.apache.org/tobago/extension;

  xmlns:ui= http://java.sun.com/jsf/facelets;

  xmlns:h= http://java.sun.com/jsf/html;

  xmlns:f= http://java.sun.com/jsf/core;

  id= workTaskTable

  columns =*;*

  value =#{contractCtrl.planning}

  var =intervention 



   tc:column

 tc:link

  id =workTaskDetailLink

  image =image/edit. PNG

  action =contractCtrl.editTaskCmd

  actionListener =contractCtrl.editTaskLsnr /

  / tc:column



   tc:column label =|Categorie 

 tc:link

  id =category

  label =#{intervention.category.name}

  action =contract /

  / tc:column



   tc:column label =#{i18n.intervenant} 

 tc:link

  id =intervenant

  label =#{intervention.intervenant.firstName} #{
intervention.intervenant.lastName}

  action =contract /

  / tc:column



   tc:column label =#{i18n.workStartDate} 

 tx:date

  id =workStartDate

  value =#{intervention.workStart}

  labelWidth =0px 

   f:convertDateTime pattern =dd.MM. /

/ tx:date

  / tc:column



   tc:column label =#{i18n.workStartTime} 

 tc:time

  id =workStart

  value =#{intervention.workStart} /

  / tc:column



   tc:column label =#{i18n.workEndTime} 

 tc:time

  id =workEnd

  value =#{intervention.workEnd} /

  / tc:column



   tc:column label =#{i18n.workEndDate} 

 tx:date

  id =workEndDate

  value =#{intervention.workEnd}

  labelWidth =0px 

   f:convertDateTime pattern =dd.MM. /

/ tx:date

  / tc:column



   tc:column label =#{i18n.note} 

 tc:in value =#{intervention.note} /

  / tc:column

/ tc:sheet




18:23:05,453 INFO  [STDOUT] 2007-10-03 18:23:05,437 [http-127.0.0.1-8080-2]
DEBUG org.apache.myfaces.tobago.component.UIPage.markSubmittedForm (156) -
actionId = 'page:taskTableSubview:workTaskTable:0:workTaskDetailLink'

18:23:05,468 INFO  [STDOUT] 2007-10-03 18:23:05,468 [http-127.0.0.1-8080-2]
INFO  org.apache.myfaces.tobago.component.UIPage.markSubmittedForm(176) -
command = [EMAIL PROTECTED] 

*java.lang.Exception*

  at org.apache.myfaces.tobago.component.UIPage.markSubmittedForm (*
UIPage.java:176*)

  at org.apache.myfaces.tobago.component.UIPage.processDecodes (*
UIPage.java:138*)

  at javax.faces.component.UIComponentBase.processDecodes (*
UIComponentBase.java:1001*)

  at javax.faces.component.UIViewRoot.processDecodes (*UIViewRoot.java
:493*)

  at org.apache.myfaces.tobago.component.UIViewRoot.processDecodes (*
UIViewRoot.java:183*)

  at
org.apache.myfaces.tobago.lifecycle.ApplyRequestValuesExecutor.execute(*
ApplyRequestValuesExecutor.java :78*)

  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:244* )

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
*ApplicationFilterChain.java :290*)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
ApplicationFilterChain.java:206*)

  at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter (*
ExtensionsFilter.java:147*)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
*ApplicationFilterChain.java:235*)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter (*
ApplicationFilterChain.java:206*)

  at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter (*
ReplyHeaderFilter.java:96*)

  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(

Re: [tobago] Tag vs. component with facelets

2007-10-04 Thread Bernd Bohmann

Hello Zied,

maybe two Commands with the rendered attribute would be a better choice.

Regards

Bernd



Zied Hamdi wrote:

Hi,

I have a little problem with runtime vs build-time tags:

I have a component page categories.xhtml containing the snippet:

  c:if test=#{not empty ajaxScope}

tc:attribute

 name=renderedPartially

 value=#{ajaxScope} /

  /c:if




included by a page as follows:

 ui:include src=/contract/categories.xhtml

   ui:param

 name=ajaxScope

 value=:page:mainInfoTabPanel /

 /ui:include



The c:if evaluates correctly at build time and adds the attribute to its
parent. But it seems tc:attribute evaluates at runtime: it finds null.

Having two varibales one runtime and one build time with the same value is a
little barbar.

Anyone knows how to resolve this? Any idea is welcome.

Regards,
Zied



Re: renderedPartially is a great function, it could have more framework support

2007-10-04 Thread Bernd Bohmann

Hello Zied,

please add jira issues for your requests.

Regards

Bernd

Zied Hamdi wrote:

Hi,

I decided to focus on all my renderedPartially my attributes to make them
work. And I understood they doesn't work with tc:cell, tc:tab, tc:tabgroup
and maybe others. In addition, when pointed to tc:tab, tc:tabgroup
javascript errors are generated and doesn't let the job done.

I think a sort of tree view building-time compiler could be of good help
to community saying: component with id:xx of type xx can't be rendered
partially.

Otherwise, a very minor bug when the renderedPartially value is null (I
think this business case is similar to an empty string value rather than an
unallowed value):
java.lang.NullPointerException
at
org.apache.myfaces.tobago.renderkit.html.CommandRendererHelper.initOnclick(
CommandRendererHelper.java:100)
at org.apache.myfaces.tobago.renderkit.html.CommandRendererHelper.init(
CommandRendererHelper.java:61)
at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TreeOldRenderer.getTreeNodeCommandVar
(TreeOldRenderer.java:292)
at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TreeOldRenderer.createJavascript
(TreeOldRenderer.java:251)
this happens on templating such as:

tc:attribute

 name=renderedPartially

 value=#{ajaxScope} /


Regards,
Zied



Re: [TOBAGO] defaultCommand does not work with renderedPartially

2007-10-04 Thread Bernd Bohmann

Hello Stojan,

i think defaultCommand and renderedPartially didn't work together.
(Maybe Volker knows some javascript hack)

If you need this feature you can add a jira issue.

Regards

Bernd

Stojan Peshov wrote:

Hi all,

I have button that does some search and reloads the panel for results

tc:button id=submit
label=#{someBundle.search}
action=#{searchTermSimple.search}
tc:attribute name=renderedPartially
value=termSimpleSearchPanel /
/tc:button

if I add defaultCommand=true partial rendering does not work anymore :(
Any solution, please?

Thanks,
Stojan



Re: [tobago] tx:date displays incorrectly in sheets

2007-09-22 Thread Bernd Bohmann

Hello Zied,

please try 10px for labelWidth instead of 10.

Regards

Bernd

Zied Hamdi wrote:

Hi,

Under facelets, I have an editable sheet in which I wanted to include dates;
there are two disfunctions:

   - The date button doesn't display
   - the sheet line becomes two lines high (but increasing the width
   doesn't display any wrapped elements)

Here's my code:


tc:sheet

  xmlns=http://www.w3.org/1999/xhtml;

  xmlns:jsp=http://java.sun.com/JSP/Page;

  xmlns:tc=http://myfaces.apache.org/tobago/component;

  xmlns:tx=http://myfaces.apache.org/tobago/extension;

  xmlns:ui=http://java.sun.com/jsf/facelets;

  xmlns:h=http://java.sun.com/jsf/html;

  xmlns:f=http://java.sun.com/jsf/core;

  columns=*;*

  value=#{contractCtrl.planning}

  var=intervention



  tc:column

tc:link

  id=workTaskDetailLink

  image=image/edit.PNG

  tc:attribute

name=renderedPartially

value=editContractForm /

  f:facet name=popup

tc:popup

 id=editContractForm

 height=200px

 width=200px

 tc:box label=test/tc:box

/tc:popup

  /f:facet

/tc:link

  /tc:column



  tc:column label=|Categorie

tc:link

  id=category

  label=#{intervention.category.name}

  action=contract /

  /tc:column



  tc:column label=#{i18n.intervenant}

tc:link

  id=intervenant

  label=#{intervention.intervenant.firstName} #{
intervention.intervenant.lastName}

  action=contract /

  /tc:column



  tc:column label=#{i18n.workStartDate}

tx:date

  id=workStartDate

  value=#{intervention.workStart}

  labelWidth=10

  f:convertDateTime pattern=dd.MM. /

/tx:date

  /tc:column



  tc:column label=#{i18n.workStartTime}

tc:time

  id=workStart

  value=#{intervention.workStart} /

  /tc:column



  tc:column label=#{i18n.workEndTime}

tc:time

  id=workEnd

  value=#{intervention.workEnd} /

  /tc:column



  tc:column label=#{i18n.workEndDate}

tx:date

  id=workEndDate

  value=#{intervention.workEnd}

  labelWidth=10

  f:convertDateTime pattern=dd.MM. /

/tx:date

  /tc:column



  tc:column label=#{note}

tc:in value=#{intervention.note} /

  /tc:column

/tc:sheet


Regards,
Zied



Re: [Tobago] Target-attribute not working on javascript-submit

2007-09-08 Thread Bernd Bohmann

Hello Adam,

Tobago.submitAction has following signature

 Tobago.submitAction(actionId, transition, target)

But you may try the action facet of page.

In the current snapshot the target and transition attribute are 
supported, too.


tc:page
  f:facet name=action
   tc:link action=.. target=.. /
  /f:facet

you can also try the tc:object tag instead of using a iframe in the 
current snapshot.


Regards

Bernd




[EMAIL PROTECTED] wrote:

Hi,

i have a problem with the target-attribute of the tc:link or 
tc:button-Tag.


tc:page id=page width=800px height=600px label=Print
...
tc:link label=Show it id=sendStream action
=#{streamingBean.doStream} target=myiframe /
...
f:verbatim
iframe id=pdfiframe name=myiframe width=100% height=100% 
frameborder=0/iframe

/f:verbatim
...

When i click on the link then it works fine and the content is displayed 
in the Iframe. 



But when i submit the action by javascript then the content is displayed 
in the main window (like target=_self).

...
tc:script onload=Tobago.submitAction('page:sendStream')/tc:script
...

What's the problem? Is it a bug?



kind regards

Adam A. Henne


Re: [tobago] error not verbose enough

2007-09-06 Thread Bernd Bohmann

Hello Zied,

ok, i will check the sources. but i'm not sure this happend until 
tomorrow.


We should go back to the user list :-)

Regards

Bernd

Zied Hamdi wrote:
 Hello Bernd,

 Yes I did in all implied files. I resent you the modified files so 
you can

 see the result directly.

 Regards,
 Zied

 2007/9/6, Bernd Bohmann [EMAIL PROTECTED]:
 Hello,

 have you removed the doctype declaration?

 Bernd

 Zied Hamdi wrote:
 Hello,

 I'll have to go out from hour 16 again, so I won't be able to 
answer you

 immediately. Did you reproduce the problem with the non verbose
 exception
 (you must have entries in the Client table, you can do that by pressing
 the
 + button in the persons table box, then pressing 'sauvegarder' after
 entering first and last name, in the welcome page you'll see the 
person,

 click on edit and you'll get the exception)? if I can help anyway, just
 let
 me know. I can send you the datasource config file for JBoss 4.2 if
 you'd
 like.

 Your hint on facelets.SKIP_COMMENTS corrected a lot of layout problems
 thanks, there's still one little problem under ie 7 (denoted with red
 arrows): the box surrounder seems to stop in its minimum size (doesn't
 happen with firefox 2.0). And another problem in both ie and firefox
 (the
 purple arrow). I didn't have these problems when I was under jsps. To
 have
 this layout I augmented the page size (in layout.xhtml) to 1200/1100.

 Regards,
 Zied








 2007/9/6, Zied Hamdi [EMAIL PROTECTED]:
 Hello Again Bernd,

 I wasn't at work this morning, I alredy come up and reread your mail
 and I
 see you're talking about ie 5.5, I'm under ie 7 and firefox 2...

 I'll take a look at your links anyway.

 *Please remove the line

 !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
 * *http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd*
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
 **



 2007/9/5, Zied Hamdi [EMAIL PROTECTED]:
 Hello Bernd,

 Thanks a lot for your time and comments. And sorry for the dirty code
 :-), I'm still searching the final schema.

 Regards,
 Zied

 2007/9/5, Bernd Bohmann [EMAIL PROTECTED]:
 Hello Zied,

 after a short look:

 you should set this in the web.xml

   context-param
 param-namefacelets.SKIP_COMMENTS/param-name
 param-valuetrue/param-value
   /context-param

 if you don't set this the comments are UIComponents and would 
confuse

 the layoutmanager.

 Please remove the line

 !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd 

 We are using some workaround for fixing some bugs in ie 5.5 this
 requires the non standards-compliant mode.

 See:

 http://css.maxdesign.com.au/listamatic/about-boxmodel.htm
 http://en.wikipedia.org/wiki/Internet_Explorer_box_model_bug
 http://msdn2.microsoft.com/en-us/library/ms535242.aspx

 Regards

 Bernd

 Zied Hamdi wrote:
 Hi Bernd,

 Seen I have fixed the problem, I had to reproduce the exception 
case

 manually redoing the changes from an older archive. I'm joining two
 cases of
 the app, the second case (20070905-193216 problems with layout.zip)
 has a
 totally different problem : elements seem to have positioning
 problems (as
 you can see in joined screenshots), in case you have an idea of
 where is the
 problem (to take less space I removed the jars).
 Thanks again Bernd,
 Regards

 --
 Zied Hamdi
 zatreex.sourceforge.net


 --
 Zied Hamdi
 zatreex.sourceforge.net








Re: [tobago] error not verbose enough

2007-09-05 Thread Bernd Bohmann

Hello Zied,

can you send the complete web application, please.
(to my personal account)

Regards

Bernd



Zied Hamdi wrote:

 Hi again,

 Here's the page structure (by facelets) if it can help.
Regards,
Zied
 UIViewRoot clientProperties=
[EMAIL PROTECTED] locale=fr_FR
renderKitId=tobago rendered=true transient=false
viewId=/person/person.xhtml
 UIPage actionId=page:personForm:personTableSubview:personData:0:j_id14
height=1243 id=page prependId=true rendered=true submitted=false
transient=false width=1891
 UIForm id=personForm prependId=true rendered=true submitted=true
transient=false  UIPanel id=j_id9 markup=[Ljava.lang.String;@12442a2
rendered=true transient=false layout UIGridLayout columns=1*
id=j_id52 ignoreFree=false rendered=true rows=300px;20px;600px;100px
transient=false/  UIBox id=j_id11 markup=[Ljava.lang.String;@192d7d0
rendered=true transient=false toolBar UIToolBar iconSize=small
id=tableToolBar labelPosition=right orientation=left rendered=true
transient=false  UICommand action=#{personCtrl.newPersonCmd}
actionExpression=#{personCtrl.newPersonCmd} defaultCommand=false
disabled=false id=newPersonCmd immediate=false rendered=true
renderedPartially=[Ljava.lang.String;@196b73e transient=false
transition=true/  UICommand action=#{personCtrl.hideEditWindowCmd}
actionExpression=#{personCtrl.hideEditWindowCmd} defaultCommand=false
disabled=false id=stopEditingCmd immediate=false rendered=true
renderedPartially=[Ljava.lang.String;@1d85ab9 transient=false
transition=true/ /UIToolBar  UIPanel id=personTablePanel markup=[
Ljava.lang.String;@12c4d8f rendered=true transient=false
UINamingContainer
id=personTableSubview rendered=true transient=false  UIPanel
id=j_id12 markup=[Ljava.lang.String;@197f538 rendered=true
transient=false  UIData columns=18px;70px;70px;100px;110px;*;18px
directLinkCount=9 first=0 id=personData rendered=true rowIndex=-1
rows=100 selectable=multi showDirectLinks=none showHeader=true
showPageRange=center showRowRange=right sortActionListener=
transient=false var=currentPerson binding=#{personCtrl.personTable}
pagerPage UICommand defaultCommand=false disabled=false id=ToPage
immediate=false rendered=true
renderedPartially=[Ljava.lang.String;@1646de5
transient=false transition=true/ Next UICommand defaultCommand=false
disabled=true id=Next immediate=false rendered=true
renderedPartially=[Ljava.lang.String;@6b0a6a transient=false
transition=true/ Last UICommand defaultCommand=false disabled=true
id=Last immediate=false rendered=true renderedPartially=[
Ljava.lang.String;@178efd5 transient=false transition=true/ Prev
UICommand
defaultCommand=false disabled=true id=Prev immediate=false
rendered=true renderedPartially=[Ljava.lang.String;@c9b2bc
transient=false transition=true/ First UICommand
defaultCommand=false disabled=true id=First immediate=false
rendered=true renderedPartially=[Ljava.lang.String;@1f58334
transient=false transition=true/ pagerRow UICommand
defaultCommand=false disabled=false id=ToRow immediate=false
rendered=true renderedPartially=[Ljava.lang.String;@1790458
transient=false transition=true/  UIColumn align=center id=j_id13
markup=[Ljava.lang.String;@c5e60 rendered=true sortable=false
transient=false  UILinkCommand action=#{personCtrl.edit}
actionExpression=#{personCtrl.edit} defaultCommand=false
disabled=false id=j_id14 immediate=false
markup=[Ljava.lang.String;@7f1ac
rendered=true renderedPartially=[Ljava.lang.String;@18b91cb
transient=false transition=true/ /UIColumn  UIColumn
id=firstNameCol label=Prénom markup=[Ljava.lang.String;@10b69b
rendered=true sortable=true transient=false sorter UICommand
defaultCommand=false disabled=false id=firstNameCol_sorter
immediate=false rendered=true
renderedPartially=[Ljava.lang.String;@1447c32
transient=false transition=true/  UIOutput createSpan=true
escape=true id=firstName markup=[Ljava.lang.String;@135ea8e
rendered=true transient=false/ /UIColumn  UIColumn id=lastNameCol
label=Nom markup=[Ljava.lang.String;@ba4bb9 rendered=true
sortable=true transient=false sorter UICommand defaultCommand=false
disabled=false id=lastNameCol_sorter immediate=false rendered=true
renderedPartially=[Ljava.lang.String;@c18c31 transient=false
transition=true/  UIOutput createSpan=true escape=true id=lastName
markup=[Ljava.lang.String;@dafcf2 rendered=true transient=false/
/UIColumn  UIColumn align=right id=zipCodeCol label=Code Postal
markup=[Ljava.lang.String;@11486c5 rendered=true sortable=true
transient=false sorter UICommand defaultCommand=false disabled=false
id=zipCodeCol_sorter immediate=false rendered=true
renderedPartially=[Ljava.lang.String;@9c0287 transient=false
transition=true/  UIOutput createSpan=true escape=true id=zipCode
markup=[Ljava.lang.String;@6a21b2 rendered=true transient=false/
/UIColumn  UIColumn id=townCol label=Ville
markup=[Ljava.lang.String;@1ca337c
rendered=true sortable=true transient=false sorter UICommand
defaultCommand=false disabled=false id=townCol_sorter
immediate=false rendered=true

Re: [tobago] error not verbose enough

2007-09-04 Thread Bernd Bohmann

Hello,

can send the page, please.

Regards

Bernd

Zied Hamdi wrote:

Hi the good team,

I'm experiencing a problem while I'm moving to facelets. This is absolutely
normal until the point where I don't know where the problem occurs ;-p.

In fact, I have an existing set of jsp that I attempted to transform to
facelets templates. I had a lot of jsp includes until a deepness of 4. The
probem is that when an exception occurs, there's no info on which page is
beeing processed.

Is there a way to activate a logger that writes which page is beeing
included? (all I have is Invalid tag found: unexpected input while looking
for attr name or '/' at line 3. Surroundings: '!DOCTYPE html PUBLIC
-//W3C/')

Thanks in advance if you have any idea...

This is my exception to give you an idea :-)


16:31:57,593 ERROR [STDERR] 4 sept. 2007 16:31:57
com.sun.facelets.FaceletViewHandler *handleRenderException*

GRAVE: Error Rendering View[/person/person.xhtml]

*java.lang.IllegalArgumentException*: argument type mismatch

  at sun.reflect.NativeMethodAccessorImpl.invoke0(*Native Method*)

  at sun.reflect.NativeMethodAccessorImpl.invoke(*
NativeMethodAccessorImpl.java:39*)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(*
DelegatingMethodAccessorImpl.java:25*)

  at java.lang.reflect.Method.invoke(*Method.java:597*)

  at javax.faces.component.UIComponentBase$AttributesMap.put(*
UIComponentBase.java:1590*)

  at javax.faces.component.UIComponentBase$AttributesMap.put(*
UIComponentBase.java:1499*)

  at
org.apache.myfaces.tobago.renderkit.html.StyleClasses.ensureStyleClasses(*
StyleClasses.java:70*)

  at
org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.createCssClass(*
HtmlRendererUtil.java:119*)

  at
org.apache.myfaces.tobago.renderkit.html.HtmlRendererUtil.prepareRender(*
HtmlRendererUtil.java:94*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.prepareRender
(*DefaultLayoutRenderer.java:40*)

  at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(*
RenderUtil.java:73*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.encodeChildrenOfComponent
(*DefaultLayoutRenderer.java:47*)

  at
org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(*
UILayout.java:71*)

  at org.apache.myfaces.tobago.renderkit.RenderUtil.encodeChildren(*
RenderUtil.java:56*)

  at
org.apache.myfaces.tobago.renderkit.html.speyside.standard.tag.TabGroupRenderer.encodeContent
(*TabGroupRenderer.java:74*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.renderTabGroupView
(*TabGroupRenderer.java:342*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.TabGroupRenderer.encodeEnd
(*TabGroupRenderer.java:155*)

  at javax.faces.component.UIComponentBase.encodeEnd(*
UIComponentBase.java:836*)

  at org.apache.myfaces.tobago.component.UITabGroup.encodeEnd(*
UITabGroup.java:106*)

  at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(*
RenderUtil.java:84*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent
(*GridLayoutRenderer.java:366*)

  at
org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(*
UILayout.java:71*)

  at
org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent(*
UIGridLayout.java:276*)

  at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren(*
UIPanelBase.java:43*)

  at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(*
RenderUtil.java:77*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.GridLayoutRenderer.encodeChildrenOfComponent
(*GridLayoutRenderer.java:366*)

  at
org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(*
UILayout.java:71*)

  at
org.apache.myfaces.tobago.component.UIGridLayout.encodeChildrenOfComponent(*
UIGridLayout.java:276*)

  at org.apache.myfaces.tobago.component.UIPanelBase.encodeChildren(*
UIPanelBase.java:43*)

  at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(*
RenderUtil.java:77*)

  at org.apache.myfaces.tobago.renderkit.RenderUtil.encode(*
RenderUtil.java:81*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.DefaultLayoutRenderer.encodeChildrenOfComponent
(*DefaultLayoutRenderer.java:47*)

  at
org.apache.myfaces.tobago.component.UILayout.encodeChildrenOfComponent(*
UILayout.java:71*)

  at
org.apache.myfaces.tobago.renderkit.html.scarborough.standard.tag.PageRenderer.encodeEnd
(*PageRenderer.java:128*)

  at javax.faces.component.UIComponentBase.encodeEnd(*
UIComponentBase.java:836*)

  at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:896*)

  at javax.faces.component.UIComponent.encodeAll(*UIComponent.java:892*)

  at com.sun.facelets.FaceletViewHandler.renderView(*

Re: [Tobago] More layout problems with 1.0.12

2007-08-23 Thread Bernd Bohmann

Hello Helmut,

should work now.

Thanks

Bernd

Helmut Swaczinna wrote:

Hi,

with the current Tobago 1.0.12 snapshot I've got some new layout 
problems in popups.
With 1.0.11 and older 1.0.12 snapshots the layout is ok. Please have a 
look at the attached
screenshot. The input elements on the popup are cut off at their right 
sides.


This is the jsp code:

tc:page id=inputPage width=500px height=300px
   tc:panel id=inputPanel
 tc:button id=popupButton
   label=Popup
   f:facet name=popup
 tc:popup id=popup width=400 height=220

   tc:box id=box label=Popup
   f:facet name=layout
 tc:gridLayout rows=*;fixed;fixed;fixed;54px;fixed 
columns=*;*;*/

   /f:facet
   tc:cell spanX=3
 tc:out value=Text/
   /tc:cell

   tc:cell spanX=2
 tc:label value=label1/
   /tc:cell
   tc:cell/

   tc:cell spanX=2
 tc:selectOneChoice id=choice
   tc:selectItem itemLabel= itemValue=/
 /tc:selectOneChoice
   /tc:cell
   tc:cell/

   tc:cell spanX=3
 tc:label value=label2/
   /tc:cell
   tc:cell spanX=3
 tc:textarea id=textarea/
   /tc:cell

   tc:cell/
   tc:button id=saveButton
 label=save
 tc:attribute name=popupClose value=afterSubmit/
   /tc:button
   tc:button id=cancelButton
 label=cancel
 tc:attribute name=popupClose value=immediate/
   /tc:button
   /tc:box
 /tc:popup
   /f:facet
 /tc:button
   /tc:panel
 /tc:page

Regards
   Helmut


Re: Charting for Tobago

2007-08-18 Thread Bernd Bohmann

Hello Florian,

maybe you give

http://jsf-comp.sourceforge.net/components/chartcreator/index.html

a try

Regards

Bernd

Florian Reiser wrote:

Hello,

I use Tobago and I enjoy it very much.
Now I want to generate some charts for my application.

Which charting libraries do you use in conjunction with Tobago?
I first thought of Trinidad, but that seems to be impossible.

With kind regards
Florian Reiser


Re: [Tobago] Improvements

2007-08-13 Thread Bernd Bohmann

Hello Helmut,

we just testing your improvements.

Regards

Bernd

Helmut Swaczinna wrote:

Hi Tobago developers,

I've done some improvements to Tobago in the last few days. I created 
jira issues for these with the source
code modifications attached. Please have a look at the source code. I 
would be glad if the improvements

will be included in the svn repository.

Regards
Helmut



Re: [Tobago] How to provide source code modifications?

2007-08-01 Thread Bernd Bohmann

Hello Helmut,

in the attach file dialog is a checkbox for this.

Bernd

Helmut Swaczinna wrote:

Is there somewhere a template for this license grant?

Helmut

- Original Message - From: Bernd Bohmann 
[EMAIL PROTECTED]

To: MyFaces Discussion users@myfaces.apache.org
Sent: Tuesday, July 31, 2007 6:24 PM
Subject: Re: [Tobago] How to provide source code modifications?



Hello Helmut,

you can open a jira issue and attach the svn diff to the issue. With 
the issue we can review and discuss your source code submission. 
Dont't forget to grant license to ASF for inclusion in ASF works.


Regards

Bernd

Helmut Swaczinna wrote:

Hi,

I've made a small extension to the Tobago tag lib and want to provide 
this to the community.
Is there an instruction somewhere how to do this? Should I mail the 
output of svn diff?


The extension is an align attribute for tc:label:

tc:label align=right .../

Regards
Helmut







Re: [Tobago] How to provide source code modifications?

2007-07-31 Thread Bernd Bohmann

Hello Helmut,

you can open a jira issue and attach the svn diff to the issue. With the 
issue we can review and discuss your source code submission. Dont't 
forget to grant license to ASF for inclusion in ASF works.


Regards

Bernd

Helmut Swaczinna wrote:

Hi,

I've made a small extension to the Tobago tag lib and want to provide 
this to the community.
Is there an instruction somewhere how to do this? Should I mail the 
output of svn diff?


The extension is an align attribute for tc:label:

tc:label align=right .../

Regards
Helmut



Re: [tobago] an unexpected block is executed with RI 1.2 (in JBoss 4.2.1 GA) // TODO: remove this if block if prooven this never happens anymore

2007-07-23 Thread Bernd Bohmann

Hello Zied,

the nightly build should posted every night when no compile or test 
failures occurs. Unfortunately the continuum version (1.1-alpha-1) has 
some memory issues :-(


The nightly build from 22-Jul-2007 on 
http://people.apache.org/builds/myfaces/nightly/ should contain the 
sheet fix.


Regards

Bernd

Zied Hamdi wrote:

Thxs Bernd,

I think I'll try to install MF 1.2. I didn't compile code from maven until
now, but as I go through, I realize it's more and more necessairy. Why
aren't the nightly builds posted every night?, does it depend on test
results?

Regards,
Zied


2007/7/22, Bernd Bohmann [EMAIL PROTECTED]:


Hello Zied,

the sheet issue should be fixed on trunk.

Please try the next nightly build.

Regards

Bernd

Zied Hamdi wrote:
 Hi friends,
 I have experienced a problem that seems to come back from rip :-). Seen
 that
 JBoss 4.2 is now based on tomcat 6 and supports EJB3, I've decided to
jump
 my app into it. The problem is that it doesn't rely on myfaces core
 anymore,
 today to support the JSF 1.2 spec, it uses the sun implementation and
says
 it shouldn't expose any problem to use myFaces components with it:
 http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5AndMyFaces

 When I start my app, I have on the first page a visual bug with icons
that
 appear before the sheet (see picture) : this doesn't happen when I use
 myFaces core. Then on my first click I have the following exception
stack
 trace. Looking at the source I found that the code shouldn't enter this
 section:

// *TODO*: remove this if block if prooven this never happens 
anymore


*if* (command == *null*

 currentActionId != *null* 
 currentActionId.matches(.*:\\d+:.*))
 {

  // If currentActionId component was inside a sheet the id contains
the

  // rowindex and is therefore not found here.

  // We do not need the row here because we want just to find the

  // related form, so removing the rowindex will help here.

  currentActionId = currentActionId.replaceAll(:\\d+:, :);

  *try* {

command = findComponent(currentActionId);

*LOG*.*info*(command = \ + command + \, *new* 
Exception());


  } *catch* (Exception e) {

// ignore

  }



 11:14:24,229 INFO  [STDOUT] 2007-07-20 11:14:24,229 [
http-127.0.0.1-8080-2]
 ERROR
 org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(348)
 - Don't find any RendererClass for org.apache.myfaces.ScheduleRenderer.
 Please check you configuration.

 11:14:24,244 INFO  [STDOUT] 2007-07-20 11:14:24,244 [
http-127.0.0.1-8080-2]
 INFO  
org.apache.myfaces.tobago.util.DebugPhaseListener.afterPhase(65) -

 Total response time : 5936 milliseconds

 11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter 


(204)

 - No context init parameter 'org.apache.myfaces.PRETTY_HTML' found,
using
 default value true

 11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter 


(204)

 - No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' 
found,

 using default value true

 11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter 


(204)

 - No context init parameter '
org.apache.myfaces.READONLY_AS_DISABLED_FOR_SE
 LECTS' found, using default value true

 11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter 


(204)

 - No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT'
found,
 using default value false

 11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter 


(204)

 - No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found,
using
 default value false

 11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter 


(229)

 - No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS'
found,
 using default value
 org.apache.myfaces.renderkit.html.util.DefaultAddResource

 11:14:24,276 INFO  [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter 


(229)

 - No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH'
 found, using default value /faces/myFacesExtensionResource

 11:14:24,276 INFO  [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
 INFO

org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter 


(204)

 - No context init parameter 
'org.apache.myfaces.CHECK_EXTENSIONS_FILTER'

 found, using default

Re: [tobago] an unexpected block is executed with RI 1.2 (in JBoss 4.2.1 GA) // TODO: remove this if block if prooven this never happens anymore

2007-07-22 Thread Bernd Bohmann

Hello Zied,

the sheet issue should be fixed on trunk.

Please try the next nightly build.

Regards

Bernd

Zied Hamdi wrote:

Hi friends,
I have experienced a problem that seems to come back from rip :-). Seen 
that

JBoss 4.2 is now based on tomcat 6 and supports EJB3, I've decided to jump
my app into it. The problem is that it doesn't rely on myfaces core 
anymore,

today to support the JSF 1.2 spec, it uses the sun implementation and says
it shouldn't expose any problem to use myFaces components with it:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5AndMyFaces

When I start my app, I have on the first page a visual bug with icons that
appear before the sheet (see picture) : this doesn't happen when I use
myFaces core. Then on my first click I have the following exception stack
trace. Looking at the source I found that the code shouldn't enter this
section:

   // *TODO*: remove this if block if prooven this never happens anymore

   *if* (command == *null*

currentActionId != *null*  
currentActionId.matches(.*:\\d+:.*))

{

 // If currentActionId component was inside a sheet the id contains the

 // rowindex and is therefore not found here.

 // We do not need the row here because we want just to find the

 // related form, so removing the rowindex will help here.

 currentActionId = currentActionId.replaceAll(:\\d+:, :);

 *try* {

   command = findComponent(currentActionId);

   *LOG*.*info*(command = \ + command + \, *new* Exception());

 } *catch* (Exception e) {

   // ignore

 }



11:14:24,229 INFO  [STDOUT] 2007-07-20 11:14:24,229 [http-127.0.0.1-8080-2]
ERROR 
org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(348)

- Don't find any RendererClass for org.apache.myfaces.ScheduleRenderer.
Please check you configuration.

11:14:24,244 INFO  [STDOUT] 2007-07-20 11:14:24,244 [http-127.0.0.1-8080-2]
INFO  org.apache.myfaces.tobago.util.DebugPhaseListener.afterPhase(65) -
Total response time : 5936 milliseconds

11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter(204) 


- No context init parameter 'org.apache.myfaces.PRETTY_HTML' found, using
default value true

11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter(204) 


- No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found,
using default value true

11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter(204) 


- No context init parameter 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SE
LECTS' found, using default value true

11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter(204) 


- No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT' found,
using default value false

11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter(204) 


- No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found, using
default value false

11:14:24,260 INFO  [STDOUT] 2007-07-20 11:14:24,260 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter(229) 


- No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found,
using default value
org.apache.myfaces.renderkit.html.util.DefaultAddResource

11:14:24,276 INFO  [STDOUT] 2007-07-20 11:14:24,276 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter(229) 


- No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH'
found, using default value /faces/myFacesExtensionResource

11:14:24,276 INFO  [STDOUT] 2007-07-20 11:14:24,276 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter(204) 


- No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER'
found, using default value true

11:14:24,276 INFO  [STDOUT] 2007-07-20 11:14:24,276 [http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getCurrentInstance(177) 


- Starting up Tomahawk on the RI-JSF-Implementation.

11:14:36,897 INFO  [STDOUT] 2007-07-20 11:14:36,866 [http-127.0.0.1-8080-3]
INFO  org.apache.myfaces.tobago.component.UIPage.markSubmittedForm(176) -
command = [EMAIL PROTECTED]

*java.lang.Exception*

at org.apache.myfaces.tobago.component.UIPage.markSubmittedForm(*
UIPage.java:176*)

at org.apache.myfaces.tobago.component.UIPage.processDecodes(*
UIPage.java:138*)

at javax.faces.component.UIComponentBase.processDecodes(*
UIComponentBase.java:1001*)

at 

Re: [tobago] an unexpected block is executed with RI 1.2 (in JBoss 4.2.1 GA) // TODO: remove this if block if prooven this never happens anymore

2007-07-20 Thread Bernd Bohmann

Hello Zied,

can you send the jsf pages, please.

Regards

Bernd

Zied Hamdi wrote:

Hi again,

I'm sorry for announcing these problems, it's not a pleasure at all, I will
help as I can to resolve them.

I have some other side effects on using sun RI (bundled with JBoss 
4.2.1.GA),

I don't know if it's a consequense of the exception described in the first
mail, there are both visual and programmatic bugs:

1. visually (see picture):
 .It seems there's a first iteration on sheets with no arguments: before
some sheets header we see a complete line with no values in

2 programmatically I have this exception : If you want me to activate the
Trace mode on Phasis or component tree just let me know


14:44:18,011 INFO  [STDOUT] 2007-07-20 14:44:18,011 [http-127.0.0.1-8080-1]
INFO  org.apache.myfaces.tobago.util.DebugPhaseListener.afterPhase(65) -
Total response time : 5875 milliseconds

14:44:18,136 INFO  [STDOUT] 2007-07-20 14:44:18,120 [http-127.0.0.1-8080-2]
WARN
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.getLastModified(81) 


- Unparsable lastModified : @lastModified@

14:44:18,136 INFO  [STDOUT] 2007-07-20 14:44:18,120 [http-127.0.0.1-8080-1]
WARN
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.getLastModified(81) 


- Unparsable lastModified : @lastModified@

14:46:00,931 INFO  [STDOUT] 2007-07-20 14:46:00,931 [http-127.0.0.1-8080-1]
ERROR 
org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/IntoServicesTobagoWeb].[FacesServlet].invoke(278) 


- Servlet.service() pour la servlet FacesServlet a généré une exception

*java.lang.IllegalStateException*:
org.apache.myfaces.custom.schedule.UISchedule$ScheduleActionListener

at javax.faces.component.StateHolderSaver.restore(*
StateHolderSaver.java:98*)

at javax.faces.component.UIComponentBase.restoreAttachedState(*
UIComponentBase.java:1406*)

at javax.faces.component.UIComponentBase.restoreState(*
UIComponentBase.java:1272*)

at org.apache.myfaces.custom.schedule.UISchedule.restoreState(*
UISchedule.java:378*)

at org.apache.myfaces.custom.schedule.HtmlSchedule.restoreState(*
HtmlSchedule.java:189*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1141*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at javax.faces.component.UIComponentBase.processRestoreState(*
UIComponentBase.java:1157*)

at com.sun.faces.application.StateManagerImpl.restoreView(*
StateManagerImpl.java:171*)

at com.sun.faces.application.ViewHandlerImpl.restoreView(*
ViewHandlerImpl.java:290*)

at
org.apache.myfaces.tobago.application.ViewHandlerImpl.restoreView(*
ViewHandlerImpl.java:113*)

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:244*)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(*ApplicationFilterChain.java:290*)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
ApplicationFilterChain.java:206*)

at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(*
ExtensionsFilter.java:147*)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(*ApplicationFilterChain.java:235*)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
ApplicationFilterChain.java:206*)

at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(*
ReplyHeaderFilter.java:96*)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(*ApplicationFilterChain.java:235*)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(*
ApplicationFilterChain.java:206*)

at org.apache.catalina.core.StandardWrapperValve.invoke(*
StandardWrapperValve.java:230*)

at org.apache.catalina.core.StandardContextValve.invoke(*
StandardContextValve.java:175*)

at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(*

Re: [tobago] can we create a UIMenu structure on the fly (from the server side)?

2007-07-17 Thread Bernd Bohmann

Hello Zied,

just added a menu example to test

see:

http://svn.apache.org/repos/asf/myfaces/tobago/trunk/example/test/src/main/webapp/menu.jsp


and method getFileMenu in TestBean

http://svn.apache.org/repos/asf/myfaces/tobago/trunk/example/test/src/main/java/org/apache/myfaces/tobago/example/test/TestBean.java

Regards

Bernd

Zied Hamdi wrote:

Hello again, I forgot to tell you I'm new to JSF, It's possible I'm doingit
all bad.

I took a look in debug mode at a UIMenu instance initialized with Jsf tags,
and I've found an attribute containing the list of nested commands ids. I
suppose there's a factory for doing these routines... Does someone have the
info please?

Regards,
Zied


2007/7/13, Zied Hamdi [EMAIL PROTECTED]:


Hi Tobago,

I have a little problem filling a UIMenu (I took a look at the mailing
list and no one had the problem) : I've tried this:


  *public* UIMenu getPhoneMenu() {

*return* phoneMenu ;

  }





  *public* *void* setPhoneMenu(UIMenu phoneMenu) {

PhoneNumber number = *super* .getThroughEl ( phone ,
PhoneNumber.*class* );

*this*. phoneMenu = phoneMenu ;

phoneMenu.setId( phoneTypes );

phoneMenu.getAttributes().*put*( image, 
image/phone_types/+

number.getType() + .PNG  );

*for* ( PhoneType type : PhoneType.*values*() ) {

  UICommand command = *new* UICommand();

  phoneMenu .getChildren().*add*( command );

  MapString, Object attributes = 
command.getAttributes();


  attributes.*put* ( image, image/phone_types/+ 
type +

.PNG  );

  attributes .*put*( label , 
type.toString().toLowerCase() );


}

  }


It doesn't work, it seems UIMenu has in its attributes Map the list of
the Command ids it contains...
Are the factories used to interpret the jsf structure designed to be used
by third parties? Or there another solution for creating my UIMenu

Regards,

--
Zied Hamdi








Re: [tobago] integrating Tomahawk Shedule componenent in Tobago

2007-07-17 Thread Bernd Bohmann

Hello Zied,

just moved the tomahawk example in the sandbox to the example test 
project. Some of the js libs of the shedule component clashed with the 
prototype js lib of tobago. Maybe you can create a modified tomahawk 
version of the shedule js libs in a different namespace.


Regards

Bernd

Zied Hamdi wrote:

Hi Again,

I've downloaded the last night build (1.0.12 SNAPSHOT), there's a lot of
interesting stuff like radio and checkbox menus, extended text area,
unfortunately there's nothing dealing with the Shedule yet (I took a 
look at

the tld).

Can someone of the team please tell me if it's planned to be adapted in the
near future? I'd like to do and submit it, but I'm not exerienced with JSF
and it would take me a lot of time and frustrations (especially that I'm
already late for my project :-)...

Regards,
Zied

2007/7/17, Zied Hamdi [EMAIL PROTECTED]:


Thanks for the hint Matthias (and the rapid answer),

I'll take a look there and give a feedback to the mailing list if I've
found a solution.

Regards,
Zied


2007/7/17, Matthias Wessendorf [EMAIL PROTECTED]:

 I know there is a tobago sandbox, which aims to support some tomahawk
 stuff,
 perhaps it's worth to take a look ?

 -Matthias

 On 7/17/07, Zied Hamdi [EMAIL PROTECTED] wrote:
  Hi there,
 
  I have a strong need of a shedule, and I saw
  http://myfaces.apache.org/tomahawk/schedule.html that is
  really excellent. I've chosen Tobago because of the time I can 
gain on
  design (not developping css files, and have nice skins that 
fulfill my


  needs), I saw it's not possible to have compatibility between tobago
 and
  other myFaces libs, because of the unique View id imposed by the
 specs. So
  the only solution to have the tomahawk schedule in my tobago app 
seems

 to be
  to port the classes to Tobago. I'm new to JSF so I'd ask: is it a big
 time
  consuming task to do that? or maybe should I ask before that: does
 Tobgao
  plan to have its shedule in the next two months?
 
  If anyone has the answer, please tell me, my project must be finished
 in two
  months, so I'm beginning to be scared ;-+;
 
  Regards,
  Zied
 


 --
 Matthias Wessendorf

 further stuff:
 blog: http://matthiaswessendorf.wordpress.com/
 mail: matzew-at-apache-dot-org




--
Zied Hamdi
zatreex.sourceforge.net







  1   2   3   4   >