#1254 new
John Cunningham

Cannot deploy a Play 1.2.3 on JBoss 6M2 or 7

Reported by John Cunningham | November 15th, 2011 @ 08:22 AM

If you build a new app using

play new myapp

then create an exploded WAR

play war myapp -o myapp.war

and deploy this folder into the JBoss deployment area, it fails for multiple reasons.

1) issue with Groovy re: jira.codehaus.org/browse/GROOVY-4673, removing the groovy file from the groovy jar seems to work, however it would be better to ship with a working version of Groovy for JBoss

2) java.lang.VerifyError: (class: net/sf/oval/guard/GuardAspect2, method: ajc$inlineAccessMethod$net_sf_oval_guard_GuardAspect2$net_sf_oval_guard_Guard$guardConstructorPost signature: (Lnet/sf/oval/guard/Guard;Ljava/lang/Object;Ljava/lang/reflect/Constructor;[Ljava/lang/Object;)V) Illega....

This seems to be a bug in AspectJ code which their site states can be fixed by using the -XnoInline java param - how can this be done in Play though?

3) Could be related to the above 2, Deployment "vfsfile:/C:/jboss-6.0.0.20100216-M2/server/default/deploy/messaging/connection-factories-service.xml" is in error due to the following reason(s): java.lang.LinkageError: loader constraint violation: loader (instance of ) previously initiated loading for a different type with name "org/w3c/dom/UserDataHandler"

I did use the specified jboss-web.xml file to isolate but this does not work.

I can use workarounds for now if you have them but I would like to evaluate this for enterprise use on a JBoss environment and this is a major stumbling block,

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem. WARNING: Do not fill bugs related describing security vulnerabilities. Email directly guillaume dot bort at gmail dot com for that.

Framework version: 1.2.3
Platform you're using: Windows 7, JBoss 6M2

Reproduction steps:as above

Details:

Comments and changes to this ticket

  • Stefano Crosta

    Stefano Crosta February 13th, 2012 @ 04:27 PM

    Similar issues still persist with Play 1.2.4 and JBoss 7

    While it's understood that JBoss deployment is not the favorite deployment method, it would be nice to have a collection of issues and workarounds!

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Pages