| WTP 3.0.4, JBoss 5.1.0.Beta1, and Web Beans RI (beta) [message #229657] |
Thu, 26 March 2009 11:46  |
 Marcos
Messages: 68
Registered: July 2009 |
Member |
|
|
- WTP 3.0.4
- Eclipse 3.4.2
- JBoss 5.1.0.Beta1
Hello, everybody!
I'm trying to try the new Web Beans RI (beta release) that comes with
JBoss 5.1
in WTP. First of all, I noticed that the Web Beans annotations were not
available to use in code. Eclipse was not finding the packages implemented
by Web Beans. So, looking in the JBoss directoy I found jars related to
Web Beans in the directory
{JBOSS_HOME}\server\default\deployers\webbeans.deployer and copy them to
my application's WEB-INF\lib directory. These are the jars:
jsr299-api.jar
webbeans-ri-int-jboss-ejb.jar
webbeans-ri-int-microcontainer.jar
webbeans-spi.jar
webbeans-core.jar
webbeans-ri-int-jbossas.jar
I also create an empty beans.xml file in the WEB-INF directory. The Web
Beans documentation says that this is necessary. But when I deploy my
application I get this error in the server log:
org.jboss.deployers.spi.DeploymentException: Error deploying:
vfszip:/C:/jboss-5.1.0.Beta1/server/default/deploy/Solicitac oesEAR2.ear/
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploym entException(DeploymentException.java:49)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryV isitor.deploy(BeanMetaDataFactoryVisitor.java:136)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeploye rWithInput.deploy(AbstractRealDeployerWithInput.java:125)
at
org.jboss.deployers.spi.deployer.helpers.AbstractComponentDe ployer.deployComponents(AbstractComponentDeployer.java:102)
at
org.jboss.deployers.spi.deployer.helpers.AbstractComponentDe ployer.internalDeploy(AbstractComponentDeployer.java:82)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeploye r.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy (DeployerWrapper.java:171)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy (DeployersImpl.java:1439)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstal lParentFirst(DeployersImpl.java:1157)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install( DeployersImpl.java:1098)
at
org.jboss.dependency.plugins.AbstractControllerContext.insta ll(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(Abst ractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementSta te(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveConte xts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveConte xts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(Abstr actController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(Abstr actController.java:553)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process( DeployersImpl.java:781)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(Ma inDeployerImpl.java:698)
at
org.jboss.system.server.profileservice.repository.MainDeploy erAdapter.process(MainDeployerAdapter.java:117)
at
org.jboss.system.server.profileservice.repository.ProfileDep loyAction.install(ProfileDeployAction.java:59)
at
org.jboss.system.server.profileservice.repository.AbstractPr ofileAction.install(AbstractProfileAction.java:53)
at
org.jboss.system.server.profileservice.repository.AbstractPr ofileService.install(AbstractProfileService.java:355)
at
org.jboss.dependency.plugins.AbstractControllerContext.insta ll(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(Abst ractController.java:1598)
at
org.jboss.dependency.plugins.AbstractController.incrementSta te(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveConte xts(AbstractController.java:1062)
at
org.jboss.dependency.plugins.AbstractController.resolveConte xts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.change(Abstr actController.java:822)
at
org.jboss.dependency.plugins.AbstractController.change(Abstr actController.java:553)
at
org.jboss.system.server.profileservice.repository.AbstractPr ofileService.activateProfile(AbstractProfileService.java:310 )
at
org.jboss.system.server.profileservice.ProfileServiceBootstr ap.start(ProfileServiceBootstrap.java:241)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerI mpl.java:461)
at org.jboss.Main.boot(Main.java:216)
at org.jboss.Main$1.run(Main.java:546)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalArgumentException: Exception loading class for
ScopeKey addition.
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryV isitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryV isitor.deploy(BeanMetaDataFactoryVisitor.java:126)
... 34 more
Caused by: java.lang.ClassNotFoundException:
org.jboss.webbeans.integration.jbossas.bootstrap.JBossWebBea nDiscovery
from
BaseClassLoader@c87802{VFSClassLoaderPolicy@13ed2e3 {name=vfszip:/C:/jboss-5.1.0.Beta1/server/default/deploy/Sol icitacoesEAR2.ear/
domain=ClassLoaderDomain@1117a20{name=DefaultDomain parentPolicy=BEFORE
parent=org.jboss.system.NoAnnotationURLClassLoader@5d173}
roots=[MemoryContextHandler@25639641[path=
context=vfsmemory://a5k03d-gt01vd-fsrdbtc3-1-fsrdd4h5-24
real=vfsmemory://a5k03d-gt01vd-fsrdbtc3-1-fsrdd4h5-24],
DelegatingHandler@19440197[path=SolicitacoesEAR2.ear
context=file:/C:/jboss-5.1.0.Beta1/server/default/deploy/
real=file:/C:/jboss-5.1.0.Beta1/server/default/deploy/Solici tacoesEAR2.ear],
DelegatingHandler@11896726[path=SolicitacoesEAR2.ear/SolicitacoesEJB2.jar
context=file:/C:/jboss-5.1.0.Beta1/server/default/deploy/
real=file:/C:/jboss-5.1.0.Beta1/server/default/deploy/Solici tacoesEAR2.ear/SolicitacoesEJB2.jar],
DelegatingHandler@30973108[path=SolicitacoesEAR2.ear/SolicitacoesEJB2Client.jar
context=file:/C:/jboss-5.1.0.Beta1/server/default/deploy/
real=file:/C:/jboss-5.1.0.Beta1/server/default/deploy/Solici tacoesEAR2.ear/SolicitacoesEJB2Client.jar]]
delegates=null exported=[META-INF,
br.urca.solicitacoes.implementacao.seguranca,
br.urca.solicitacoes.implementacao, br.urca.solicitacoes]
<IMPORT-ALL>NON_EMPTY}}
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(Bas eClassLoader.java:422)
at java.lang.ClassLoader.loadClass(Unknown Source)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryV isitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:63)
... 35 more
Is WTP already prepared to use this release of JBoss? Am I missing
something?
Thank you.
Marcos
|
|
|
| Re: WTP 3.0.4, JBoss 5.1.0.Beta1, and Web Beans RI (beta) [message #229753 is a reply to message #229657] |
Fri, 27 March 2009 09:06  |
Eclipse User |
|
|
|
Originally posted by: wknauf_NO_._INSIDE_hg-online.de
Hi Marcos,
the easiest way to achieve this is:
-open file
" plugins\org.eclipse.jst.server.generic.jboss_1.5.205.v200805 140145\servers\jboss5.serverdef "
-in the section "<classpath id="jboss.project" >", add an "include" tag:
<include name="server/default/deployers/webbeans.deployer/*.jar" />
-start eclipse with option "eclipse.exe -clean"
-delete and re-create your server runtime! Otherwise, your project classpath
would not be updated.
Please file an enhancement request in bugzilla.
The best solution would be to add a new server runtime "JBoss 5.1", but the WTP
guys could also modify the "5.0".
Are there more differences in the library structure compared to 5.0?
I would not advice to copy the JARs to your own webapp, because the JBoss
classloaders might get confused if they find a class in two JARs, and this
probably is the reason for your error.
Best regards
Wolfgang
Marcos schrieb:
> - WTP 3.0.4
> - Eclipse 3.4.2
> - JBoss 5.1.0.Beta1
>
> Hello, everybody!
>
> I'm trying to try the new Web Beans RI (beta release) that comes with
> JBoss 5.1
> in WTP. First of all, I noticed that the Web Beans annotations were not
> available to use in code. Eclipse was not finding the packages
> implemented by Web Beans. So, looking in the JBoss directoy I found jars
> related to Web Beans in the directory
> {JBOSS_HOME}\server\default\deployers\webbeans.deployer and copy them to
> my application's WEB-INF\lib directory. These are the jars:
>
> jsr299-api.jar
> webbeans-ri-int-jboss-ejb.jar
> webbeans-ri-int-microcontainer.jar
> webbeans-spi.jar
> webbeans-core.jar
> webbeans-ri-int-jbossas.jar
>
|
|
|
|
| Re: WTP 3.0.4, JBoss 5.1.0.Beta1, and Web Beans RI (beta) [message #229777 is a reply to message #229761] |
Fri, 27 March 2009 16:34 |
| Eclipse User |
|
|
|
Originally posted by: wknauf_NO_._INSIDE_hg-online.de
Hi Marcos,
about the WTP runtime fix: well, file a bug report and see when it will be fixed
;-).
I don't know WebBeans, and I don't whether there are any plans for WTP to
support this :-(.
Best regards
Wolfgang
Marcos schrieb:
> Hello, Wolfgang.
>
>
> I think this is the right thing to be made. Regarding this, do you have
> an idea when a new server runtime for JBoss 5.1 or an update to the
> JBoss 5.0 runtime that works with JBoss 5.1 will be available? I think
> that Web Beans is a big step in productivity for the JEE developer and
> that WTP should support it as soon as possible.
>
> Marcos
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03320 seconds
] 
Search
Help
Register
Login
Home
