Tuesday, May 27, 2014

Retrieve the signer certificates in Websphere 8.5

You can use the Retrieve from port option in the administrative console to retrieve the certificate and resolve the problem. If you determine that the request is trusted, complete the following steps:

1. Log into the administrative console.
 2. Expand Security and click SSL certificate and key management. Under Configuration settings, click Manage endpoint security configurations. 3. Select the appropriate outbound configuration to get to the (cell):A967DCOKNode01Cell:(node):A967DCOKNode01 management scope.
 4. Under Related Items, click Key stores and certificates and click the NodeDefaultTrustStore key store.
 5. Under Additional Properties, click Signer certificates and  Retrieve From Port.
 6. In the Host field, enter wmworldtst.cruises.princess.com in the host name field, enter 443 in the Port field, and wmworldtst.cruises.princess.com_cert in the Alias field.
 7. Click Retrieve Signer Information.
 8. Verify that the certificate information is for a certificate that you can trust.
 9. Click Apply and Save.

Wednesday, May 14, 2014

Useful Eclipse Plugins that didn't make it to the Top 10 list

http://blog.manupk.com/2012/01/useful-eclipse-plugins-that-didnt-made.html

Monday, May 5, 2014

org.hibernate.exception.ConstraintViolationException

Primary Key not matching or not set for update the object.

Friday, May 2, 2014

Error creating bean with name 'scopedTarget.xxyyzz.class'

 Root Cause:  org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scopedTarget.xxyyzz.class': Scope 'session' is not active for the current thread;

Consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

Use RequestContextListener  in wex.xml file.


org.springframework.web.context.request.RequestContextListener