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

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by kabir.khan＠jboss.com

The AspectManager bean needs to depend on the mbeanserver in order to register itself into JMX, and appying @JMX to that will not work since the @JMX aspect in turn will depend on the AspectManager service? This was originally done to be able to run the AOP testsuite since that needs to turn on weaving with JMX. I see what you mean wrt the JBossServer being injected at the end. I'll try creating a new wrapper bean for the JMX registration of the AspectManager so that the original AspectManager can start up in the same way as in the standalone tests then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009965#4009965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009965

18 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by thomas.diesler＠jboss.com

Hey, Jason this is excellent work - well done. anonymous wrote : | The custom provider can be specified using the "org.jboss.ws.tools.jaxws.webServiceImporterProvider" system property, or the static field on WebServiceImporter.class. | Please have a look at javax.xml.soap.FactoryLoader | /** | * Load a factory using this ordered lookup procedure | * | * 1. Use the system property | * 2. Use the properties file "lib/jaxm.properties" in the JRE directory | * 3. Use the Services API (as detailed in the JAR specification), if available, to determine the classname | * 4. Use the default factory implementation class | * | * @return the factory impl, or null | */ | public static Object loadFactory(String propertyName, String defaultFactory) | This is the lookup we use thrughout the jaxws impl. And most importantly, now that we have wsgen + wsimport functionality we should make it available in jbossws-1.2.0. This would give us the much needed community QA before 2.0.0 Could you please merge your work to branches/jbossws-1.2.0 For sake of clarity I suggest we do not refer to wsgen + wsimport when we talk about our tool set. How about: wswsdl, wsjava? cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009942#4009942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009942

18 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: javax classes in jbossws-client.jar

by thomas.diesler＠jboss.com

Yes, this should change in 1.2.0 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009935#4009935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009935

18 years, 11 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: Reducing Java object lock contention in org.jboss.invoca

by scott.stark＠jboss.org

We decided to move to a 4.2.x basis for the javaee 1.4 platform to make java5 the base jdk and update some jboss/thirdparty dependencies that could not go into another minor release of 4.0.x. At this point 4.0.x is in maintence mode with no planned next release and 4.2.0 will essentially be the next javaee 1.4 platform release. This will still have the pooled invoker available as far as I understand. The question back is do you really want to use that invoker or would you want to switch to the remoting/unified invoker? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009870#4009870 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009870

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by scott.stark＠jboss.org

I reversed that change as it actually made the problems worse; none of the aspects were being applied. Why does the AspectManager need to depend on the mbeanServer/JMXKernel? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009868#4009868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009868

18 years, 11 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: Reducing Java object lock contention in org.jboss.invoca

by ScottMarlow

I would like to get the change into 4.0.5sp1 if there is time (or a 4.0.x something release). What do you recommend? I didn't know about the switch to using remoting in 4.2, so it doesn't make sense to make my proposed change there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009828#4009828 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009828

18 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by jason.greene＠jboss.com

"omatzura" wrote : | to make my life easier, integrated tools in soapui are launced by spawning a seperate process and running the command-line versions.. maybe not the best from a resource-perspective, but it keeps the code clean from "linking"/class-loaders/etc.. I'll try to go with this strategy for these 2 as well (unless there is some reason to do otherwise..) | OK, however you like to do it. One thing I was thinking of doing to help integrators concerned with dependencies is to provide a tiny jar (with no dependencies) that contains just the JAX-WS tools API and SPI. An integrator could then include this tiny jar in their classpath. The code would something like: | WebServiceGenerator generator = WebServiceGenerator.newInstance(new URLClassLoader(impljars)); | generator.setGenerateSource(true); | generator.setGenerateWsdl(true); | generator.setOutputDirectory(new File("output")); | generator.setMessageStream(stream); | generator.generate(TestMe.class); | anonymous wrote : | Do I "just" need the latest jbossws 2.0 sources to build/run these? | The least amount of steps would be to checkout and build jbossas/trunk. The wsgen.sh and wsimport.sh scripts are in the bin directory, you can extract the needed jars from those scripte. anonymous wrote : | Also, have there been any changes to the wstools command-line options/config since 1.0.3 that I should support in our dialogs? (just point me to the docs and I can look at the details myself..) | Just a small change: http://fisheye.jboss.com/browse/JBossWS/trunk/jbossws-core/src/main/resou... -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009805#4009805 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009805

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by scott.stark＠jboss.org

I moved the install of the JBossServer bean to before the loading of the bootstrap xml. Update your system module to pickup the org.jboss.system.server.profileservice.ProfileServiceBootstrap change and try that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009788#4009788 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009788

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by scott.stark＠jboss.org

If the AspectManager does need an MBeanServer, this could be created as a bean and injected into the JMXKernel rather than having the AspectManager depend on the JMXKernel for it. A bean factory would be needed to created it similar to how the JMXKernel does things. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009781#4009781 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009781

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by scott.stark＠jboss.org

There certainly are different dependencies. The jboss5 the AspectManager depends on the JMXKernel for the mbeanServer which in turn depends on the JBossServer, which is not in the bootstrap descriptor. Rather, its magically injected after the bootstrap, but before the validation by the jboss5 ServerImpl class, org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap method: | ... | deploy(bootstrapURL); | | Kernel kernel = getKernel(); | controller = kernel.getController(); | | // Register the Server instance in the kernel | if (server != null) | { | AbstractBeanMetaData metaData = new AbstractBeanMetaData("JBossServer", server.getClass().getName()); | controller.install(metaData, server); | } | | // Validate that everything is ok | checkIncomplete(); | So I guess this is causing issues. The JBossServer bean is the bean implementing the org.jboss.system.server.Server that is loaded to define the jboss server behavior. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009775#4009775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009775

18 years, 11 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 February 2007