[JBoss Seam] - Re: using DAO design pattern with Seam apps
by asookazian
"christian.bauer(a)jboss.com" wrote : Don't quote Rod Johnson bullshit here. In the same book he goes on and basically tells you to not use an ORM software. Don't believe anything he says about data management because he obviously doesn't know what he is talking about.
|
First off I'm not a big advocate of Spring. I think pulling a lot of code into XML is a disaster in most cases. And I think Seam is a big improvement over Struts + EJB 2.x technology from a developer's perspective at least. But Spring integrates out of the box with Hibernate (versions 2 and 3), JDO (versions 1 and 2), TopLink. If Johnson was anti-ORM, why would this be the case then?
To be faire here, his basic premise is in some cases it's advantageous to use ORM and some cases not (use JDBC or iBATIS as myspace.com does for added flexibility). I'm not saying he's right or wrong, just wanted to let his stance be known all here...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077407#4077407
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077407
18Â years, 8Â months
[JBossWS] - Cannot find service endpoint target
by hansOtto
I have deployed several Webservices as EJB endpoints successfully on the JBoss 4.2.1 with JBossWS 1.2.1. There are many SLSBs inside the Webservices, injected by the @EJB annotation and build as local deployment.
Now, after upgrading from JBossWS 1.2.1 to JBossWS 2.0.0, I get the following error during the EAR deployment:
14:01:25,984 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/v1, warUrl=.../tmp/deploy/deploy.last-webservices.ear-webservices_ejb3.jar5109.war/
| 14:01:26,578 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/C:/jboss_4.2.1_WS/server/default/data/wsdl/deploy.last/webservices.ear/webservices_ejb3.jar/TestService5107.wsdl
| 14:01:26,875 INFO [org.jboss.wsf.spi.management.BasicEndpointRegistry] register: jboss.ws:context=v1,endpoint=TestService
| 14:03:09,734 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/C:/jboss_4.2.1_WS/server/default/tmp/deploy/tmp5106webservices.ear-contents/webservices_ejb3.jar
| javax.xml.ws.WebServiceException: Cannot find service endpoint target: jboss.j2ee:name=TestService,service=EJB3,jar=webservices_ejb3.jar,ear=webservices.ear
| at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.start(InvocationHandlerEJB3.java:78)
| at org.jboss.wsf.spi.deployment.BasicLifecycleHandler.start(BasicLifecycleHandler.java:57)
| at org.jboss.wsf.stack.jbws.LifecycleHandlerImpl.start(LifecycleHandlerImpl.java:40)
| at org.jboss.wsf.spi.deployment.EndpointLifecycleDeployer.start(EndpointLifecycleDeployer.java:49)
| at org.jboss.wsf.spi.deployment.BasicDeployerManager.deploy(BasicDeployerManager.java:81)
| at org.jboss.wsf.container.jboss42.MainDeployerHook.deploy(MainDeployerHook.java:46)
| at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy32.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
I tried to debug the deployment process and noticed that the error occurred in line 77 of the InvocationHandlerEJB3:
if (dispatcher.getRegistered(objectName.getCanonicalName()) ==null)
| throw new WebServiceException("Cannot find service endpoint target: " + objectName);
|
The problem is, that the dispatcher wants to invoke the webservice project before it is registered. At this point, the dispatcher has all deployed projects registered except the webservice project.
If I remove all SLSB with the @EJB injections from the Webservices, the deployment runs successfully.
Has anybody an idea?
Harry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077405#4077405
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077405
18Â years, 8Â months
[JBossCache] - JBossCache 2.0 with JBoss AS 4.2.1 problems
by mohali
Is it possible to use JBossCache with JBoss AS 4.2.1?
As per JBoss Cache 2.0.0 docs somethings may not work as quoted below:
anonymous wrote : It is possible to deploy a JBoss Cache 2.0 instance in JBoss AS 4.x (at least in 4.2.0.GA; other AS releases are completely untested). However, the significant API changes between the JBoss Cache 2.x and 1.x releases mean none of the standard AS 4.x clustering services (e.g. http session replication) that rely on JBoss Cache will work with JBoss Cache 2.x. Also, be aware that usage of JBoss Cache 2.x in AS 4.x is not something the JBoss Cache developers are making any significant effort to test, so be sure to test your application well (which of course you're doing anyway.)
I downloaded JBossCache 2.0.0 GA, copied all the jars from lib folder to JBOSS_CONFIG/lib folder (I am using all configuration) and then copied replSync-service.xml from etc/META-INF to JBOSS_CONFIG/deploy folder and I get the following error during server startup:
anonymous wrote :
| [java] --- MBeans waiting for other MBeans ---
| [java] ObjectName: jboss.cache:service=TreeCache
| [java] State: FAILED
| [java] Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@ef5641 on mbean jboss.cache:service=TreeC
| ache; - nested throwable: (java.lang.VerifyError: (class: org/jboss/cache/config
| /Configuration, method: setCacheLoaderConfig signature: (Lorg/jboss/cache/config
| /CacheLoaderConfig;)V) Incompatible argument to function)
| [java] I Depend On:
| [java] jboss:service=Naming
| [java] jboss:service=TransactionManager
|
| [java] --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| [java] ObjectName: jboss.cache:service=TreeCache
| [java] State: FAILED
| [java] Reason: org.jboss.deployment.DeploymentException: Exception settin
| g attribute javax.management.Attribute@ef5641 on mbean jboss.cache:service=TreeC
| ache; - nested throwable: (java.lang.VerifyError: (class: org/jboss/cache/config
| /Configuration, method: setCacheLoaderConfig signature: (Lorg/jboss/cache/config
| /CacheLoaderConfig;)V) Incompatible argument to function)
| [java] I Depend On:
| [java] jboss:service=Naming
| [java] jboss:service=TransactionManager
|
Did I miss any step or is this a compatibility issue?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077399#4077399
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077399
18Â years, 8Â months