- This topic has 162 replies, 89 voices, and was last updated 16 years, 8 months ago by
.
-
Posts
-
When is 5.5 scheduled for release? We have 4 licenses and are considering a switch to Exadel specifically for it’s Facelet support. I think that 10 pages worth of posts would merit some sort of Facelet Support announcement on your home page. As everyone is well aware, Exadel Studio is now free (as in beer) and you guys will be hard pressed to retain users if you can’t stay ahead of the curve.
What is the status on this?
Facelets support is in-progress right now. I’ve been testing it the last few days, unfortunately it isn’t going to make the cut for the 5.5M2 release. We found a series of deployment scenarios where without automated help, your deployments won’t work on specific app servers (for the folks in the know, this isn’t an issue, but for new users it’s a total PIA). Management decided to pull it out of the M2 release and we are going to make a run at getting it into the GA release at the end of this month.
That being said Facelets isn’t of issue of “if” but an issue of “when”. We’ve been working on it and testing it for a bit now and will continue to until it makes it’s debut. Then I’m sure you guys will pound it to death and come back to us with a lot of suggestions (which is good) and we’ll keep banging away at it.
It’s clear Facelets is a must-have JSF technology for a huge number of our users and that’s why it’s getting done.
I’m definitely looking forward to the completion of this. Especially with respect to “tag insight” for the Facelets tagset.
Especially with respect to “tag insight” for the Facelets tagset.
That’s the other reason it was held back… we can’t do anything until we get code assist working correctly.
The deployment scenarios are coming to a head… it’s such a pain. One set of libs works on Jetty 6, but then fails on Tomcat 6. Then another set work on Glassfish, but fail on WebLogic, etc. etc.
It just has to do with some app servers shipping default libs that overlap with the ones facelets uses and visa versa.
Maybe you already know it, but there is a bug in the XHTML editor.
The editor is empty, I need to minimize and back maximize the editor pane to see my code. This happens everytime I open a XHTML file.
Empty (direct after opening file)
Partially rendered after resizing the pane.
Fully rendered after minimizing/maximizing the editor pane.@jkva wrote:
Maybe you already know it, but there is a bug in the XHTML editor.
The editor is empty, I need to minimize and back maximize the editor pane to see my code. This happens everytime I open a XHTML file.
Empty (direct after opening file)
Partially rendered after resizing the pane.
Fully rendered after minimizing/maximizing the editor pane.Anything in the log?
This might be a page-specific issue. Can you reproduce it with other pages?@support-eugene wrote:
@jkva wrote:
Maybe you already know it, but there is a bug in the XHTML editor.
The editor is empty, I need to minimize and back maximize the editor pane to see my code. This happens everytime I open a XHTML file.
Empty (direct after opening file)
Partially rendered after resizing the pane.
Fully rendered after minimizing/maximizing the editor pane.Anything in the log?
This might be a page-specific issue. Can you reproduce it with other pages?1 At the moment I dont have a log. I’ll check that today/tomorrow.
2 Yes, every Facelets page I open has this problem. I have the most recent version as far as I know. Somewhere near 5.5.@jkva wrote:
1 At the moment I dont have a log. I’ll check that today/tomorrow.
2 Yes, every Facelets page I open has this problem. I have the most recent version as far as I know. Somewhere near 5.5.I haven’t seen any other reports of this issue. It is likely it is specific to your pages and/or workspace. Please, check the log for stack traces. It would be great if you sent some page that you have problems with (stripping all sensitive information) to [email protected]. Please include “For Eugene” in the subject field.
Thank you in advance.@jkva wrote:
@support-eugene wrote:
@jkva wrote:
Maybe you already know it, but there is a bug in the XHTML editor.
The editor is empty, I need to minimize and back maximize the editor pane to see my code. This happens everytime I open a XHTML file.
Empty (direct after opening file)
Partially rendered after resizing the pane.
Fully rendered after minimizing/maximizing the editor pane.Anything in the log?
This might be a page-specific issue. Can you reproduce it with other pages?1 At the moment I dont have a log. I’ll check that today/tomorrow.
2 Yes, every Facelets page I open has this problem. I have the most recent version as far as I know. Somewhere near 5.5.It is not the page. With other pages, I have the same problem. Also with simple HTML pages, like a redirect index.html file. Probably it has something to do with the fact that I don’t use the MyEclipse version of Facelets, but my own.
If I’m correct, MyEclipse ships 1.1.11 and I use 1.1.12 or a self-built version from the Facelets CVS.
