September 2008 - jboss-dev-forums

[Design of POJO Server] - Re: JBossWebService WS4EE Deployments and JACC

by anil.saldhana＠jboss.com

https://jira.jboss.org/jira/browse/JBAS-5935 has the necessary fixes. This issue is now resolved. WS deployers need to be reworked to adhere to AS5 deployer mechanism. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175196#4175196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175196

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: JBossWebService WS4EE Deployments and JACC

by anil.saldhana＠jboss.com

One hack would be to create the jacc war permissions in the web services module at the location where it attaches the JBossWebMetaData to the deployment unit. This seems fine because we are just going to add the web perms to the ejb jacc policy configuration because the jacc context id is going to be the same. The dynamic web app is just an auxiliary side effect generated by the WS layer. * This would make webservices module dependent on server module. Scott, thoughts on this one? The distinct deployer architecture in the WS layer is certainly a stumbling block in all that we have strived for in AS5 (staging deployers etc). :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175190#4175190 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175190

17 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: sar vs ear packaging

by alex.guizar＠jboss.com

anonymous wrote : Isn't the enterprise jar supposed to expose some functionality remotely? If so, the console would be a client of that functionality like any other component deployed on the container, like in fact a remote test case. If test cases could use the enterprise beans to deploy processes remotely, all that cactus stuff would not be needed, right? The enterprise jar exposes the command service remotely, and the jms messaging / ejb scheduler services locally. If test cases were written in terms of commands (the EjbSchedulerTest actually is) then Cactus would not be needed. Nevertheless, the web console is not written in terms of commands because it is meant to work either standalone or in tandem with the enterprise jar. Because (a) it relies on the local functionality and (b) it is the only client provided with the distribution, it is not like any other client component. anonymous wrote : So what is the actual benefit of using the ear packaging? From my perspective it only adds another level of component packaging. In fact, since the enterprise beans do not form an integral part with the console alone, it would be quite inappropriate to package them together with the console. It removes a duplicate set of environment references between the console and the enterprise jar. The console may not be the only possible client, but it is the only official client for sure. The ear packaging does not affect other clients: they bind their references to the JNDI names used by the jBPM enterprise beans and voila. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175188#4175188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175188

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: JBossWebService WS4EE Deployments and JACC

by adrian＠jboss.org

There isn't one. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059193#4059193 anonymous wrote : What do I find, you've reinvented the wheel again (the deployers framework) | with something called DeployerHooks. Why?????? and anonymous wrote : | One example of (2) is how do I modify the webserivices metadata with a new deployer? | I can't. I have to use a different api, the DeployersHook to do this. | This is just stupid. | Since all the DeployerHooks are invoked from a single deployer, you can't interleave them with other deployers either. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175187#4175187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175187

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: JBossWebService WS4EE Deployments and JACC

by scott.stark＠jboss.org

What is the ws deployer for step b)? Adding any output type it produces to the WarSecurityDeployer inputs would order these correctly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175183#4175183 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175183

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: JBossWebService WS4EE Deployments and JACC

by anil.saldhana＠jboss.com

A solution to this problem will clear 3 failing tests in the AS5 test suite. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175173#4175173 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175173

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ManagedObject tests failing

by scott.stark＠jboss.org

With the latest JBMAN-2 related changes all of the deployer tests are passing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175168#4175168 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175168

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Classloading problem in proxy factories

by bstansberry＠jboss.com

Adrian, I assume you are referring to the "forceReleaseOnSoftReferences()" method in JVMTIInterface? Yes, that does deliberately fill memory until OOME if necessary, and then forces a GC to try to recover. The "[JVMTIInterface] 4069000 references received" logging Andrew reported occurs later in the process when JVMTIInterface is trying to analyze the heap snapshot it took after having returned from forceReleaseOnSoftReferences(). All of the heap analysis data is being kept in the heap as well; I've found that that standard heap size isn't adequate to do the full analysis w/ AS 5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175163#4175163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175163

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by clebert.suconic＠jboss.com

anonymous wrote : We need a super class we could reuse for other similar tests I mean... something that will start an INVM Transport, and a fake journal using FakeSequentialFiles (in memory) for quick tests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175161#4175161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175161

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by clebert.suconic＠jboss.com

"ataylor" wrote : anonymous wrote : We also need to test case where recovery occurs without the server being restarted. | | I still have some more tests to write which will include this. We need a super class we could reuse for other similar tests As you're going through that, that will same me some time later! (Sorry for being so selfish like that :-P ) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175160#4175160 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175160

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