Im deploying an ADF Web Application for GlassFish. (https://blogs.oracle.com/shay/entry/deploying_oracle_adf_applications_to) My application runs on Glassfish but the generated EAR is too big (100 Mbs), the application only have two jsf pages. Exploring the .war i have see that JDeveloper exports a lot of ADF Internal libraries.
Do you know if is it possible to reduce this size of the EAR?
Thanks
Alex
If you are using ADF you need the ADF libraries - that's why your EAR is big.
It however won't grow at the same rate if you add more pages etc.
On WebLogic we use shared libraries for all the ADF libraries - which results in smaller EAR files.
Related
I have created a ADF fusion application deployed in Jdev. When I deploy it as war file in Integrated weblogic server - works fine. When I deployed that as war in standalone weblogic server - it gives me error 500.
In the console (startweblogic.cmd) "java.lang.NoClassDefFoundError: oracle/adf/model/RegionBinding"
So I found on internet that deploying it as EAR the whole application would solve. Yes. It indeed was solved. My application runs fine in standalone weblogic.
Can we not deploy it as war in standalone weblogic?
The war file is working fine in integrated but not in stand alone.
Why?
P.S.: I installed ADF runtime, prepared the deployment profile to deploy as a web application.
I think you should make a quick research on the difference between these two types of archives EAR and WAR, then it should be clear to you.
Anyways, the fact is that you are trying to deploy a Fusion application, which includes in itself two different projects: the ViewController project and the Model one. The reason why on the standalone version it can only work if you deploy as an EAR is that this type of archive can contain several WARs, JARs (and other types of archives). While a WAR can contain only one of the projects (you can create a WAR for each, the Model and the ViewController project) and related jars. But they would be separate, so they would not have access to each-others files. I bet you've tried to deploy the ViewController.war only. This is the reason why you should deploy an .ear on the standalone version.
Instead, the integrated version, if an EAR file is deployed at the application level, and it has dependencies on a JAR file in the data model project and dependencies on a WAR file in the view-controller project. (It means, you are not deploying just the war from JDeveloper, it internally creates an EAR).
I hope this link would be useful.
I am currently writing a site in Spring, Thymeleaf, JBoss and I am using Spring Tool Suite. The turnaround time is horrible. I have to recompile and package the app, every time I make a change and then push it out to the server. How to make my turnaround time quicker?
Try JRebel. You can get it free if you spread some social media love for them.
http://zeroturnaround.com/software/jrebel/
Consider using a tool which supports continuous integration, and which supports working on an exploded war file.
For example, sbt supports that mode. It integrates jetty, and the webapp is restarted, if a source file changes (resources like .html, .css and .jsp do not restart the container).
As for details look here: Eclipse + Tomcat - Serve webapp directly from workspace. This question shows other possibilities as well.
If you use EJB features like session beans, you can split your project. If the EJB and pressentation is kept separate, the turn around times for redeploying EJB ears are acceptable.
We have created gwt application on eclipse juno 4.2 and gwt 2.5.1 and exported the application as war file using GWT Web App Export. Added the war file to the EAR project
of the eclipse.
If I deploy it on the websphere through eclipse it gets deployed. But if I try to deploy the same ear file through the admin console of WAS , the process hangs, I have tried all
the suggestions available over the net but all in vain.
Can anybody throw some light on this and provide guidence.
Thanks
Bhavani
Now I am able to deploy it through Websphere console.
Thanks for (fnt) by specifying about the size of the application.
When I posted the question the size of the war/ear was 111MB ,I removed
all the jar files and placed it in Websphere app servers ext foloder and
I build the war file through GWT compiler to contain only the binary codes of sources required for the application. The size was reduced to 7MB (the previous war file was
having jasper jars which was accounting for the most of the size)
Then I deployed the ear file through the admin console. Still It almost took
more than 20 minutes to deploy it through the admin console and I am
successfully able to deploy it and aceess the GWT application.
Thanks
Bhavani
Has anyone deployed autopatch (the database upgrade tool) in an ear application (on jboss server). Autopatch supports war kind of applications out of the box but for ear kind of applications it would need some extensions.
Moreover I am unable to provide the .sql files inside the ejb jar inside the ear as the location to look for patches to autopatch. Jboss 5 uses VFS and hence there is no reliable way to know the full URL to the jars.
Thanks in advance.
My team is taking over an existing web product that is made up of 3 Maven projects: one for a WAR, one for a couple of EJBs, and one that contains a few JBoss config files and builds an EAR that contains the WAR and EJB-JAR from the other two projects. We use Eclipse Helios and are currently building the projects individually with maven install and copying the resulting EAR to an instance of JBoss AS 6 for testing. While that process works, I am exploring the possibility of somehow streamlining that process; ideally a setup where small changes are automatically published to JBoss. Can anyone recommend a resource for configuring our projects/Eclipse to publish changes to JBoss automatically?
Get yourself "Eclipse IDE for Java EE Developers" and install JBoss Tools. The combination of the two will allow you to configure projects and server instances such that it is easy to deploy and test incremental changes.
Note that for this to work, your projects need to be WTP conformant. If you aren't using WTP already, take a look at the structure and metadata of projects created with Dynamic Web Project, EJB and Enterprise Application Project wizards. Either copy your source into new projects or copy the metadata files and fragments (very carefully).