The only thing that is bothering me is that there is no error message out put from glassfish. It would have been nice to have been able append some output to the bug report. Not being a web guy I'm not sure what other info I could add but I do know that bugs are easier to trace when you have a place to start.

In any event it will be interesting to know if the problem lies in glassfish or with the component.

Dennis

Romanowski, Tim wrote:

Dennis, thanks for the heads up; comment added.

 


From: Dennis Gesker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 24, 2007 7:02 PM
To: MyFaces Discussion
Subject: Re: Tomahawk on Glassfish-v2

 

Tim:

Could you add a comment confirming that you are seeing the same behavior in the bug database?


https://issues.apache.org/jira/browse/TOMAHAWK-872
 
Dennis



Romanowski, Tim wrote:

No, you are right -- the first doesn't link doesn't appear to do what is
intended, although it does 'work.' 
 
Is there an error with the source for the example?  I've never used the
collapsible panel before, but from the code, it doesn't look like anything
is changing the boolean value for the "collapsed" property in the first
test.  Or is it supposed to work as is?
 
<t:collapsiblePanel id="test1"
value="#{firstCollapsiblePanelBean.collapsed}" title="testTitle">
            <h:panelGrid>
                <h:outputText
value="#{firstCollapsiblePanelBean.firstName}"/>
                <h:inputText value="#{firstCollapsiblePanelBean.surName}"/>
                <t:inputCalendar
value="#{firstCollapsiblePanelBean.birthDate}" renderAsPopup="true"/>
            </h:panelGrid>
        </t:collapsiblePanel>
 
        <t:collapsiblePanel id="test2"
value="#{secondCollapsiblePanelBean.collapsed}" title="testTitle"
                            var="test2collapsed">
            <f:facet name="header">
                <t:div style="width:500px;background-color:#CCCCCC;">
                    <h:outputText value="Person"/>
                    <t:headerLink immediate="true">
                        <h:outputText value="> Details"
rendered="#{test2collapsed}"/>
                        <h:outputText value="v Overview"
rendered="#{!test2collapsed}"/>
                    </t:headerLink>
                </t:div>
            </f:facet>
 
 
Tim
 
-----Original Message-----
From: Dennis Gesker [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, January 24, 2007 3:36 PM
To: MyFaces Discussion
Subject: Re: Tomahawk on Glassfish-v2
 
Tim:
 
When you deployed the example did the first on one the page work as
well? When I loaded the example war here only the first one failed
(small one at the very top) to toggle. The rest worked.
 
Dennis
 
Romanowski, Tim wrote:
  
I just tested the myfaces-example-simple-1.war of a Tomahawk 1.1.5 nightly
from a week ago and it seems to be running ok on Glassfish V2, B31.  I ran
the collapsible panel demo, and that worked fine as well.  Also, I am
currently using the Tomahawk popup component in my own app and it is
    
working
  
ok.  
 
While this isn't a solution for you, it may still be that you have a
configuration issue to resolve.  Also, are you using facelets? I haven't
been able to use the panelMenu or JSCookMenu since early this past summer,
so that combination could be a source of problems.
 
Tim  
 
-----Original Message-----
From: Dennis Gesker [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, January 24, 2007 1:48 PM
To: MyFaces Discussion
Subject: Re: Tomahawk on Glassfish-v2
 
I just entered a bug report. --drg
 
Mike Kienenberger wrote:
  
    
On 1/24/07, Dennis Gesker <[EMAIL PROTECTED]> wrote:
    
      
Also, if I bind the component to my report backing bean and set the
value to false then redeploy the collapsiblePanel does display however
it still won't toggle.
      
        
I've never used that component so I can't help with details.
 
 
On 1/24/07, Dennis Gesker <[EMAIL PROTECTED]> wrote:
    
      
I found their examples but couldn't find where to download so I could
try their build on my test server. --drg
      
        
Yes, I was recommending looking at the behavior in the public example
pages.   That gives you a baseline since everything is theoretically
configured correctly on those examples.   If those examples are
broken, you know it's a bug in Tomahawk or MyFaces.
 
 
 
 
    
      
Mike Kienenberger wrote:
      
        
If you're using Glassfish, you're using the JSF 1.2 RI.   I recall
that there were issues that were fixed in Tomahawk 1.1.5 in order to
make it compatible with JSF 1.1 RI _javascript_.    That would explain
differences between 1.1.3 and 1.1.5 behavior.
 
Working with the examples is probably the best thing to verify
behavior.   Have you compared that behavior to the online examples at
http://www.irian.at/home.jsf?  You'll need to select Products ->
Myfaces and try the two tomahawk example sets (one is the latest build
-- not sure what the version number for the other one is).
        
          


Reply via email to