Re: [flexcoders] Portal with Flex
I don't think Flex is suitable to Portal solution now, Coenraets' article using Flex1.5 technique, but the Taglib method is proved not a good direction for Flex portal. One way I think the great Flex portal solution is workday Portal solution: http://www.adobe.com/newsletters/edge/december2007/articles/article6/index.html?trackingid=BOYNJ although they do ERP software, but I think this solution is also feasible to Flex portal. -- lwz7512 Ultrapower Flex Team Leader OpenRIA -- A Window You Exploring RIA World http://www.openria.cn - Original Message From: Peeyush Tuli [EMAIL PROTECTED] To: flexcoders@yahoogroups.com Sent: Monday, March 31, 2008 11:02:59 PM Subject: Re: [flexcoders] Portal with Flex Maybe any J2ee gurus can comment better, but here are my 2 cents. Regarding point 2, Flex is a client side technology, while session management and clustering are server side concerns. Is it not all about appending a session id as one of the parameters in the remote call for the calling client. Whenever some data is committed in a session, it is the server's duty to persist it isn't it? Flex would report you an error in case a remote call would fail, in case your server -1 is down. You can set a retry call in your code after a definite interval to check if the server 2 is up and then you receive a proper response. I dont think the usage of LCDS would depend on this, it is just a going to serialize the flex call to java call and vice-versa. It is required when you directly need to invoke a server side java method. ~Peeyush On Mon, Mar 31, 2008 at 8:01 AM, olegkon [EMAIL PROTECTED] com wrote: Hi, I just started a new job. We are moving large mainframe application Unix servers, rewriting whole thing in J2EE. I am in the GUI group, they are planning to use JSF+AJAX and portlets. I have no JSF, no portlets, no WebSphere portal and little AJAX experience, beginner in Flex. [but do have 5 yrs of Swing + 6 yrs of JSP/servlets+ Struts/Spring MVC]. I am trying hard to convince them to use Flex instead of JSF/AJAX. They have a few doubts: 1) Does Flex work with portals/portlets ? I was able to find Coenraets' article: http://www.adobe. com/devnet/ flex/articles/ flex_portals_ print.html but it seems to be based or written in 2004 [Flex1 ?] And somehow it doesn't even mention FlexDS. I have seen short discussion about portal support in LCDS documentation. So do I have to use LCDS for that or not ? 2) Architect here is very concerned that Flex won't work in clustered WebSphere Portal 6 environment, especially in session management area: Is Is Flex able to run within a clustered environment? The answer is sorta, we know it will render in a cluster environment, BUT do we have session failover capabilities with it? a. Scenario A, we are entering data on Form 2 of 5 on Server1 in a clustered environment with two servers(Server1, Server2) b. Server 1, crashes b/c somebody tripped over the power cord. c. WebSphere will failover any session info we have, how will the Flex application react? i. Will it continue where we left off? On Form 2 of 5 or start back at Form 1 of 5? ii. Will it just restart itself from point a within the application? And again, do we need LCDS for that or not ? 3) Any Portlet - Flex samples with the source code ? 4) Any good article on JSF+AJAX vs. Flex ? [it will be in the browser, not AIR yet] Could you please shed some light on these issues ? Thank you in advance, Oleg. You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com
Re: [flexcoders] Portal with Flex
Maybe any J2ee gurus can comment better, but here are my 2 cents. Regarding point 2, Flex is a client side technology, while session management and clustering are server side concerns. Is it not all about appending a session id as one of the parameters in the remote call for the calling client. Whenever some data is committed in a session, it is the server's duty to persist it isn't it? Flex would report you an error in case a remote call would fail, in case your server -1 is down. You can set a retry call in your code after a definite interval to check if the server 2 is up and then you receive a proper response. I dont think the usage of LCDS would depend on this, it is just a going to serialize the flex call to java call and vice-versa. It is required when you directly need to invoke a server side java method. ~Peeyush On Mon, Mar 31, 2008 at 8:01 AM, olegkon [EMAIL PROTECTED] wrote: Hi, I just started a new job. We are moving large mainframe application Unix servers, rewriting whole thing in J2EE. I am in the GUI group, they are planning to use JSF+AJAX and portlets. I have no JSF, no portlets, no WebSphere portal and little AJAX experience, beginner in Flex. [but do have 5 yrs of Swing + 6 yrs of JSP/servlets+Struts/Spring MVC]. I am trying hard to convince them to use Flex instead of JSF/AJAX. They have a few doubts: 1) Does Flex work with portals/portlets ? I was able to find Coenraets' article: http://www.adobe.com/devnet/flex/articles/flex_portals_print.html but it seems to be based or written in 2004 [Flex1 ?] And somehow it doesn't even mention FlexDS. I have seen short discussion about portal support in LCDS documentation. So do I have to use LCDS for that or not ? 2) Architect here is very concerned that Flex won't work in clustered WebSphere Portal 6 environment, especially in session management area: Is Is Flex able to run within a clustered environment? The answer is sorta, we know it will render in a cluster environment, BUT do we have session failover capabilities with it? a. Scenario A, we are entering data on Form 2 of 5 on Server1 in a clustered environment with two servers(Server1, Server2) b. Server 1, crashes b/c somebody tripped over the power cord. c. WebSphere will failover any session info we have, how will the Flex application react? i. Will it continue where we left off? On Form 2 of 5 or start back at Form 1 of 5? ii. Will it just restart itself from point a within the application? And again, do we need LCDS for that or not ? 3) Any Portlet - Flex samples with the source code ? 4) Any good article on JSF+AJAX vs. Flex ? [it will be in the browser, not AIR yet] Could you please shed some light on these issues ? Thank you in advance, Oleg.
[flexcoders] Portal with Flex
Hi, I just started a new job. We are moving large mainframe application Unix servers, rewriting whole thing in J2EE. I am in the GUI group, they are planning to use JSF+AJAX and portlets. I have no JSF, no portlets, no WebSphere portal and little AJAX experience, beginner in Flex. [but do have 5 yrs of Swing + 6 yrs of JSP/servlets+Struts/Spring MVC]. I am trying hard to convince them to use Flex instead of JSF/AJAX. They have a few doubts: 1) Does Flex work with portals/portlets ? I was able to find Coenraets' article: http://www.adobe.com/devnet/flex/articles/flex_portals_print.html but it seems to be based or written in 2004 [Flex1 ?] And somehow it doesn't even mention FlexDS. I have seen short discussion about portal support in LCDS documentation. So do I have to use LCDS for that or not ? 2) Architect here is very concerned that Flex won't work in clustered WebSphere Portal 6 environment, especially in session management area: Is Is Flex able to run within a clustered environment? The answer is sorta, we know it will render in a cluster environment, BUT do we have session failover capabilities with it? a. Scenario A, we are entering data on Form 2 of 5 on Server1 in a clustered environment with two servers(Server1, Server2) b. Server 1, crashes b/c somebody tripped over the power cord. c. WebSphere will failover any session info we have, how will the Flex application react? i. Will it continue where we left off? On Form 2 of 5 or start back at Form 1 of 5? ii. Will it just restart itself from point a within the application? And again, do we need LCDS for that or not ? 3) Any Portlet - Flex samples with the source code ? 4) Any good article on JSF+AJAX vs. Flex ? [it will be in the browser, not AIR yet] Could you please shed some light on these issues ? Thank you in advance, Oleg.
