a question about migration of applications based on adf version 11.1.1.6 to version 11.1.2.0
app: core java jsf / adf components
whether there is a possibility to occur, there are any conflicts.
oracle writes http://www.oracle.com/technetwork/developer-tools/jdev/index-091111.html
If exist the ability to migrate to 11.1.1.9 with no problem.
Anyone have any experience related
You will require modifications to the application code?
You will be required to update the script builder app?
and it looks like a case of the configuration of WebLogic Server with an increase version.
If you are planning an upgrade go directly to the latest version 12.2.1 and not to the outdated 11.1.2.*.
See the support matrix:
http://www.oracle.com/technetwork/developer-tools/jdev/documentation/122-cert-2708091.html#MigrationSupport
In general the main difference is that the JSF engine switched from JSF 1 to 2 - when you open the application in the new JDeveloper it will migrate your project for you.
I am using Eclipse with Google App Engine Development Server right now on Win-7 platform . I have to create a simple website using Java . I am confused that do I need Tomcat Server installed in-order to develop Java based site using Eclipse Framework ? Can Tomcat be installed on Win-7 platform ? please guide on this . If any better framework is available please suggest (as I am new to this) .
The GAE development server is specifically designed to help you develop applications for Google App Engine by simulating the actual GAE environment. If you plan to deploy the webapp on GAE, then it's all you need.
If you want to develop a standard Java EE webapp, then you indeed need a standard Java EE web container. Tomcat is one of them, but you could also use Jetty, GlassFish, JBooss, Resin or any other Java EE web container. And since they're all written in Java, they're all multiplatform and can all be installed on Windows.
Also Eclipse is not a framework. It's an IDE. Developing a webapp using Eclipse, IntelliJ, NetBeans or a text editor and the JDK doesn't change anything to the webapp. They're just tools to help you write Java code.
We have deployed our JBoss Seam 2.2 application on JBoss 5.1 with PostgreSQL as the database. It makes use of EJBs, JPA (Hibernate), JSF (Richfaces and Primefaces), Servlets, and JMS queues and topics. Recently, we've decided to migrate the platform to JBoss 7.1 to take advantage of its lower overhead, as well as to keep in step with changes in technology.
Is it possible to run Seam 2.2 applications on JBoss 7.1? I realize the Hibernate/JPA version is different, and I'm assuming the JSF version is as well. Are there ways to compensate for this? What changes to our code and configuration could I potentially have to make in order to run it on this platform?
The short answer is yes you can migrate your Seam 2.2 app to JBoss AS 7.
The main challenge is going to be classloading because of how class loading is completely re-architected with AS 7.
Instead of me going through all the steps here I simply want to point you to the official documentation of how this was done on one of the sample apps (Seam Booking application). It provides a step-by-step guide on how you can migrate a Seam 2.x app to JBoss AS 7 and also points some of the issues you will face and how you can handle them.
The guide is located here.
Other useful references
JBoss AS 7 Classloading
Seam 2 JPA Example
Good luck!
I have recently begun learning Java EE 6 after doing Java SE for some years now (together with other languages). I have bought different books about Maven, EJB, JSF, Glassfish and so on (not read them all yet though), and I feel absolutely overwhelmed of the complexity of just making a project.
How would I start a project from "scratch" (Not copying a from an example in the book) in eclipse? I can choose from Dynamic Web project, Maven project, EJB project, EAR application etc. Which should I use if I want to make an application that has EJB/JPA and JSF inside (web application)?
I know about the Standard Maven Directory Layout and archetypes, however I do not know which to choose if this is the way to do it. Of course, I understand that there are many ways of doing it and it is dependent on what I will use it for, but I am learning Java EE 6 so I want to at least have some knowledge of how to set up a basic project as well.
I am also rather overwhelmed by the POM file. How do I know which dependencies I need just to get started with a web application? Or is this included in the correct archetype (if I find one?)
I am using Glassfish as application server, Eclipse, EJB, JPA and JSF. Currently learning from book examples only.
Well, a complete answer to your question would pretty much need an entire book on it's own, but here's some pointers.
The notion of Java EE applications represents any kind of Java application that uses one or more of the Java EE APIs implementation and needs a Java EE application server to run. Java APIs are those such: Servlet,JSP, EJB, JPA, etc. Implementations of these APIs are usually provided by the application Server (like Tomcat has servlet and JSP implementations, Glassfish has those as well plus EJB, etc). There are, let's say non-application server Java EE APIs implementations like Hibernate's implementation of JPA. So in short if you use some of these APIs implementations in your app and deploy it into some application server like Tomcat, Glassfish, JBoss AS, etc, you have a Java EE application.
I've told you all this because in reality, most of the project management tools (like Eclipse, Maven, etc) use these subdivisions like Web-Application, EJB Module, Dynamic Web Project etc, as a custom denomination that establishes the ball park of what set of Java EE APIs your application will use. I.E. a Web Application or Dynamic Web Project will more likely use Servlet and JSP APIs, an EJB Module will (duh) use the EJB APIs and so on. These are, as I said, ball park denominations. A Dynamic Web Application can use EJB or JPA as well, it's not like it's written in stone.
When you use either of these tools such as Eclipse or Maven, to start one of these above mentioned, denominated projects, such as a Dynamic Web Project in Elcipse or a Standard Web Application with Maven, that respective tool will add the common sense dependencies to your template project (like Servlet and JSP in this case), and then let you handle it from here.
The idea here is to understand each type of template of your chosen tool before you use it at the start of your project. Like if you decide to use Eclipse and start with a Dynamic Web Project, you should check out what exactly Eclipse asks of you and does when you do that (it will ask you for the location of a locally installed Java EE application server from where it will pull in such dependencies as a Servlet Implemnentation and a JSP implementation amongs others). Or if you chose Maven, and start a standard web project, you should check out what dependencies it adds to your project via the pom.xml file, what the basic functions of THAT pom.xml file are, etc. You should also check out how each of these tools deploys your application when you tell it to do that, does it use some hot deploy feature of your Java EE server, does it need credentials to access that server first etc.
My brief advice is to start with the very basic example: Install a Tomcat (version 7 is recommended), start Eclipse for Java EE Development, add that Tomcat installation to your Eclipse config, start a Dynamic Web project that uses that Tomcat as Application server, and just do some basic servlets and JSP pages, then use Eclipse to deploy that sucker to tomcat and run it. Then you can branch off to more advanced stuff, like doing the same thing with Maven, integrating a Maven project with Eclipse, adding some more Java EE Stuff (like a JPA Implenentation), etc etc.
http://blogs.oracle.com/arungupta/entry/web_app_development_using_java provides a complete explanation of how to create a Java EE 6 project using Eclipse and GlassFish.
Alternatively, you can also NetBeans to create a Java EE 6 project as explained at:
http://blogs.oracle.com/arungupta/entry/screencast_37_java_ee_6
I can choose from Dynamic Web project, Maven project, EJB project,
EAR application etc. Which should I use if I want to make an
application that has EJB/JPA and JSF inside (web application)?
Before EJB 3.1 spec it was not possible to deploy EJBs in war files, but now, you can. So for a quick prototype you can use a war file rather than an ear file if that's all you require and you are more familiar with it. Of course you can also deploy it in an .ear file.
I believe the Dynamic Web project in Eclipse generates a .war file that you can deploy in your AS.
If you are using Maven, you can also create your project with Maven beforehand, and then import using Maven (via M2Eclipse plugin). This works pretty well for me. Then, with the Glassfish Maven plugin, you can deploy your app to Glassfish via command line.
I am also rather overwhelmed by the POM file. How do I know which
dependencies I need just to get started with a web application? Or is
this included in the correct archetype (if I find one?)
You need the Java EE dependencies at least in a "provided" scope as the server will probably provide these for you. This way they will be available for you in compilation mode. For instance, the one for the JBoss Java EE 5 stack is as follows (not sure about the GlassFissh dependency, but the important stuff is not to include the library in your .ear / .war in order to avoid library conflicts):
<dependency>
<groupId>org.apache.openejb</groupId>
<artifactId>javaee-api</artifactId>
<version>5.0-1</version>
<scope>provided</scope>
</dependency>
Added: As you said, this can be overwhelming at the start, I think this is a good resource on how to setup a Glassfish / Java EE project. Pick the bits you are interested on and good luck.
The first thing I'd ask you is why you're learning so many technologies. If your purpose is getting a job, in my experience, there's a trend in companies away from Java EE and towards simpler solutions. For example, application servers are overkill for most organizations and Tomcat (or another web server) with helper technologies like Spring and standalone JMS servers replacing full-featured and much more complex Java EE servers.
I think you'd be better served focusing on core concepts and simpler technologies as you get started and staying away from IDEs, complex builds, EARs, etc. Instead, start with one or two technologies (e.g. a hello Tomcat app with a simple Ant build) and gradually add each technology in as you find the need. Better yet if you have a real world problem to solve, even if it doesn't pay.
Most companies (at least those with a technical clue) would rather hire a programmer who understands what value a technology like JSF adds and at what cost of complexity than someone with a lot of acronyms on their resume.
How to start a new web app project in Eclipse with Maven?
Just type "archetype:generate" and select JSF + EJB/JPA if available.
This one seems fine: 360: remote ->
org.jboss.weld.archetypes:weld-jsf-jee (Weld archetype for creating a
Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1 and JPA 2.0
(persistence unit included))
The Appfuse are quite more complete and may embed stuff you will never
use and that you will have to remove.
After that mvn eclipse:eclipse to be able to load the project in eclipse.
I believe netbeans doesn't support BPEL.
Is there a workaround for it, or can you please suggest some other IDE, where I can compose web services together?
I have two web services, one which churns the data and gives the output as a JSON/string and the other web services which will have the input as the output of the previous webservice and visualize/graph the data.
Thanks
Netbeans supports BPEL. For that please download Glassfish ESB (Open ESB) which includes Netbeans IDE also. You can find Glassfish ESB from here.
Generally, BPEL support is consists of two components: an visual editor and a runtime. Since Netbeans is an IDE, it can provide the editor part but not the runtime. For the runtime part, OpenESB was used to be bundled with Netbeans and could execute BPEL 2.0 processes. I'm not entirely sure, but to me it seems that Oracle decided to drop BPEL support in favor of their own BPEL solution. OpenESB has been taken over by LogiCoy and I could not find any version of the Netbeans Enterprise Pack on the Netbeans web site. So I assume it is not available anymore.
Alternatives could be Eclipse BPEL designer (editor) and Apache ODE (runtime)
If you have only two Web services, BPEL is probably overkill for your scenario. Also, BPEL strictly relies on WSDL and XML Schema. If your services produce and consume JSON, BPEL cannot directly processes this data, instead it will consider it just as String data.
NetBeans itself doesn't support BPEL, however there is OpenESB Which is built on top of the NetBeans platform that does.