April 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by heiko.braun＠jboss.com

anonymous wrote : | The InvocationContextCallback should not exist. | OK, I am going to deprecate it and let you know how to pick up the WebServiceContext from a ThreadLocal. Carlo is going to provide the WebServiceContext proxy that will be injected into the bean before it becomes method ready. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145444#4145444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145444

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by heiko.braun＠jboss.com

anonymous wrote : | You need the intermediate deployer to access any EJB 3 meta data. WebServiceDeployment and WebServiceDeclaration should not be implemented by any runtime container or even exist in the first place. | I don't get it. How is an intermediate deployer different from what we already do to Ejb3Deployment? Those interfaces just specify our requirements towards EJB3 meta data. If I am going to put another deployer in between, I still need to work on Ejb3Deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145442#4145442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145442

16 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Annotation scanning

by alesj

OK, this issue is quite a blocker for few other JIRAs, and probably a good API changing candidate, meaning it needs to be done before CR1. :-) Not to mention that it spans over many areas, from AOP, EJBs, Seam, ... and even our MC will benefit from it. So, resolving this would relieve the pita of many. ;-) The initial discussion about starting this solution in classloading: - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132400 And the root JIRA issue: - http://jira.jboss.com/jira/browse/JBCL-9 So, what would be a good entry point into this in our classloading? Part of ClassLoadingPolicy? And the user hooks? We discussed it could be similar to Java6 APR: e.g. - http://java.sun.com/javase/6/docs/api/javax/annotation/processing/RoundEn... But instead on compiling, we could do this on class loading. And we should also consider our instance annotations. Which can kick in as late as in real deployment stage. How does this relate with the work we've done in metadata project? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145436#4145436 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145436

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Scripting Language ESB Action

by Kevin.Conner＠jboss.com

Hiya David. I have had a quick look at your donation and it looks great, thanks very much for doing this work. Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145401#4145401 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145401

16 years, 5 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: Problem in setting up JBoss Profiler 2 in Jboss 4.2.1

by justinwalsh

anonymous wrote : My guess is this being disabled, its not able to establish socket connection ! Is it so? Correct. You can enable the socket connection by changing the attribute in the connector MBean. This change will not persist across application server restarts though. Alternatively you could edit jboss-profiler.sar/META-INF/jboss-services.xml and 1) Remove the duplicate socket attribute 2) Set the socket attribute to true:<attribute name="Socket">true</attribute> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145389#4145389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145389

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Scripting Language ESB Action

by dward＠redhat.com

I have submitted a donation to address this issue. My methodology and reasoning are explained in JIRA: http://jira.jboss.org/jira/browse/JBESB-1683 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145378#4145378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145378

16 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portlet Container 1.2 changes

by julien＠jboss.com

that makes me thing that we would really benefit from a deployment model based on war files that would allow to avoid to repeat/copy deployment descriptors. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145360#4145360 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145360

16 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portlet Container 1.2 changes

by julien＠jboss.com

I have update the common / web / portlet modules to use JBoss Microcontainer 2.0.0.Beta13 . the good news is that I made a lot of cleanup and that MC also now looks more modular (i.e it does not need the VFS / Deployment / AOP stuff anymore) and it looks more maintainable overally (in poms + build.xml). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145359#4145359 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145359

16 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: fromContext dependency regression

by alesj

"adrian(a)jboss.org" wrote : | Each FromContext enumeration value should have an associated state | when it becomes valid. Most will be PreInstall, but some like BeanInfo | will Instantiated. | Fixed. And I also removed pre-configured dependentState==INSTALLED in AbstractDependencyValueMetaData. With different usages of Injection/DependencyValueMetaData, only null can tell us that the user didn't set this, so we apply defaults for different usages, e.g. for FromContext we take its getWhenValid. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145322#4145322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145322

16 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - fromContext dependency regression

by adrian＠jboss.org

I'm seeing a horrible regression in the fromContext dependency injection. e.g. this config from the system-jmx tests in the appserver | <?xml version="1.0" encoding="UTF-8"?> | | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | |  | <bean name="ServiceControllerLocator" class="org.jboss.test.system.controller.integration.support.ServiceControllerLocator" /> | | <bean name="ServiceLifecycle" class="org.jboss.test.system.controller.integration.support.TestServiceControllerLifecycleCallback"> | <property name="mbeanServer"> | <inject bean="ServiceControllerLocator" property="mbeanServer"/> | </property> | <property name="serviceController"> | <inject bean="ServiceControllerLocator" property="serviceController"/> | </property> | </bean> | | <bean name="TransactionManager" class="org.jboss.test.system.controller.integration.support.MockTransactionManager"> | <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=TransactionManager", exposedInterface=org.jboss.test.system.controller.integration.support.MockTransactionManagerMBean.class, registerDirectly=true)</annotation> | <property name="transactionTimeout">300</property> | <property name="objectStoreDir">${jboss.server.data.dir}/tx-object-store</property> | <install bean="ServiceLifecycle" method="install"> | <parameter><inject fromContext="context"/></parameter> | </install> | <uninstall bean="ServiceLifecycle" method="uninstall"> | <parameter><inject fromContext="context"/></parameter> | </uninstall> | </bean> | | </deployment> | is causing a circular dependency of the bean on itself. | AbstractDependencyItem@e59e40{name=TransactionManager dependsOn=TransactionManager whenRequired=Installed dependentState=Installed resolved=false} | Each FromContext enumeration value should have an associated state when it becomes valid. Most will be PreInstall, but some like BeanInfo will Instantiated. Something like: [code public enum FromContext { ... BEANINFO(FromContextDelegate.BEANINFO, ControllerState.INSTANTIATED), View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145168#4145168 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145168

16 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008