Can WebLogic 12C support Camel 2.10?

I have been trying to implement Camel 2.10 with Weblogic 12C without success.
The exact .ear file can be implement on Weblogic 10.3 without any issues.
I have tried sourcing for solutions but it seems that there are very limited resource pertaining to issue that i have encountered.
Can anyone tell me if weblogic 12C supports Camel 2.10 in the first place?
Edited by: 965266 on Oct 14, 2012 8:29 PM

2.1 is the latest JSF version supported by recent
WLS 12.1.3 product release.
EJB 3.1 is supported in all 12.x release of WLS
Please check the below doc
What's New in Oracle WebLogic Server
Hope this helps!!
regards,
Vijaya

Similar Messages

Did Weblogic 12C support the Oracle Forms11gR2

Hi,
Did Weblogic 12C(12.1.1.0.0) support the Oracle Forms 11g R2(11.1.2.0.0).
Regards,
user

Make the discussion at the end of this post (http://middlewaremagic.com/weblogic/?p=7716) gives you some insight.

Does weblogic 12c support beehive controls

Hi ,
we are migrating our weblogic server from 10.3 to 12C , i just import existing project into eclipse(Oracle enterprise pack for eclipse) came with weblogic 12C , it is showing errors on project for shared libraries like beehive controls , weblogic controls ,
Please let us know does WLS 12C support beehive controls ? do we have any solution for this
Regards
Srikanth

Apache Beehive is not supported on Weblogic 12c.
Apache Beehive has been deprecated as of WebLogic Server 10.3.
Oracle recommends that you migrate your Beehive applications and infrastructure to other frameworks such as Oracle's ADF or Java Server Faces at your earliest convenience.
Please check the below Doc and Page No. 16.
http://docs.oracle.com/cd/E12839_01/web.1111/e13852.pdf
Hope this answers your question!!
Thanks,
Vijaya
Edited by: Vijaya_Gopal on May 1, 2013 8:01 PM

Why can't Weblogic 12c find Managed Bean by annotation,which in a jar?

the detail:
why can't Weblogic 12c find Managed Bean by annotation,which in a jar?

Hi,
I got the same problem with weblogic 12c.
Somehow this guy got it working by using CDI and creating an empty beans.xml, it did not work for me.
i found the tricky problem is that should put a empty but include the <beans> tag beans.xml file.
http://www.coderanch.com/t/562233/JSF/java/WebLogic-Eclipse-Indigo-develop-JSF
I also tried to skip managedbean and use CDI ( @named ) but then I get some jboss weld exceptions on the value attribute of some jsf components.
I also saw this post
Can't seem to get a trivial CDI example to work on Weblogic 12c
I don't use OEPE very often so I'll need to kick this around a little when I get a chance.
Just as an out there kind of thought, OEPE does use the split-directory model for deployment by default -- perhaps try adjusting it to use the exploded archive model instead, just as a test to see if it removes the error?
Right click the server config and select Properties > WebLogic > Publishing > Publish as exploded archive
It seems like the Virtual Application deployment model of OEPE doesn't support CDI.
thanks
Edited by: Edwin Biemond on Dec 28, 2011 10:07 PM
Edited by: Edwin Biemond on Dec 28, 2011 10:25 PM

OSB installed in WebLogic 12C - when it will be supported

As I believed that OSB is nothing more than a webaplication with specific tables in Oracle database I imagined that I could try to install OSB in WebLogic12C. Maybe I am telling a stupid thing because I can see that after installed OSB, there is a specific new server on WebLogic console.
Anyway, even if it was right, there a huge difference between I installed locally to test and I confirmed to do this without comercial support. Then, my question is: Is there some prediction about OSB, OER, OSR (SOA tools) be supported in WebLogic 12C? The more important for me is OSB.
Other question is: is there some prediction about new version of OSB? If so, this probably will work by default at weblogic 12c.

Anyway, even if it was right, there a huge difference between I installed locally to test and I confirmed to do this without comercial supportYou are correct. As Abhishek has already mentioned, OSB is not merely a web-app and it is tightly integrated with Weblogic app server. So there is no meaning putting any effort to try to get it work on Weblogic 12c.
Is there some prediction about OSB, OER, OSR (SOA tools) be supported in WebLogic 12C? The more important for me is OSB.It is too early to talk about 12c but yes, all these products will be part of OFMW 12c.
Other question is: is there some prediction about new version of OSB? If so, this probably will work by default at weblogic 12c.The next version of OSB will be 11g R1 patch set 6 (11.1.1.7) and hence it will only be certified with Weblogic 10.3.7
Regards,
Anuj

What is the supported version of Oracle Enterprise Quality Data for WebLogic 12c

Hi All,
The recent release of Oracle Enterprise Data Quality is 11.1.1.6.1 for which supported weblogic server is WebLogic 10.3.6
Can anyone tell me that if WebLogic 12c also is a supported version for Oracle Enterprise Data Quality 11.1.1.6.1 and if no, then which version of Oracle Enterprise Data Quality is supported on WebLogic 12c (12.1.2)
Its really urgent.Please guide!
Thanks in Advance!

Hi,
Thanks But I already followed this link and I forgot to mention that I am looking for the supported version of Oracle Enterprise Data Quality for Product Data for Oracle WebLogic 12.1.2. In the certification matrix of Oracle Enterprise Data Quality for Product Data 11g it is listed that the supported weblogic version is 10.3.6. So I wanted to know which version of Oracle Enterprise Data Quality for Product Data would support weblogic 12.1.2 or if Oracle Enterprise Data Quality for Product Data 11g is supported on weblogic 12.1.2 also.
I checked the certfication matrix for Oracle Enterprise Data Quality for Product Data 11g from Oracle Fusion Middleware Supported System Configurations link only.
Please suggest!

Where You can create a support case for weblogic server?

Hi all,
I would like to know where I can create a support case for weblogic server?
I logged me in metalink3 but I did not found a way to create a service request for WLS.
Thanks in Advance.

I believe you still need to use BEA's support resources at this point: http://www.oracle.com/bea/support.html

Weblogic 12c not picking up persistence unit in WAR

I'm trying to get an example CRUD application to run on WebLogic 12c (for the app see: http://henk53.wordpress.com/2012/04/15/jsf2-primefaces3-ejb3-jpa2-integration-project/)
So far the applications runs on JBoss AS 7.1, GlassFish 3.1.2 and TomEE beta 2. In all those application servers persistence.xml is picked-up, and processed so I'm at a loss what's wrong with WebLogic. I'm using Eclipse 3.7.2 and the Oracle WebLogic 12C WTP server adapter for the deployment.
I'm getting the following exception:
java.lang.IllegalArgumentException: No persistence unit named 'entityManager' is available in scope jsf_ejb_jpa. Available persistence units: []
     at weblogic.persistence.ModulePersistenceUnitRegistry.getPersistenceUnit(ModulePersistenceUnitRegistry.java:130)
     at weblogic.persistence.BasePersistenceContextProxyImpl.<init>(BasePersistenceContextProxyImpl.java:40)
     at weblogic.persistence.TransactionalEntityManagerProxyImpl.<init>(TransactionalEntityManagerProxyImpl.java:31)
     at weblogic.persistence.EntityManagerInvocationHandlerFactory.createTransactionalEntityManagerInvocationHandler(EntityManagerInvocationHandlerFactory.java:20)
     at weblogic.persistence.PersistenceManagerObjectFactory.createPersistenceContextProxy(PersistenceManagerObjectFactory.java:66)
     at weblogic.persistence.PersistenceManagerObjectFactory.getObjectInstance(PersistenceManagerObjectFactory.java:31)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:251)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
     at weblogic.j2eeclient.java.ClientReadOnlyContextWrapper.lookup(ClientReadOnlyContextWrapper.java:35)
     at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at javax.naming.InitialContext.doLookup(InitialContext.java:265)
     at com.oracle.pitchfork.inject.Jsr250Metadata.jndiLookup(Jsr250Metadata.java:307)
     at com.oracle.pitchfork.inject.Jsr250Metadata.resolveByName(Jsr250Metadata.java:303)
     at com.oracle.pitchfork.inject.Jsr250Metadata.resolve(Jsr250Metadata.java:266)
     at com.oracle.pitchfork.inject.Jsr250Metadata.applyInjections(Jsr250Metadata.java:228)
     at com.oracle.pitchfork.inject.Jsr250Metadata.inject(Jsr250Metadata.java:219)
     at com.oracle.pitchfork.spi.BaseComponentBrokerImpl.getBean(BaseComponentBrokerImpl.java:63)
     at com.oracle.pitchfork.spi.EjbComponentCreatorBrokerImpl.getBean(EjbComponentCreatorBrokerImpl.java:33)
     at weblogic.ejb.container.injection.EjbComponentCreatorImpl.getBean(EjbComponentCreatorImpl.java:76)
     at weblogic.ejb.container.manager.BaseEJBManager.createNewBeanInstance(BaseEJBManager.java:209)
     at weblogic.ejb.container.manager.BaseEJBManager.allocateBean(BaseEJBManager.java:235)
     at weblogic.ejb.container.manager.StatelessManager.createBean(StatelessManager.java:293)
     at weblogic.ejb.container.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:185)
     at weblogic.ejb.container.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:114)
     at weblogic.ejb.container.manager.StatelessManager.preInvoke(StatelessManager.java:174)
     at weblogic.ejb.container.internal.BaseLocalObject.getBeanInstance(BaseLocalObject.java:146)
     at weblogic.ejb.container.internal.BaseLocalObject.preInvoke(BaseLocalObject.java:103)
     at weblogic.ejb.container.internal.BaseLocalObject.__WL_preInvoke(BaseLocalObject.java:67)
     at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:20)
     at com.example.dao.jpa.JpaUserDAO_wrkew_UserDAOImpl.add(Unknown Source)
     at com.example.backing.IndexBacking.addUser(IndexBacking.java:38)
Notice that "entityManager" is the name of the instance variable in which injection is being performed:
@PersistenceContext(name="example")
private EntityManager entityManager;
If I rename this variable to "em: as follows:
@PersistenceContext(name="example")
private EntityManager em;
Then, lo and behold, the exception changes into:
java.lang.IllegalArgumentException: No persistence unit named 'em' is available in scope jsf_ejb_jpa. Available persistence units: []
As the example uses a data-source defined in web.xml, which is only marginally supported in most application servers, I tried to define a WebLogic specific application scoped data-source instead and let the persistence unit use that. I couldn't find a way to do this in a .war (is this even possible?), so I created an .ear archive instead. When deploying the EAR, the data-source is clearly being created, but I'm getting the same exception again.
I finally created an EJB module with a persistence.xml and a simple Singleton that's injected with the entityManager, and added that to the EAR. This works for the EJB module, but in the web module injection of the other entity manager still fails.
Any idea what might be the problem?

After some more fiddling, I discovered it's not WebLogic itself that's at fault here, but most likely Oracle's WTP adapter. Apparently it doesn't include persistence.xml in the archive that gets deployed. When I export the project as an .ear archive and copy this to WebLogic's autodeploy directly, things do work.
I tried to find out what the main difference was between the deployments, but I could not find where the Oracle WTP adapter creates the deployment. I tried to test where a resource inside the EAR resides on the filesystem via the following code inside a backing bean:
URL url = Thread.currentThread().getContextClassLoader().getResource("com/example/backing");
It looks like there isn't a real .war or .ear being created and deployed, but there's a link back to the workspace, as the URL resolves to:
file:/Users/henk/eclipse37ee/workspace/jsf_ejb_jpa/build/classes/com/example/backing/
If I execute the same code for the ear in the autodeploy folder, the URL resolves to some jar inside:
/Users/henk/eclipse37ee/wls1211_dev/mydomain/servers/myserver/tmp/_WL_user/_appsdir_jsf_ejb_jpa_ear_ear/2jzks6/war/WEB-INF/lib/
In case of the WTP 'deployment' linking back to the Eclipse workspace, META-INF/persistence.xml is actually there too, but for some reason Weblogic can't find it there?
Edited by: Henk on Apr 29, 2012 2:57 PM

Error invoking WebService in Eclipse with WebLogic 12c plugin

I am using Eclipse Indigo with WebLogic 12c plugin to create a standalone WebService Client which invokes a simple WebService. The WebService is protected by Security Policies Wssp1.2-2007-Wss1.0-X509-Basic256.xml and Wssp1.2-SignBody.xml.
I get the following exception when I run the standalone client:
h2. Exception in thread "main" java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider weblogic.wsee.jaxws.spi.WLSProvider could not be instantiated: java.lang.ExceptionInInitializerError
The same program works fine using JDeveloper 11g but not in Eclipse Indigo or in Juno. Has anyone faced this issue?
Thanks,
Madhav

The stand-alone client JAR file does not, however, support invoking Web services that use the following advanced features:
Web services reliable SOAP messaging
Message-level security (WS-Security)
http://docs.oracle.com/cd/E14571_01/web.1111/e13760/client.htm#i229632
Can you try running by adding weblogic.jar. but if you run the client inside the wls Server it should work.
Regards,
Sunil P

Override Spring jar in Weblogic 12c

Hi Folks,
We have been facing an issue while overriding the Spring jar in Weblogic 12c. Basically we need to write a bean based on some 3rd party API calling their interfaces. Now they use Spring 2.5 jar for their own implementation. Since Weblogic inherently supports Spring 3.0 jar. As a result when we write our bean wrapping their interfaces and deploy it, it doesn't work. We replicated the issue by replacing Spring 2.5 jar with Spring 3 in local environment.
If we modify the server classpath to load the Spring 2.5 jar (preceding Spring 3.0), entire soa-infra application goes down, so what We wanted to know if it is possible to override the Spring jar only for our application itself? While loading the application it will override the Spring 3.0 jar with Spring 2.5 in the application context but server will keep using Spring 3.0?
Any ideas/suggestions highly appreciated!
Thanks,
Bhaskar

Hi Bhaskar,
have you tried packing the Spring libraries in your application and using the Filterring Classloader? Maybe this links can help you :
Understanding WebLogic Server Application Classloading
http://docs.oracle.com/cd/E24329_01/web.1211/e21049/weblogic_xml.htm#WBAPP601
http://stackoverflow.com/questions/11476874/weblogic-10-3-5-overriding-spring-version
best regards, Nicolas

CDI not working in Weblogic 12c Embedded EJB Container?

Hi,
we are trying to use embedded ejb container from weblogic 12c (12.1.2.0) for our junit tests.
As our application is running in weblogic 12c, we would like to run our tests in same environment.
But we encountered two problems, which brings me to the conclusion that CDI is not working correctly in embedded ejb container.
1. CDI Interceptor are not working
2. CDI Objects (@Inject) are null
I can provide an error message, which I think is thrown, when container tries to access the interceptor, because if I delete the interceptors the error message gets no longer thrown:
Caused by: java.lang.UnsupportedOperationException: authenticatedLookup is unavailable for BasicNamingNode types
      at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:234)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:463)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:274)
      at weblogic.jndi.internal.ServerNamingNode_12120_WLStub.authenticatedLookup(UnknownSource)
      at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:483)
We just want to know, if CDI is not working in embedded ejb container, so we can go ahead and look for another solution for our junit tests.
Stefan

Hi There,
If you have access to Oracle Support Portal, please go through below Knowledge Articles which can provide more information on your requirement:
Sample Application Using Timer API (CommonJ) to configure Timer Based tasks in Oracle WebLogic Cluster 10.3.X Cluster (Doc ID 1614886.1)
Clustered EJB Timer - The minimum time for recurring execution of a timer (Doc ID 1931091.1)
Let us know if it helps.
Cheers,
Naveen

Upgrading to weblogic 12c issue with JSF

Migrating to the Weblogic 12c faced so many issue with the shared class library. After fixing all the issue stuck with JSF and on google everywhere it was mentioned error happening due to multiple JSF version colliding.
My whole application works like a charm in 10.3.6 but same app not working after updating the spring 4 and hibernate 4.
This is the error I am receiving below errors ...
<javax.enterprise.resource.webcontainer.jsf.application> <BEA-000000> <JSF1029: The specified InjectionProvider implementation 'com.bea.faces.WeblogicInjectionProvider' does not implement the InjectionProvider interface. >
1. Cause: Unable to create a new instance of 'org.springframework.web.jsf.DelegatingVariableResolver': javax.faces.FacesException: org.springframework.web.jsf.DelegatingVariableResolver
2. Cause: Unable to create a new instance of 'org.springframework.web.jsf.DelegatingVariableResolver': javax.faces.FacesException: org.springframework.web.jsf.DelegatingVariableResolver
    at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(Unknown Source)
    at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(Unknown Source)
    at com.sun.faces.config.processor.ApplicationConfigProcessor.process(Unknown Source)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(Unknown Source)
    at com.sun.faces.config.processor.LifecycleConfigProcessor.process(Unknown Source)
    Truncated. see log file for complete stacktrace
Caused By: javax.faces.FacesException: org.springframework.web.jsf.DelegatingVariableResolver
    at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(Unknown Source)
    at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(Unknown Source)
    at com.sun.faces.config.processor.ApplicationConfigProcessor.addVariableResolver(Unknown Source)
    at com.sun.faces.config.processor.ApplicationConfigProcessor.process(Unknown Source)
    at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(Unknown Source)
    Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: org.springframework.web.jsf.DelegatingVariableResolver
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
    Truncated. see log file for complete stacktrace
3. ]] Root cause of ServletException.
java.lang.IllegalStateException: Could not find backup for factory javax.faces.context.FacesContextFactory.
    at javax.faces.FactoryFinderInstance.getFactory(Unknown Source)
    at javax.faces.FactoryFinder.getFactory(Unknown Source)
    at javax.faces.webapp.FacesServlet.init(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:299)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:250)
    Truncated. see log file for complete stacktrace
4.Error> <javax.faces> <BEA-000000> <Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup.>
<Error> <javax.enterprise.resource.webcontainer.jsf.config> <BEA-000000> <Unexpected exception when attempting to tear down the Mojarra runtime
java.lang.IllegalStateException: Could not find backup for factory javax.faces.application.ApplicationFactory.
    at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:1010)
    at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:342)
    at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:141)
    at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:583)
    Truncated. see log file for complete stacktrace
I had the classloader from weblogic but unable to find if there is anything related with Multiple JSF versions colliding. Here is the classloader log
**System Classloaders**
Type: sun.misc.Launcher$ExtClassLoader
HashCode: 1956433926
Classpath:
/C:/Java/jdk1.7.0_45/jre/lib/ext/access-bridge-64.jar
/C:/Java/jdk1.7.0_45/jre/lib/ext/dnsns.jar
/C:/Java/jdk1.7.0_45/jre/lib/ext/jaccess.jar
/C:/Java/jdk1.7.0_45/jre/lib/ext/localedata.jar
/C:/Java/jdk1.7.0_45/jre/lib/ext/sunec.jar
/C:/Java/jdk1.7.0_45/jre/lib/ext/sunjce_provider.jar
/C:/Java/jdk1.7.0_45/jre/lib/ext/sunmscapi.jar
/C:/Java/jdk1.7.0_45/jre/lib/ext/zipfs.jar
Type: sun.misc.Launcher$AppClassLoader
HashCode: 345487281
Classpath:
/C:/Oracle12c/Middleware/modules/features/weblogic.server.modules_12.1.1.0.jar
/C:/Oracle12c/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar
/C:/Oracle12c/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar
/C:/Oracle12c/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar
/C:/Oracle12c/Middleware/patch_wls1211/profiles/default/sys_manifest_classpath/weblogic_patch.jar
/C:/Oracle12c/Middleware/wlserver_12.1/common/derby/lib/derbyclient.jar
/C:/Oracle12c/Middleware/wlserver_12.1/server/lib/weblogic.jar
/C:/Oracle12c/Middleware/wlserver_12.1/server/lib/weblogic_sp.jar
/C:/Oracle12c/Middleware/wlserver_12.1/server/lib/webservices.jar
/C:/Oracle12c/Middleware/wlserver_12.1/server/lib/xqrl.jar
/C:/Program%20Files/Java/jdk1.7.0_45/lib/tools.jar
Type: weblogic.utils.classloaders.GenericClassLoader
HashCode: 1277718374
Classpath:
**Application Classloaders**
Type: weblogic.utils.classloaders.FilteringClassLoader
HashCode: 929366372
Filter: [antlr.*, antlr.collections.*, antlr.collections.impl.*, antlr.debug.misc.*, com.sun.activation.*, com.sun.istack.*, com.sun.mail.*, com.sun.xml.*, org.apache.commons.*, org.joda.time.*, org.apache.xalan.*, org.apache.xml.*, org.apache.wml.*, org.apache.xerces.*, org.apache.xpath.*, com.ctc.wstx.*, org.slf4j.*, javax.faces.*, com.sun.faces.*, com.bea.faces.*, com.sun.el.*, javax.el.*, javassist.*]
Classpath: empty
Type: weblogic.utils.classloaders.GenericClassLoader
HashCode: 2137066604
Classpath:
**Type: weblogic.utils.classloaders.FilteringClassLoader**
HashCode: 1212049573
Filter: []
Classpath: empty
Type: weblogic.utils.classloaders.ChangeAwareClassLoader
HashCode: 1604673952
Classpath:
C:\s-ear-1.0-SNAPSHOT_4
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\classes
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\FastInfoset-1.2.12.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\_wl_cls_gen.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\acegi-security-1.0.7.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\activation-1.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\activation.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\antlr-2.7.7.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\aopalliance-1.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\aspectjrt-1.8.5.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\aspectjweaver-1.8.5.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\backport-util-concurrent-3.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\bcprov-jdk16-140.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\cacauth-2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\camel-core-2.5.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\camel-josql-2.5.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\caps-handshake-3.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\caps2-liquibase-1.0-SNAPSHOT.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\caps2domain-1.0-SNAPSHOT.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\caps2util-1.0-SNAPSHOT.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\cloning-1.7.4.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-beanutils-1.8.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-codec-1.9.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-collections-3.2.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-dbcp-1.4.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-digester-2.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-httpclient-3.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-io-1.4.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-lang-2.4.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-logging-1.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-logging-api-1.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-management-1.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\commons-pool-1.5.4.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\dom4j-1.6.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\gentlyweb-utils-1.5.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\hibernate-commons-annotations-4.0.4.Final.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\hibernate-core-4.2.18.Final.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\hibernate-entitymanager-4.2.18.Final.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\hibernate-jpa-2.0-api-1.0.1.Final.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\hibernate-validator-4.2.0.Final.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\icefaces-3.2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\icefaces-ace-3.2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\icefaces-compat-3.2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\icepush-3.2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\itext-4.2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\itextpdf-5.0.6.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jackson-core-asl-1.9.9.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jackson-core-lgpl-1.9.9.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jackson-mapper-asl-1.9.9.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jasperreports-ca-4.8.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\javassist-3.18.2-GA.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\javax.el-api-2.2.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\javax.faces-2.2.9.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\javax.inject-1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jax-qname.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jaxb-api-2.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jaxb-api.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jaxb-impl-2.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jaxb1-impl.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jaxp-api.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jaxws-api-2.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jboss-archive-browsing-5.0.0alpha-200607201-119.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jboss-logging-3.1.3.GA.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jboss-logging-annotations-1.2.0.Beta1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jboss-transaction-api_1.1_spec-1.0.1.Final.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jcl-over-slf4j-1.5.2.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jersey-bundle-1.18.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\joda-time-2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\joda-time-hibernate-1.3.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\josql-1.5.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\josql-2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\json-20140107.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jsr173_1.0_api.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jsr250-api-1.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jsr311-api-1.1.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jstl-1.2.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\jta-1.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\log4j-1.2.14.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\mail-1.4.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\mail.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\objenesis-1.2.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\opencsv-1.7.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\oro-2.0.8.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\portlet-api-2.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\primefaces-3.4.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\quartz-1.8.4.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\saaj-api-1.3.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\saaj-api.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\saaj-impl.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\serializer-2.7.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\serializer.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\service-1.0-SNAPSHOT.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\servlet.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\slf4j-api-1.5.2.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\slf4j-log4j12-1.5.2.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-aop-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-aspects-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-beans-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-context-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-context-support-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-core-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-expression-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-jdbc-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-jms-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-orm-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-oxm-3.0.5.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-security-core-4.0.0.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-tx-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-web-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-webmvc-4.0.9.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-ws-core-2.0.0.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-ws-security-2.0.0.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\spring-xml-2.0.0.RELEASE.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\stax-api-1.0-2.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\3capture-1.0.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\s-beans-1.0-SNAPSHOT.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\usertype.core-3.1.0.CR10.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\usertype.jodatime-1.9.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\usertype.spi-3.1.0.CR10.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\validation-api-1.0.0.GA.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\wss4j-1.5.8.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xalan-2.7.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xercesImpl-2.8.1.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xercesImpl.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xml-apis.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xmldsig.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xmlsec-1.4.3.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xmlsec.jar
C:\s-ear-1.0-SNAPSHOT_4\war\WEB-INF\lib\xws-security-3.0.jar
jsf myfaces weblogic1
Here are links for more details.
http://stackoverflow.com/questions/29857571/weblogic-12c-java-lang-illegalstateexception-could-not-find-backup-for-factory
http://www.coderanch.com/t/649308/JSF/java/Faces-Servlet-failed-preload-startup
Sorry incase question not formatted. Any suggestions appreciated.

hi.
I had faced this behavior on weblogic 12c(12.1.1).
Maybe This problem was solved by 12.1.2.
But, when text item submitted together with a upload file, multibyte characters was garbage characters.
See Multibyte character was garbage characters, when multipart requested (Multipartリクエストで文字化けが発生する) on WebLogic12(12.1.2.0)

Weblogic 12c exam

Does any one know answers for the below questions ??
Question 1: Which four of the following NOT included in Weblogic lighter version (WLS Zip Distribution for only development)
A. JVM
B. Webserver plug-in
C. Samples
D. Smart update
E. Deployment plan
Question 2: A WebLogic team is developing an enterprise application from their desktop WebLogic environment. All development systems are connected to the same eight data sources for testing. As a WebLogic Administrator supporting this team, which two actions should you perform to free the developers from creating and configuring all the data sources on their desktop WebLogic environment?
A. Provide the team with a WebLogic domain template with the testing data sources configured.
B. Provide the development team with a preconfigured domain archive file.
C. Provide the development team with the [datasource] -jdbc.xml file to overwrite their local copy.
D. Create the data sources on behalf each of the developer.
E. Provide the development team with WLST scripts to create and configure the testing data sources.
Question 3: What are the three steps you should take to tune a JDBC Connection pool in WebLogic from the initial settings in a production environment?
A. Ensure the maximum size is increased to an appropriate setting.
B. Set the minimum and maximum size of the connection pool to the same value.
C. Increase the statement cache size.
D. Add more heap to the JVM.
E. Add more nodes to the cluster.
Question 4: A customer needs to ensure that the number of threads servicing an application does not exceed the number of database connections available to the application. What step must you take to address this situation?
A. Configure a Max Threads Constraint and add your application to the list of applications for the Constraint.
B. Configure a Work Manager with a Maximum Threads Constraint tied to the Connection Pool and configuration your application to use the Work Manager.
C. Configure a Work Manager with a Minimum Threads Constraint tied to the Connection Pool and configure your application to use the Work Manager.
D. Configure a global MaxThreads constraint and target it to the server or clusters where your application is deployed.
E. Configure the startup parameter "-Dwls-maxThreads" to be the same as the number of database connections configured.
Question 5: In a Java EE messaging application, one MDB is consuming a lot of memory at high traffic. What configuration should you use to prevent possible out-of-memory error at high traffic and at the same time not losing messages?
A. Configure a Work Manager for the MDB with a Maximum Thread Constraint.
B. Configure a Work Manager for the MDB with a Minimum Thread Constraint.
C. Configure a Work Manager for the MDB with a Maximum Thread Constraint and a Capacity Constraint.
D. Configure a Work Manager for the MDB with a Minimum Thread Constraint and a Capacity Constraint.
E. Configure a Work Manager for the MDB with both a Maximum Thread Constraint and Minimum Thread Constraint.
Question 6: An airline is building a booking system for its premium and general customers. The goal is to ensure premium members are given higher access priority when user traffic is high.
What configuration will achieve this goal?
A. Configure a Work Manager for premium users with a Minimum Thread Constraint.
B. Configure a Work Manager for premium users with a higher fair-share-request-class.
C. Configure a Work Manager for premium users with a higher response-time-request-class.
D. Configure a Work Manager general users with a Maximum Thread Constraint.
E. Configure a Work Manager for premium users with a custom request-class.
Question 7: Which WebLogic optimization allows one non-XA resource to participate in a distributed transaction?
A. enabling Pinned to Thread
B. enabling Logging Last Resource
C. increasing the Statement cache size
D. setting the statement cache type to LRU
E. setting the initial and maximum capacity to the same number
Question 8: You deploy two different applications to the WebLogic container. One application use Xerces parser version A and the other application uses Xerces parser version B. Both these versions are different from the parser version that the WebLogic server uses internally. You want to use the Filtering Classloader feature to solve this problem. What action would you take to generate proper filtering Classloader entries?
A. Modify the applications to use the same version that WebLogic uses internally.
B. Based on available examples of Filtering Classloader entries, try to modify get the proper entries.
C. Deploy and use the Classloader Analyzing Tool to resolve all conflicts with conflicting libraries. This tool will generate all proper entries.
D. Split the application into separate WebLogic containers and use different WLS versions of Xerces but identical that applications require.
E. Look for a WebLogic release that uses the same version of Xerces that the applications use.
Question 9: Identify the two options that can be used to patch WebLogic Server without Incurring application downtime.
A. automated process using the Admin Server
B. automated using JDeveloper
C. manual process with or without Smart Update
D. scripted with WLST
E. automated process using Enterprise Manager 12c
Question 10: WebLogic 12c, the Maven plug-in has been enhanced with which Maven goal?
A. wls:unzip, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
B. wls:install, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
C. wls:unzip, wls:create-domain, wls:start-domain, wls:wlst, wls:appc
D. wls:install, wls:create-domain, wls:start-server, wls:wlst, wls:appc:

Hello user7776, I am also looking for answers to the above Questions. Can you please send me the correct answers if you got the answers already? I really appreciate your response. Thank you sir.
-VCS

Jrockit with oracle weblogic 12c

We have Oracle Weblogic 12c and I followed this thread and update the start up files mentioned here, but still couldn't connect.
http://jdeveloperfaq.blogspot.com/2011/03/faq-32-how-to-get-started-with-jrockit.html
Has anyone been able to get the JROCKIT to pull data from Weblogic Oracle 12c and if so what version of the JROCKIT did you use and did you need to tweak the start up files, setdomain.env and startWebLogic cmd files.
Thanks

To my knowledge the plug-ins are not yet supported for WebLogic 12c.
"For information on WebLogic Server 10gR3 (10.3.0) and 11gR1 (10.3.x) Web Server Plug-In support, refer to My Oracle Support Doc ID 1111903.1 on https://support.oracle.com"
- New plug-ins will be released for WebLogic Server 12c.
- The location for the WLS 12c plug-ins will be released when they are available.
Instructions on configuration (note they come from the WebLogic 10.3.5 documentation) can be found here: http://docs.oracle.com/cd/E23943_01/web.1111/e14395/nsapi.htm#BGBFCGBJ
- The latest plug-ins can be found here: http://www.oracle.com/technetwork/middleware/ias/downloads/wls-plugins-096117.html
The documentation for WebLogic 12c only has instructions for the HttpClusterServlet: http://docs.oracle.com/cd/E24329_01/web.1211/e24425/setup.htm#CLUST466

Install weblogic 12c

can i install adf 11.1.1.6 on weblogic 12c ?
then , upgrade adf 11.1.1.6 up to 11.1.2.3 (JDeveloper) ?
and there is any guide to install weblogic 12c and adf 11.1.1.6 ??
can any body tell me , it 's urgent

AFAIK, ADF is not currently supported in WLS 12.1.1 version.

Can WebLogic 12C support Camel 2.10?

Similar Messages

Maybe you are looking for