List Info

Thread: RE: Myfaces/Tomahawk on IBM WebSphere Portal Server 6




RE: Myfaces/Tomahawk on IBM WebSphere Portal Server 6
country flaguser name
United States
2007-10-05 10:11:39

We have

 WPS 6.0.1      on        Was 6.0.2.21  . It was the WAS version ( fixpack upgrade ) , that fixed our deployment problem . Earlier we were not even able to deploy the application.

Ofcourse,  What IBM recommends is to use IBM jsf libraries .   If you re using RAD for your development , may be that's a good idea.

Shipra



<mario.buonopaneaccenture.com>

10/05/2007 05:05 AM
Please respond to
";MyFaces Discussion" <usersmyfaces.apache.org>;

To
<usersmyfaces.apache.org>;
cc
Subject
RE: Myfaces/Tomahawk on IBM WebSphere Portal Server 6





I’m just starting a new project using WAS Portal Server and we are deciding wich jsf library to use. What’;s the version of your WebSphere? 6.0.x or 6.1.x?
 
Thanks
Mario  
 



From: SJainSperianProtection.com [mailto:SJainSperianProtection.com]
Sent:
4 ottobre 2007 20.28
To:
MyFaces Discussion
Subject:
Re: Myfaces/Tomahawk on IBM WebSphere Portal Server 6

 

We are using following


MyFaces version  1.1.5


Tomhawk version 1.1.5


Portlet class  -  
org.apache.myfaces.portlet.MyFacesGenericPortlet

So are you saying you have a MyFaces/Tomhawk application that is running without any issues on Websphere Portal 6 ?


What exact portal 6 fixpack are you using ? We initially were not even able to install the app on Websphere . Then the consultant came in & upgraded our fixpack . That resolved half the problem , then we found out the tomhawk java script is not working . For that he made a hack in
StreamingAddResource class to get the javascript working . Now , our next problem is this duplicate client id  issue .

It would be very nice of you if you can send in a example application for
Websphere Portal 6 using Myfaces/Tomahawk . Please include a tag using javascript , example <t:inputCalendar >  or <t:popup>

Thanks

Shipra Jain


Bernhard Huemer <bernhard.huemergmail.com&gt;

10/04/2007 01:58 PM


Please respond to
";MyFaces Discussion" <usersmyfaces.apache.org>;


To
MyFaces Discussion <usersmyfaces.apache.org>;
cc
 
Subject
Re: Myfaces/Tomahawk on IBM WebSphere Portal Server 6

 


   





Hello,

which version of MyFaces and which portlet bridge are you using? I'm
just asking as I didn't face those exceptions. Perhaps, if I've got time
left on the weekend, I'll create an example project (sort of "archetype
project";).

regards,
Bernhard

On 10/04/2007 +0200,
SJainSperianProtection.com wrote:
&gt;
> We had tough time . Then finally we had to hack My Faces ( with help of
> IBM consultant ) to make it somewhat work .  Of particular note IBM
> support is useless . You have to pay them to get a consultant.
>
> Still getting duplicate clientId exceptions , due to which page renders
> incorrectly when visited again in same session .
>
> What stage are you at ? What is the error you are getting?
>
> If someone have any solution to this , please let us know.
&gt;
> Shipra Jain
>;
>
>
> *<mario.buonopaneaccenture.com>*
>
> 10/04/2007 09:36 AM
> Please respond to
> "MyFaces Discussion" <usersmyfaces.apache.org>;
>
>
>                  
&gt; To
>                  <usersmyfaces.apache.org>;
> cc
>                  
&gt; Subject
>                  Myfaces/Tomahawk on IBM WebSphere Portal Server 6
>
>
>                  
&gt;
>
>
>
>
> Hi, is there any one have used successfully Myfaces/Tomahawk on IBM
&gt; WebSphere Portal Server 6?
>  
&gt; Regards
> Mario Buonopane
>  
&gt;
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete
> the original. Any other use of the email by you is prohibited.
>

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

ajax4jsf and expanded tree2
country flaguser name
Germany
2007-10-05 10:53:48
Hi All...
I use:
Myfaces 1..1.5
Tomahawk 1.6
ajax4jsf 1.1.1

Problem:
When you expand the tree and navigate to an other page and
com back, the 
tree is collapsed. And you can not see, which tree-node is
selected.
the scope of the bean which manage this page is session.

Structure:
page1: <t:tree2> and <t:dataTable>
the tree2 is concluded in <a4j:outputpanel>
and the <t:dataTable concluded in <a4j: region>
when you click the tree, the datatable will bee updated!
All this works fine.

But how can I let the tree be expanded??

thanks for any help..
naba

Re: ajax4jsf and expanded tree2
user name
2007-10-05 13:23:16
Put the tree state in the session scope. Use component
binding or the
tree model to re-load the old state when the tree component
is built

-A

On 10/5/07, NABA <naba.nabougmx.net> wrote:
> Hi All...
> I use:
> Myfaces 1..1.5
> Tomahawk 1.6
> ajax4jsf 1.1.1
>
> Problem:
> When you expand the tree and navigate to an other page
and com back, the
> tree is collapsed. And you can not see, which tree-node
is selected.
> the scope of the bean which manage this page is
session.
>
> Structure:
> page1: <t:tree2> and <t:dataTable>
> the tree2 is concluded in <a4j:outputpanel>
> and the <t:dataTable concluded in <a4j:
region>
> when you click the tree, the datatable will bee
updated!
> All this works fine.
>
> But how can I let the tree be expanded??
>
> thanks for any help..
> naba
>

Re: ajax4jsf and expanded tree2
country flaguser name
Germany
2007-10-08 03:20:00
Thanks Andrew...
I will try it. I don't know how component binding works...
but it is a 
reason to deal with it.
I will write how it works..
naba


Andrew Robinson schrieb:
> Put the tree state in the session scope. Use component
binding or the
> tree model to re-load the old state when the tree
component is built
>
> -A
>
> On 10/5/07, NABA <naba.nabougmx.net> wrote:
>   
>> Hi All...
>> I use:
>> Myfaces 1..1.5
>> Tomahawk 1.6
>> ajax4jsf 1.1.1
>>
>> Problem:
>> When you expand the tree and navigate to an other
page and com back, the
>> tree is collapsed. And you can not see, which
tree-node is selected.
>> the scope of the bean which manage this page is
session.
>>
>> Structure:
>> page1: <t:tree2> and <t:dataTable>
>> the tree2 is concluded in <a4j:outputpanel>
>> and the <t:dataTable concluded in <a4j:
region>
>> when you click the tree, the datatable will bee
updated!
>> All this works fine.
>>
>> But how can I let the tree be expanded??
>>
>> thanks for any help..
>> naba
>>
>>     
>
>   


Re: ajax4jsf and expanded tree2
country flaguser name
Germany
2007-10-08 05:38:34
Hi...
I bound the tree2 to an HtmTree and it works.
I got a new Problem:
When  I leaved the application and loged-on again, the tree2
was shown, 
like how I leaved it (it was still expanded).
I set the HtmlTree = new HtmlTree(). And it was Ok...
thanks for help...
naba



NABA schrieb:
> Thanks Andrew...
> I will try it. I don't know how component binding
works... but it is a 
> reason to deal with it.
> I will write how it works..
> naba
>
>
> Andrew Robinson schrieb:
>> Put the tree state in the session scope. Use
component binding or the
>> tree model to re-load the old state when the tree
component is built
>>
>> -A
>>
>> On 10/5/07, NABA <naba.nabougmx.net> wrote:
>>  
>>> Hi All...
>>> I use:
>>> Myfaces 1..1.5
>>> Tomahawk 1.6
>>> ajax4jsf 1.1.1
>>>
>>> Problem:
>>> When you expand the tree and navigate to an
other page and com back, 
>>> the
>>> tree is collapsed. And you can not see, which
tree-node is selected.
>>> the scope of the bean which manage this page is
session.
>>>
>>> Structure:
>>> page1: <t:tree2> and <t:dataTable>
>>> the tree2 is concluded in
<a4j:outputpanel>
>>> and the <t:dataTable concluded in <a4j:
region>
>>> when you click the tree, the datatable will bee
updated!
>>> All this works fine.
>>>
>>> But how can I let the tree be expanded??
>>>
>>> thanks for any help..
>>> naba
>>>
>>>     
>>
>>   
>


[1-5]

about | contact  Other archives ( Real Estate discussion Medical topics )