[wciesiel]

Hi there,

I am working on a project where two separate web applications share a lot of common elements. Hence the need to create a “commons” project, holding components, templates, even resources like images and CSS stylesheets. And we’ve encountered a problem…

We’re creating JSF “components” using Facelets taglibs. Everything is working great apart of one thing, which is prohibiting us from taking full advantage of MyEclipse tools…

Situation look like this: let’s say we have two projects:
www-commons – containing xhtml templates, facelets taglibs, images, CSSes. This project is included as a JAR library to the www-app

www-app – an application containing proper web-context root, faces-config.xml etc. This app is deployed as a proper war.

The problem: managed bean definitions are in www-app but are referenced from xhtml facelets templates in www-commons. And in such config content assist is not working…

Any ideas how to achive the same results but be able to use content assist for EL references to managed beans?

And a bit off-topic: we’re using Spring beans as managed beans (using delegate variable resolver from spring framework) in our JSF application. It would be great if future MyEclipse releases would allow EL content assist in this case … Any chances?

Regards,
Wojtek

[Riyad Kalla]

Wojtek,

Those are actually pretty complicated resolution cases for the parsers at the moment and I’ve filed them both as future enhancements, but in the mean time I cannot offer any relief with that exact setup.

I don’t know if common changes infrequently enough that blending it back into the projects that use it at design-time to get the autocomplete would be helpful though. Sorry for the lackluster answer, I know keeping things separated at times like these are a big win organizationally, from a tooling perspective it can really be a trick though to get it exactly right.

[wciesiel]

@support-rkalla wrote:

Wojtek,
I don’t know if common changes infrequently enough that blending it back into the projects that use it at design-time to get the autocomplete would be helpful though.

Unfortunatelly it’s impossible in our scenario… From day one of this project we know that there’re gonna be two separate apps sharing a lot of elements. Both apps are being built simultaneously by sevaral people. Moving changes back and forth in such environment would be extremly mundane and error-prone job…

Is that really that difficult? I didn’t see the source codes but it _seemed_ that it might be not that problematic… But I understand that a lot of things might seem like this when looked from such perspective like mine 😉

Nevertheless – keep up a good work, MyEclipse is really a cool tool

[Riyad Kalla]

Is that really that difficult? I didn’t see the source codes but it _seemed_ that it might be not that problematic… But I understand that a lot of things might seem like this when looked from such perspective like mine 😉

Oh that’s not the issue, it just goes onto a list with 600 other things that have to be investigated whether it be new features, frameworks, etc. etc. I was hoping to get you a workaround that you could use right away.

[Author]

Posts