Skip to main content

jmaki and richfaces/a4j impossible ?

2 replies [Last post]
garyng
Offline
Joined: 2007-12-30
Points: 0

Hi,

I tried to see if jmaki can work together with richfaces/a4j(3.1.3) and got the following error :

31-Dec-2007 8:37:04 PM jmaki.runtime.jsf.AjaxWrapperPhaseListener getBinaryResource
SEVERE: AjaxWrapperPhaseListener Error: Could not load css/panel.xcss

Any hint on what to look at ? All I know is that richfaces basically use ajax4jsf which has its own filter that can cause all sorts of trouble, and added to that the facelets viewhandler, another source of trouble.

BTW, have been spending time for the past few days to check which JSF component framework works with which and my conclusion is that this JSF thing seems to be nothing like a spec(or it is too loose so everyone can have their imterpretation) as everyone one said we work with 'JSF x.x' yet putting them to work together is basically impossible. Even among the certain projects from within SUN.

jmaki + woodstock at least work(don't know if there are cases that fails).

May be Microsoft's 'monopoly approach is better. I thought .NET was bad until I have tried all these JSF thing :-)

BTW, among all these JSF stuff, I think jmaki is the only sensible one as all others require significant tie in in which case at least ASP.NET 2.0+ are much more polished than woodstock, richfaces, icefaces etc.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
garyng
Offline
Joined: 2007-12-30
Points: 0

> Hi,
> 31-Dec-2007 8:37:04 PM
> jmaki.runtime.jsf.AjaxWrapperPhaseListener
> getBinaryResource
> SEVERE: AjaxWrapperPhaseListener Error: Could not
> load css/panel.xcss
>
ok. this error is not actually an error. It is the Listener listen for things that is not belonging to jmaki. It is a requst by richfaces(the xcss extension).

now I am wondering, all these component frameworks now make use of the URL somehow for supplement info(the above for richfaces which got accidentally picked up by jmaki, and woodstock use /Theme/* for something else), it would be quite possible for them to step on each other's foot.

Shouldn't each allocate their own 'sub-url' and making it configuration a better way ?

Another interesting problem I also don't understand :

xmlns:a="http://jmaki/v1.0/jsp"
xmlns:ax="http://jmaki/v1.0/jsf"

If I use facelets, I must use 'http://jmaki/v1.0/jsf' or the widget would not be properly rendered. However, if I use plain jsp(still for JSF), this would give me some strange errors and I must use 'http://jmaki/v1.0/jsp'

don't know the difference between the two though.

garyng
Offline
Joined: 2007-12-30
Points: 0

ok, taking out facelets, at least I have this error go away and the dojo datepicker shown.

But the richfaces' ajax function no longer work :-(

Looks like even though there are many people praising facelets, it has lots of trouble in this ajax world. But the question becomes, what templating solution can work as sitemesh which is a nice solution also has lots of trouble with JSF and development seems to be stalled too.