- This topic has 162 replies, 89 voices, and was last updated 16 years, 8 months ago by Karsten Gresch.
-
AuthorPosts
-
Riyad KallaMemberDave I think this is the big sticking point at the moment, the full XHTML support (which I believe is what Facelets needs). Will likely require code changes.
David Orriss JrParticipantTartar sauce….! :-/
jeff_bondMemberI use Facelets with MyEclipse at a large company, setup similar to William’s. (side note- also use MyFaces Trinidad, formerly ADF Faces, and support for those tags would be awesome as well) Have only recently upgraded to 5.1, but I noticed the El auto-completion didn’t seem to work in .xhtml files. Assuming this is as expected (El auto-completion only in JSP files), it would be a nice incremental step to get this enabled for the Facelets file type.
Garth SchneiderMemberNo support for EJB3 and no support for facelets *.xhtml is a major problem for MyeclipseIDE. This IDE is proving less and less supportive of my efforts.
yeecnMember@support-rkalla wrote:
Is anyone here using MyEclipse 5.0 successfully to do facelets development, or is the tool still not “Aware” of any of the tags or necessary parts of JSF to help?
I have been doing Facelets ‘successfully’ for almost a year. You don’t need much to get things to work, notepad will be plenty sufficient. Notepad is sufficient for the whole JEE development for that matter; it is IDE support that we are looking for. Currently MyEclipse is only marginally better than Notepad in terms of facelets/JSF supports.
Regards,
Yee
JeffMemberI’d like to request support for Facelets/.xhtml too. About 10 devs where I work using MyEclipse and our project is using Facelets/JSF.
Riyad KallaMemberThe management team and I had a great planning meeting about this the other day, they are fully aware of the demand and are assessing the technical costs right now to do this.
dkittleMemberAfter almost a year of waiting and still not even seeing it on the roadmap, I gave up. I let my subscription elapse and have moved onto other tools. At work we’ve now purchased a much more expensive tool and are happy again. At home I’m learning to do without all the less used stuff and use NetBeans with their Facelets support (includes EL completion) and my life is good again. Sorry guys (Genuitec), but I -really- feel you missed the boat on this one. Your product was great, your support fantastic, but I won’t wait any more.
Riyad KallaMemberdkittle,
We never want to loose a customer, but at times we aren’t the right tool for the job. After 5.0.3 facelets support is going to be evaluated by our editor/designer team and then an assessment as far as what it would take to get it done will be handed to management to evaluate for inclusion starting with 5.1 and moving forward.We want to address the big demands of our user base, but at any given time you’d be surprised just *how* many things there are on the table and so far I’d say we’ve done a fair job of covering the tooling that most of our users need. I’ll be the first to admit that Facelets and JEE 5 support is a little slower moving than I’d like, but these aren’t cheap/easy tools to build so I can understand why it’s taking longer.
I’ll ping our product manager on this and I hope we win you back with a future release.
Mark RicardMemberIf ADF or Trinidad is not included in the upcomming 1/2 year, I’m afraid all 9 of us will be letting our licenses lapse in favor of another tool that supports it. 🙁 No choice.
Niklas EkmanMemberAt our company we’re 7 developers using Facelets and it would be extremely good to have at least code assist for it. A visual editor would be sweeter 🙂
Riyad KallaMemberWe just had an evaluation of the Source editor and Designer to see if they were XHTML compatible as a first step towards full facelets support. Things were in surprisingly good shape, with just a few time consuming tweaks that were needed, unfortunately we just entered QA for 5.0.3 so management decided to descope that first step for 5.0.3 and instead put it into 5.1.
David Orriss JrParticipant@support-rkalla wrote:
We just had an evaluation of the Source editor and Designer to see if they were XHTML compatible as a first step towards full facelets support. Things were in surprisingly good shape, with just a few time consuming tweaks that were needed,
WOO HOO!!
@support-rkalla wrote:
unfortunately we just entered QA for 5.0.3 so management decided to descope that first step for 5.0.3 and instead put it into 5.1.
DOH!
Hopefully 5.1 isn’t too far away…
Riyad KallaMemberHopefully 5.1 isn’t too far away…
Our last estimate was Q42009, so it’s practically right around the corner!
😀
More seriously though, if I had to give an uneducated guess we should start pushing out milestones for it right around the new year depending on how aggressively we want to get features into that release. If it’s real aggressive, it might be more like January-ish for milestones starting.
We are going to be doing a lot of tone-setting for all future releases with the 5.1 release, so we really want it to go off well.
mlsalcedoMemberCould u tell which features are included in 5.0.3 that pushed XHTML support for a feature release? I was expecting XHTML in your next release but I will have to let developers use Exadel due to your lack of support for XHTML. Hopefully you can recover quickly and catch up.
-
AuthorPosts