[JBoss Tools] - m2e(clipse)-wtp 0.14.0 : New & Noteworthy
by Fred Bricon
Fred Bricon [http://community.jboss.org/people/fbricon] modified the blog post:
"m2e(clipse)-wtp 0.14.0 : New & Noteworthy"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/09/30/m2eclipse-wtp-...
--------------------------------------------------------------
Maven Integration for Eclipse WTP 0.14.0, a.k.a m2eclipse-wtp, a.k.a m2e-wtp is out the door. This new release brings its share of new features and enhancements, as well as a bunch of bug fixes. The complete release notes are available https://issues.sonatype.org/secure/ReleaseNote.jspa?projectId=10310&versi... here.
m2e-wtp 0.14.0 works with Eclipse Helios and Indigo, requires at least m2e 1.0 and mavenarchiver plugin > 0.14.0 (0.15.0 should be automatically installed). As usual, m2e-wtp can be installed from :
* the Maven Discovery mechanism : Window > Preferences > Maven > Discovery > Open catalog
* the http://marketplace.eclipse.org/content/maven-integration-eclipse-wtp Eclipse Marketplace : Help > Eclipse Marketplace
* the update site : *http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/ http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/*
So what's new and noteworthy in 0.14.0? Let's see :
h3. New support for Application Client projects
Application Client packaging has been introduced with the new http://maven.apache.org/plugins/maven-acr-plugin/ maven-acr-plugin. Support for app-client type dependencies has been http://jira.codehaus.org/browse/MEAR-137 added in maven-ear-plugin 2.6. Since Application Client projects are natively supported in WTP, we added a new configurator for app-client projects. When an app-client project is imported / configured via m2e, the Application Client Facet will be automatically installed, its version inferred from the contents of META-INF/application-client.xml. Filtering of the deployment descriptor is supported.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-acr-plugin</artifactId>
<version>1.0</version>
<extensions>true</extensions>
<configuration>
<archive>
<manifest>
<mainClass>foo.bar.appclient.Main</mainClass>
</manifest>
</archive>
<filterDeploymentDescriptor>true</filterDeploymentDescriptor>
</configuration>
</plugin>
http://community.jboss.org/servlet/JiveServlet/showImage/38-4192-17064/ap... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4192-1706...
h3. New support for Web Fragment projects
If a project contains a META-INF/web-fragment.xml in it's compilation output folder, the Web Fragment Facet is automatically installed upon maven project configuration (the Utility Facet is removed if necessary). Note that, as per the Java EE6 spec - and WTP is very picky about it-, Web Fragment projects *must* use Java 1.6. Failure to comply will fail the configuration and an error marker will be displayed.
http://community.jboss.org/servlet/JiveServlet/showImage/38-4192-17065/we... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4192-1706...
h3. The use of target/m2e-wtp/web-resources is now optional
Remember, target/m2e-wtp/web-resources/ https://github.com/sonatype/m2eclipse-wtp/wiki/What-is-this-web-resources... is used to allow the deployment of automatically generated web resources with WTP.
On some occasions however, having target/m2e-wtp/web-resources/ might cause some troubles (incompatibilities with WTP editors, https://issues.sonatype.org/browse/MECLIPSEWTP-136 IBM RAD, https://issues.sonatype.org/browse/MECLIPSEWTP-180 using Servlet.getRealPath(...) in your code).
As a workaround, you can choose to not use target/m2e-wtp/web-resources/ and generate the pom.properties and MANIFEST.MF files in your source directory instead (It'll be your responsibility to add these files to your SCM ignore list).
In order to remove target/m2e-wtp/web-resources/ from the list of deployed folders, you need to change some preferences :
* on your project only : right-click on the project > Properties > Maven > WTP : check "Enable Project Specific Settings" and uncheck "Maven Archiver generates files under the build directory"
* on the whole workspace : Window > Preferences > Maven > WTP : uncheck "Maven Archiver generates files under the build directory"
http://community.jboss.org/servlet/JiveServlet/showImage/38-4192-17067/wa... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4192-1706...
Please note that *this setting will be overridden if web resource filtering is in use*, that is if the maven-war-plugin http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filterin... configuration declares <webResources> or sets <filterDeploymentDescriptor> to true. The reason is simple : you don't want to see your source files overwritten by the filtering mechanism (and it would also lead to some not-so-funny build loops).
h3. Custom file name mapping for web project dependencies
Since the maven-war-plugin allows file name customization for librairies and TLDs, based on patterns ( http://maven.apache.org/plugins/maven-war-plugin/examples/file-name-mappi... http://maven.apache.org/plugins/maven-war-plugin/examples/file-name-mappi...), we added the the same feature in m2e-wtp. That will allow you to use a version-less name mapping for dependencies, like :
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<outputFileNameMapping>@{groupId}@-@{artifactId}@.(a){extension}@</outputFileNameMapping>
</configuration>
</plugin>
The trick here is, in order to support non default filename mappings of dependencies listed in the Maven Library, the artifact is copied to the build directory (the target/ folder by default) under its new name. So if you happen to run a clean build of your project, wiping out that directory, you will need to manually run "Maven > Update Project configuration" on your project.
h3. Option to not publish overlay changes automatically
In order to support publishing of overlay changes automatically, m2e-wtp aggressively cleared the cache of the servers your application is deployed to. However, The overlay feature still being in an experimental state, we decided to be more conservative with regard to server publishing, so a new "Automatically republish servers on overlay modification" preference has been added to *Window > Preferences > Server > Overlays*.
http://community.jboss.org/servlet/JiveServlet/showImage/38-4192-17066/ov... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4192-1706...
Overlays support is not bound to Maven, that's why it's under the Server preferences.
h3. Support for the new tag="defaultRootSource" introduced in WTP 3.3.1
When several source folders are declared in the .settings/org.eclipse.wst.common.component file, WTP prior to 3.3.1 (Indigo SR1) tended to generate files (web.xml, faces-config.xml, ...) in the first folder it found. Since web projects define +target/m2e-wtp/web-resources+ as the first source folder (+target/m2e-wtp/ear-resources/+ for EAR projects), that would cause some issues. In WTP 3.3.1, a new tag has been introduced, designed to indicate which source folder should be used by default, when files need to be looked for / generated. m2e-wtp now adds this tag when WTP 3.3.1 is installed :
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="web-0.0.1-SNAPSHOT">
<wb-resource deploy-path="/" source-path="/target/m2e-wtp/web-resources"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp" tag="defaultRootSource"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
<property name="context-root" value="multi-web"/>
<property name="java-output-path" value="/multi-web/target/classes"/>
</wb-module>
</project-modules>
h3. A bit of documentation
As many projects, unfortunately, m2e-wtp doesn't shine in the documentation area. I've been using the github Wiki ( https://github.com/sonatype/m2eclipse-wtp/wiki https://github.com/sonatype/m2eclipse-wtp/wiki) to start a relatively modest FAQ. I'm planning on adding more content in the near future, but I'm also hoping the community at large will want to contribute some docs of its own. You just need a github account to be able to edit the Wiki.
As always, if you find any issue, please open a bug report at https://issues.sonatype.org/browse/MECLIPSEWTP https://issues.sonatype.org/browse/MECLIPSEWTP (and don't forget to attach some test projects).
Happy coding.
Fred.
https://twitter.com/#%21/fbricon https://twitter.com/#!/fbricon
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/09/30/m2eclipse-wtp-...]
12 years, 7 months
[EJB3] - EJB deployment error when migrating to jboss 6.1
by Dohan Chinthaka
Dohan Chinthaka [http://community.jboss.org/people/dohancrp] created the discussion
"EJB deployment error when migrating to jboss 6.1"
To view the discussion, visit: http://community.jboss.org/message/629496#629496
--------------------------------------------------------------
I am migrating from jboss 5.1 to 6.1. I have an ear which having some EJBs and a war. I am getting following error after deploying it in 6.1.
12:00:23,184 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=ZServer.ear/#ZPersistCtx
12:00:23,204 ERROR [AbstractKernelController] Error installing to Start: name=persistence.unit:unitName=ZServer.ear/#ZPersistCtx state=Create: java.lang.ClassCastException: org.hibernate.ejb.HibernatePersistence cannot be cast to javax.persistence.spi.PersistenceProvider
at org.jboss.jpa.builder.DefaultCEMFBuilder.build(DefaultCEMFBuilder.java:46) [:1.0.2-alpha-4]
at org.jboss.as.jpa.scanner.HackCEMFBuilder.build(HackCEMFBuilder.java:49) [:6.1.0.Final]
at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:275) [:1.0.2-alpha-4]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26]
.
.
.
at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.1.0.Final]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.1.0.Final]
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-6]
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-6]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
12:00:23,442 INFO [EJBContainer] STARTED EJB: com.al.sqlgen.ejb.ResponseListnerMDBBean ejbName: ResponseListnerMDBBean
12:00:23,751 WARN [TimerServiceContainer] EJBTHREE-2193: using deprecated TimerServiceFactory for restoring timers
I have following libs in ear.
dohan@mypc:~/usr/local/jboss-6.1.0.Final/server/all/deploy/ZServer.ear/lib> ls
antlr-2.7.6.jar flex-messaging-remoting.jar
asm-attrs.jar hibernate3.jar
asm.jar hibernate-annotations.jar
cglib-2.1.3.jar hibernate-commons-annotations.jar
commons-collections-2.1.1.jar hibernate-entitymanager.jar
commons-io-1.4.jar hibernate-tools.jar
commons-logging-1.1.jar HsmSEE.jar
dom4j-1.6.1.jar javassist.jar
ehcache-1.2.3.jar jdbc2_0-stdext.jar
ejb3-persistence.2.jar jta.jar
I tried changing class loading procedure as mentioned http://community.jboss.org/docs/DOC-9288 here but still getting same error. Appreciate if anyone can help me to solve this.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/629496#629496]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 7 months
[JNDI and Naming] - Re: Using JNDI to connect to Websphere MQ, without hardcoded info
by zecas zecas
zecas zecas [http://community.jboss.org/people/zecas] created the discussion
"Re: Using JNDI to connect to Websphere MQ, without hardcoded info"
To view the discussion, visit: http://community.jboss.org/message/629442#629442
--------------------------------------------------------------
Hi,
First of all, thank you for your help and precise replies. Untill today, I had given up temporarily on this subject, and rolled back to using just the JBoss Messaging, as I had lot's of other things going on, things to be developed. :)
Now I'm again, back to this subject, and I'll give it another try.
Some things about the subject are a bit confusing, but your last post gave me a fresh new hope about putting this thing up and running.
About the incomming/outgoing messaging, I will have both, an MDB to consume from an MQ queue, and an injected JMS connection to send up messages to another MQ queue, both with diferent jndi names, etc.
So since I was going for an MDB in EJB3, I was not thinking about the need for an ejb-jar.xml on the project ... I'll have to try it out.
If I can take everything that is specific to the environment out of code, I'll have exactly what I'm looking for.
I'll re-try this all over again, starting from the incomming MDB message consuming first.
I'll post my findings, so someone else may get some more insight examples from my mess :D
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/629442#629442]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 7 months
[jBPM] - Re: jBPM 5.1 with SQL Server
by Dominique Paquin
Dominique Paquin [http://community.jboss.org/people/paqman] created the discussion
"Re: jBPM 5.1 with SQL Server"
To view the discussion, visit: http://community.jboss.org/message/629413#629413
--------------------------------------------------------------
Unfortunately, I didn't come to any valid solution yet so I deffered this to one of out top-gun resources herre which is currently on prolonged vacations. He should be back in 10 days and he will most assuredly work on this and try to find a solution.
But it really seems to boil down to provide an already working entity manager as well as a transaction manager with the environment object. The only problem is that the one we are currently implementing in our product (which works directly with hibernate instead of JPA) does not extends the exact same Interface that jBPM expects to receive in the environment (refer to my first post).
So there are a bit more research to do, but as soon as we have a valid solution, I will try to come back here and provide a solution.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/629413#629413]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 7 months
