ADFC-0619: Authorization check failed: User 'weblogic' does not have 'VIEW' permission on 'jsf.resourcesPageDef'

Issue : oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization check failed: User 'weblogic' does not have 'VIEW' permission on 'jsf.resourcesPageDef'.
 at oracle.adf.controller.internal.security.AuthorizationEnforcer.handleFailure(AuthorizationEnforcer.java:198) at oracle.adf.controller.internal.security.AuthorizationEnforcer.internalCheckPermission(AuthorizationEnforcer.java:166) at oracle.adf.controller.internal.security.AuthorizationEnforcer.checkPermission(AuthorizationEnforcer.java:120) at oracle.adfinternal.controller.state.ControllerState.checkPermission(ControllerState.java:913) at oracle.adfinternal.controller.state.ControllerState.synchronizeStatePart2(ControllerState.java:723) at oracle.adfinternal.controller.application.SyncNavigationStateListener.afterPhase(SyncNavigationStateListener.java:83) at oracle.adfinternal.controller.lifecycle.ADFLifecycleImpl$PagePhaseListenerWrapper.afterPhase(ADFLifecycleImpl.java:537) at oracle.adfinternal.controller.lifecycle.LifecycleImpl.internalDispatchAfterEvent(LifecycleImpl.java:120) at oracle.adfinternal.controller.lifecycle.LifecycleImpl.dispatchAfterPagePhaseEvent(LifecycleImpl.java:168) at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.dispatchAfterPagePhaseEvent(ADFPhaseListener.java:302) at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.afterPhase(ADFPhaseListener.java:88) at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.afterPhase(ADFLifecyclePhaseListener.java:53) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:489) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:225)


 Solution 

 Oracle SOA Suite 12c needs JDK Minium version JDK 1.6 but it does not support JDK 1.8. I Installed JDK 1.7 and it resolves the Issue.

Missing artifact org.aspectj:aspectjweaver:jar:1.8.0.M1 for spring 4.0.0

Problem When you upgrade pom version to Spring 4.0.0.RELEASE, it is prompting missing artifact org.aspectj:aspectjweaver:jar:1.8.0.M1

Solution

upgrade aspectjweaver 1.7.4 as 1.8.0 is not available.
1) org.aspectj aspectjweaver 1.7.4
2) Add the Aspect in the configuration false src/main/java src/main/webapp/schemas **/*.xsd src/main/resources/bindings false org.springframework spring-aspects true

nested exception is java.lang.incompatibleclasschangeerror org.springframework.asm.classvisitor

Problem BeanDefinitionStoreException Failed to read candidate component class nested exception is java.lang.incompatibleclasschangeerror org.springframework.asm.classvisitor Solution upgrade Spring all version to 4.0 Check the dependency version by the following command. mvn dependency:tree Change the Spring version by adding the dependenncy in the pom.xml org.springframework spring-core ${spring.version} org.springframework spring-web ${spring.version} org.springframework spring-webmvc ${spring.version} org.springframework spring-context ${spring.version} org.springframework spring-beans ${spring.version} org.springframework spring-aop ${spring.version} org.springframework spring-aspects ${spring.version} commons-collections commons-collections 3.2 org.springframework spring-oxm ${spring.version} org.springframework.ws spring-ws-core ${spring.ws.version} org.apache.ws.commons.schema XmlSchema 1.4.3 org.springframework spring-jms ${spring.version} org.aspectj aspectjweaver 1.7.4 org.hibernate hibernate-core 4.3.5.Final

ERROR 2003 (HY000): Can't connect to MySQL server on localhost (10061)

Problem : ERROR 2003 (HY000): Can't connect to MySQL server on localhost (10061) Solution : Start the mysql as service. "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld" --install-manual go to services.msc start the mysql as automatic

Format DateTime in Tibco BW

WSDL 2.0 VS WSDL 1.1

WSDL 2.0

1  1) WSDL 2.0 was designed to solve the interoperability issues found in WSDL 1.0/1.1 by using Improved SOAP v1.2 bindings

2   2) WSDL 2.0 permits fault messages to be declared within the interface element in order to facilitate reuse of faults across operations. If a fault occurs, it terminates whatever message sequence was indicated by the message exchange pattern of the operation,

     3) WSDL2.0 provides Support for additional message patterns (ex:  “Out – Multi In” could correspond to Register for Events, Receive 0-n Events 

     4) WSDL 2.0 Provides Better and more powerful fault handling notation, allowing clearer and easier reuse of WSDL segments within the WSDL file

     5) WSDL2.0 Support for interface inheritance.

      6)      RESTful services

RESTful services can be described fairly with the structure supported by WSDL 2.0. WSDL 2.0 provides a              better model for describing RESTful services than WSDL 1.1

However with WSDL 1.1,

RESTful services could also be defined using WADL (Web Application Description Language.

7) WS-I Basic Profile
            WS-I Basic Profile v1.1 provides guidance for using SOAP 1.1, WSDL 1.1, and UDDI 2.0

            WS-I Basic Profile v2.0 provides guidance for using SOAP 1.2, WSDL 1.1, UDDI 2.0, WS-Addressing, and               MTOM.

8)      Changes from WSDL 1.1 Specification

1)      target Namespace a required attribute of the definitions element in WSDL 2.0

2)      Message constructs are specified using the XML schema type system in the types element in WSDL 2.0

3)      No support for operator overloading in WSDL 2.0

4)      PortTypes renamed to interfaces. Support for interface inheritance is achieved by using the extends attribute in the interface element.

5)      Ports renamed to endpoints




    9) Differences between WSDL1.1 and WSDL 2.0:

tokenize() Usage to split the String in Tibco BW

Tokenize Usage in Tibco


Example

Input String  :  PS00007.ELEM~1,PS00012.ELEM~1

Output Expected
<ns0:POFLine>
<ns0:ProductPartNumber>PS00007.ELEM</ns0:ProductPartNumber>
<ns0:Count>1</ns0:Count>
</ns0:POFLine>
<ns0:POFLine>
<ns0:ProductPartNumber>PS00012.ELEM</ns0:ProductPartNumber>
<ns0:Count>1</ns0:Count>

</ns0:POFLine>

Steps
tib:tokenize($Start/root/param, ',')

output
 PS00007.ELEM~1
 PS00012.ELEM~1