Jars in the JBoss EAP 6 Runtime

Latest response

I have downloaded JBoss developer Studio, by adding the JBoss EAP 6 runtime, I have seen that it contains only some jars but not all of them. So I have errors in some jar import in my code (exp : ironjacamar-jdbc-jar which is in the folder C:\jboss-eap-6.1\modules\system\layers\base\org\jboss\ironjacamar\jdbcadapters\main).

What are these jars that JBoss eap 6 runtimes contains by default?
How to fix the missing jars that comes with JBoss eap 6 but are not seen in the Java Build Path?

PS: I don't like to use maven.

Attachments

ma
Log in to join the conversation

Responses

Mustafa Musaji's picture Red Hat Guru 1798 points
28 November 2013 9:58 AM

Hi Mariem

You are asking a lot of question on the CSP, perhaps it may be easier if you raise a support case for all related questions to Developer Studio?

I'm not sure what you are doing here, as your other posts say you are using Eclipse and don't want to use JBDS. I also don't have enough information on your project or what you are importing. The errors are there because the libraries could not be found, but I'm not sure what you mean by "what are these jars that eap 6 contains by default?".

Maven has nothing to do with this. If you have missing JAR's in the project then you need to import them has part of a library or manually. This is the same for any other Eclipse project and nothing to do with JBoss or JBDS.

Thanks
Mustafa

ma Community Member 80 points
28 November 2013 10:13 AM

I am working with the Eclipse IDE, my team also. As I have strange setting issues, I have decided to use JBoss Developer Studio as it supports better JBoss eap 6. But my team don't like to move to JBDS.
Using JBDS, I wonder to now why the runtime server (in the Java Build Path) didn't contain all the JBoss System jars (as in previous jboss version) I gave you the example of "ironjacamar-jdbc-jar" which is in the JBoss system folder.

Mustafa Musaji's picture Red Hat Guru 1798 points
28 November 2013 10:23 AM

Hi Mariem

Let me try understand your steps.

So you have a project which you imported in to JBDS along with the a runtime of EAP 6.x. When you open your project you get a lot of compiler errors because of missing libraries. At this point you add the EAP runtime to the build path and expect the dependencies to be fixed but some libraries do not get added?

Libraries were split and in EAP 6 the whole format was changed. I'm not sure what version you are comparing it to but depending on if you actually need runtime library or EJB3 library etc, it may mean you need to add the dependency yourself.

ma Community Member 80 points
28 November 2013 10:44 AM

When my application was running on JBoss as6, I have this code

if (pStmnt instanceof org.jboss.resource.adapters.jdbc.jdk6.WrappedPreparedStatementJDK6)

The class org.jboss.resource.adapters.jdbc.jdk6.WrappedPreparedStatementJDK6 is in the JBoss Server libs (lib jboss-common-jdbc-wrapper.jar) (please see pict wrappedPreparedStatement). So when adding the JBoss as6 Runtime, there is no need to add any jar as the jar is present in the jboss.
When moved to JBoss eap 6.1. The I have modified the code,

if (pStmnt instanceof org.jboss.jca.adapters.jdbc.jdk6.WrappedPreparedStatementJDK6)

This class is present in jboss, in the module "C:\jboss-eap-6.1\modules\system\layers\base\org\jboss\ironjacamar\jdbcadapters\main". But when I add the JBoss eap 6.1 runtime, this jar is not present as apperently JBoss runtime don"t load all the Jars in its classpath. So I have error in imports. I have fixed it manually.
That"s why I am asking what are these jars in the JBoss runtime (java build path), and how normally we fix this issue.

Mustafa Musaji's picture Red Hat Guru 1798 points
28 November 2013 10:55 AM

JBoss EAP 6 did not have a common/lib directory so either you added this yourself or you are talking about JBoss AS 6 in which case you can't compare the two as they are completely different. JBoss EAP 6 is based off JBoss AS 7.x.

You fix it by doing exactly what you have done and that is by adding the relevant JARs to your build path.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.