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

[Design the new POJO MicroContainer] - Some Maven related changes

by pgier

I'd like to make a couple of changes in the microcontainer build. The first is to change the parent/aggregate relationship so that the pom in the root directory functions as the parent. This will be more like how the app server build and the aop maven build are set up, and more like how maven builds itself. The build subdirectory will then be just for creating the combined jar files. Also, is there any reason not to change the directory names to follow the maven conventions? Currently we have src/main and src/tests. I'd like to change these to src/main/java and src/test/java. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172414#4172414 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172414

17 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: how big is portal/portlet session?

by prabhat.jha＠jboss.com

Answer is no. I modified ContentTypeInterceptor to spit out values in HttpSession since over there I have access to it and this is what I get: Object org.jboss.portal.session.contexts value is [/failover-portlet] Object jboss.portlet.session.FailoverTestPortletInstance value is org.jboss.portal.portlet.session.SubSession@1127dc0 Object portal.principalview_id value is 0 Object portal.principal/default/FailoverTestPortletPage/FailoverTestPageWindow value is org.jboss.portal.core.model.portal.navstate.WindowNavigationalState@17a1ad3 So, total session size will be sum of sizes of all these. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172409#4172409 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172409

17 years, 7 months

1
0
0 / 0

[QA of JBoss Portal] - Regarding JBoss Portal 2.7

by hfn

When will the stable version JBoss Portal 2.7 be released? (At this time it is JBoss Portal 2.7beta). Could someone on the JBoss team please provide an estimate? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172399#4172399 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172399

17 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - how big is portal/portlet session?

by prabhat.jha＠jboss.com

Hello :-) If I add an attribute to Portlet Session as following: | PortletSession session = request.getPortletSession(true); | Integer data = new Integer(0); | session.setAttribute("my_data", data); | I then do serialization/deserialization to find the size of this object: | ByteArrayOutputStream bs = new ByteArrayOutputStream(); | ObjectOutputStream os = new ObjectOutputStream(bs); | os.writeObject(seqNumber); | int sessionSize = bs.size(); | Does it mean that Http Session size is value of sessionSize in above code snippet? I have iterated through all the attributes in PortletSession (both app and portlet scope) and I see that there is nothing else in the session. There does not seem to be a way to get hold on HttpSession from Portlet and PortletSession is not serializable and rightly so, can I safely conclude based on above code that value of sessionSize is the value of HttpSession? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172392#4172392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172392

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by jaikiran

"ALRubinger" wrote : | getName() is inherited by way of EJBContainer... | | The name in the EJBContainer is being set by the SessionContainer as follows: super(Ejb3Module.BASE_EJB3_JMX_NAME + ",name=" + ejbName,...); Relying on the getName implementation of the EJBContainer (which just returns this name), results in failure of a couple of tests in the EJB Core. I have provided an overriden implementation in SessionContainer which does this: | public String getName() | { | return this.getObjectName().getCanonicalName(); | } Question: The SessionContainer, is using the deprecated Ejb3Module to create a name for the container. Do you want me to change (and test) the SessionContainer to create the name as follows: super(JavaEEComponentHelper.createObjectName(deployment,ejbName), ...); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172356#4172356 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172356

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by jaikiran

"bstansberry(a)jboss.com" wrote : | Since these classes are extensions, there's a fair amount of overriding of protected methods, including some methods you're probably changing (e.g. JndiSessionRegistrarBase.createJndiReferenceBindingSet(...)). So, you're patch will need to include changes to proxy-clustered as well. AIUI, you're mostly working on passing an InvokableContext param instead of a bunch of details. The changes to proxy-clustered needed to handle that should be simple and pretty obvious. Sure, i will include these in my changes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172354#4172354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172354

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Adding a *core* queue to JBM 2 configuration

by timfox

"jmesnil" wrote : | How does it work for all the queues already defined in queues.xml? | There are no queues defined in queues.xml. queues.xml defines security and queue settings groups which are applied to queues based on their addresses. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172351#4172351 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172351

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Adding a *core* queue to JBM 2 configuration

by jmesnil

For the management tasks, I wanted to add a core queue (e.g. admin.adminQueue) to the queues configured in scr/config.queues.xml to have it available on the server by default. However, sending messages to this queue did not work. When the message is routed by the post office, it first looks if the message's destination is in the post office destinations (configured in jbm-configuration by require-destinations, true by default). since the destination is not there, the message is not routed. When I flag "require-destinations" as false, it still did not work because no binding was created for this queue. How does it work for all the queues already defined in queues.xml? The proper setup (adding the destination, creating the binding, registering the queues) is done when deploying the JMS Objects defined in jbm-jndi.xml. Either I've missed an obvious configuration setting or we are not able to properly add a *core* queue to JBM 2 configuration without also making it available for JMS. any ideas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172336#4172336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172336

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Status on proxy-clustered

by ALRubinger

Great, it's on my TODO this week to attempt a resolve on the CL leak without introducing regression in the web injection areas this dumb code was originally placed to placate. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172325#4172325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172325

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Status on proxy-clustered

by bstansberry＠jboss.com

That's expected yes. The clusteredentity tests are unrelated to this work; I'll look this week. IIRC, that has to do w/ including "ear=foo.jar" in ObjectNames even when no ear is involved; it's a matter of making the test expect that behavior (or better yet, getting rid of that behavior if the metadata now allows us to detect it). 18 clusteredsession failures sounds right. If you hack in a workaround to EJBTHREE-1471 [1], that should drop to 2. The two represents a known and acceptable change in behavior from AS 4.x where I haven't had time to tweak the test to account for it. [1] The workaround; this doesn't remove CL leak; just blunt-force stops it from affecting later deployments, allowing testsuite to run properly: | Index: /home/bes/dev/ejb3/trunk/proxy/src/main/java/org/jboss/ejb3/proxy/factory/session/SessionProxyFactoryBase.java | =================================================================== | --- /home/bes/dev/ejb3/trunk/proxy/src/main/java/org/jboss/ejb3/proxy/factory/session/SessionProxyFactoryBase.java (revision 77377) | +++ /home/bes/dev/ejb3/trunk/proxy/src/main/java/org/jboss/ejb3/proxy/factory/session/SessionProxyFactoryBase.java (working copy) | @@ -212,7 +212,11 @@ | constructor = this.createProxyConstructor(businessInterfaces, tcl); | | } | - catch (ClassNotFoundException cce) | +// catch (ClassNotFoundException cce) | +// { | +// // Ignore | +// } | + catch (Throwable t) // BES: temporary workaround to CL leak issue so I can test | { | // Ignore | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172322#4172322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172322

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 August 2008