[JBoss Seam] - Re: NullPointerException in D2DViewHandler.calculateRenderKi
by jalupa
Yes, I tried to combine JSF 1.2 with IceFaces and Facelets and came to the conclusion that this requires a lot of patching of IceFaces (despite Ted Goddard's claims elsewhere on this forum).
I encountered and investigated your problem:
Section 10.4.5 of the JSF 1.2 specification states that you must "provide a constructor that takes a single argument of the appropriate type (in casu ViewHandler), if you want that the custom implementation receives a reference to the implementation that was previously fulfilling the role."
The D2DViewHandler uses the "original" (id est the Default ViewHandler) ViewHandler in the calculateRenderKitId method, unfortunately, the D2DSeamFaceletViewHandler doesn't provide the aforementioned constructor, so the original view handler is never passed in this custom view handler, causing the NullPointerException (as we all know, constructors aren't inherited). The patch is trivial, however, when you patch this, you will run into other issues. See for example my post in "Seam doesn't play with ICEFaces".
Apparently the ICEFaces people don't seem to have a public bug tracking system (yet), ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001973#4001973
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001973
19 years, 3 months
[JBoss Seam] - Re: Seam coupling
by petemuir
Seam certainly decreases the amount of abstraction required, but not really by increasing the coupling, but by hiding most of the glue away in the framework (where it belongs) than in the business classes.
Seam means that the coupling between the business layer and the presentation layer is low (I mean at some point you have to actually connect the presentation layer and the business layer, no matter how many layers you put in the way).
I think it would be fair to say that Seam promotes a simple (i.e. very few layered) design, but still makes possible a traditional layered design (but be prepared for people to go What?? Why??? ;) ).
But I'm sure others can write this more eloquently than me :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001963#4001963
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001963
19 years, 3 months
[JBoss Seam] - Re: Logging using java.util.logging.*?
by SmokingAPipe
Yeah, I'll post this in some other forum. It is certainly a bug and it's very easily reproducible. I need to report it on some other forum. Virt. hosts are working fine. The only two problems I encountered were 1. Seam-managed persistence contexts were not being isolated between apps. I fixed this by using different SMPC names. And 2. Logging stops working entirely.
So I spent about 6 hours so far trying to get a simple log message to work in a virt. host. This isn't a problem with Seam or JBoss. It's a problem with Sun's logging implementation. Logging should be reliable and not sensitive to config settings.
I'm starting to think this is a Tomcat issue because even System.out.println isn't working. What this means is that maybe the console logger is working fine, but the console itself isn't working. I think I have seen this behavior before in Tomcat.
I should maybe write a JNDI logger that sends directly to console and is non-interceptable by anything at the Java layer. This really really should have been including with Sun Java, since the 1.4 days.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001962#4001962
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001962
19 years, 3 months