Databases
StackOverflow2013
Postsdbo
PObehavior for @PostConstruct exception handling in WebSphere
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PObehavior for @PostConstruct exception handling in WebSphere
    primarykey
    data
    text
    <p>Short: (Portlet-)Container swallows Exception thrown by @PostConstruct method in backing bean.</p> <p>Is this behavior intentional, a bug or container specific?</p> <p>Long: I am running a portlet on WebSphere Portal 7, where i force managed bean construction in a PhaseListener so it can send the user back to the start page, when the system encounters unrecoverable problems during Bean construction/post-construction.</p> <p>I am using the following code to 'force' construction:</p> <pre><code>@SuppressWarnings("unchecked") public static &lt;T&gt; T getManagedBean(final String beanName) { final FacesContext context = getFacesContext(); return (T)context.getApplication().evaluateExpressionGet(context, "#{" + beanName + "}", Object.class); } </code></pre> <p>I tested throwing a RuntimeException from the @PostConstruct method</p> <pre><code>@PostConstruct public void initialize() { throw new RuntimeException("test"); } </code></pre> <p>The stacktrace ends up on the RAD(Eclipse) log:</p> <pre><code>com.ibm.ws.webcontainer.annotation.WASAnnotationHelper doInvoke unable to invoke method --&gt; [initialize] on class --&gt; [foo.bar.UpdateAddress] java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.doInvokeSingle(WASAnnotationHelper.java:432) at com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.doInvokeChain(WASAnnotationHelper.java:400) at com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.doPostConstruct(WASAnnotationHelper.java:220) at com.sun.faces.vendor.WebSphereInjectionProvider.invokePostConstruct(WebSphereInjectionProvider.java:86) at com.sun.faces.mgbean.BeanBuilder.invokePostConstruct(BeanBuilder.java:225) ... Caused by: java.lang.RuntimeException: test at foo.bar.UpdateAddress.initialize(UpdateAddress.java:119) ... 121 more </code></pre> <p>But there is no exception to catch in my PhaseListener and it happily continues without being aware of an Exception during the @PostConstruct.</p> <p>Is this behavior intentional, a bug or container specific?</p> <p>It looks like at least JBoss has a similar way of handling : <a href="http://www.coderanch.com/t/499013/JSF/java/PostConstruct-exception-handling" rel="nofollow">http://www.coderanch.com/t/499013/JSF/java/PostConstruct-exception-handling</a></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USStefan
    1. USStefan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PObehavior for @PostConstruct exception handling in WebSphere
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PObehavior for @PostConstruct exception handling in WebSphere
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload