Out of the box Weblogic does not come with its own JSF libraries active. For complete details see Weblogic In the administration console navigate to the Deployments page using the left hand menu. Then select the Install button at the top of the deployments table. Then select the jsf Make sure that the Install this deployment as a library is selected. Click the Next button on the Install Application Assistant page.
Click the Next button on the Optional Settings page. Make sure that the Yes, take me to the deployment's configuration screen. Click the Finish button on the Review your choices and click Finish page. On the Settings for jsf 1. Then click the Save button. There is another step that is needed for this to work. For some reason, even with the steps above classes in the jsf-api. The only way for this to work is to put the javax.
This requires a restart of the server. If so there are some obstacles that you will have to avoid, or some patches that are needed from BEA. For several releases of Weblogic there has been an issue with how Weblogic generates stubs and compiles EJB's that use variable arguments in their methods. This is confirmed in the Weblogic 9. X and MP1 versions. Unfortunately the The basic explanation of the issue is that the Weblogic EJB compiler mistakes methods that use varargs as having the transient modifier.
When BEA generates its own stub class from those classes during deployment it fails and the deployment does not succeed. If you see exceptions like below during deployment you are running an unpatched version of This issue has been fixed in Weblogic MP1 CR for this issue that can be requested from their support.
Unfortunately a second issue has been reported and verified by BEA. This issue was only found once the CR patch had been applied to This new issue has been confirmed by BEA and they created a patch for MP1 that addresses this issue. This patch has been referred to as both CR and CR As with the other patch this can be requested through the BEA support. This issue causes certain EJB methods to be incorrectly left out of Weblogic's generated internal stub classes.
This results in the following error messages during deployment. It appears that when Weblogic This means that Weblogic MP1 with patches will function correctly, but When they do we will update this reference guide as needed. The only difference between this jar and the jboss-seam. To use this jar simply rename the jboss-seam-wls-compatible. Obviously with this jar you will not be able to use the TimerServiceDispatcher functionality.
This example uses the in memory hypersonic database, and the correct data source needs to be set up. The admin console uses a wizard like set of pages to configure it.
Copy hsqldb. Start up the server and navigate to the administration console following Section Then select the New button at the top of the data source table. Select Next button on the Transaction Options page. Fill in the following on the Connection Properties page:. Username: sa will empty password fields. Driver Class Name: org. Choose the target domain for the data source in our case the only one AdminServer.
Click Next. OK - now we are ready to finally begin adjusting the seam application for deployment to the Weblogic server.
Change the jta-data-source to what you entered above :. Then add these two properties for weblogic support. This file needs to be created and should contain the following:. These changes do two two different things. The first element library-ref tells weblogic that this application will be using the deployed JSF libraries. The second element prefer-application-packages tells weblogic that the antlr jars take precedence.
This avoids a conflict with hibernate. The changes described here work around an issue where Weblogic is only using a single instance of the sessionBeanInterceptor for all session beans.
Seam's interceptor caches and stores some component specific attributes, so when a call comes in - the interceptor is primed for a different component and an error is seen.
To solve this problem you must define a separate interceptor binding for each EJB you wish to use. When you do this Weblogic will use a separate instance for each EJB. Modify the assembly-descriptor element to look like this:. This file and the element library-ref tells Weblogic that this application will using the deployed JSF libraries.
This is needed in both this file and the weblogic-application. There are some changes needed to the build script and the jboss-seam. Where incompatibilities arise, they are fully documented in the Upgrading WebLogic Application Environments guide. This compatibility allows a J2EE 1. With one exception, upgrading to WebLogic Server 9. The 9. This means that source files that use the Javadoc-style tags must be upgraded to use the equivalent annotation, and then recompiled using the 9.
Upgrading to WebLogic Server 9. WebLogic Server 7. Rose Rose 1 2 2 bronze badges. Add a comment. Active Oldest Votes. WebLogic will allow you to be backwards compatible, but forward compatibility is not guaranteed. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.
0コメント