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

[Design of EJB 3.0] - Re: Accessing stateful session beans from stateless session

by winterer

(At least) since JBoss 4.2.0.GA, it is possible to query and return the remote interface of an existing (stateful) session bean: @Stateful | @Remote( { MyRemoteInterface.class }) | public class MyStatefulSessionBean implements MyRemoteInterface, MyLocalInterface { | | //... any remote/local methods ... | | // method defined in MyLocalInterface: | public MyRemoteInterface getRemoteInterface() { | Object obj = ctx.getBusinessObject(MyRemoteInterface.class); | return (MyRemoteInterface)obj; | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059917#4059917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059917

18 years, 6 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: HOWTO: remove a deployment context that is in error?

by wolfc

Since I'm hacking anyway, I've removed Brian's dodgy hack and changed the code to: // TODO: JBAS-4292 | delegate.checkComplete(deployment); | contextMap.put(url, deploymentName); (using checkComplete(Deployment)) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059877#4059877 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059877

18 years, 6 months

1
0
0 / 0

[QA of JBoss Portal] - SSO Unit Testing

by julien＠jboss.com

We need to discuss the unit testing of the various SSO integration we are developping. This topic should be used. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059874#4059874 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059874

18 years, 6 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - HOWTO: remove a deployment context that is in error?

by wolfc

"Brian" wrote : I think something recently changed in the deployer code. I have a test that deployers a sar where some beans are deliberately meant to fail. At the end of the deployment, the following is logged: | | 2007-07-01 10:30:16,968 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/C:/dev/jboss/jboss-head/testsuite/output/lib/partitionstatetransfer.sar | 2007-07-01 10:30:16,968 WARN [org.jboss.deployment.MainDeployer] Failed to deploy: file:/C:/dev/jboss/jboss-head/testsuite/output/lib/partitionstatetransfer.sar | org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | | *** CONTEXTS IN ERROR: Name -> Error | | BadStatePartition -> org.jboss.test.cluster.partition.BadHAPartitionStateException: BadHAPartitionState cannot be deserialized | | BadProviderPartition -> java.lang.IllegalStateException: Initial serviceState transfer failed: Channel.getState() returned false | | | at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:552) | at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:379) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814) | at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:587) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 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:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | 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:668) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:270) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 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:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 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:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | 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:668) | at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:815) | at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:416) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) | at sun.rmi.transport.Transport$1.run(Transport.java:153) | at java.security.AccessController.doPrivileged(Native Method) | at sun.rmi.transport.Transport.serviceCall(Transport.java:149) | at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) | at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) | at java.lang.Thread.run(Thread.java:595) | | The test then does some stuff accessing other bean for a couple seconds, and then undeploys the sar. This doesn't go correctly. You get this logging: | | 2007-07-01 10:30:19,312 WARN [org.jboss.deployment.MainDeployer] undeploy 'file:/C:/dev/jboss/jboss-head/testsuite/output/lib/partitionstatetransfer.sar' : package not deployed | | Thereafter, any test that includes testServerFound() will fail with an org.jboss.deployers.client.spi.IncompleteDeploymentException that lists the above two failed deployments. Adding Brian's dodgy hack won't work: anonymous wrote : | 2007-07-03 09:38:48,868 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/carlo/work/jboss-head/ejb3/output/test-lib/jsr181-client.jar | 2007-07-03 09:38:48,868 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Not scheduling removal of context already in error: vfsfile:/home/carlo/work/jboss-head/ejb3/output/test-lib/jsr181-client.jar Thus remains the question: how to remove a deployment context that is in error state? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059873#4059873 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059873

18 years, 6 months

1
0
0 / 0

[Design of JBoss Portal] - Re: News reader portlet

by julien＠jboss.com

The actual source code can be found in SVN or jboss portal 2.6 download. Now it is in the package core-samples under org.jboss.portal.core.samples.news View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059857#4059857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059857

18 years, 6 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Ear deployment ordering broken in trunk

by adrian＠jboss.org

There shouldn't be any need to define the ordering. If the services (including ejb and web modules) have the correct dependencies it does not matter. However, deployment (rather than service) dependencies are on the road map http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036378#4036378 these will include "implicit" rules like: Russian doll ordering Explicit ordering All or nothing deployment (either all the subdeployments are deployed or none are) etc. In fact, we'll likely support "random order" so people can check that they have all dependencies defined (i.e. they are not being implicit) but this is more useful for testing our dependencies are properly specified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059842#4059842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059842

18 years, 6 months

1
0
0 / 0

[Design of JBoss Portal] - Re: News reader portlet

by manousopul

that's my thought. To make it a little more functional. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059833#4059833 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059833

18 years, 6 months

1
0
0 / 0

[Design of JBoss Portal] - Re: News reader portlet

by bdaw

Hi If you want to contribute thats great! You can work on this for sure and extend the rss portlet features. When you have something working you can create a JIRA issue and put your code as an attachment, and will pick it up. You could also put your portlet into portletswap repository. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059815#4059815 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059815

18 years, 6 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Ear deployment ordering broken in trunk

by dimitris＠jboss.org

I think explicit ordering should be the default for EARs in JB5, but we most probably need a flag to fall back to the legacy behavior. But it depends if the new deployment framework can support the legacy behavior? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059803#4059803 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059803

18 years, 6 months

1
0
0 / 0

[Design of JBoss Portal] - News reader portlet

by manousopul

I' like to add functionality to news reader portlet developed by Roy Russo. At the existing version of the portlet, the logged user reads rss items of one single rss feed. The idea is to handle with more rss feeds that will be saved at user preferences. Thank you, Chris View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059797#4059797 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059797

18 years, 6 months

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 July 2007