- This topic has 4 replies, 3 voices, and was last updated 10 years, 1 month ago by tazybaba.
-
AuthorPosts
-
support-piotrParticipantSome projects require WebSphere runtime jars present in the build path during compilation. If you want to configure a WebSphere runtime for your project, do as follows:
1. Create User Library for WebSphere Runtime. Go to: Window -> Preferences -> Java -> Build Path -> User Libraries and add jars you need from WebSphere installation.
2. Go to Deployment Settings of Web Projects (Window > Preferences > MyEclipse > Java Enterprise Projects > Web Project -> Deployment) and uncheck “Jars from users libraries” and “User library jars exported from dependent java projects” making sure, that the others two are checked.
3. Add runtime to projects path (Project -> Properties > Java build path -> Libraries -> Add library -> Select User library).
ad9c14MemberI added the JAX-RS support to my WAR project and it automatically added following two User Libraries to Java Build Path. This project also use WAS 7 as target server.
JAX-RS Core Libraries
JAX-RS JAXB LibrariesUnchecking “Jars from users libraries” and “User library jars exported from dependent java projects” prevent JAX-RS Jar files including from exported WAR file. It makes sense to not to include WAS 7 runtime jar files into WAR while exporting it. but I do want to include JAX-RS jar files into exported WAR file.
How do I this ?
support-piotrParticipantad9c14,
This tip applies to ME 10.5 and below. In ME10.6 we have added possibility to select target WebSphere server (Project properties -> MyEclipse -> Target WebSphere Server), which would automatically add the runtime to the classpath. However, in case of Web projects, those libraries would get deployed. We are going to release MyEclipse 10.7 with a fix for that and several other issues in the end of the next week (26.10.2012). This issue affects only Web projects. For now, one can do the following workaround:
1. Open .mymetadata file from the root folder of Web project
2. Paste following code inside <project-module> element:<packaging-strategy>com.genuitec.eclipse.blue</packaging-strategy>
3. Restart/open MyEclipse
4. The workaround should be removed when updated to ME10.7
ad9c14MemberThank you so much for your response. It worked great using workaround.
tazybabaMemberThank you so much…… NICE POSITING….!
-
AuthorPosts