after I make some editing to few source java files, the weblogic plugin seems to not re-deploy the application because it show me a older version of build.
I've tried to:
Add-remove resource from weblogic plugin
Clean and republish
Reinstall weblogic
Into bin directory I see that the .class are correctly updated!
Any suggestions?
many thanks
Deleting all classes directory folder solved the problem!
Related
I downloaded the latest axis2 snapshot from Apache Axis2 repository however I cannot find the dependency list of jars I need at runtime. Where can I find the dependency list for this project?
I think you will have better luck if you just download builds, they worked for me
distribution
there is a war file for the server installation and there is bin for your ide use
I am having two queries
1. Can I deploy web application as a folder instead of war file in JBoss AS 7?
2. If not ,how to update the JSP or html or js files with out building/deploying the war file again?
JBoss supports the ability to deploy an archive file or as an exploded directory. To explode a Java EE archive, unzip the archive to a directory that is named the same as the archive file. As long as the directory name has the correct extension (.war, .ear, etc.) JBoss will deploy the directory normally. So if your war file has name HelloWorld.war, your exploded directory name should be HelloWorld.war too.
Please also note that it is recommended to edit your deployment-scanner in the standalone.xml configuration file and changing auto-deploy-exploded property back to false for exploded deployment. Quote from JBoss 7.1 Documentation:
Manual deploy mode is strongly recommended for exploded content, as
exploded content is inherently vulnerable to the scanner trying to
auto-deploy partially copied content.
Edit:
Please see link https://community.jboss.org/thread/200114. Looks like this is a confirmed bug in JBoss 7.1.1 that JBoss ignores the configuration in jsp-configuration and does not reload modified jsp. It is fixed in 7.1.2. You need to build 7.1.2 nightly build yourself. Or talk to JBoss Support if you have Enterprise support.
Hi guys previously i was deploying my project WAR on JBOSS AS 7 and whenever resources got changed the eclipse Juno auto republished the war file. But since I added my war into a ear and deployed that ear on JBOSS, now eclipse doesn't auto republish. I also tried changing publishing setting but nothing worked for me. Now I republish manually after every single change. Please help me out.
I had this same issue, but got it to work after checking the 'Deploy projects as compressed archives' box (open up the server configuration and go to the Deployments tab)
I created a sample plugin which includes a simple view in eclipse and ran the plugin from inside the workbench, my plugin is installed and I get my view showing up in Window/Show View/Other... . I packaged the plugin as a jar file and installed it under the plugins directory of eclipse and restarted my eclipse workbench. I am not able to find my plugin view. I dont know whats is wrong
I am using eclipse RCP SR2 (3.6) for developing plugins and my packaged jar file includes the code, META-INF/MANIFEST.MF and plugin.xml files.
I created the plugin from the book 'Eclipse Plug-ins, 3rd Edition'. I followed the steps outright and am not able to set up the plugin as a jar file.
I got it to work somehow? The plug-in project was created using Execution Environment JavaSE-1.6. 'It was given in the book I referred'. Now the manifest editor had the entry 'Bundle-RequiredExecutionEnvironment: JavaSE-1.6'. Now I ran the application with-in eclipse, it was working. But when I bundled the plugin as jar and copied the plug-in jar under plugins folder and restarted eclipse the plugin was not working, I dont know why, I thought my eclipse is not running under JRE1.6, but I checked my Windows->Preferences->Java->Installed JREs-> I have only jdk1.6.0_27 checked (So I assume that the eclipse is running under JavaSE1.6). This is bit confusing for me! I removed the Execution Environment entry in the Manifest editor Overview tab. Now there is no 'Bundle-RequiredExecutionEnvironment' entry in my Manifest, I created the bundle jar again and installed in eclipse plugins folder and restarted eclipse using -clean option. It started working in my eclipse. I got it to work somehow but with no understanding! I am still looking for answers from some one who can help me figure out what went wrong?
Open an OSGI console and type 'ss'. It should list all of the plugins. Can you see it? What is the state of it.
You can use Preferences/plug-in development/target platform edit running 'running platform' content tab to list and check/uncheck plugins. I hope it helps.
You could try copying your jar file to the eclipse/dropins folder.
I have a maven build of a multi module enterprise project. I am running WAS from RAD. In command prompt I ran
mvn clean
mvn install
mvn -Dwtpversion=2.0 eclipse:eclipse
The build is success. I then import it into my workspace in RAD and add project to WAS. When the server starts publishing. I get an error as pop up saying
ADMA0176E : Application installation of MYPROJECT failed with
PrivilegedActionException
I am able to deploy the same project on tomcat. Also, I created a sample project and published it to WAS. So I dont understand why the application is asking for privileges. I tried enabling application security, cleared the server cache, restarted server, restarted PC. Nothing helps. I can deploy the ear through admin console, however. Only through rad I am getting issues. How do I solve this ? I tried what is mentioned here but it does not help.
I had this problem after making some pom.xml changes. I solved it by running Maven Update Dependencies then Maven Update Project Configuration.
I had this problem today and could solve it by deleting the according folder in \profiles\AppSrv1\installedApps\. I don't think this is a general solution for this problem, but I could not find this hint on any of the other discussions for ADMA0176E.
Following files were missing for my project. Copying these files from another project solved the problem.
security.xml at path: [ibmconfig/cells/defaultCell]
deployment.xml, resources.xml and variables.xml at path: [ibmconfig/cells/defaultCell/applications/defaultApp/deployments/defaultApp]
This worked on IBM WAS 7.