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

[Design of POJO Server] - Re: Unauthenticated Identity for ejb timers

by scott.stark＠jboss.org

The old metadata was doing a jmx call to the security manager to pickup a DefaultUnauthenticatedPrincipal setting. This needs to be moved into the parsing deployer layer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100842#4100842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100842

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Accessing content of vfsfile url fails

by scott.stark＠jboss.org

I could not find one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100838#4100838 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100838

17 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Microcontainer integration and the test framework

by timfox

"ataylor" wrote : There will be 2 ways to run a server. | | 1. similar to how it works now as if it was running within the jbossas using the service container | 2. Bootstrapped standalone directly with just the microcontainer. | | I prefer the second way altho' | Me too. anonymous wrote : this doesn't test integration. | I don't think that's problem, it's the purpose of the AS integration testsuite to test integration, not our test suite. anonymous wrote : | also, when Tim implements the new persistence mechanism do we really need to run all the tests against every database we support? No we won't have to This will make life a lot simpler. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100837#4100837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100837

17 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Unauthenticated Identity for ejb timers

by anil.saldhana＠jboss.com

Scott, there is a null for the unauthenticatedprincipal from the application meta data. http://jira.jboss.com/jira/browse/JBAS-4923 There is a pending issue for the unauthIdentity to be placed in the SecurityDeployer as per JIRA - http://jira.jboss.com/jira/browse/JBAS-4369 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100812#4100812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100812

17 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Unauthenticated Identity for ejb timers

by anil.saldhana＠jboss.com

Scott, there is a null for the unauthenticatedprincipal from the application meta data. http://jira.jboss.com/jira/browse/JBAS-4923 There is a pending issue for the unauthIdentity to be placed in the SecurityDeployer as per JIRA - View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100811#4100811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100811

17 years, 2 months

1
0
0 / 0

[Design of JBoss ESB] - NewProcessInstanceFacade bug?

by kadlecp

Hello, I think I have found a bug in NewProcessInstanceFacade.java. Field _keyPath is never set. I think there should one more line in the constructor of the class NewProcessInstanceFacade _keyPath= config.getAttribute(Constants.KEYPATH); Constant "Constants.KEYPATH" does not exist yet. But according to bpm_orchestration3 in jbossesb-4.2.1.IR2 the value of that constant should be "key"... Pavel Kadlec View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100808#4100808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100808

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Accessing content of vfsfile url fails

by alesj

Scott, any existing tests for http://jira.jboss.com/jira/browse/JBMICROCONT-205? Probably putting a few in each project - VFS and MC? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100797#4100797 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100797

17 years, 2 months

1
0
0 / 0

[Design of JBoss ESB] - Re: How does a service work when the payload classes as not

by kurt.stam＠jboss.com

Closed issue: [url] http://jira.jboss.com/jira/browse/JBESB-1282 [/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100791#4100791 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100791

17 years, 2 months

1
0
0 / 0

[Design of JBoss ESB] - How does a service work when the payload classes as not avai

by kurt.stam＠jboss.com

TomF: Just wondering e.g. the DLQ is running as a centralized service... it's forwarded a failed message that contains payload types that it knows nothing about... what should happen? I'm seeing an exception related to this on th aggregator quickstart. The DLQ service is running on the AS, while the individual serives are all running standalone. The DLQ Service has no visibility on the payload types bound to them failed messages that get delivered to it. Kurt: Let me clarify this. This is a generic issue with our transport where do NOT leave the payload opaque. Instead we serialize the *entire* message on the way out and deserialize it on reception in the Courier. So now this courier will need access to the specific java classes contained in the message (let's say the dvd store classes). This is a consequence of the transport/message Implementation design and has nothing to do with the DLQ Service. IMO we should leave the payload OPAQUE until we need to interact with the message. This will make sending messages around much easier. Kev: The generic problem with this issue is that each service is forced to deserialise the object when the message is deserialised. It is not just the DLQ which will be affected by this, all other services will be. It should be possible to modify the message implementation so that this deserialising is done on a Just In Time basis, this would solve the generic problem. This will not happen for the GA though, it will have to make it into the release (CP and trunk) at a later date. TomF: Kurt and I had a chat about this and came to the conclusion that there 2 issues... the generic issue as described by Kev above (i.e that the message payload is not opaque) and that there's potentially a general "patterns" type issue re whether or not messages being sent to the DLQ (or other orthogonal type services) should themselves be wrapped as payloads to a new message that is itself governed by its own set of contracts (i.e. between the ServiceInvoker and the DLQ). Mark: I've seen JIRA used several times for discussions like this. We should be using the forums for design discussions and/or the mailing list(s), but not JIRA. Let's change our habits please before Adrian (Brock) comes down hard on us ;-) Kurt: We don't want that to happen. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100790#4100790 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100790

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: Seeing IAssemblyDescriptorMetaData error again?

by alex.loubyansky＠jboss.com

It passes for me with the current mc trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100736#4100736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100736

17 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2007