January 2009 - jboss-user - Jboss List Archives

[JBoss Portal] - Portlet Instance ID error

by hreintke

LS, I am running Portal 2.7.0GA and defining new portlets/pages for the portal. Created a new Portlet Instance of the RSS News portlet, named NU news. Now when accessing the "Portlet Instances" tab of the "admin portal" I get the error : ERROR Cause: javax.portlet.PortletException: Error process faces request Message: Error process faces request StackTrace: javax.portlet.PortletException: Error process faces request at javax.portlet.faces.GenericFacesPortlet.doFacesDispatch(GenericFacesPortlet.java:346) at javax.portlet.faces.GenericFacesPortlet.doView(GenericFacesPortlet.java:306) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328) at javax.portlet.faces.GenericFacesPortlet.doDispatch(GenericFacesPortlet.java:287) at javax.portlet.GenericPortlet.render(GenericPortlet.java:233) Using a fresh/new portal installation I managed to find that this is caused by the space in the name that I used when creating the portlet instance. When using no spaces in the portlet I can configure with no problems. But now I have a partly configured portal which I cannot administer due to the error and I would like to prevent that I have to start all over again. I expected that the configuration I did using the admin interface would be visible in the jboss configuration files but I was not able to find any of my specific configurations in there. Questions : - Should it be possible to use spaces in Portlet Instance ID's ? - Where is the configuration saved that I do using the admin interface ? - Could I manually change that configuration to remove the space from the name ? Kind regards, Herman View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201598#4201598 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201598

17 years, 6 months

1
0
0 / 0

[JBossWS] - Re: WSSE UsernameToken without HTTP basic auth?

by mikaeljl

For anyone watching/tracking this thread: Looks like JBWS-1999 has been implemented and is now scheduled for the 3.0.6 release. Docs updated at: http://jbossws.jboss.org/mediawiki/index.php?title=WS-Security_options look for POJO endpoint. This seems to be exactly what I was looking for when I initially started this thread, looking forward to try this out! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201597#4201597 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201597

17 years, 6 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: JBoss Cache 3.x is not present in maven repo

by tkimura＠redhat.com

Hi Amit, >From JBoss Cache 2.1.0 we use org.jboss.cache for groupId and the groupId "jboss" is no longer in use. http://repository.jboss.com/maven2/org/jboss/cache/jbosscache-core/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201592#4201592 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201592

17 years, 6 months

1
0
0 / 0

[JBoss Cache: Core Edition] - JBoss Cache 3.x is not present in maven repo

by amit.bhayani＠jboss.com

Hi Guys, I don't find the JBC 3.x in maven repo http://repository.jboss.com/maven2/jboss/jboss-cache/ Am I looking at right repo? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201591#4201591 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201591

17 years, 6 months

1
0
0 / 0

[EJB 3.0] - Re: JBoss 5 deployment error

by jaikiran

So that has solved your EJB3 problem. The other exception: anonymous wrote : Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration | looks like a classloader issue. Remove the xml and xerces related jar files from your application package and deploy it. Those jars are already available in JBoss. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201589#4201589 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201589

17 years, 6 months

1
0
0 / 0

[Remoting] - Re: Socket Read Timeout on stressing calls for validating pr

by ron.sigal＠jboss.com

"ImmortAlex" wrote : | invokerDestructionTimer in org.jboss.remoting.Client, which is created and started in disconnect() | Good catch, Alexey. EJB3 creates a new Client with each invocation, so there you are. I've created JIRA issue JBREM-1083 "Each Client creates a new invokerDestructionTimer", and I'll fix it in the next release. "ron.sigal(a)jboss.com" wrote : | Well, I don't think this is a Remoting problem, because the socket transport doesn't create new threads on the client side. | Ah, my mistake. org.jboss.remoting.Client does. Thanks, Alexey. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201587#4201587 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201587

17 years, 6 months

1
0
0 / 0

[Remoting] - Re: Socket Read Timeout on stressing calls for validating pr

by ImmortAlex

"vink" wrote : | Issue 1: | On providing invokerDestructionDelay=10000, my system run out of threads. I mean my client side. Every call results in the creation of new thread, it seems old invoker thread is not getting reused. | I have the same issue. I think reason is invokerDestructionTimer in org.jboss.remoting.Client, which is created and started in disconnect() but isn't stopped in connect(). My situation is not artifically created stress test (but, of course, not every day working scheme). Worst thing is that I can't remove invokerDestructionDelay from Connector configuration. I'm using SSL, and without destruction delay every remote call works so slow... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201584#4201584 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201584

17 years, 6 months

1
0
0 / 0

[JBoss jBPM] - Re: JBPM 3 or 4

by tbeernot

"kukeltje" wrote : Weeks? No... hahaha... there are fixed releasecycles of 8 weeks, so expect alpha2 in 8, maybe a beta1 in 16, then another beta, a cr or 2 and final. So don't expect a GA release before summerhollidays... | Thanks for the clear answers. Not that I am happy with them, but still. :-) I will examine if 3.2.3 and 4.0 can be used along side each other, or if the packages overlap. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201583#4201583 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201583

17 years, 6 months

1
0
0 / 0

[JBossWS] - Re: XML signatures as WS payload?

by richard.opalka＠jboss.com

"sstaible" wrote : Hi, | Any help or explanation of this behaviour is highly appreciated. | I suggest you to call Node.normalize() method before calling XML digital signature API. You can't rely on the precondition SOAP message will be unmodified (regarding the whitespaces) on other side. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201582#4201582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201582

17 years, 6 months

1
0
0 / 0

[Remoting] - Re: Why so many retries?

by ron.sigal＠jboss.com

"mohitanchlia" wrote : | Is there a way to change the timeout and make it applicable only for certain EJBs. The change timeout=xxxx is a global change but what I really want is to apply it to only certain EJB invocations. | Well, one thing you could try would be to create multiple EJB3 Connectors in $JBOSS_HOME/server/$CONFIG/deploy/ejb3.deployer/META-INF/jboss-service.xml, each with a different "timeout" value, and associate different JNDI bindings with the different Connectors. For example, something like this in jboss.xml: | <session> | <ejb-name>SampleEjb3Bean</ejb-name> | <remote-binding> | <jndi-name>SampleEjb3Bean/fasttimeout</jndi-name> | <client-bind-url> | socket://${jboss.bind.address}:3873/?timeout=1000 | </client-bind-url> | </remote-binding> | <remote-binding> | <jndi-name>SampleEjb3Bean/slowtimeout</jndi-name> | <client-bind-url> | socket://${jboss.bind.address}:3873/?timeout=3600000 | </client-bind-url> | </remote-binding> | </session> | where the InvokerLocators for the two Connectors would be "socket://${jboss.bind.address}:3873/?timeout=1000" and "socket://${jboss.bind.address}:3873/?timeout=3600000". Then, you could get two proxies for the same EJB3, and use each as appropriate. Note: I haven't tried it. If it works for you, let us know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201581#4201581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201581

17 years, 6 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-user January 2009