I'm making a little project with Seam, Hibernate and JSF. This project run on JBoss 5.1.
My boss wants to deploy this project on WebLogic. I read on the seam documentation that seam and WebLogic don't work fine together.
I would like to know if I can use Hibernate (with JPA) and JSF on WebLogic and what framework (struts, spring?) I can use to replace Seam.
Edit: I read in the seam documentation (chapter 39, weblogic integration) and I find that:
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 10.0.MP1 versions. Unfortunately the 10.3 version only partially addresses the issue as detailed below. So, I want to know if other problems like this exist.
Edit 2: I use Weblogic 10.3
What do you mean by "don't work fine together"? I've already seen Seam applications on WebLogic and the Seam documentation provides detailed instruction to run Seam on WebLogic without mentioning any blocking issue.
If you have something specific in mind, please clarify. But in the current state of the question, my advice would be to stick to Seam and to deploy your application on WLS.
Related
Using Spring within Websphere, when using the javax.transaction.Transactional. Running the code locally or within Tomcat works as intended but while running within Websphere, it appears that the javax.transaction.Transactional annotation is not resulting in a Transaction that includes the JPA-EntityManager. Replacing the javax.transaction.Transactional annotation with the Spring version of Transactional solves this issue.
We would like to know what is required to fix this issue. I found this Stackoverflow-issue: spring-jta-transaction-with-jpa-and-jndi-datasource-for-websphere which links to the Article: 0609_alcott-pdf.pdf
The advise given is to configure Spring to use the WebSphereUowTransactionManager as transaction manager.
The stackoverflow answer is from 2012. But since we are running a farely old WebSphere 7 version, it might sill be relevant to us.
Does anyone experienced the similar or a related problem?
Update
The following dependencies are used:
spring-core: 4.3.9
hibernate.core: 4.2.15.Final
spring-boot starter: 1.5.4.RELEASE
I'd like to deploy the OSS version of artifactory in my existing Tomcat environment. My first try was to simply throw in the two wars that come with the bundled Tomcat. I had to copy over the derby jar, too, so that part seemed to work. I then got blocked by an issue with authentication tokens.
The manual I found is pretty outdated and talks about V2.x only. What I found here was this:
Deployment of my application in existing tomcat
Now - how official is this statement? I didn't find anything on their website saying that it's not supported anymore.
I'd need now
either a helpful resource (for me)
or a link to an official statement (for my management)
Thanks!
Well, I guess this qualifies as an official statement (at https://www.jfrog.com/confluence/display/RTF/Release+Notes#ReleaseNotes-Artifactory4.0)
Tomcat 8 as the Container
JFrog Artifactory 4.0 only supports Tomcat 8 as its container for both RPM and standalone versions. If you are currently using a different container (e.g. Websphere, Weblogic or JBoss), please refer to Upgrading When Using External Servlet Containers for instructions on how to migrate to Tomcat 8.
I am a little new to J2EE. I have a EJB3 project and I want to run a class on application start-up, how can I do that?
I know in EJB3.1 I can use #startup and #singleton unfortunately that is not a option and I have to use EJb3 and java 5. I have done some research and there were a few solutions but I have been unable to make it work.
WebSphere Application Server version 6.1 does not support EJB3 with a standard installation. You also need to have a feature pack for EJB 3.0 installed.
See this information on the IBM site.
If this is not your issue you should update your question with more detail of what goes wrong.
Your only options prior to WebSphere 8 (with EJB 3.1 support) are:
WebSphere startup beans. These are a programming model extension
Package a WAR with the application, and use a ServletContextListener to initialize state used by the EJBs.
I just migrated my web app from JSF managed beans to CDI managed beans, and I specifically wanted Tomcat or TomEE Plus to be the container of choice, because of the great things I heard about 'OpenWebBeans'. After deploying, configuring, and testing the TomEE 1.5+ / CDI-managed-beans web application, Full Page Refreshes are much much slower than Glassfish 3.1.2.2 / MyFaces 2.1.9 / JSF managed beans.
With Glassfish 3.1.2.2 / MyFaces 2.1.9 / JSF managed beans, full page refreshes only take 2 to 3 seconds.
With TomEE 1.5+ / CDI-managed-beans, full page refreshes take 5 to 10 seconds, and maybe even more than that at times. :(
Can you please tell me why is that?
Yesterday, prior to deploying the TomEE 1.5+ / CDI managed beans webapplication to the production server (Windows 2003 32-bit 4GB RAM and 1TB of diskspace), I read the following, which really did not answer my/this question at all:
glassfish v3 vs tomcat 7
I read that PPR is better on performance than FPR, but my session timeout/management implementation involved the following:
LoginFilter (servlet filter)
the following in h:head
meta http-equiv="refresh" content="#{session.maxInactiveInterval};url=pf_viewExpired.jsf"
Is CDI more (time) expensive than JSF managed beans, or is TomEE the container of choice for CDI? I know that JBoss (or Weld) is or has the reference implementation for CDI, so it may be best to consider JBoss/Weld.
Prior to completing the task of migrating from JSF-managed bean to CDI-managed bean (as well as migrating from Glassfish to TomEE), I had issues starting CDI-managed-bean web app on Glassfish/Weld.
Please answer the following questions above, and/or advise. Thanks.
As inidicated in the comments above, I am working with OpenEJB (TomEE) committers to resolve this issue. Personally, I feel the issue is possibly due to the following:
CDI managed beans defined and referenced in the app
Possible CDI cyclic references (which will possibly be resolved in CDI 1.1)
A really large CDI #SessionScoped bean, which references/injects many other CDI beans to accomplish business logic (or tasks) within the app
TomEE/OpenWebBeans (which is still under development)
So, the answer remains to be determined. I opened the following OpenEJB JIRA for this issue (URL below). Feel free to watch this JIRA, if interested.
TomEE 1.5.1 SNAPSHOT (and CDI beans) running slow on my production server
UPDATE:
Now, TomEE/CDI-managed-beans is performing just as well as Glassfish/JSF-managed-beans on the production server, because I recently did the following:
replace frequently-used dynamic SQL with #entity named queries
added query hints to JPA createQuery() and createNamedQuery()
replaced frequently-used rendered="#{EL expression}" with new facelets and ui:include src="#{EL expression}", since TomEE committers advised that rendered="#{EL expression}" gets called 6 times.
So, my TomEE/CDI-managed-beans is now running on production server and I'm monitoring performance and enduser reports/experience.
A simple web search didn't really turn up any examples... so I'm wondering if anyone could point me to any information on configuring Spring on Glassfish? Everything I've been finding is horribly outdated.
Thanks!
Download Netbeans 6.8 it will give you glassfish and spring configured by default.
http://netbeans.org/community/releases/68/
Configuring Spring is not really related to the fact that you are using GlassFish or Tomcat or whatever, you just configure it for an application that you then deploy on a server.
If you have a specific GlassFish related issue, you should probably clarify the question.