weblogic12c

问题 I am having issues with the Omnifaces FullAjaxExceptionHandler (http://showcase.omnifaces.org/exceptionhandlers/FullAjaxExceptionHandler). It does not redirect to the specified error page after the session is invalidated. I have the following in my faces-config: <factory> <exception-handler-factory>org.omnifaces.exceptionhandler.FullAjaxExceptionHandlerFactory</exception-handler-factory> </factory> And the following in my web.xml: <error-page> <exception-type>javax.faces.application

问题 I'm having difficulty with my EJB3.1 bean initialisation and more specifically to do with it failing due to perceived transaction rollback, even though I've marked the bean with @TransactionAttribute(NOT_SUPPORTED) . This should mean that any client transaction is paused on bean method entry until exit (when it will be resumed. It's definitely the transactional apprach I want. The "gist" of the code and error are as follows (note some of it is hand-cranked to hide details but is all relevant

问题 Spring application using JNDI lookup to get datasource as following: @Bean(name = "dataSource1", destroyMethod = StringUtils.EMPTY) public DataSource dataSource() { final JndiDataSourceLookup lookup = new JndiDataSourceLookup(); lookup.setResourceRef(true); return lookup.getDataSource(this.environment.getProperty(Constants.DB_JNDI_NAME_ES)); } and getting a connection from the datasource as follows : @Autowired @Qualifier("dataSource1") private DataSource ds; Connection conn = null; conn =

问题 I am trying to encrypt a database password for my Java EE Application in the terminal. according to this tutorial The steps are as follows: Change directory to your domain’s bin folder (For Eg. cd WLS_home\user_projects\domains\mydomain\bin) Use setDomainEnv.cmd/sh script to setup the environment Run java weblogic.security.Encrypt which will prompt for the password and will print the encrypted value in stdout. However, when I execute 'java weblogic.security.Encrypt', I am presented with the

问题 Normally weblogic 12c doesnt support jax-rs 2.0 but by the help of jax-rs shared library which comes with weblogic itself it is possible to upgrade jax-rs version from 1.1 to 2.0. The problem is library implementation is jersey 2.5 which doesnt satisfy my needs. I found a link about upgrading jersey version on weblogic which looks a lil bit complex. Is it enough to replace jersey jars 2.5 with my jersey version 2.13? Do i need to do anything else? 回答1: I have created a simple maven project to

问题 How can I make an external directory (where additional jars will be deployed) available on the classpath of a war deployed to WebLogic? I am familiar with how to do this on Tomcat by defining a Loader element in the context.xml and including a virtualClasspath attribute which specifies Additional repositories to search for resources . Is there a similar feature in WebLogic? 回答1: Yes weblogic has the option to do this as well with virtual-directory-mapping inside weblogic.xml: <?xml version="1

问题 How can I make an external directory (where additional jars will be deployed) available on the classpath of a war deployed to WebLogic? I am familiar with how to do this on Tomcat by defining a Loader element in the context.xml and including a virtualClasspath attribute which specifies Additional repositories to search for resources . Is there a similar feature in WebLogic? 回答1: Yes weblogic has the option to do this as well with virtual-directory-mapping inside weblogic.xml: <?xml version="1

问题 I have an application that is using jsf2,hibernate4,spring4 and i am using the annotations in all the project ,the project was working fine on the Tomcat server ,but a new requirement appear that i have to use weblogic application server so i have installed weblogic 12.1.3 cause i have read it supports web module 3.0 ,but when to deploy to weblogic i got this error <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\EclipseWorkspace\TESTAPP\target

问题 Weblogic 12.2.1 has Jersey 2.21.1 inside as implementation of JAX-RS 2.0,but we would like to use Jersey 2.5.1 or Jersey of the latest version. General way to solve the conflict is to define classes in configuration file to load classes from application. But when you upgrade weblogic or Jersey, you have to look into the class conflict and make changes to configuration, is there a convenient way to disable Jersey from weblogic? 回答1: You need to include the jersey files in the web-inf lib of

问题 I'm not really a Java developer, but a project for a client has required me to be, so maybe I'm missing something glaringly obvious. I'm using SpringBoot and everything works fine when the application runs in Tomcat on my local machine and on our testing server. However, as soon as the application is deployed to Weblogic it's as if there is no security at all with all routes accessible. Login and logout routes are non-existent as well. That being said. Everything else appears to work fine,