Latest posts for the topic "any issues with JSF Components and JSF Portlets"

any issues with JSF Components and JSF Portlets

akhopkar — GMT

Are there any known issues with apps using ICESoft Components being ported to Portlets using a JSF Pridge. Does the portlet maintain the Direct to DOM Rendering technology that only does partial refresh? Amarish

Re: any issues with JSF Components and JSF Portlets

deryk.sinotte — GMT

Hey Amarish. Thanks for your question. We don't officially support the portlet environment and haven't been running or testing ICEfaces with portlets. We did some preliminary work in the past to prepare the ICEfaces framework to work with portlets due to what we perceived as a high level of interest from potential customers at last year's JavaOne. However, our work since then has concentrated on other areas (e.g. Facelets) where customer demand has been more consistent. If I had to guess (and was being brutally honest) I'd suspect that you'll run into serious problems pretty quickly if you try to use ICEfaces with portlets. Of course, don't let my opinion stop you from giving it a go and letting us know how it goes ;-). The good news is that we make the input from these forums an important part of our planning. I'll make sure that portlet support makes it's way onto our roadmap in some way, shape, or form. Any additional information you can provide on your application requirements is always appreciated. Deryk

Re: any issues with JSF Components and JSF Portlets

Admin — GMT

Hi Derek, Thanks for your honesty. Unfortunately it is really a requirement of my client that this be deployed in a portal, so I'm not sure if I really have the time to invest to dig into ICEFaces and then deploy it to a portal, especially if you think it will have serious problems. What is your expected date for portal compliance? Amarish

Re: any issues with JSF Components and JSF Portlets

deryk.sinotte — GMT

Our next release is 1.0 and will be released before JavaOne which starts on May 15th, 2006. Portlets will not be supported in that release. Past that, the road map is a bit more fluid and will depend on customer feedback. What kind of schedule do you have for you project? At this point, depending on the characteristics of your project, it is possible to influence the roadmap. Deryk

Re: any issues with JSF Components and JSF Portlets

deryk.sinotte — GMT

Oops, I guess JavaOne officially starts on May 16th. By the way, if you our your company is attending, we'll have a booth there. Unfortunately, I won't be able to attend bure you can talk to several of our engineers and product people. It would be a good time to pressure us for portlet support. Deryk

Re: any issues with JSF Components and JSF Portlets

akhopkar — GMT

Hi Deryk, Thanks for your posts. We are planning to build a suite of dynamic AJAX enabled web applications for a prospect in the Health-Care industry. In my mind, ICEFaces is an extremely promising technology that I think is a strong candidate for use. Our plan is to integrate all these into some open source portal. We're thinking either LifeRay or StringBeans. I think our use of this technology is probably going to depend on where portlet support is on the roadmap. We will be beginning development within a few weeks and finishing up Phase 1 of this project within 4 months. I think I can even go far enough to say that we can try to get by Phase 1 without using a portal, but as we start adding more and more applications to the platform, portlet support will become essential. Can you please let me know if there are any definite plans for portlet support at all, and how far down the road are these plans? Thanks, Amarish

Re: any issues with JSF Components and JSF Portlets

steve.maryka — GMT

Amarish, Customer demand is the number one thing that will drive our roadmap beyond the 1.0 release. Portlets will definately be on our roadmap somewhere - we just need to sort out how to prioritize it against other feature requests. Naturally, supported Enterprise customers will have the greatest influence. We will be in touch with you directly to understand better your plans, requirements, timing and business opportunity. Steve

Re: any issues with JSF Components and JSF Portlets

philip.breau — GMT

Hi Erwin, Not yet, we're working on Portlet support in an upcoming release. Thanks, Philip

Re: any issues with JSF Components and JSF Portlets

erwinka@matrix.co.il — GMT

Hi, Is ICEFaces support jsr 168 portlet? Erwin Karbasi

Re: any issues with JSF Components and JSF Portlets

erwinka@matrix.co.il — GMT

Hi, It could be in the beginning (january) of 2007? Thank's Erwin Karbasi Development Architect Matrix

Re: any issues with JSF Components and JSF Portlets

philip.breau — GMT

Hi, Sorry, no firm deadline yet, but it's one of our biggest priorities. Have you evaluated any portlet implementations yet? What are your own project requirements? Thanks, Philip

Re: any issues with JSF Components and JSF Portlets

erwinka@matrix.co.il — GMT

Hi Philip The following techonlogies: - JSR168 Portlets - JSF Framework & Components - WebSphere Portal Server V6.0 would be included in an enterprise (public) portal project which should be started in 2 months. What do you mean by portlet implementations? We are already working with JSF-Portlet implementation in WebSphere Environment (by IBM). The other products we are evaluating are: - Infragistics - Ajax4JSF - Backbase - WebGalielo Your assistance would be much appreciated Erwin

Re: any issues with JSF Components and JSF Portlets

erwinka@matrix.co.il — GMT

Hi Philip, Could you please reply to this issue. It is importent for me to prepare for "AJAX+JSF" frameworks in our company. I need to select between ICEFaces, Infragistics, backbase or Ajax4Jsf. Your assistance would be much appreciated Erwin Karbasi Development Architect

Re: any issues with JSF Components and JSF Portlets

philip.breau — GMT

Hi Erwin, Sorry for the late reply, was just waiting for some info. Our Portlet-integration developers are currently working on a more clear roadmap and timeline for this. So we should have some firm dates next week. Thanks, Philip

Re: any issues with JSF Components and JSF Portlets

erwinka@matrix.co.il — GMT

Hi, Thank's. I am waiting for your reply. Erwin Karbasi Message was edited by: Erwin

Re: any issues with JSF Components and JSF Portlets

ted.goddard — GMT

Can you provide additional details on your ICEfaces/portlet requirements? - can ICEfaces portlet share a common session on the application server? - must ICEfaces portlets support WSRP? - must the portal page (including the portlet controls) be ICEfaces-enabled? - are the requested portal servers absolute requirements? - how should connection status be displayed (for application-initiated update)? - to what degree will the portlets interact with each other (i.e. if the user interacts with one portlet, are the others expected to be updated)?

Re: any issues with JSF Components and JSF Portlets

jnadler — GMT

We're looking for Portlet-enabled components as well. I can answer some of these questions based on my own requirements: -yes, multiple portlets will share a common session, this is how portlets work -we do not need WSRP support -the portal page itself (i.e. the WebSphere Portal or Liferay or StringBeans portal screens) do not need to use ICEfaces components, just the portlets themselves (did I understand this question correctly?) -we are using Liferay 4.1, we would consider eXo as well -portlets are independent in our implementation (one portlet does not need to listen to another)

Re: any issues with JSF Components and JSF Portlets

jjchung — GMT

What is the timeline for the portlet integration?

Re: any issues with JSF Components and JSF Portlets

philip.breau — GMT

Hi, It's looking like early 2007 for a preliminary release. If you have any more detailed requirements on Portlet integration (preferred Portal implementation etc.) please let us know. Thanks, Philip

Re:any issues with JSF Components and JSF Portlets

erwinka@matrix.co.il — GMT

Hi, Is ICEFaces 1.5 support jsr 168 portlet? Erwin

Re:any issues with JSF Components and JSF Portlets

philip.breau — GMT

Hi Erwin, No, ICEfaces 1.5 does not yet fully support Portals. We have some initial support in this version, but there's still some work to do on this. We should have Portal support sometime in Q1 2007. Thanks, Philip

Re:any issues with JSF Components and JSF Portlets

nimms — GMT

Hi I'd also like to register my interest in a portal version of ice faces. Our IT department is looking at standardising on ICE Faces. We have a mixture of straight browser apps along with an intranet running on WebSphere Portal. we don't need WSRP, our portal page doesn't need ICEFaces, but our portlets do. Portal interaction will be through the Shared Application Portal Session scope as defined in the JSR168 Spec Regards Nimai Etheridge

Re:any issues with JSF Components and JSF Portlets

ananum — GMT

Hi We're currently in the early stages of developing a jsf/ajax application and are very interested in utilizing ICEfaces. We have been developing a portal solution using Liferay for several months now and hope to go live by the end of this year. My current project, as well as the other systems we have built, will be getting moved in some way shape or form to the portal beginning sometime in Q1 07. I'm hoping our development can coincide with your release of a portal capable version of icefaces - and it looks like it just might. I will be discussing this with my team next week, at which point I will be able to post some more detailed requirements. If you have any specific questions I can answer (outside of ted_g's initial set) please let me know. Thanks!

Re:any issues with JSF Components and JSF Portlets

ngriffin7a — GMT

I would like to weigh-in on this issue as well, and encourage the IceSoft folks and IceFaces community to support JSF portlets. I manage our corporate portal, which is based on Liferay 4.1.0 and JSF. Because MyFaces Tomohawk is dependent on the MyFaces filter, it is impossible to use Tomohawk within portlets, because JSR-168 portals do not support filters. Because of this, I had to develop a suite of JSF components to do ordinary things (DataTable, FileUpload, etc..) but none of them are AJAX enabled. So rather than AJAX-ify my own components, I would much rather migrate to IceFaces. BTW, the FileUpload component I developed uses a PhaseListener to intercept the enctype="multipart/form-data" from the request. I had to do it this way because the typical FileUpload JSF component makes use of a filter (like Tomahawk). Again, filters don't work with portals, so these are the types of things we have to deal with. I have attached the relevant Java files to this post. So since I have a lot of experience in this area, I would like to offer my services to the IceFaces community in order to get IceFaces and portlets working together, especially in conjunction with Liferay. I'm sure there are many JBoss portal folks out there too who would love to use IceFaces too. Regards, Neil Griffin Triton Services, Inc.

Re:any issues with JSF Components and JSF Portlets

danielmesser — GMT

Hi, What is the status about the Icefaces integration in portlets? We need to move a standard JSF web app using icefaces to a portlet. Thanks, Daniel Messer

Re:any issues with JSF Components and JSF Portlets

deryk.sinotte — GMT

Previous versions of ICEfaces had limited portlet support but we're working to make it much easier to use ICEfaces for portlet development in 1.6. The framework in the 1.6 codebase has undergone some significant changes to help make it easier to integrate with other technologies like portlets and Seam. Although I can't commit to any firm dates, we're hoping to provide an initial drop of the improved portlet support in the next developer release of 1.6 (around the end of March). For the official release of 1.6, our goal is to support the JSR 168 specification and have ICEfaces-based portlets running in JBoss and Liferay portal in the official 1.6 version of the product. We're definitely committed to supporting portlets in ICEfaces.

Re:any issues with JSF Components and JSF Portlets

danielmesser — GMT

That's great news since we're using Jboss. Thanks for your effort.

Re:any issues with JSF Components and JSF Portlets

jnadler — GMT

Hi Deryk, The 1.6 DR2 is now out - does this build contain fixes which will resolve the portal (esp Liferay) problems? If not, are there specific JIRAs which we should be watching for? Thanks, Jeff

any issues with JSF Components and JSF Portlets

deryk.sinotte — GMT

It's not in this release and likely won't make the official 1.6 release which is due out in a few weeks time. However, we are working on it and the likely scenario is that portlet support will be released against the 1.6 branch. The initial drop may be something like a separate early access download. I don't have any firm dates but you will be able to run and test your portlet applications against 1.6 in the not too distant future.

Re:any issues with JSF Components and JSF Portlets

jgrange — GMT

Given that full portlet support won't be in 1.6 :-( , it would be very useful to have an idea of when this will appear. In particular, I am looking for support of WSRP JSR168 portlets (I'm tied to oracle portal) and really need to understand whether it is worth continuing to monitor this forum or not. (if we're looking at Q3/4 07, then for me, the answer is not)

any issues with JSF Components and JSF Portlets

deryk.sinotte — GMT

An early access version of JSR 168 portlet support should be out shortly (measured in weeks) after the official 1.6 release (also measured in weeks). Initial portlet support is aimed at adherence to the JSR 168 spec for a couple of the most popular containers (JBoss and Liferay to start). We'll integrate additional features (like WSRP) and containers from there as indicated by customer demand. So portlet support should be available well before your deadline but I can't promise support for WSRP - at least initially.

any issues with JSF Components and JSF Portlets

jzaefferer — GMT

deryk.sinotte wrote:

An early access version of JSR 168 portlet support should be out shortly (measured in weeks) after the official 1.6 release (also measured in weeks). Initial portlet support is aimed at adherence to the JSR 168 spec for a couple of the most popular containers (JBoss and Liferay to start). We'll integrate additional features (like WSRP) and containers from there as indicated by customer demand.

Is there an update to this? Is there any code in a repository that I could try? I'm heavily interested in getting a datagrid component with ajax-based paging and sorting to work on WebSphere Portal 5.1 and 6. I can offer quite a lot of experience with JSF and those servers and I'd like to contribute to get ICEFaces to work there. Is there any way I can help to get some progress?

any issues with JSF Components and JSF Portlets

deryk.sinotte — GMT

There is no code in the repository yet. We're in the midst of releasing 1.6 DR 3 (which won't have portlet support) but shortly after that, we'll check in our preliminary work so that everyone can pitch in on their favourite portal container.