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

[JBoss OSGi Development] - Re: Service integration with MC

by thomas.diesler＠jboss.com

"adrian" wrote : | The ServiceFactory is just a lazy version of the service. i.e. you only construct it | if somebody wants to use it. Its still a singleton. It only controls when the object | is constructed (first access instead of upfront). | Not quite. The main purpose of the ServiceFactory is that every client (bundle) of the service gets its own individual instance of the service. The service implementation may be stateful and maintain state on behalf of the client bundle. If the same bundle gets the service multiple times, it will receive the same service instance. An internal usage count is used to determine when the service can cleanup its state (i.e. when the usage count is 0) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266702#4266702 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266702

16 years, 4 months

1
0
0 / 0

[JBoss OSGi Development] - Re: JBoss OSGi logging policy

by thomas.diesler＠jboss.com

anonymous wrote : | As I've said, it should be Hudson or Maven that redirects logging to a file using the log4j.configuration system property. | yes, I've tried that by setting the surefire system properties. It worked for some test cases but not all. I didn't look into the log4j initialization to find out why it did not work for all cases. In another attempt to make you happy, I now added log4j-console.xml to the test resources. Please put the log4j.configuration property in your test setup like shown below. This should produce eclipse console logging. http://drop.io/sfodign View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266700#4266700 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266700

16 years, 4 months

1
0
0 / 0

[JBoss Web Services Development] - The ignoreParseErro issue

by jim.ma

I am looking at the ignoreParseError issue : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231557#4231557. Looks like simply set the ignoreParseError to false can not resolve it. There are two cases make the MassageFactoryImpl/EnvelopeBuilder to throw parse soap message exception if we set the igonreParseError to false . (a). HTTP response code OK and soap message is missing close tag etc . (b). HTTP reponse code OK and soap message is empty. Throwing parse exception for case (a) is no problem . But throwing exception for case (b) should be considered : if a ws-addressing webservice's ReplyTo is another address. The response soap message from this addressing service will also empty . So how can we modify the current code slightly and let MessageFactoryImpl know its replyTo address is another url and automatically ignore the parse error (empty response message) ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266686#4266686 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266686

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Supporting qualifiers in MC

by alesj

"kabir.khan(a)jboss.com" wrote : | do you have any examples of what OSGi needs? | OSGi has a notion of LDAP filtering; class + ldap-string filter. e.g. org.acme.FooBar + (a=b) Which means we're looking for service registry with FooBar impl which also contains explicit property; key a, value b. * http://anonsvn.jboss.org/repos/jbossas/projects/jboss-osgi/trunk/reactor/... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266660#4266660 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266660

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool

by flavia.rainone＠jboss.com

"flavia.rainone(a)jboss.com" wrote : So I'll use the recursion structure itself to deduct when the module needs to be filtered out and I'll abort the CP creation for those modules. That worked. :) However, I still see failures. This time, it looks like there is an error with the unregistering of "non-depolyment" modules. This error is not visible because ClassLoading.removeModule ignores Exceptions thrown by ModuleRegistries. But as a result of this Exception, the cleanup is not done properly and we end up with trash class pools in the default domain, which results in a failure on ReflectTestSuite. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266653#4266653 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266653

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development POJO Server] - Re: Getting rid of conf/jboss-service.xml

by smcgowan＠redhat.com

With these changes, the 'standard' and 'web' configs fail to boot. The conf/jboss-service.xml files for these configs contains more than what's defined in https://jira.jboss.org/jira/browse/JBAS-7469. 'default' and 'all' configs start fine. The standard config fails to boot with: | 2009-11-19 12:14:23,281 INFO [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (Thread-2) Loading profile: ProfileKey@1f1ad4a[domain=default, server=default, name=standard] | 2009-11-19 12:14:23,281 DEBUG [org.jboss.system.server.profileservice.repository.AbstractProfileService] (Thread-2) Activating profile: NoopProfile@c7bf90{key = ProfileKey@1f1ad4a[domain=default, server=default, name=standard]} | 2009-11-19 12:14:23,317 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (Thread-2) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | | DEPLOYMENTS MISSING DEPENDENCIES: | Deployment "NamingService" is missing the following dependencies: | Dependency "RemoteNamingBean" (should be in state "Configured", but is actually in state "**ERROR**") | Deployment "jboss.jmx:alias=jmx/rmi/RMIAdaptor" is missing the following dependencies: | Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | Deployment "jboss.jmx:name=Invoker,protocol=jrmp,service=proxyFactory,type=adaptor" is missing the following dependencies: | Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | Deployment "jboss.jmx:name=MBeanProxyRemote,protocol=jrmp,type=adaptor" is missing the following dependencies: | Dependency "jboss.jmx:name=Invoker,protocol=jrmp,service=proxyFactory,type=adaptor" (should be in state "Create", but is actually in state "Configured") | Deployment "jboss:service=CorbaNaming" is missing the following dependencies: | Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | Deployment "jboss:service=KeyGeneratorFactory,type=UUID" is missing the following dependencies: | Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | Deployment "jboss:service=Mail" is missing the following dependencies: | Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | Deployment "jboss:service=NamingProviderURLWriter" is missing the following dependencies: | Dependency "jboss:service=Naming" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | Dependency "jboss:service=Naming" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | Deployment "jboss:service=invoker,type=iiop" is missing the following dependencies: | Dependency "jboss:service=Naming" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss:service=Naming' **") | | DEPLOYMENTS IN ERROR: | Deployment "jboss:service=Naming" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss:service=Naming' ** | Deployment "JndiViewBean" is in error due to the following reason(s): javax.management.InstanceAlreadyExistsException: jboss:service=JNDIView already registered. | Deployment "RemoteNamingBean" is in error due to the following reason(s): javax.management.InstanceAlreadyExistsException: jboss:service=Naming already registered., **ERROR** | and the web config: | 13:59:01,245 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@1ff8de3[domain=default, server=default, name=web] | 13:59:01,245 DEBUG [AbstractProfileService] Activating profile: NoopProfile@17ccb2f{key = ProfileKey@1ff8de3[domain=default, server=default, name=web]} | 13:59:01,248 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | | DEPLOYMENTS MISSING DEPENDENCIES: | Deployment "WebServer" is missing the following dependencies: | Dependency "jboss.security:service=JaasSecurityManager" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss.security:service=JaasSecurityManager' **") | Deployment "jboss.jca:name=DefaultDS,service=DataSourceBinding" is missing the following dependencies: | Dependency "jboss.jca:name=DefaultDS,service=LocalTxCM" (should be in state "Create", but is actually in state "Configured") | Deployment "jboss.jca:name=DefaultDS,service=LocalTxCM" is missing the following dependencies: | Dependency "jboss.security:service=JaasSecurityManager" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.security:service=JaasSecurityManager' **") | Deployment "jboss.jdbc:datasource=DefaultDS,service=metadata" is missing the following dependencies: | Dependency "jboss.jdbc:service=metadata" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jdbc:service=metadata' **") | Deployment "jboss.web.deployment:war=/ROOT" is missing the following dependencies: | Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **") | Deployment "jboss.web.deployment:war=/invoker" is missing the following dependencies: | Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **") | Deployment "jboss.web.deployment:war=/jmx-console" is missing the following dependencies: | Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **") | | DEPLOYMENTS IN ERROR: | Deployment "jboss.security:service=JaasSecurityManager" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.security:service=JaasSecurityManager' ** | Deployment "jboss.jdbc:service=metadata" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jdbc:service=metadata' ** | Deployment "jboss.web:service=WebServer" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.web:service=WebServer' ** | | Another issue seen is that minimal fails to shutdown as part of the jboss-minimal-tests target but that may require changes. Is there still work being done for these configs? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266648#4266648 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266648

16 years, 4 months

1
0
0 / 0

[JBoss OSGi Development] - Re: Service integration with MC

by kabir.khan＠jboss.com

"adrian(a)jboss.org" wrote : | As part of the OSGi stuff, I've made the DeploymentUnit part of the MDR's | deployment level metadata. You should extend this concept so that the | dependency project can look for a "ServiceTracker" in the MDR rather than | a DeploymentUnit. The deployers project would then add the ServiceTracker | attachment by the default to the deployment level metadata. | Where is this code? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266618#4266618 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266618

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool

by flavia.rainone＠jboss.com

This is the lifecycle of module resgistry and class pools creation today: 1. Use RegisterModuleCallback as a ModuleRegistry so it can be notified of modules being deployed and undeployed 2. RegisterModuleCallback.addModule adds the module to an unrgisteredModules collection. 3. When ClassPoolRepository.registerClassLoader(CL) is invoked, this will trigger a call to JBossClDelegatingCPFactory. 4. The factory will invoke RegisterModuleCallback.registerModule. At this point, the module is going to be reomved from the unregisteredModules collection and added to the registeredModulesCollection. 5. The factory will iterate through all unregisteredModules of RegisterModuleCallback (the so-called "bootstrap" modules) in order to create the "bootstrap" CPs. Ales suggested me that I got rid of this way of creating ClassPools, making sure that the ClassPool is created by RegisterModuleCallback.addModule. This way, we get rid of the unregisteredCP collection and we get rid of the "bootstrap" CP creation that causes the aforementioned bug. Unfortunately, that doesn't work :(. I need the ClassLoader in order to create the ClassPool, and at the point RegisterModuleCallback.addModule is invoked the class loader associated with the module is null. I'm assuming that there is no easy way of filtering out the modules I need to filter. So I'll use the recursion structure itself to deduct when the module needs to be filtered out and I'll abort the CP creation for those modules. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266616#4266616 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266616

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Bug in Microtainer - recursive resoltion

by adrian＠jboss.org

JIRA: https://jira.jboss.org/jira/browse/JBKERNEL-62 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266613#4266613 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266613

16 years, 4 months

1
0
0 / 0

[JBoss Microcontainer Development] - Re: New features in classloading

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : | | In all three routines. | | | I only found two - found and not-found. | Where's the third? No that's right. The ClassLoaderHandler only notifies the domain to which the classloader was added/removed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266598#4266598 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4266598

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