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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Creation of topic @ runtime

by timfox

"desuraghu" wrote : But in 1.2 we have ServerPeerMBean and in 1.4 this one has been removed. | | So we don't have any option to get ServerPeer instance. That is not correct, ServerPeer is still there in 1.4, here it is in SVN: http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_4_4_GA/int... And here it is in 1.2: http://anonsvn.jboss.org/repos/messaging/tags/JBossMessaging_1_2_0_GA/src... As I mentioned in my previous post you can see in jmx-console since the object name might have changed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243578#4243578 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243578

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Creation of topic @ runtime

by desuraghu

But in 1.2 we have ServerPeerMBean and in 1.4 this one has been removed. So we don't have any option to get ServerPeer instance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243574#4243574 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243574

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Creation of topic @ runtime

by timfox

In both 1.2 and 1.4 the ServerPeer should be visible in the jmx-console in a similar way. Take a look in the jmx-console to get the object name. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243572#4243572 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243572

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Creation of topic @ runtime

by desuraghu

Is there any other alternative to get ServerPeer MBean instance. For ex : --------- MBeanServer mbeanServer = MBeanServerLocator.locateJBoss(); ObjectName objectName = new ObjectName( "jboss.mq:service=DestinationManager"); mBean = (DestinationManagerMBean) MBeanServerInvocationHandler .newProxyInstance(mbeanServer, objectName, DestinationManagerMBean.class, false); View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243563#4243563 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243563

16 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ClassPool for JBoss Reflection

by flavia.rainone＠jboss.com

"Kabir" wrote : Do you mean this: | | | protected boolean convertReferences(CtClass clazz, ClassAdvisor clazzAdvisor) throws Exception | | { | | boolean converted = false; | | String ref = null; | | try | | { | | AOPClassPool pool = AOPClassPool.createAOPClassPool(clazz.getClassPool(), AOPClassPoolRepository.getInstance()); | | | It is something I've always assumed was there for a reason and taken for granted since it has been there since before my time. However, all that seems to do is to delegate to the parent classpool so maybe it can be removed and clazz.getClassPool() can be used? I'll test that and see what happens. "Kabir" wrote : | It looks like StandaloneClassPool(Factory) is used when run standalone, i.e. in the testsuite. But that can maybe live in AOP? Yes, that's what I'm thinking. The whole point here is that if JBoss Reflection is used with a standalone application, the javassist ClassPool can be used. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243558#4243558 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243558

16 years, 8 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Implement WorkContextProvider Check

by gurkanerdogdu

anonymous wrote : Figure 11-1 shows that the getWorkContexts() method is called by the WorkManager after the Work instance has been submitted by doWork(), startWork() and scheuleWork(). | | Chapter 10.3.3.5 states that a WorkCompletedException can be thrown with an appropriate error code which in this case is one of the WorkContextErrorCodes. Then, place that I put "setupWorkcontext" is wrong. I have to setup work contexts just before "Work" is run by the "WorkManager". In current codebase, it seems that there are several different methods that are responsible for setting up "ExecutionContext", namely "WorkManagerImpl#importWork" and "WorkManagerImpl#startWork". *Import* work is called by the "doWork()..." methods but *Start* work is called from "WorkWrapper#execute" method. But according to the spec., context has to be setup after *Work* is accepted and just before it is run. Then it seems that current implementation is wrong because context is imported before submitting work instance via "importWork" method. AFAIK from the specification, execution context is setup in "start" phase of the work lifecycle (submit->accept->start). And again according to the specification, if execution context is not setup succesfully within "start" phase, it throws "WorkCompletedException". But in WrapperImpl#execute method, it first calls "WorkManagerImpl#startWork" to do some execution context specific actions. If it gets exception it throws WorkRejectedException, otherwise it calls "run" method of the work instance. But spec says to throws WorkCompletedException. Sorry for pollution, but I do not exactly understand which methods in the codebase correspond to work's lifecycle phases "submitted, accepted, rejected, started and completed". Therefore, I do not know where to put "setupWorkContext" implementation. Morever, I guess that current execution context setups has to be changed also using new work context provider semantic. Effected places are "WorkManagerImpl#importWork,startWork, cancelWork,endWork" methods. anonymous wrote : There is a bit more work in regards to custom contexts if you see the last paragraph in 11.4.2 - the container must always check the most specific context first - and then go up the in hierarchy to find a supported one. | Specification says that this must done by the resource adapter before it submits work instance to the server via BootstrapContext#isContextSuported. I think that this is not related with the application server. Currently, I checked specific context support via method "WorkManagerImpl#getSupportedWorkContextClass(Class". This method checks given context class with application server supported context classes using ".equals". If it does not support specific instance, it falls through "super class" of the adaptor context class. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243554#4243554 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243554

16 years, 8 months

1
0
0 / 0

[Design of Security on JBoss] - URGENT: SAML support example with an JBOSS application

by jbossShm

I want to integrate my application with SAML. Please share with me the steps required to do so. I have to stick to the SAML only, so please keep it specific to it and if possible provide me any sample application as an example. Please reply ASAP. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243538#4243538 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243538

16 years, 8 months

1
0
0 / 0

[Design of Security on JBoss] - SAML 2.0 Support in jboss

by jbossShm

I want to integrate my application with SAML. Please share with me the steps required to do so. I have to stick to the SAML only, so please keep it specific to it and if possible provide me any sample application as an example. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243537#4243537 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243537

16 years, 8 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Implement WorkContextProvider Check

by jesper.pedersen

Figure 11-1 shows that the getWorkContexts() method is called by the WorkManager after the Work instance has been submitted by doWork(), startWork() and scheuleWork(). Chapter 10.3.3.5 states that a WorkCompletedException can be thrown with an appropriate error code which in this case is one of the WorkContextErrorCodes. There is a bit more work in regards to custom contexts if you see the last paragraph in 11.4.2 - the container must always check the most specific context first - and then go up the in hierarchy to find a supported one. You can just attach a single patch with all the changes needed if you don't want to split the patch into separate pieces. And more tests are always good :) You can get additional checkstyle checks by uncommenting | <module name="UnusedImports"/> | in tools/checkstyle/checkstyle.xml. A couple of checkstyle bugs does that we can't enable this module by default at the moment. Thanks for your contributions ! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243531#4243531 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243531

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Creation of topic @ runtime

by gaohoward

Hi, you need use jmx interface. for example: | MBeanServerConnection mBeanServer = lookupMBeanServerProxy(ic); | | ObjectName serverObjectName = new ObjectName("jboss.messaging:service=ServerPeer"); | | String queueName = jndiName.substring(jndiName.lastIndexOf('/') + 1); | | mBeanServer.invoke(serverObjectName, "deployQueue", | new Object[] {queueName, jndiName}, | new String[] {"java.lang.String", "java.lang.String"}); | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243528#4243528 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243528

16 years, 8 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 2009