We have an existing application which has an ANT script used for deployment and running on weblogic version 9.2.3.
We had a request to upgrade the weblogic to version 12.1 and I was able to successfully upgrade this by changing the application specific WL_HOME and giving the build using the ANT script already present. But unfortunately we were having a dependency on another application that is running on weblogic 8.1 and weblogic 12.1 is not compatible with 8.1.
So we are now in the process of downgrading the weblogic to version 10.3.6 and after installation of weblogic 10.3.6, I changed the same application specific property WL_HOME to point to weblogic 10.3.6 and tried the ANT build.
But this time the ANT script failed, throwing errors saying error: package javax.ejb does not exist
import javax.ejb.CreateException;
The application and weblogic is installed in a solaris/unix machine and we are using jdk 1.7.0.60 for the application.
I am not an expert on weblogic or ANT, and I couldn't figure out where I went wrong. I see that we have javax.ejb_3.0.1.jar present in the modules directory.
It will be really grateful if somebody could let me know where I might have gone wrong.
Thanks for your help in advance.
Related
I am working on a WebApp with Vaadin and Hibernate which is using Version 3.2.3 of Liquibase as a dependency.
When I build this App and test it with the Tomcat7 Maven Plugin everything works fine.
When I deploy the .war file manually to Azure (running Tomcat 8.5) or a Tomcat 8.5 on my local machine I get the following error:
liquibase.exception.ServiceNotFoundException: Could not find implementation of liquibase.logging.Logger
When I deploy the .war manually to a Tomcat 7.0 running locally it works again.
The database is the same in all cases.
What might be the reason for this?
How can I fix this?
Looks like it's a should-be-fixed-but-still-reproduced issue.
There are two issues in Liquibase's Jira:
CORE-2003
CORE-2042
Try updating liquibase. Version 3.2.3 is very old already.
The client has upgraded the worklight server 6.2 to Mobile First 6.3, and deployed the updated war file. Now when we open the console to deploy the adapter, "It shows no runtime can be found"
But the same project works fine in the local development environment, where we installed the mobilefirst studio plugin in eclipse. We are able to build the project and run the app.
Java - 1.7
Eclipse - Juno SR2
MobileFirst studio 6.3
Cannot access the remote server for now, will attach the logs shortly.
Kindly let us know if there are any known issues on upgrading to 6.3(mobile first) from 6.2(worklight)
Thanks
Hi we are able to fix it. The reason is the client has not built the war file in 6.3, they have updated the old war, when we tried building the war file from the 6.3 and deployed. it worked.
My problem is when adding WildFly 8.x Runtime in targeted runtimes in eclipse, then I can't run servlets, I mean the server runtime library is not in the path.
can you provide me with help.
I'm running ubuntu 14.10, eclips luna, JRE 1.8 and WildFly 8.2.0.
note: I don't want to manually add the servlet-api jar file.
Thank's in advance.
Edit1:
I found that not only the servlet implementation part is not loaded, but all other modules of WildFly, so this ensures me that the problem is in the whole server runtime!
Edit2:
as stated here in 2.1.1. Installing a new runtime section,
You will also note a Deploy-Only Runtime type. This type does not provide a classpath for WTP projects. It is used solely by it's server type for the purpose of setting up a deploy directory for users who do not wish to make use of starting, stopping, or debugging their projects inside Eclipse.
can I conclude that my version is has a "deploy-only runtime type", but it's Version 8.2.0.Final 2014-11-20 Java EE7 Full & Web Distribution !!!
It's OK now, I just installed JbossAS Tools, which is described in eclipse as follows:
Provides WTP server adapters for JBoss installations. These adapters are capable of deployment and providing classpaths for projects
then I could specify project runtime for new projects directly, or add WildFly runtime as a server library from build path for old projects.
I am new to weblogic 12c server. previously i was using tomcat 6, jdk6 eclipse luna, and my project type is tomcat project.now in our company they migrated to weblogic 12c.
the problem is i used to start/stop tomcat like this by using sysdeo plugin.
After start i used to right click on project ->upload context->click.
it used to deploy automatically to tomcat than in browser i can access that.
now how to achieve this in weblogic 12c.i googled and find out that if my project is dynamic web project than i can add server instance of weblogic and can achieve the above by selecting runas server option.
but my project type is tomcat project structure.
so can any one help me with this.
Update
i found this plugin but it works from weblogic 6 to weblogic 8.1 but not for weblogic 12c.
you need to install the enterprise pack
http://www.oracle.com/technetwork/developer-tools/eclipse/overview/weblogicservertools-161590.html
I would recommend also, to try netbeans 8
It has better integration with maven, weblogic etc
this post is little old but I wanna share that I found just and I guess it is related to this post, there is no config combination exists between Jdk 1.6 + Eclipse luna + Oracle Service pack(12c) for Eclipse! You will have to upgrade or downgrade at least one of them...
I have a Java project using Groovy and Java mixed. Now I want to publish it to my tomcat, but it says
Could not publish to the server. java.lang.IndexOutOfBoundsException
Platform : OS X / Eclipse Kepler Service Release 1 / Java 1.6 / Tomcat 7.0.39
How can I deal with this issue ? I can deploy a new create Dynamic Web Project, but not my exist project.
My server configuration :
My Jar files are way too old, I just deploy my project into Tomcat manually and found a lot of error log.
Just update them into newer version.