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

[Design of JBoss Remoting, Unified Invokers] - Re: Exception propagation using HTTP servlet transport on 1.

by twiedenmann

Hey there, another tip after some frustrating hours of trying to get the f**ck running: Update the jboss remoting lib in the JBossAS with the current version. Sounds stupid, but it worked for me until the Eception and WebServerError thing... So at least i replaced the jboss-remoting.jar in server/default/lib in my 4.2.2GA with the release 2.4 CR1 of the jboss remoting project. After this, the ServerInvokerServlet/?return-exception=true works. Bye, Timo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151869#4151869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151869

17 years, 10 months

1
0
0 / 0

[Design of JBoss ESB] - JCRMessageStoreImpl store only message body?

by maeste

Hi folks, I'm taking a look to JCRMessageStoreImpl class, because I'm evalueting to write a JBossDNA's sequencers on message stored in JCR repository by esb. I noticed current implementation only store Message Body and properties in JSR-170 repository. Are there some reason for that? I would need all information available about message (Header, context, fault, attachment) to extract and correlate any information useful from a SOA governance point of view. For example EPRs in Header would be very useful, isn't it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151863#4151863 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151863

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: EAR structure mock scanning

by alesj

"scott.stark(a)jboss.org" wrote : So in reality for the javaee ear structure deployer, it should not matter if it used its class loader to access the annotations. Just in general a structure deployer should not be loading classes that may be application specific. Yup, that's the case here. OK, I'll try to extract my previous code - or see if it can be directly reused - to add ear scanning for javaee annotations. Or even generic for structure deployers as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151850#4151850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151850

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: EAR structure mock scanning

by scott.stark＠jboss.org

So in reality for the javaee ear structure deployer, it should not matter if it used its class loader to access the annotations. Just in general a structure deployer should not be loading classes that may be application specific. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151847#4151847 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151847

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: EAR structure mock scanning

by scott.stark＠jboss.org

Its not true that Stateful won't be available. These standard javaee annotations will have been brought in by server deployers into a shared server level domain as these are part of the server api when configured for javaee. They are not overridable by client applications. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151840#4151840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151840

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: EAR structure mock scanning

by alesj

"scott.stark(a)jboss.org" wrote : The annotations scanning happens at the post class loader level in jbossas. Where is it happening in your new work? | Pre-real. Obviously it must be after classloading and before real, so I chose pre-real, leaving some classloader modifications for post-cl still open. "scott.stark(a)jboss.org" wrote : | The annotations scanning happening at the structure phase is duplicate that cannot be reused later. It should be based on VFS/javassist usage to avoid introducing the annotations into an incorrect class loader that cannot be determined during the structure phase. | That's what I'm doing - VFS/javassist. ;-) But like I said, structure phase is not the right place to do this, OSGi wise. e.g. we want to scan for @Stateful, but java-ee.jar bundle is not yet installed - it will only be pulled in by my apps javax.ejb.* import - so in structure phase we won't be able to resolve any @Stateful annotation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151836#4151836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151836

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - JBMETA-42

by scott.stark＠jboss.org

What do you mean by this Andrew? anonymous wrote : | My last commit introduced no regression but has now interfered with the policy's expectations of bases upon which to build. As shown from the Proxy TestSuite: | | 02:24:31,424 INFO [ProxySessionTestCase] Business Remote JNDI Name: MyStatelessBean/remote | 02:24:31,427 INFO [ProxySessionTestCase] Business Remote JNDI Name for org.jboss.ejb3.test.proxy.session.MyStatelessRemote: MyStatelessBean/remote/remote-org.jboss.ejb3.test.proxy.session.MyStatelessRemote | 02:24:31,427 INFO [ProxySessionTestCase] Local JNDI Name: MyStatelessBean/local | 02:24:31,427 INFO [ProxySessionTestCase] Business Local JNDI Name for org.jboss.ejb3.test.proxy.session.MyStatelessLocal: MyStatelessBean/remote/local-org.jboss.ejb3.test.proxy.session.MyStatelessLocal | 02:24:31,427 INFO [ProxySessionTestCase] Local Home JNDI Name: MyStatelessBean/remote/localHome | 02:24:31,427 INFO [ProxySessionTestCase] Home JNDI Name: MyStatelessBean/remote/remoteHome | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151834#4151834 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151834

17 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: EAR structure mock scanning

by scott.stark＠jboss.org

The annotations scanning happens at the post class loader level in jbossas. Where is it happening in your new work? The annotations scanning happening at the structure phase is duplicate that cannot be reused later. It should be based on VFS/javassist usage to avoid introducing the annotations into an incorrect class loader that cannot be determined during the structure phase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151832#4151832 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151832

17 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Optimizing Pointcut Matching

by kabir.khan＠jboss.com

I have implemented this for ClassContainers and ClassAdvisors http://jira.jboss.com/jira/browse/JBAOP-575 See the linked JIRA issues for outstanding tasks related to this. For AS startup, I have only focused on ClassContainers for now, since they are used by the proxies used in AS 5, i.e. there is no weaving involved. For the "default" config on my machine, the startup time has gone from 34s to 28s. For "all" from 48s to 42s. Basically when adding bindings, we only add the new binding to the end of the chains for the existing advisors. This causes slightly different behaviour if we have an advisor with an instance domain in GeneratedAdvisor mode, since then bindings for the class-level domain are handled before the bindings for the instance domain. Now, the last added is added to the end of the chain regardless of what domain level it is added to. However, precedence rules are still calculated following an added binding, so that can be used to determine the order where critical. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151827#4151827 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151827

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Proxy Remote Call Handling

by alesj

"wolfc" wrote : | Can't we leverage the MC registry for this? To do what? Remote invocation of MC component? I don't understand what you mean. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151790#4151790 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151790

17 years, 10 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 May 2008