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

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ManagedObject stuff for AOP

by kabir.khan＠jboss.com

Scott/Adrain, I have almost completed the underlying beans to do this, but need some answers for my previous post to be able to progress. 1) Am I ok to replace the old underlying beans with my existing ones? 2) Can I rip out the old <aop:aspect> xml stuff, and replace it with something that looks more like -aop.xml? Or do I create a new schema and keep the old <aop:aspect> stuff? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104158#4104158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104158

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by adrian＠jboss.org

"wolfc" wrote : | Stop mucking up the generics. They are there for a reason (to find old smug). :-) You mean cause ClassCastExceptions that I don't understand. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104157#4104157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104157

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JndiInject and confused use of generics for polymorphism

by wolfc

Already did that. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104153#4104153 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104153

18 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [Productivity] Level 1 - Start from scratch

by alessio.soldano＠jboss.com

Hi Max, thanks for the time spent in reading these threads. "max.andersen(a)jboss.com" wrote : 0) I am not a big WS guy - I've found WS to be to clunky to be bothered with; mainly because even with tooling WS is an XML hell and waaay to compliated (I know the annotated way make this more managable but annotation solutions didn't exist when I had to bother with web services ;) - Just know that when I in the future ask some stupid WS beginner question or assume too much or too litle about WS. It's almost the opposite for me, never worked at plugin development before. anonymous wrote : | 1) The only WS tooling we have right now in RHDS is what comes with Eclipse WTP (and that is mainly axis biased) | | 2) We *want* to get SoapUI back into the JBossTools build again - once when we get over the release hurdle of JBossTools/RHDS GA this will be a priority OK, these are 2 important things, thanks for stating them clearly. In particular I also think it will be really good to have the SoapUI plugin back in the build again; I expect this integration to give JBossTools the same functions RHDS has from the WTP Eclipse, but based on JBossWS instead of Axis. anonymous wrote : | 3) Be aware that just because something is in JBoss Tools does not mean it will show up in RHDS Does this simply means that things from JBossTools are not automatically coded into RHDS too, but they require additional work and this depends on strategic decisions about RHDS features, or I am missing something else? anonymous wrote : | 4) Looking into how you can integrate your docs/samples with Eclipse Cheatsheets would be very interesting Thanks for the suggestion, I'll think about this too. anonymous wrote : | 5) Providing Ant or Maven kind of samples is good - neither of these exclude good JBoss Tools support as long as they are done correctly | | 6) We/you shouldn't just go out and create an isolated WS-way of creating sample/projects - look into how the eclipse best support it...just using Eclipse as an glorified text editor to calling ant isn't really adding value ;) I agree with you, Ant based samples and JBoss Tools / Eclipse support do not exclude each other and I believe providing both is the right things to do. In particular on point 6, I think I get the overall idea that is, of course, let's leverage what Eclipse is beyond a powerful text editor to provide ws added value. May be we might go a bit further into details on this in future.. anonymous wrote : 7) We need someone who knows about WS to build proper WS support into tooling....preferably someone who likes to do both WS and write plugins ;) I understand what you mean. After and apart having SoapUi back, further WS tooling efforts will of course require our contribution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104150#4104150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104150

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by wolfc

LOL, I got the appclient passing as well, but in a different way. I put the entire metaData in JNDI in the Ejb3ClientDeployer and retrieve it in the ClientLauncher. PersistenceContextHandler is removed from ClientContainer, because a client can't use one. Stop mucking up the generics. They are there for a reason (to find old smug). :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104148#4104148 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104148

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JndiInject and confused use of generics for polymorphism

by scott.stark＠jboss.org

"wolfc" wrote : Stop, stop. PersistenceContext shouldn't be available for a client. Got it. I'm dropping this from the ClientContainer handlers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104146#4104146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104146

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JndiInject and confused use of generics for polymorphism

by scott.stark＠jboss.org

Looking at the application-client.xml xsd, persistence-context-ref is not supported. The PersistenceContextHandler should not be part of the ClientContainer handlers then. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104145#4104145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104145

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - EJB3 AppClient - tests now pass but there are issues

by adrian＠jboss.org

I've added the parsing to the ClientLauncher which revealed a number of other issues, "fixing" these now makes the ejb3 appclient tests pass. * HARDWIRING I had to hack the resolver to hardwire the schemalocation -> annotated class There must be a better way to do this? Perhaps we can include a META-INF/schema-binding.xml in the jar and jbossxb can look for this config at bootstrap/hotdeployment? ClientLauncher.java - YUCK! :-) | /** The schema resolver */ | private static DefaultSchemaResolver resolver = (DefaultSchemaResolver) SingletonSchemaResolverFactory.getInstance().getSchemaBindingResolver(); | | static | { | // FIXME hardwiring | resolver.addClassBindingForLocation("application-client", ApplicationClient14DTDMetaData.class); | resolver.addClassBindingForLocation("application-client_1_2.dtd", ApplicationClient14DTDMetaData.class); | resolver.addClassBindingForLocation("application-client_1_3.dtd", ApplicationClient14DTDMetaData.class); | resolver.addClassBindingForLocation("application-client_1_4.xsd", ApplicationClient14MetaData.class); | resolver.addClassBindingForLocation("application-client_5.xsd", ApplicationClient5MetaData.class); | resolver.addClassBindingForLocation("jboss-client", JBossClient5DTDMetaData.class); | resolver.addClassBindingForLocation("jboss-client_3_0.dtd", JBossClient5DTDMetaData.class); | resolver.addClassBindingForLocation("jboss-client_3_2.dtd", JBossClient5DTDMetaData.class); | resolver.addClassBindingForLocation("jboss-client_4_0.dtd", JBossClient5DTDMetaData.class); | resolver.addClassBindingForLocation("jboss-client_4_2.dtd", JBossClient5DTDMetaData.class); | resolver.addClassBindingForLocation("jboss-client_5_0.dtd", JBossClient5DTDMetaData.class); | resolver.addClassBindingForLocation("jboss-client_5_0.xsd", JBossClient5MetaData.class); | } | * PROFILE SERVICE Really we shouldn't be parsing the jar anyway. The profile service may override the configuration so we should have an option to retrieve the merged (and overridden) JBossClientMetaData from the server and bootstrap from there (including downloading the classes/jar?). Something like: | ./jboss-client.ch server=hostname:1099 client=my.ear/some.car | * MAIN I added the code to main() for the parsing, but the ejb3 testsuite doesn't test this? * PersistenceContextHandler I found the same problem that Scott had with Environment vs RemoteEnvironment "Fixed" it with a similar hack to the jndi binding described on the other thread. I guess there is some missing implementation here? | +++ src/main/org/jboss/injection/PersistenceContextHandler.java (working copy) | @@ -23,6 +23,7 @@ | | import org.jboss.metadata.javaee.spec.Environment; | import org.jboss.metadata.javaee.spec.PersistenceContextReferenceMetaData; | +import org.jboss.metadata.javaee.spec.RemoteEnvironment; | import org.jboss.logging.Logger; | import org.jboss.annotation.IgnoreDependency; | | @@ -42,7 +43,7 @@ | * @version $Revision$ | * @Inject and create Injectors | */ | -public class PersistenceContextHandler<X extends Environment> implements InjectionHandler<X> | +public class PersistenceContextHandler<X extends RemoteEnvironment> implements InjectionHandler<X> | { | @SuppressWarnings("unused") | private static final Logger log = Logger | @@ -51,8 +52,10 @@ | public void loadXml(X xml, InjectionContainer container) | { | if (xml == null) return; | - if (xml.getPersistenceContextRefs() == null) return; | - for (PersistenceContextReferenceMetaData ref : xml.getPersistenceContextRefs()) | + if (xml instanceof Environment == false) return; | + Environment env = (Environment) xml; | + if (env.getPersistenceContextRefs() == null) return; | + for (PersistenceContextReferenceMetaData ref : env.getPersistenceContextRefs()) | { | String encName = "env/" + ref.getPersistenceContextRefName(); | // we add injection target no matter what. enc injection might be overridden but | * TEST CLASSPATH Why is it necessary to add jars other than jbossall-client.jar to the classpath to run the client? See my comment in ejb3/build-test.xml I added jboss-metdata.jar which should be included (at least in part) in jbossall-client.jar? | <path id="client.classpath"> | <pathelement path="${jboss.dist}/client/jbossall-client.jar"/> | |  | <path refid="apache.codec.classpath"/> | <path refid="apache.log4j.classpath"/> | <path refid="apache.logging.classpath"/> | <path refid="jboss.test.classpath"/> | <path refid="sun.servlet.classpath"/> | <pathelement path="${jboss.dist}/client/jboss-ejb3-client.jar"/> | <pathelement path="${jboss.dist}/lib/jboss-vfs.jar"/> | <path refid="jboss.microcontainer.classpath"/> | <path refid="jboss.metadata.classpath"/> | </path> | I'll leave Carlo to decide which of these issues needs further attention in the EJB3 project. We should probably raise a main appserver JIRA for the jbossall-client.jar issue? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104144#4104144 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104144

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JndiInject and confused use of generics for polymorphism

by wolfc

EJBHandler extends EJBInjectionHandler so there is no problem there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104142#4104142 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104142

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JndiInject and confused use of generics for polymorphism

by wolfc

Stop, stop. PersistenceContext shouldn't be available for a client. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104139#4104139 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104139

18 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 2007