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

[Design of JBoss Portal] - Re: exception in HellowIPCportlet

by lucastle

I've had the same problem deploying to JBoss Portal 2.6. I've been able to solve it by overriding the processAction method into the HelloWorldPortletA class. The overridden method doesn't need any code. I hope it helps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144404#4144404 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144404

16 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - JBoss Portal 2.6.3 - 2.6.4 changes

by Aldvin

Can I check somewhere which portal components was updated in 2.6.4 release in comparison with 2.6.3? We did many specific patches in some modules so I have to evaluate can we quickly migrate. Maybe is some summary (apart from release notes) anywhere ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144387#4144387 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144387

16 years, 5 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - 3.0.0-M2 Released

by david.lloyd＠jboss.com

Remoting 3.0.0-M2 is released. I've got the jars uploaded in a ZIP file, but you'll want to check out the project and look in the "samples/" for (a pitiful few) samples of using the standalone API. The Microcontainer integration is scheduled for M3, so standalone is pretty much all that you can really play with at the moment. Report bugs in JIRA as "found in: 3.0.0-M2" and "fix for: 3.0.0-M3" to make sure I see them. This release means that the API is getting close to stable. I want to roll quickly to the next release, so I've set an aggressive date for M3 - just one month away. We need to get a final release out there as soon as possible. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144368#4144368 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144368

16 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Noise at undeployment

by clebert.suconic＠jboss.com

I've tried it with both all and default.. same result.. no noise. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144365#4144365 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144365

16 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Noise at undeployment

by clebert.suconic＠jboss.com

I've tried it and I didn't get any noise. Or someone fixed it before me, or the work i was doing fixed it indirectly. Please let me know If you (or someone else) sees this issue. Thanks, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144360#4144360 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144360

16 years, 5 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: grep jboss in linux serevr return many lines

by kelvinlow

Hi PeterJ, Thanks for reply. Would it be any perfomance issue on this practice? Since the number of processes I saw is keep on increasing, does this means my project got some problems will causing some of the threads cannot be end properly? Thanks and regards, kelvin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144357#4144357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144357

16 years, 5 months

1
0
0 / 0

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

by julien＠jboss.com

I simplified the interceptor/invocation of the portlet container in order to simplify and unify the framework. The PortletInvocation base class does not extend anymore the o.j.p.common.invocation.Invocation class. The PortletInterceptor class has been removed and replace by a PortletInvokerInterceptor class that is code such as: public class PortletInvokerInterceptor implements PortletInvoker { | | .. | | private PortletInvoker next; | | public void setNext(PortletInvoker next) | { | this.next = next; | } | | public Set<Portlet> getPortlets() | { | if (next == null) | { | throw new IllegalStateException(); | } | return next.getPortlets(); | } | | ... | | } The different interceptors of the portlet module have been updated to extend that class. The classes ProducerPortletInvoker / ConsumerPortletInvoker / ContainerPortletInvoker now also extend that class. The benefit for interceptors is that now they can intercept all methods and not only the portlet life cycle method which extend the range of what an interceptor can do (such as a security interceptor can intercept all methods). I was considering also the ProducerPortletInvoker and such as interceptor anyway, so it's a good thing to remove the now obsolete dependency on the o.j.p.common.invocation.* package and unify these interceptors. Beside the minor API changes, I think the most important update is the wiring since the InterceptorStack and InterceptorStackFactory are not used anymore in favor of a direct wiring with the getNext/setNext field on each interceptor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144356#4144356 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144356

16 years, 5 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: grep jboss in linux serevr return many lines

by PeterJ

There is a Linux option whereby each thread runs as its own process. You probably have that option set. And yes, a busy app server will run hundreds of threads. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144297#4144297 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144297

16 years, 5 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - grep jboss in linux serevr return many lines

by kelvinlow

Hello, I m using jboss-4.2.1.GA to run at Redhat Enterprice linux 4 server. After I bring up the jboss services and I issue the command ps -ef | grep jboss | wc -l it return about 200++, and when I check 1 by 1, all are the same jboss process, and it is still increase from time to time. Is this a acceptable scenario? Does anyone encounter this problem? Thanks and Regards, Kelvin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144296#4144296 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144296

16 years, 5 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Another interface rename

by david.lloyd＠jboss.com

As time goes by, I am finding the interface "Context" to be increasingly confusing of a name - especially since creating a "ContextContext" interface on the server side of a request channel. In the Remoting spirit, I think that "Client" would be a better name for this interface. Related interfaces would become "ClientContext", "ClientSource", "ClientIdentifier". Sounds good? If there's no objections I'll make this change for the M2 release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144293#4144293 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144293

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