-
1. Re: Is JBoss 6 already up to this task?
jaikiran Jun 29, 2010 6:26 AM (in response to o.bergner)Olaf,
Welcome to the forums.
Olaf Bergner wrote:
I'm currently implementing a prototype application meant to evaluate the usefulness of JEE6 in general and CDI specifically for my needs. Since mine is not a web application but rather a complex back office solution divided into several modules using contract-first web services and JMS as its remoting layer, an appropriate application server should fulfill the following requirements:
- Ear deployment
Definitely, (any version of) JBoss AS allows this (and so do other application servers).
Olaf Bergner wrote:
The rules for this are governed by the JPA spec and aren't specific to JBoss AS.
Olaf Bergner wrote:
Yes, the latest 6.0.0 M3 of JBoss AS provides this.
Olaf Bergner wrote:
Yes, JBoss AS has this.
Olaf Bergner wrote:
5. JMS support
Yes, JBoss AS has this. Infact, the latest version 6.0.0 M3 of JBoss AS has the impressive HornetQ by default.
You might also want to go through these series of articles/tutorials before deciding what you require http://in.relation.to/Bloggers/AHitchhikersGuideToJavaEE6ApplicationSetupPartI
-
2. Re: Is JBoss 6 already up to this task?
o.bergner Jun 29, 2010 10:54 AM (in response to jaikiran)Hi Jaikiran,
thanks for your efforts, I will definitely give JBoss a try.
{quote}
Olaf Bergner wrote:
I'm currently implementing a prototype application meant to evaluate the usefulness of JEE6 in general and CDI specifically for my needs. Since mine is not a web application but rather a complex back office solution divided into several modules using contract-first web services and JMS as its remoting layer, an appropriate application server should fulfill the following requirements:
- Ear deployment
Definitely, (any version of) JBoss AS allows this (and so do other application servers).
{quote}
I asked this question because I got a strange exception as soon as I added a jboss-app.xml deployment
descriptor to my ear. Therefore, I suspected that JBoss 6 may not support ear deployment yet.
{quote}
Olaf Bergner wrote:
The rules for this are governed by the JPA spec and aren't specific to JBoss AS.
{quote}
Yes, I thought so, too, but Glassfish seems to have a lot of problems with this setup.
{quote}
Olaf Bergner wrote:
Yes, JBoss AS has this.
{quote}
Since my web services were originally developed on Glassfish's Metro stack, and since JBossWS is rumored
to support Metro, I would naturally like to use this option. Does anyone know what I have to do to
activate Metro support in JBoss 6? I'm asking since deploying my unmodified web services on top of JBoss 6'
default CXF stack fails. Metro and CXF - amongst other differences - seem to resolve the "wsdlLocation"
attribute differently.
Many thanks,
Olaf