[darbvin]

I was thrilled to see J2EE SDK 5 (Sun Java Application Server Platform Edition 9) in MyEclipse, however quickly realized that there is no support for JSF 1.2 – which is what SJASPE9 includes). Any time frame estimate for support of JSF 1.2?

[Riyad Kalla]

darbvin,
You are right out of the box we don’t offer a JEE 5 library set yet, but you can work around this by creating your own using the Sun App Server (or Glassfish) libraries. I was working on a project thta was using JSF 1.2 and this is how we got around it, worked fine.

[arjan.tijms]

@support-rkalla wrote:

darbvin,
You are right out of the box we don’t offer a JEE 5 library set yet,

Of course there’s more to supporting JSF 1.2 than just offering a library set. Things that quickly come to mind are the unified EL and the TLD plug-ins.

[augustientje]

There’s a lot more actually. One thing we’re having problems with in MyEclipse is the global resource bundle definition. The MyEclipse editor doesn’t recognize this at all, and thus flags all uses of this bundle as warnings. Of course, the pages in question run just fine.

Rkalla, are there any plans for specific support for JSF 1.2 syntax and features? I’m really not interested in bundled implementations or wizards, just looking for edtor support for the basic new things in JSF 1.2.

[Riyad Kalla]

There’s a lot more actually. One thing we’re having problems with in MyEclipse is the global resource bundle definition. The MyEclipse editor doesn’t recognize this at all, and thus flags all uses of this bundle as warnings. Of course, the pages in question run just fine.

Yes, I’ve personally confirmed this and filed it as a bug.

Also JSF 1.2 support will come, but I don’t know what has been hard-confirmed for each release yet. I’m pushing on management who are in a marketing cycle right now to update the roadmaps and product plan a bit earlier than they were going to.

[arjan.tijms]

@support-rkalla wrote:

There’s a lot more actually. One thing we’re having problems with in MyEclipse is the global resource bundle definition. The MyEclipse editor doesn’t recognize this at all, and thus flags all uses of this bundle as warnings. Of course, the pages in question run just fine.

Yes, I’ve personally confirmed this and filed it as a bug.

Rkalla,

I personally don’t think this could be classified as a bug. The global (application wide) resource bundle was a new feature introduced with 1.2. Since you don’t support 1.2, it can’t possible be a bug in 1.1, can it? 😉

To quote from the Sun what’s new text at http://java.sun.com/developer/technicalArticles/J2EE/jsf_12/

New resource-bundle Configuration Element

Prior to version 1.2 of JavaServer Faces technology, page authors used the loadBundle tag to load a resource bundle into a page in order to reference localized data from a page. Page authors can still load resource bundles into a page using this method in version 1.2.

A new, more efficient way of loading resource bundles involves registering a resource bundle with the entire application by using a resource-bundle element in the application’s configuration file. The following resource-bundle element registers a ResourceBundle class named CustomMessages, which is in the resources package.

     <resource-bundle>
         <var>customMessages</var>
         <base-name>resources.CustomMessages</base-name>
     </resource-bundle>

[…]

The MyEclipse validator specifically has to recognize this new tag in faces-config to be able to validate JSF pages using this new bundle correctly.

[Riyad Kalla]

I personally don’t think this could be classified as a bug. The global (application wide) resource bundle was a new feature introduced with 1.2. Since you don’t support 1.2, it can’t possible be a bug in 1.1, can it? 😉

I like your interpretation better 🙂

(yes you are right, thanks for the text and link to clarify)

[guyr]

I found this old thread and I’m having trouble with editing support for resource-bundle JSF 1.2 is now officially supported ;). I’m running a Pulse version of 7.5.

I have the following in faces-config.xml:

<faces-config version="1.2"  ...>
  <application>
  <resource-bundle>
     <var>bundle</var>
    <base-name>com.jsfdemo.MessageBundle</base-name>
  </resource-bundle>
  </application>

I’ve got a red X next to the var line claiming it is an invalid element. If I switch to a JSP file and comment out the f:loadBundle tag, then the editor says “bundle cannot be resolved” everywhere I’ve used it.

However, if I “Run on MyEclipse Tomcat”, everything works fine; strings in the MessageBundle are correctly displayed. So this appears to be only an editing issue. Of course, I’d like to be able to use ctrl-space to pull up values from the message bundle.

I’d appreciate any pointers to get this working. BTW, if I use f:loadBundle, context assist works fine.

[support-joy]

Guy Rouillier,

The work around for the resource bundle issue is to use message-bundle tag instead of resource bundle tag. The syntax is as follows:
<message-bundle>
com.jsfdemo.MessageBundle
</message-bundle>
Try this and let me know.

[guyr]

Joy, thank you for the reply. Unfortunately, I’m not understanding how using message-bundle helps. The point of using resource-bundle is to define a global resource, so I don’t have to explicitly f:loadBundle on every page. message-bundle does not do that; I’d still need to add f:loadBundle to every page.

[guyr]

Just uncovered another variation of this issue. I tried the Facelets tutorial. With a facelet, even with the f:loadBundle tag, context assistance is not available on the bundle. I am getting context assistance on my Java classes, so I know that CA is working.

[support-joy]

Guy,

I have discussed the above with our dev team members. This is currently not supported by MyEclipse. I have notified the dev team.

Sorry for the inconvinience.

[Author]

Posts