[Michael Flanakin]

When I open faces-config.xml, I get the following error:

Unable to locate JSF model extension file .faces-config.mex
A new file will be created to retain graphical layout data between modeling sessions.

Not sure if this is a problem or not, but I wanted to report it.

[support-michael]

The warning is benign. The faces-config.mex file stores the information of a navigation flow-diagram for the corresponding faces-config.xml file such as node layout and line routing info. Upon creation of a faces-config.xml file there is no .mex file. Upon 1st save the .mex file is created and referenced thereafter.

[Michael Flanakin]

Thanks. I kind of figured that after playing around with it.

There is a bug in the designer, tho. When you drag an existing JSP page (from the package explorer) to the editor, the default ID is the path with slashes. These slashes need to be replaced with either underscores or dashes. I’d say two underscores and maybe replace dots with dashes. For instance, “/admin/UpdateUser.jsp” could be changed to “admin__UpdateUser-jsp”.

[support-michael]

By ID do you mean the label of a flow-designer node?

Each node corresponds to a navigation-rule. The node’s label depicts the nav-rule’s <from-view-id> value. We can not change the <from-view-id>. So are you advocating a reformated label while the <from-view-id> value remains a slash delimited path? Help me understand.

[Michael Flanakin]

No, I’m suggesting that the <from-view-id> be changed. That’s the one that gave me the error. Well, there’s also the <to-view-id> to consider.

BTW, you’ll have to excuse me a little if I’m off – this is my first attempt at JSF.

[Author]

Posts