Use MyFaces instead of Mojarra
by Rafael Castro
Hello JBoss Team,
I would like to know if i can use MyFaces instead of Mojarra as jsf implementation. Sorry if this is not the place to ask this question.
Thanks
Rafael Castro
12 years, 9 months
Exploded Oddity with that Spring/Hibernate Example
by Jim Tyrrell
Team,
See the attached screen shot:
I have an exploded war file (spring/hibernate) that I made changes to based on Marius (THANK YOU!!!!!!!!!) feedback. The application deploys, but does not run when executed with the following errors:
10:08:12,829 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BRMSPoc].[brmsDispatcher]] (http--127.0.0.1-8080-1) Servlet.service() for servlet brmsDispatcher threw exception: java.lang.IllegalAccessException: Class org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer can not access a member of class org.jboss.stdio.StdioContext$DelegatingPrintStream with modifiers "public"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) [:1.6.0_24]
at java.lang.reflect.Method.invoke(Method.java:588) [:1.6.0_24]
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:957) [mvel2-2.0.16.jar:]
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:314) [mvel2-2.0.16.jar:]
at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:137) [mvel2-2.0.16.jar:]
at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:137) [mvel2-2.0.16.jar:]
at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85) [mvel2-2.0.16.jar:]
at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:104) [mvel2-2.0.16.jar:]
at org.mvel2.MVEL.executeExpression(MVEL.java:1001) [mvel2-2.0.16.jar:]
at org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:103) [drools-core-5.1.1.jar:]
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917) [drools-core-5.1.1.jar:]
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:856) [drools-core-5.1.1.jar:]
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1071) [drools-core-5.1.1.jar:]
Is the .failed from the screen shot on all the exploded jars in the war from when I had not made all of Marius changes?
Is it expected behavior on an exploded war?
How would I clean these up? Do I need to?
What effect/affect are these having on my current deployment? Now that I mostly think I have my application in a state where I can run/deploy my application?
Does it make sense to mark all of these "embedded/included" jar files as failed?
I am not sure if this is expected behavior, bugs or what? Some advice pretty please?
I guess you have to love lazy loading, and runtime exceptions. :S!!!!!
Jim Tyrrell
Senior JBoss Solutions Architect
Did you see RHT on Fox News around Cloud?
http://video.foxbusiness.com/v/1039347607001/red-hat-ceo-on-the-growth-of...
12 years, 9 months
Extending AS 7 and testing subsystem parsing
by Kabir Khan
There is a guide to extending AS 7 which currently lives in the Admin Guide https://docs.jboss.org/author/display/AS7/Admin+Guide#AdminGuide-Extendin... (although I've seen mention of moving it somewhere else).
The guide has a maven archetype to set up a skeleton project, this will be deployed later today. The archetype contains tests for parsing the model, most of this was stolen from other places but what I think it is new in getting different things together. So we can parse the model and install in the controller, making sure that the proper operations get called resulting in a real model in the controller and services getting installed without the need for any fancy module setup. It is still a bit basic but I think it would be a good idea to copy the utility classes into the AS 7 codebase somewhere (the question is where) so that we can evolve them to give better functionality in the archetype and of course to our own subsystem testing. The example code using this stuff can be found at https://docs.jboss.org/author/download/attachments/5439694/acme-subsystem....
The main thing I can think of that is missing at the moment is to be able to preinitialize the controller with model elements and services that should be there before your extension is deployed.
12 years, 9 months
jboss-msc and jboss-modules m2eclipse issue
by Michal Linhard
Hi all,
I'm using Eclipse + m2e to browse and debug AS7 code.
Recently I updated to Eclipse 3.7 + m2eclipse 1.0.0.20110607-2117, which
does advanced validation of maven projects it imports.
It has problem with maven-injection-plugin we use in projects jboss-msc
and jboss-modules.
I was able to work around this issue by defining lifecycle mapping as
described here:
http://wiki.eclipse.org/M2E_plugin_execution_not_covered
to avoid doing this on every import for those who use m2eclipse we could
define the lifecycle mappings somewhere in the project pom or parent pom.
WDYT ?
m.
--
Michal Linhard
Quality Assurance Engineer
Red Hat Czech s.r.o.
Purkynova 99 612 45 Brno, Czech Republic
phone: +420 532 294 320 ext. 62320
mobile: +420 728 626 363
12 years, 9 months
Re: [jboss-as7-dev] MDB Support in AS 7
by Carlo de Wolf
Ah yes, at the moment you have to specify a manual dependency on the
hornetq-ra module.
See
https://github.com/wolfc/jboss-as/blob/AS7-579/testsuite/spec/src/test/re...
Don't know how to specify this in a war, but somebody on the dev list
will...
Carlo
On 07/12/2011 11:39 PM, Martin Schwartzman wrote:
>
> Carlo,
>
> I used the downloaded zip wolfc-jboss-as-f896114.zip from github.
> Using it I builtjboss-as-7.1.0.Alpha1-SNAPSHOT. I deployed my test app
> and got the following from the standalone/log
>
> 15:33:30,807 INFO [org.jboss.as.server.deployment] (MSC service
> thread 1-6) Starting deployment of "jboss-as-helloworld.war"
>
> 15:33:30,932 INFO [org.jboss.weld] (MSC service thread 1-3)
> Processing CDI deployment: jboss-as-helloworld.war
>
> 15:33:30,978 INFO [org.jboss.weld] (MSC service thread 1-6) Starting
> Services for CDI deployment: jboss-as-helloworld.war
>
> 15:33:30,994 INFO [org.jboss.weld.Version] (MSC service thread 1-6)
> WELD-000900 1.1.2 (AS7)
>
> 15:33:31,010 INFO [org.jboss.weld] (MSC service thread 1-7) Starting
> weld service
>
> 15:33:31,010 ERROR [org.jboss.msc.service.fail] (MSC service thread
> 1-3) MSC00001: Failed to start service
> jboss.deployment.unit."jboss-as-helloworld.war".component.HelloWorldMDB.CREATE:
> org.jboss.msc.service.StartException in service
> jboss.deployment.unit."jboss-as-helloworld.war".component.HelloWorldMDB.CREATE:
> Failed to start service
>
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1786)
>
> at
> org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> [:1.6.0_25]
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> [:1.6.0_25]
>
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
>
> Caused by: java.lang.RuntimeException:
> java.lang.ClassNotFoundException:
> org.hornetq.ra.inflow.HornetQActivationSpec from [Module
> "deployment.jboss-as-helloworld.war:main" from Service Module Loader]
>
> at
> org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:84)
>
> at
> org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:69)
>
> at
> org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:78)
>
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
>
> ... 4 more
>
> Caused by: java.lang.ClassNotFoundException:
> org.hornetq.ra.inflow.HornetQActivationSpec from [Module
> "deployment.jboss-as-helloworld.war:main" from Service Module Loader]
>
> at
> org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
>
> at
> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
>
> at
> org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:330)
>
> at
> org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
>
> at
> org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
>
> at java.lang.Class.forName0(Native Method) [:1.6.0_25]
>
> at java.lang.Class.forName(Class.java:247) [:1.6.0_25]
>
> at
> org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:68)
>
> ... 7 more
>
> 15:33:31,447 INFO [org.jboss.as.server.controller]
> (DeploymentScanner-threads - 2) Deployment of
> "jboss-as-helloworld.war" was rolled back with failure message
> {"Failed services" =>
> {"jboss.deployment.unit.\"jboss-as-helloworld.war\".component.HelloWorldMDB.CREATE"
> => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"jboss-as-helloworld.war\".component.HelloWorldMDB.CREATE:
> Failed to start service"},"Services with missing/unavailable
> dependencies" =>
> ["jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/wpsCompressQueue.jboss.deployment.unit.\"jboss-as-helloworld.war\".module.jboss-as-helloworld.jboss-as-helloworld.3
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/queue/wpsCompressQueue
> ]","jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionFactory\".jboss.deployment.unit.\"jboss-as-helloworld.war\".module.jboss-as-helloworld.jboss-as-helloworld.2
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/jms/QueueConnectionFactory
> ]","jboss.deployment.unit.\"jboss-as-helloworld.war\".jndiDependencyService
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/wpsCompressQueue,
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionFactory\"
> ]","jboss.deployment.unit.\"jboss-as-helloworld.war\".component.\"org.jboss.as.quickstarts.helloworld.HelloWorldServlet\".START
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/wpsCompressQueue,
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionFactory\"
> ]"]}
>
> 15:33:31,447 INFO [org.jboss.weld] (MSC service thread 1-6) Stopping
> weld service
>
> 15:33:31,463 INFO [org.jboss.as.server.deployment] (MSC service
> thread 1-1) Stopped deployment jboss-as-helloworld.war in 25ms
>
> 15:33:31,478 ERROR [org.jboss.as.deployment]
> (DeploymentScanner-threads - 1) {"Composite operation failed and was
> rolled back. Steps that failed:" => {"Operation step-2" => {"Failed
> services" =>
> {"jboss.deployment.unit.\"jboss-as-helloworld.war\".component.HelloWorldMDB.CREATE"
> => "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"jboss-as-helloworld.war\".component.HelloWorldMDB.CREATE:
> Failed to start service"},"Services with missing/unavailable
> dependencies" =>
> ["jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/wpsCompressQueue.jboss.deployment.unit.\"jboss-as-helloworld.war\".module.jboss-as-helloworld.jboss-as-helloworld.3
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/queue/wpsCompressQueue
> ]","jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionFactory\".jboss.deployment.unit.\"jboss-as-helloworld.war\".module.jboss-as-helloworld.jboss-as-helloworld.2
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/jms/QueueConnectionFactory
> ]","jboss.deployment.unit.\"jboss-as-helloworld.war\".jndiDependencyService
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/wpsCompressQueue,
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionFactory\"
> ]","jboss.deployment.unit.\"jboss-as-helloworld.war\".component.\"org.jboss.as.quickstarts.helloworld.HelloWorldServlet\".START
> missing [
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.env/wpsCompressQueue,
> jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionFactory\"
> ]"]}}}
>
> Martin
>
>
12 years, 9 months
MDB Support in AS 7
by Martin Schwartzman
I just built today's jboss-as-7.1.0.Alpha1-SNAPSHOT. I used the
jboss-as-quickstarts-7.0.0.CR1\helloworld example and added an MDB. I
modified the HelloWorldServlet to send a TextMessage to the MDB but it
seems MDB's are still not working? Any idea when MDB's will be working
in JBoss AS 7? Below is the error message I get in the standalone log.
09:15:51,233 INFO [org.jboss.as.server.controller]
(DeploymentScanner-threads - 1) Deployment of "jboss-as-helloworld.war"
was rolled back with failure message {"Services with missing/unavailable
dependencies" =>
["jboss.deployment.unit.\"jboss-as-helloworld.war\".component.\"org.jbos
s.as.quickstarts.helloworld.HelloWorldServlet\".START missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/wpsCompressQueue,
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionF
actory\"
]","jboss.deployment.unit.\"jboss-as-helloworld.war\".jndiDependencyServ
ice missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/wpsCompressQueue,
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionF
actory\"
]","jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-hellow
orld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connect
ionFactory\".jboss.deployment.unit.\"jboss-as-helloworld.war\".module.jb
oss-as-helloworld.jboss-as-helloworld.0 missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/jms/QueueConnectionFactory
]","jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-hellow
orld.env/wpsCompressQueue.jboss.deployment.unit.\"jboss-as-helloworld.wa
r\".module.jboss-as-helloworld.jboss-as-helloworld.1 missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/queue/wpsCompressQueue ]"]}
09:15:51,233 INFO [org.jboss.weld] (MSC service thread 1-7) Stopping
weld service
09:15:51,249 INFO [org.jboss.as.server.deployment] (MSC service thread
1-2) Stopped deployment jboss-as-helloworld.war in 25ms
09:15:51,249 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads
- 2) {"Composite operation failed and was rolled back. Steps that
failed:" => {"Operation step-2" => {"Services with missing/unavailable
dependencies" =>
["jboss.deployment.unit.\"jboss-as-helloworld.war\".component.\"org.jbos
s.as.quickstarts.helloworld.HelloWorldServlet\".START missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/wpsCompressQueue,
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionF
actory\"
]","jboss.deployment.unit.\"jboss-as-helloworld.war\".jndiDependencyServ
ice missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/wpsCompressQueue,
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connectionF
actory\"
]","jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-hellow
orld.\"env/org.jboss.as.quickstarts.helloworld.HelloWorldServlet/connect
ionFactory\".jboss.deployment.unit.\"jboss-as-helloworld.war\".module.jb
oss-as-helloworld.jboss-as-helloworld.0 missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/jms/QueueConnectionFactory
]","jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-hellow
orld.env/wpsCompressQueue.jboss.deployment.unit.\"jboss-as-helloworld.wa
r\".module.jboss-as-helloworld.jboss-as-helloworld.1 missing [
jboss.naming.context.java.module.jboss-as-helloworld.jboss-as-helloworld
.env/queue/wpsCompressQueue ]"]}}}
Thanks,
Martin
12 years, 9 months
Deployment descriptors: XML schemas backward compatible ?
by Marian Muller
Hi JBoss Team,
Sorry if this is not the right place to ask, but I had no luck in users
list.
I would like to know if JBoss's XML schemas and DTDs for deployment
descriptors support backward compatibility, and if there are plans to keep
backward compatibility in the future.
Could someone confirm it or point me to a relevant document ?
Thanks.
--
Marian MULLER
SERLI
12 years, 9 months
maven plugin doco?
by Bill Burke
Does the new AS7 maven plugin work any differently than the old one?
(i.e. does it allow you to emded AS7 instead of having to start it up
yourself?)
Is there maven plugin doco anywhere?
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
12 years, 9 months
