postconstruct

related to the commit in spring framework https://github.com/spring-projects/spring-framework/commit/5aefcc802ef05abc51bbfbeb4a78b3032ff9eee3 the initialisation is set to a later stage from afterPropertiesSet() to afterSingletonsInstantiated() In short : This prevents the caching to work when using it in a @PostConstruct use case. Longer version : This prevents the use case where you would create serviceB with @Cacheable on a methodB create serviceA with @PostConstruct calling serviceB.methodB @Component public class ServiceA{ @Autowired private ServiceB serviceB; @PostConstruct public void

I'm running with the following problem. I have a few Managed Beans that are shared between, at this moment, two JSF applications. As I don't want to copy and paste the code in the two (more in the coming future) I've put this shared managed beans inside a JAR library. I've followed this blog: http://jsflive.wordpress.com/2011/03/24/custom-component-library/ Well, even if I put the faces-config.xml inside JAR/META-INF/ the @ManagedBean and @ViewScoped didn't work. I couldn't realise why, but if I register the beans in faces-config.xml (JAR ones, not WAR ones) this problem goes away. I could

I have a product.xhtml and a ProductBean. I use /product/{id} to access the products so I have a viewParam in product.xhtml with value=ProductBean.id. The problem is that inside the bean I use an init function with a PostConstruct annotation in order to fill the details of the product. To do this I need the id to call an external function. I guess though that init is called before viewParam sets the id of the bean and therefore inside init I cannot call the external function because id is not set yet. What am I doing wrong and how do I fix this? UPDATE I found what was wrong. I think the

In the @PostConstruct doc it says about the annotated methods: "The method MUST NOT throw a checked exception." How would one deal with e.g. an IOException which can be thrown in such a method? Just wrap it in a RuntimeException and let the user worry about the faulty initial state of the object? Or is @PostConstruct the wrong place to validate and initialize objects which got their dependencies injected? Yes, wrap it in a runtime exception. Preferebly something more concrete like IllegalStateException . Note that if the init method fails, normally the application won't start. Generally, if

This question already has an answer here: @ViewScoped calls @PostConstruct on every postback request 1 answer I have a @ViewScope ManagedBean and a @PostConstruct initialisation method. This method is called when a new instance is created, but also on every ajax call. Why is this so? On an AJAX-call the init-Method is called and executed, but no changes are visible. For example if I change a property in the init-Method, this is only visible on instatiation and not for AJAX-calls. For AJAX-calls the value change is not persistent in the @ViewScoped Bean. Can anyone tell why this is so? How can

I'm using JSF 2.0 with GlassFish 3.0. I have the following Managed Bean: @ManagedBean @RequestScoped public class OverviewController{ private List<Event> eventList; @PostConstruct public void init(){ System.out.println("=> OverviewController - init() - enter"); System.out.println("=< OverviewController - init() - exit"); } } From the the overview.xhtml file I'm calling different attributes or methods from my OverviewController. <ui:repeat var="event" value="#{overviewController.eventList}"> ... </ui:repeat> Everything works just fine but the problem is on the Log File: INFO: Enter : RESTORE