March 2010 - jboss-dev-forums - Jboss List Archives

[EJB 3.0 Development] New message: "javax.naming.NameNotFoundException: JNDI name not bound"

by Richard Opalka

JBoss development, A new message was posted in the thread "javax.naming.NameNotFoundException: JNDI name not bound": http://community.jboss.org/message/530953#530953 Author : Richard Opalka Profile : http://community.jboss.org/people/richard.opalka@jboss.com Message: -------------------------------------------------------------- Hi folks, could someone have a look to https://jira.jboss.org/jira/browse/JBQA-2913 and tell me what's going wrong there? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530953#530953

16 years

1
0
0 / 0

[jBPM Development] New message: "Re: JBPM4.3 supports which Tomcat Version"

by Ronald van Kuijk

JBoss development, A new message was posted in the thread "JBPM4.3 supports which Tomcat Version": http://community.jboss.org/message/530938#530938 Author : Ronald van Kuijk Profile : http://community.jboss.org/people/kukeltje Message: -------------------------------------------------------------- Wrong forum, use the parent forum of this one -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530938#530938

16 years

1
0
0 / 0

[jBPM Development] New message: "JBPM4.3 supports which Tomcat Version"

by vijaya jangili

JBoss development, A new message was posted in the thread "JBPM4.3 supports which Tomcat Version": http://community.jboss.org/message/530935#530935 Author : vijaya jangili Profile : http://community.jboss.org/people/vijayajangili Message: -------------------------------------------------------------- As we have developed our application using jbpm 4.3 and for testing we used jboss 4.2.2 but now we want to move the application from jboss to Tomcat in real time. So i am looking for tomcat setup. Will jbpm4.3 supports Tomcat , if yes which version will it support?? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530935#530935

16 years

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Lookup to java:comp/EJBContext during postconstruction"

by jaikiran pai

JBoss development, A new message was posted in the thread "Lookup to java:comp/EJBContext during postconstruction": http://community.jboss.org/message/530932#530932 Author : jaikiran pai Profile : http://community.jboss.org/people/jaikiran Message: -------------------------------------------------------------- > marius.bogoevici wrote: > > > public class MilkMan implements MessageListener > { > > @PostConstruct > public void doAfterConstruction() > { > try > { > Context context = ((Context) new InitialContext().lookup("java:comp/EJBContext")); > } > catch (NamingException e) > { > e.printStackTrace(); > } > } > > > } > > > > Now, I would really like to know whether this assessment is corect and if that is something that is essentially expected to happen given the circumstances. If this is expected behaviour, then I think that we could work around this by treating EJBContext distinctly when injecting resources, but if not, then what would you think that would be the appropriate solution for doing a correct lookup for the purposes of CDI/Weld integration? It shouldn't fail. If it's failing, then it's a bug (looks like similar to the one we just fixed for EAP-4.x version). And i don't think it's specific to the EJBContext. I guess it will fail for anything under java:comp for that bean. Can you give a quick try by looking up something else under java:comp from within the @Postconstruct of MDB? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530932#530932

16 years

1
0
0 / 0

[EJB 3.0 Development] New message: "Lookup to java:comp/EJBContext during postconstruction"

by Marius Bogoevici

JBoss development, A new message was posted in the thread "Lookup to java:comp/EJBContext during postconstruction": http://community.jboss.org/message/530930#530930 Author : Marius Bogoevici Profile : http://community.jboss.org/people/marius.bogoevici Message: -------------------------------------------------------------- I will just refer to the problem indicated in http://seamframework.org/Community/TheMessageDrivenBeanSagaContinues While a CDI problem per se, it seems like doing this: @MessageDriven(activationConfig={ @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"), @ActivationConfigProperty(propertyName="destination", propertyValue="queue/testQueue") }) public class MilkMan implements MessageListener { @PostConstruct public void doAfterConstruction() { try { Context context = ((Context) new InitialContext().lookup("java:comp/EJBContext")); } catch (NamingException e) { e.printStackTrace(); } } @Inject Control control; public void onMessage(Message message) { try { control.setMessageDelivered(((TextMessage) message).getText().equals(EJBTest.MESSAGE)); } catch (JMSException e) { throw new RuntimeException(e); } } } will cause the deployment to fail, since doing that lookup from within the postconstructor does not get all the expected interceptors applied. Of course, this is not how exactly we intent to use this from Weld, but doing injection of resources during postconstruction has a similar effect. Now, I would really like to know whether this assessment is corect and if that is something that is essentially expected to happen given the circumstances. If this is expected behaviour, then I think that we could work around this by treating EJBContext distinctly when injecting resources, but if not, then what would you think that would be the appropriate solution for doing a correct lookup for the purposes of CDI/Weld integration? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530930#530930

16 years

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Security problems with org.jboss.test:jboss-test 1.1.5.GA"

by Flavia Rainone

JBoss development, A new message was posted in the thread "Security problems with org.jboss.test:jboss-test 1.1.5.GA": http://community.jboss.org/message/530925#530925 Author : Flavia Rainone Profile : http://community.jboss.org/people/flavia.rainone@jboss.com Message: -------------------------------------------------------------- > alesj wrote: > > > The setting of the SecurityManager to null in tearDownSecurity() needs to be in a privileged block. > > Its failing because your AOPTestDelegate doesn't have the permission. > https://jira.jboss.org/jira/browse/JBTEST-15 Tx! I ran jboss aop tests against jboss-test trunk and got no failures :-) I'll commit this as soon as a new version of jboss-test.jar is available: https://jira.jboss.org/jira/browse/JBAOP-773 -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530925#530925

16 years

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"

by Andrew Rubinger

JBoss development, A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints": http://community.jboss.org/message/530868#530868 Author : Andrew Rubinger Profile : http://community.jboss.org/people/ALRubinger Message: -------------------------------------------------------------- Looks like it's time to reschedule this in, then. The bigger issues are how we integrate it in with other dependent modules like jboss-metadata-ejb, etc. I'll dig back in starting tomorrow AM and see what estimates I can provide. S, ALR -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530868#530868

16 years

1
0
0 / 0

[EJB 3.0 Development] New message: "Deferring instance creation/injection to CDI"

by Marius Bogoevici

JBoss development, A new message was posted in the thread "Deferring instance creation/injection to CDI": http://community.jboss.org/message/530857#530857 Author : Marius Bogoevici Profile : http://community.jboss.org/people/marius.bogoevici Message: -------------------------------------------------------------- There are a number of JIRA items which currently require CDI to be able to intervene in the process of EJB and EJB interceptor instance creation process (these may not be all the items, but : https://jira.jboss.org/jira/browse/WELDINT-27 (apply decorators on EJB instances) https://jira.jboss.org/jira/browse/WELDINT-9 (perform injection on EJBs directly and not through an interceptor) https://jira.jboss.org/jira/browse/JBAS-7046 (perform injection on EJB interceptors) https://jira.jboss.org/jira/browse/WELDINT-31 (use @Inject constructors for session EJBs) So the main question at this point is whether there is currently a way to hook Weld into the EJB instantiation process? And if not, then we should probably start discussing this. Thanks, Marius -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530857#530857

16 years

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: JBREFLECT-5 - Implementing generics in JavassistClassInfo"

by Kabir Khan

JBoss development, A new message was posted in the thread "JBREFLECT-5 - Implementing generics in JavassistClassInfo": http://community.jboss.org/message/530850#530850 Author : Kabir Khan Profile : http://community.jboss.org/people/kabir.khan@jboss.com Message: -------------------------------------------------------------- > mailto:kabir.khan@jboss.com wrote: > > > 3) When accessing generics from the return type of a method, e.g. > > Collection<String> getStringCollection(){} > > > > we get hold of this method using normal reflection (A) and construct the TypeInfo for that using the ParameterizedType (B1+2) for which I extended the Javassist TypeInfo factory: > > *private* *void* assertComponentType(String methodName, Class<?> expected) *throws* Exception > { > Method method = ClassInfoGenericClassTest.class.getMethod(methodName, (Class[]) *null*); //A > Type type = method.getGenericReturnType(); //B1 > assertComponentType(type, expected); > } > > *private* *void* assertComponentType(Type type, Class<?> expected) *throws* Exception > { > TypeInfoFactory factory = getTypeInfoFactory(); > TypeInfo typeInfo = factory.getTypeInfo(type); //B2 > ClassInfo classInfo = assertInstanceOf(typeInfo, ClassInfo.class); > assertTrue(classInfo.isCollection()); > > TypeInfo expectedInfo = factory.getTypeInfo(expected); > assertEquals(expectedInfo, classInfo.getComponentType()); > } > > > However, that is probably not what will happen in real life, we would have a ClassInfo, get hold of the MethodInfo in question, and then get the return type which should contain the actualTypeArguments. This needs implementing and is not being tested at the moment, and the same goes for parameters and field types. Looking properly, I think what is there at the moment is correct. In reflect we have these additional methods: Type[] Method.getGenericExceptionTypes() Type[] Constructor.getGenericExceptionTypes() Type[] Method.getGenericParameterTypes() Type[] Constructor.getGenericParameterTypes() Type Method.getGenericReturnType() Type Field.getGenericType() The normal non-generic methods (as getReturnType()) simply return a Class. So, I think that MethodInfo.getReturnType() should just return a plain TypeInfo as it does at the moment. I'll concentrate on 1,2 and 4 for now, and see if 3 is needed, although I don't think so since it is not present in the reflect implementation either. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530850#530850

16 years

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: Externalizing Scope: Resolving EJB References and Endpoints"

by Marius Bogoevici

JBoss development, A new message was posted in the thread "Externalizing Scope: Resolving EJB References and Endpoints": http://community.jboss.org/message/530847#530847 Author : Marius Bogoevici Profile : http://community.jboss.org/people/marius.bogoevici Message: -------------------------------------------------------------- Andrew, I think that the API that you're suggesting would work well with JBossSessionObjectReference - so the next question is how quickly can you make it available to be consumed by weld-int? Thanks, Marius -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/530847#530847

16 years

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 March 2010