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

[Design of EJB 3.0] - Re: EJB3 Alignment with JBoss Security

by anil.saldhana＠jboss.com

"wolfc" wrote : I concur, but only partially. | | If we create a EJB3 security spi which is provided by the EJB3 core and implemented by both EJB3 AS 4.2 security int and EJB3 AS 5.0 security int, then we don't have a lot of divergant code. | Configuration of the security int is then done in the EJB3 deployer meta data. Rather than every individual project define a security spi in the AS workspace, why shouldn't the security integration module in the AS workspace have a spi that both the 4 and 5 code base in the AS can leverage? This is the direction. EJB3 will depend on the interfaces defined in the security module of the AS workspace. I brought this issue with Scott and he concurred. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053039#4053039 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053039

18 years, 10 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SASL Authentication

by anil.saldhana＠jboss.com

I brought this issue up with Scott during our last discussion and he concurred with my assessment of SASL doing JAAS and not the other way. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053034#4053034 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053034

18 years, 10 months

1
0
0 / 0

[Design of JMX on JBoss (JBoss/JMX)] - Re: Abnormal shutdown of JBoss

by alesj

I'll just move this to more appropriate forum: - JBoss User / Management, JMX/JBoss View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053033#4053033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053033

18 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Broken test ConnectionClosedTest.testCloseWhileReceiving

by sergeypk

The test fails saying "Timed out". I see this exception in the logs: 11:24:32,828 TRACE @main [ClosedInterceptor] Failed to close | javax.jms.IllegalStateException: Consumer is currently in receive(..). Cannot set MessageListener | at org.jboss.jms.client.remoting.MessageCallbackHandler.setMessageListener(MessageCallbackHandler.java:273) | at org.jboss.jms.client.remoting.MessageCallbackHandler.close(MessageCallbackHandler.java:334) | at org.jboss.jms.client.container.ConsumerAspect.handleClosing(ConsumerAspect.java:134) | at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect36.invoke(ConsumerAspect36.java) | at org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_N1847373599029068216.invokeNext(ClientConsumerDelegate$closing_N1847373599029068216.java) | at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_N1847373599029068216.invokeNext(ClientConsumerDelegate$closing_N1847373599029068216.java) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_N1847373599029068216.invokeNext(ClientConsumerDelegate$closing_N1847373599029068216.java) | at org.jboss.jms.client.delegate.ClientConsumerDelegate.closing(ClientConsumerDelegate.java) | at org.jboss.jms.client.container.ClosedInterceptor.maintainRelatives(ClosedInterceptor.java:308) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:165) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientSessionDelegate$closing_N1847373599029068216.invokeNext(ClientSessionDelegate$closing_N1847373599029068216.java) | at org.jboss.jms.client.delegate.ClientSessionDelegate.closing(ClientSessionDelegate.java) | at org.jboss.jms.client.container.ClosedInterceptor.maintainRelatives(ClosedInterceptor.java:308) | at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:165) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java) | at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:131) | at org.jboss.test.messaging.jms.ConnectionClosedTest.testCloseWhileReceiving(ConnectionClosedTest.java:244) | 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 junit.framework.TestCase.runTest(TestCase.java:164) | at junit.framework.TestCase.runBare(TestCase.java:130) | at junit.framework.TestResult$1.protect(TestResult.java:106) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.framework.TestResult.run(TestResult.java:109) | at junit.framework.TestCase.run(TestCase.java:120) | at junit.framework.TestSuite.runTest(TestSuite.java:230) | at junit.framework.TestSuite.run(TestSuite.java:225) | at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) | at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912) | at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766) | There's a comment above the throw statement saying "Should never happen", but apparently it does. This seems to be related to revision 2761, see http://fisheye.jboss.com/changelog/Messaging?cs=2761. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053032#4053032 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053032

18 years, 10 months

1
0
0 / 0

[Design of JBossXB] - Re: Ignoring non-ignorable white space?

by alex.loubyansky＠jboss.com

Before filtering characters, the element's type should be checked whether it can contain text content. A lot of the current tests fail if I do this. Mainly, the ones that use anyType with indented elements in its content. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053030#4053030 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053030

18 years, 10 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: MainDeployer.listDeployed() returns empty collection

by mf＠fuhrer.com

Has there been any progress in this issue? I see that in Beta2 the JMX console still doesn't show any deployed modules, i.e. that MainDeployer.listDeployed() or MainDeployer.listDeployedModules() still return empty collections. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053026#4053026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053026

18 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Example of using web services both north bound and south

by tfennelly

In the current architecture, yes. The SOAP message is received via what's called a "Gateway Listener". It's job is to receive the message, "normalize" it into an ESB Message structure and forward it to a Message Aware ActionProcessing pipeline which performs the actual message payload processing before routing the message, in it's new format, to the target Service (i.e. SOAP to RMI call in this case). At the moment, the only options for performing the Gateway->ActionProcessingPipeline routing is over the likes of JMS (see message couriers), but I think there may be an local-vm type option planned. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053024#4053024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053024

18 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Example of using web services both north bound and south

by per_nyfelt

Great, thank you! is it necessary to set-up a JMS queue for a web service to web service pipe as in the bpel example? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053022#4053022 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053022

18 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Failover on Shutdown

by maliksaheb

The clustering mechanim is Jboss Messaging handle failover by allowing the switch to another JMS server of a cluster only if the initial JMS server on which the connection is created crashes. However, if the initial JMS server is stopped with shutdown the failover to a second server does not occur. Consequently any client having a connection of that stopped will not see its connection moving to another of the same JMS cluster. I suggest to consider the shutdown as a a case to trigger the failover and not only the crash. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053017#4053017 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053017

18 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Example of using web services both north bound and south

by tfennelly

If you check out JBossESB 4.2MR, there's a quickstart in there called webservice_bpel that illustrates what you're looking for. We're working on improving these capabilities in the 4.2GA codebase, but we're not there on that yet (so don't try that quickstart from SVN trunk). Also check out the flash demos here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053010#4053010 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053010

18 years, 10 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 June 2007