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

[Design of EJB 3.0] - Re: Issues with passivation of nested SFSBs

by bstansberry＠jboss.com

Any more thoughts on this? I'd like to try to crank a lot of this out over the weekend (flu this week has lowered productivity a lot). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010214#4010214 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010214

19 years, 2 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

Certainly aspects associated with beans should not need to also have packages associated with the aspect manager in its configuration. The mc/aop integration should take care of that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010212#4010212 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010212

19 years, 2 months

1
0
0 / 0

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

by kabir.khan＠jboss.com

Having to list the package names in the "include" attribute is a pain... The main intention for that is to not have to inspect every single loaded class when loadtime weaving is used. I've not thought this through 100%, but there will be a lot less beans than loaded classes, so I am thinking of making this a bit more automatic by modifying the AOPDependencyBuilder to not use the include/exclude test. If the class is "excluded" but has aspects, then add this class to the list of "included" classes, so that when we come to the instantiate phase we get the aspects generated as expected. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010211#4010211 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010211

19 years, 2 months

1
0
0 / 0

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

by weston.price＠jboss.com

I'm getting a stack trace in JBoss 3.2.3. Is this the right forum? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010210#4010210 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010210

19 years, 2 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

"thomas.diesler(a)jboss.com" wrote : Hey, Jason this is excellent work - well done. | Thanks! anonymous wrote : | Please have a look at javax.xml.soap.FactoryLoader | This is the lookup we use throughout the jaxws impl. | This shouldn't be used like this for several reasons 1. We are not allowed to alter javax.* beyond the specification, so we can't make FactoryLoader public. 2. This loader is SAAJ specific and refers to "jaxm.properties", therefore having APIs outside of SAAJ use it will make them non comformant. (e.g javax.xml.ws.spi.Provider) 3. It introduces a dependency on our implementation of the API, which is wrong. Our code has to work with any compliant API jar. 4. In the case of javax.xml.ws.spi.Provider, it introduces a dependency between differing API jars. So jboss-jaxws.jar can only be used with jboss-saaj.jar. Regardless, in order to allow for the tools API to be standalone (easy for integrators), it needs it's own discovery mechanism. The reason I didn't implement the same number of options is because this API is not a Java spec, so I don't expect that many people will actually want to provide an alternative implementation. anonymous wrote : | Now that we have wsgen + wsimport functionality I believe 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 jbossws-1.2.0 | Sure. anonymous wrote : | For sake of clarity I suggest we do not refer to wsgen + wsimport when we talk about our tool set. How about: wswsdl, wsjava? | Personally I think that generate and import are more intuitive names, and they also reflect the API and ant task. Also unlike JAX-RPC tools, wsgen is not the direct opposite of wsimport. It's primary purpose is to generate wrapper classes, so wsdl generation is off by default. So I don't think this particular tool will get a lot of usage on our stack since we generate this dynamically anyway. The other reason I stuck with the common names is to make it easier for someone to move from say the implementation in JDK6 (which uses wsgen and wsimport). Although, the command line arguments are slightly different, which I was hesitant on. The main reason is that I wanted to use gnu getop which simplifies command line argument parsing, follows unix conventions, and is used in other jboss tools. This could be easily changed to directly mirror the arguments in the RI, if you guys think we should. We could also make them jboss-wsgen.sh and jboss-wsimport.sh but that would be extra typing. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010207#4010207 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010207

19 years, 2 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

It did not look like it worked at first, but then I saw you had updated some of the include attribute package names, and after updating that, org.jboss.deployers.spi.deployer.Deployer interception using an aop:lifecycle element works. I'll test out the others latter. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010200#4010200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010200

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Aspect integration to bootstrap classes

by kabir.khan＠jboss.com

The aop-mc-int project no longer creates lib/jboss-aop-mc-int-boot.jar lib/jboss-aop-mc-int-deployer.jar and I have removed these files from the 3rdparty repository View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010196#4010196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010196

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBossMQ XAResourceRecovery

by timfox

This class was ported, I believe from JBoss MQ into JBM: | /** | * JMS Provider Adapter based recovery. | * | * This should be done when recovery is being driven from a transaction manager deployed with JBoss AS | * since it relies on JMSProviderLoader instances being deployed that correspond to the JMS providers | * to recover for. | * | * @author <a href="adrian(a)jboss.com">Adrian Brock</a> | * @author <a href="juha(a)jboss.com">Juha Lindfors</a> | * | * @version $Revision: 1.1 $ | */ | public class JMSProviderXAResourceRecovery implements XAResourceRecovery | { | private boolean trace = log.isTraceEnabled(); | | private static final Logger log = Logger.getLogger(JMSProviderXAResourceRecovery.class); | | /** The jms provider name */ | private String providerName; | | /** The delegate XAResource */ | private XAResourceWrapper wrapper; | ... | ... | But I can't find the original version anywhere, in JBoss AS CVS HEAD. Does anyone know where I can find it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010140#4010140 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010140

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: FYI: Latest ClassInfo changes.

by alesj

"adrian(a)jboss.org" wrote : | BeanInfo property accessors | | I've fixed this new code to delegate to the PropertyInfo | such that the PropertyInfo impl can decide how to get/set the property. I've rewritten AttributeDispatchContext for AbstractKernelControllerContext to use this. What about with method / operation invocation (InvokeDispatchContext)? Will we be moving this to BeanInfo notion as well? Or is it already there? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010139#4010139 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010139

19 years, 2 months

1
0
0 / 0

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

by kabir.khan＠jboss.com

I have removed the dependency from the AspectManager on JMXKernel.mbeanServer, and now the beans seem to start in the right order. Can you try the lifecycle stuff again from your original problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010132#4010132 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010132

19 years, 2 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