December 2007 - jboss-dev-forums - Jboss List Archives

[Design of JCA on JBoss] - Re: JBAS-5023

by adrian＠jboss.org

That looks correct. This goes with the other task to be able to parse multiple files in one parsing deployer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110466#4110466 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110466

18 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM client examples

by richard.opalka＠jboss.com

Hi team/community the WS-RM public API - org.jboss.ws.extensions.wsrm.api.* was simplified and javadoc was added there. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110457#4110457 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110457

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - JBossGenericBeanMetaData for @Stateful

by scott.stark＠jboss.org

I'm seeing JBossGenericBeanMetaData being created for an annotation only deployment: | @Stateful(name="Stateful3Bean") | @Remote({Stateful3IF.class}) | public class Stateful3Bean implements Stateful3IF { | ... | for which a jboss.xml like the following has been created: | [starksm@succubus ejb]$ cat META-INF/jboss.xml | <?xml version="1.0" encoding="UTF-8"?> | | <jboss xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0"> | <unauthenticated-principal>guest</unauthenticated-principal> | <enterprise-beans> | <ejb> | <ejb-name>Stateful3Bean</ejb-name> | <jndi-name>com_sun_ts_tests_ejb30_pkg_scope_Stateful3Bean</jndi-name> | </ejb> | <ejb> | <ejb-name>Stateless3Bean</ejb-name> | <jndi-name>com_sun_ts_tests_ejb30_pkg_scope_Stateless3Bean</jndi-name> | </ejb> | </enterprise-beans> | </jboss> | Should this be translated into a JBossSessionBeanMetaData when merged with the annotation generated metadata? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110442#4110442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110442

18 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: DeploymentInfo/Template MCF

by vickyk

What does this error mean ? Testcase: testAddDataSource took 4.34 sec | Caused an ERROR | null | javax.xml.bind.MarshalException | - with linked exception: | [com.sun.istack.SAXException2: unable to marshal type "org.jboss.resource.metadata.mcf.ManagedConnectionFactoryDeploymentGroup" as an element because it is missing an @XmlRootElement annotation] | at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:320) | at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:246) | at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:96) | at org.jboss.resource.deployers.management.DsDataSourceTemplate.writeTemplate(DsDataSourceTemplate.java:120) | at org.jboss.resource.deployers.management.DsDataSourceTemplate.applyTemplate(DsDataSourceTemplate.java:61) | at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:550) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:56) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:771) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) | Caused by: com.sun.istack.SAXException2: unable to marshal type "org.jboss.resource.metadata.mcf.ManagedConnectionFactoryDeploymentGroup" as an element because it is missing an @XmlRootElement annotation | at com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:242) | at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:303) | at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:488) | at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:317) | at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:246) | at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:96) | at org.jboss.resource.deployers.management.DsDataSourceTemplate.writeTemplate(DsDataSourceTemplate.java:120) | at org.jboss.resource.deployers.management.DsDataSourceTemplate.applyTemplate(DsDataSourceTemplate.java:61) | at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:550) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:56) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:771) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at AOPProxy$1.applyTemplate(AOPProxy$1.java) | at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:404) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at AOPProxy$1.applyTemplate(AOPProxy$1.java) | at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:404) I made the following changes 1) In the start() of the org.jboss.resource.deployers.management.DsDataSourceTemplateInfo I added attachment by calling this code | ManagedObjectImpl mo = new ManagedObjectImpl(attachmentName); | | //JBAS-4671 | log.debug("Going to start in DsDataSourceTemplate"); | Object attachment = loadClass(attachmentName); | log.debug("Added attachment in loadClass"+attachment); | Serializable serAttachment = (java.io.Serializable)attachment; | mo.setAttachment(serAttachment); | log.debug("Done with attaching ."); | //JBAS-4671 2) In the writeTemplate of the DsDataSourceTemplate Object group = mo.getAttachment(); | log.debug("Getting the name "+mo.getName()); | log.debug("Getting the attachment which is added in the DsDataSourceTemplateInfo "+group); | if( group instanceof ManagedConnectionFactoryDeploymentGroup ) | { | //JBAS-4671 | log.debug("------------->"+group); | AbstractManagedObjectFactory mof = new AbstractManagedObjectFactory(); | ManagedObject dsDeploymentMO = mof.initManagedObject((Serializable)group,"DataSource", "NoTx"); | log.debug("------------->"+values.getProperties().values()); | try{ | for(ManagedProperty moprop : values.getProperties().values()) | { | ManagedProperty moProp = dsDeploymentMO.getProperty(moprop.getName()); | if(moProp!=null) | moProp.setValue((Serializable)moprop.getValue()); | log.debug("setting ManagedProperty "+moprop.getValue()+ "for "+moprop.getName()); | } | } | catch(Exception exp){ | log.debug("Eat up this "+exp); | } | //JBAS-4671 | } Earlier the group was coming as null as the attachment want not added to ManagedObject in Step 1 . Any clue what it is complaining about now ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110433#4110433 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110433

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Empty @Remote on bean class

by scott.stark＠jboss.org

The AnnotationMetaDataDeployer was assuming metadata complete unless there was a jboss metadata that was not marked as complete. Because there was no jboss.xml/ejb-jar.xml the ejb3 test is not being processed. | [starksm@succubus ejb3]$ jar -tf output/test-lib/ejbthree1146.jar | org/jboss/ejb3/test/ejbthree1146/TestBean.class | org/jboss/ejb3/test/ejbthree1146/TestBeanBase.class | org/jboss/ejb3/test/ejbthree1146/TestRemoteBusinessInterface.class | I added a metaDataCompleteIsDefault property to the AnnotationMetaDataDeployer so that you can set that to false to have a deployment without a JBossMetaData instance to be processed. | <bean name="AnnotationMetaDataDeployer" | class="org.jboss.deployment.AnnotationMetaDataDeployer"> | <property name="metaDataCompleteIsDefault">false</property> | </bean> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110428#4110428 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110428

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Annotation Processors and TCK

by ALRubinger

JBCTS-705 is now failing due to: Caused by: java.lang.IllegalArgumentException: 2.1 bean com.blah.test.RemoveBean has more than one local interface defined | at org.jboss.metadata.annotation.creator.ejb.LocalProcessor.process(LocalProcessor.java:79) | at org.jboss.metadata.annotation.creator.ejb.LocalProcessor.process(LocalProcessor.java:40) EJBTHREE-1127 has similar constructs which now pass, and don't go through this metadata project code at all. Is there some fundamental difference in the way the deployers differ in treating TCK vs. the EJB3 Testsuite? Scott and I had seen similar problems w/ EJBTHREE-1146 vs. JBCTS-719 ( http://www.jboss.com/index.html?module=bb&op=viewtopic&t=125113 ). S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110423#4110423 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110423

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Empty @Remote on bean class

by scott.stark＠jboss.org

I have been waiting to do a release on this issue. I have at least one change so I'll do the release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110410#4110410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110410

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Empty @Remote on bean class

by ALRubinger

Agreed on all points. We have code within EJB3 ProxyFactoryHelper that checks to ensure @Remote, @RemoteHome, etc data is all defined properly and is complete for either 3.0 or 2.1 views (or both); the RemoteProcessor has logic that violates the spec as it stands. I can remove these lines, but we'll have to do another release (if we haven't already) of the metadata project. You were tagging releases off trunk? Let me know if you'd like for me to handle this. Also bothers me that we're not seeing this in the EJB3 Test; it's a dead simple case. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110393#4110393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110393

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Empty @Remote on bean class

by scott.stark＠jboss.org

If we can't unconditionally make that assertion, it should not be in the RemoteProcessor code. I want to understand why this is not being hit in the current ejb3 test though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110391#4110391 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110391

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Embbedded - broken - some fixes - still not working

by epbernard

no Hibernate don't speak jarjar :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110389#4110389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110389

18 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2007