Dileep Kumar Rongali

Hi, Here I would like to explain one use case to remove Leading and Trailing spaces from input text. Use case: On tab out of input text box, leading and trailing spaces should be removed. To implement this use case I have written custom converter which will do this work. But I need to refresh my component inside the converter code in order to reflect the changes on tab out. There are many use ways to implement this. Below is my way. Create Custom Converter class by implementing javax.faces.convert.Converter import javax.faces.component.UIComponent; import javax.faces.context.FacesContext; import javax.faces.convert.Converter; import org.apache.myfaces.trinidad.context.RequestContext; public class TrimEndSpacesConverter implements Converter{     public TrimEndSpacesConverter() {         super();     }          public Object getAsObject(FacesContext facesContext, UIComponent uiComponent, String string)...

javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider I got below error while deploying my webCenter project to the integrated weblogic server. Reason: Due to unwanted jars in the project Library and classpath. Solution: Remove unwanted jar from the libraries and classpath. In my case weblogic.jar is present. javax.xml.ws.WebServiceException: javax.xml.ws.WebServiceException: java.lang.InstantiationException: weblogic.wsee.jaxws.client.async.AsyncTransportProvider        at weblogic.wsee.jaxws.WLSInstanceResolver.getSingleton(WLSInstanceResolver.java:36)        at weblogic.wsee.jaxws.WLSInstanceResolver.start(WLSInstanceResolver.java:55)        at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.start(WLSInstanceResolver.java:82)      ...

Failed to load weblogic client internal deployment descriptor. java.io.IOException. If you are getting above error while making web service call in your java code. The cause might be with missing classes in your project path. In my case, I am trying to make web service call through java class and I got the above issue. To fix the issue, I have added wseeclient.jar to the project class path. I am using IDE JDeveloper to run my main java class. And this jar will be present in below path in my case. C:\Oracle\Middleware\wlserver_10.3\server\lib 

<Sep 6, 2015 4:21:30 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638 > <Sep 6, 2015 4:21:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141268]Parsing Failure in config.xml on line 1, column 1: Content is not allowed in prolog.> <Sep 6, 2015 4:21:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> <Sep 6, 2015 4:21:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down> <Sep 6, 2015 4:21:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN> Process exited. If you are getting above error means, Jdeveloper is not closed properly. And config.xml is corrupted. Deleting DefaultDomain fold...

Many might have faced this situation while fixing bugs in ADF application. There will be one main application and it uses task flows or classes from different shared libraries. For example there is an issue in one shared library, to fix that we just run that particular project/application and try to fix the issue in that shared library project. But if the application is ADF security enabled then it is little difficult to perform exact test cases what we do when it is integrated with main application after fix. Because all the security settings are in main application jazn-data.xml file. We can disable security for a while and test the application. But it is not a good idea. Because by disabling security we are not doing full testing at all. So how to overcome this situation?   There is a sample way. We can create some dummy test users and test roles in development weblogic server. These test roles names should be same as the one we defined in jazn-data.xml in...

oracle.jbo.InvalidOperException: JBO-25221: Method EmployeeAppModuleDataControl.dataProvider.getEmployees() not supported For above issue there could be several reasons.    1)   Check in the method binding any special html characters are present. Because ADF bindings does not support generics. So for example the input value for client method has generics, there are chances that in the pageDef method binding might have special hmtl character when we drag and drop the client method in page or page fragment. We can remove those special characters to resolve the issue. For more information refer to https://community.oracle.com/message/4304798     2)   Second reason could be if AM client method and pageDef method binding not in sync. Whenever we modify client method in AM, we need to update the same in pageDef method binding also. Otherwise it will give above error.    3)   If none of the above are causing the issue then...