April 2008 - jboss-user - Jboss List Archives

[JBoss Portal] - Hyperlink not working from CMS html page to another CMS HTML

by shankarkhanna

Hi, I am new to the portal development. And i am facing an issue while using CMS which is integrated with JBoss Portal. I am using jboss portal 2.6.4. When i create a html page in cms and put a hyperlink to another page (that also created through cms). The link does not work. I also checked the default portal which is having default page. There are few links in default page which all are working. But as soon as i edit that index.html file under the default folder, the links do not work. The links in new version of index.html file do not work. It does not work even if i just open the index.html file and press create button that creates a new version of index.html file. Please help me that i able to use hyperlinks in cms content. Thanks Shankar Khanna View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142712#4142712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142712

18 years

1
0
0 / 0

[JBossWS] - Re: HELP with error

by jp_kr

Ajay, I am facing the same problem. My endpoint is correct. Have any other chance to get this same error? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142710#4142710 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142710

18 years

1
0
0 / 0

[JBoss Messaging] - Message redistibution between 2 MDB's

by sameuh

Hello, I have 2 nodes in cluster which has same mdbs. How do I have for having that the 2 nodes consume the same number of message themself. Should I use message redistribution or clustered connection factories ? Example : I send 10 msgs to a queue A which is deployed on the 2 nodes. MDBs listen to it. I want that the node 1 treats 5 and the node 2 treats also 5 messages from the queue A. Sam View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142709#4142709 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142709

18 years

1
0
0 / 0

[JBoss Portal] - Re: PortalCMSCacheLoader.java optimization

by thomas.heute＠jboss.com

Sounds good ! Can you please open a Jira, and use the link to this forum post (no need to create a patch here) Thanks a lot ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142706#4142706 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142706

18 years

1
0
0 / 0

[JBoss jBPM] - Re: the best way for this kind of assignment?

by clandestino_bgd

Hi, just to ask if the question is either inappropriate for this forum, or not clear, or completely senseless, or too specific, so nobody wants to bother, or people who can answer are too busy in last 4 days? I would be very happy to know this. Thanks MIlan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142701#4142701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142701

18 years

1
0
0 / 0

[JBoss Portal] - Re: Updating portal jackrabbit version

by thomas.heute＠jboss.com

Can you please create a JIRA and submit a patch against: http://anonsvn.jboss.org/repos/portal/branches/JBoss_Portal_Branch_2_7 please ? The changes should not be any different than in the version you use. (read: the same patch should apply, so if you prefer you can also send a patch against 2.6.x as well) If it works and passes the testsuite then we will apply it with pleasure :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142700#4142700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142700

18 years

1
0
0 / 0

[Remoting] - ClassNotFoundException while calling remote ejb3 across isol

by avogt_sundn

Using JBoss Portal 2.6.4 with JDK1.5.0 It seems to me that RMI class loading does not work with my configuration I gave a security policy to the jboss to allow for RMI class loading. And i gave the loaderport parameter to the DefaultEjb3Connector as described here [URL]http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126930[/URL] | <mbean code="org.jboss.remoting.transport.Connector" | name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"> | <depends>jboss.aop:service=AspectDeployer</depends> |  | | <attribute name="Configuration"> | <config> | <invoker transport="socket"> | <attribute name="serverBindAddress">${jboss.bind.address}</attribute> | <attribute name="serverBindPort">3873</attribute> | <attribute name="numAcceptThreads">1</attribute> | <attribute name="maxPoolSize">300</attribute> | <attribute name="clientMaxPoolSize" isParam="true">50</attribute> | <attribute name="timeout" isParam="true">60000</attribute> | <attribute name="loaderport" isParam="true">4873</attribute> | <attribute name="serializationtype" isParam="true">jboss</attribute> | <attribute name="byvalue" isParam="true">true</attribute> | <attribute name="force_remote" isParam="true">true</attribute> | </invoker> | <handlers> | <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler> | </handlers> | </config> | | </attribute> | </mbean> | I get a ClassNotFoundException for the implementing ejb class of the method parameter, but I expected the class to be loaded via RMI loader (via WebService on localhost:8083). Is there something else that I need to configure? | Caused by: java.lang.ClassNotFoundException: palmyra.baustein.geschaeftsverwaltung.antrag.ProtokollVBeanEjb | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) | at java.security.AccessController.doPrivileged(Native Method) | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) | at java.lang.ClassLoader.loadClass(ClassLoader.java:306) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:242) | at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:430) | at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) | at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620) | at org.jboss.system.JBossRMIClassLoader.loadClass(JBossRMIClassLoader.java:91) | at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247) | at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197) | at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) | at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) | at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) | at java.rmi.MarshalledObject.get(MarshalledObject.java:135) | at org.jboss.aop.joinpoint.MethodInvocation.getArguments(MethodInvocation.java:267) | Let me explain the overall situation. Consider this: one ejb A gets another ejb B injected via @EJB annotation. ejb A is thus owning a proxy to ejb B. the respective classes are deployed in two ears that are isolated ie. have their own class loader repositories declared in jboss-app.xml In order to call methods on B, the ear with ejb A contains the ejb interface and parameter classes of ejb B. Now while there is no problem ejb A calling methods on ejb B, B cannot call on A vice versa, because the ear of ejb B does not contain the classes of ejb A. But I want ejb B to be able to callback its owning ejb A. I therefore transmitted the proxy of ejb A to ejb B. class EjbB { | public void setOwner(MyCommonInterface bean) { .. } | | class MyInterceptor{ | @Resource | SessionContext sessionContext; | void propagateOwner() { | iface = sessionContext.getInvokedBusinessInterface(); | MyCommonInterface owner = (MyCommonInterface) | sessionContext.getBusinessObject(iface); | EventListener listener = (EventListener) new InitialContext() .lookup("my-ear/EventListenerEjb/remote"); | owner.setEventListener(listener); | // the next line throw ClassNotFoundException | listener.setReceiver(vbean); | | | 14:14:39,978 ERROR [VBeanInterceptor] VBean: palmyra.baustein.geschaeftsverwaltung.antrag.ProtokollVBeanEjb@d213c: java.lang.Runti | meException: java.lang.ClassNotFoundException: palmyra.baustein.geschaeftsverwaltung.antrag.ProtokollVBeanEjb java.lang.ClassNotFo | undException: palmyra.baustein.geschaeftsverwaltung.antrag.ProtokollVBeanEjb | java.lang.RuntimeException: java.lang.ClassNotFoundException: palmyra.baustein.geschaeftsverwaltung.antrag.ProtokollVBeanEjb | at org.jboss.aop.joinpoint.MethodInvocation.getArguments(MethodInvocation.java:276) | at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:328) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:81) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:139) | at $Proxy400.setReceiver(Unknown Source) | at palmyra.core.vorgangssteuerung.interceptor.VBeanInterceptor.doEJBAnnotation(VBeanInterceptor.java:125) | at palmyra.core.vorgangssteuerung.interceptor.VBeanInterceptor.postConstruct(VBeanInterceptor.java:97) | | Caused by: java.lang.ClassNotFoundException: palmyra.baustein.geschaeftsverwaltung.antrag.ProtokollVBeanEjb | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) | at java.security.AccessController.doPrivileged(Native Method) | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) | at java.lang.ClassLoader.loadClass(ClassLoader.java:306) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:242) | at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:430) | at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) | at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620) | at org.jboss.system.JBossRMIClassLoader.loadClass(JBossRMIClassLoader.java:91) | at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247) | at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197) | at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) | at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) | at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) | at java.rmi.MarshalledObject.get(MarshalledObject.java:135) | at org.jboss.aop.joinpoint.MethodInvocation.getArguments(MethodInvocation.java:267) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142698#4142698 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142698

18 years

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: (MDB) Authentication issue with JBossMessaging

by lhunath

I forgot to post the actual exception: 10:48:17,463 ERROR [ExceptionUtil] ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ConnectionFactory] createFailoverConnectionDelegate [l-3lksntef-1-7olrntef-xogpod-a7o4c5] | javax.jms.JMSSecurityException: User null is NOT authenticated | at org.jboss.jms.server.security.SecurityMetadataStore.authenticate(SecurityMetadataStore.java:202) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:222) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:162) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) | at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:167) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83) | at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) | at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) | at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) | at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83) | at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:369) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:315) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:635) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) | at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) | at java.lang.Thread.run(Thread.java:595) | | | | 10:48:17,481 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@59e8e2(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1d2e04b destination=queue/auditBackend isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=2 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) | javax.jms.JMSSecurityException: User null is NOT authenticated | at org.jboss.jms.server.security.SecurityMetadataStore.authenticate(SecurityMetadataStore.java:202) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:222) | at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:162) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) | at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) | at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:167) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83) | at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) | at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) | at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) | at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) | at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137) | at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83) | at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:369) | at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:315) | at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:635) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) | at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) | at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142697#4142697 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142697

18 years

1
0
0 / 0

[Management, JMX/JBoss] - Re: any way to find server uptime

by dimitris＠jboss.org

Try to read that as an attribute instead of invoking an operation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142696#4142696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142696

18 years

1
0
0 / 0

[JBoss/Spring Integration] - Re: JBOSS 4.2 + Spring Security on EJB3

by noFreak

HI, in my case i have the same requirements, i have an ejb3 container (Jboss 4.2) an a classic EJB3 implemetation. I want to secure the methods of my EJB's by Spring Security. Furthermore i have a rich client application which acces the ejb components with JNDI lookups. So I can't use filter based HTTP protocol autorization/authentication. A solution for using Spring Security without web stuff u can find here: http://affy.blogspot.com/2005/10/acegi-tutorial-example-of-method-based.html But that's not everything. I have the problem that i don't know how i can secure the methods within the context of a JNDI lookup. Actualy the Spring IoC Container have to handle the MethodSecurityInterceptor aspects. But I dont' know how i could configure it in the way to stick it together...do anybody have similar requirements? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142695#4142695 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142695

18 years

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