[JBoss Portal] - Re: Using WSRP with JBoss Portal 2.4
by danny_hon
What do you mean by "cannot configure WSRP instance"? Does it mean I cannot use a WSRP portlet?
When I tried to change the portlet provider in the management portlet (under portlet), I got the following error. Is it because the feature has not been implemented yet?
2006-08-08 15:36:19,877 ERROR [org.apache.myfaces.portlet.MyFacesGenericPortlet] The portlet threw an exception
javax.portlet.PortletException: /WEB-INF/jsp/management/portlets.xhtml @35,70 value="#{portletmgr.portlets}": org.jboss.portal.core.portlet.management.PortletManagerBean
at org.apache.myfaces.portlet.MyFacesGenericPortlet.handleExceptionFromLifecycle(MyFacesGenericPortlet.java:254)
at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:400)
at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:167)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:407)
at org.jboss.portal.portlet.container.PortletContainer.invokeRender(PortletContainer.java:519)
at org.jboss.portal.portlet.container.PortletContainer.dispatch(PortletContainer.java:440)
at org.jboss.portal.portlet.container.PortletContainerInvoker$1.dispatch(PortletContainerInvoker.java:143)
at org.jboss.portal.portlet.invocation.PortletInvocation.dispatch(PortletInvocation.java:242)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:140)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(TransactionInterceptor.java:105)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_N4020346540025535540.invokeNext(TransactionInterceptor$invokeRequired_N4020346540025535540.java)
.....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963905#3963905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963905
19 years, 9 months
[EJB 3.0] - Re: Difference between JPA and Hibernate
by vitarara
I'll take a swing at this.
Hibernate is an Object Relational framework. It is owned by JBoss. It can be used in Java Enterprise Applications, as well as in Java SE apps. It works using POJO's and a descriptor, and I think it now supports annotations, so you don't need to do the descriptor.
JPA is a specification for persistance of POJO's. JPA makes heavy use of annotations, but it can also use an XML descriptor. JPA is not an implementation and each vendor must provide one to be JEE 5 compliant.
JBoss has a JPA implementation that uses Hibernate under the hood. If you use JPA on JBoss you will not use Hibernate specific syntax to do your work. You would use the JPA standard stuff. JBoss will make it all work behind the scenes.
Mark
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963902#3963902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963902
19 years, 9 months
[Security & JAAS/JBoss] - Problems following NegotiateKerberos documentation.
by kc7bfi
I have been trying to follow the NegotiateKerberos (http://wiki.jboss.org/wiki/Wiki.jsp?page=NegotiateKerberos) documentation but I'm having some trouble. First, The document references a security-service.xml in the deploy directory. I do not have one so I created one as follows:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <server>
|
| <!-- JAAS security manager and realm mapping -->
| <mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
| name="jboss.security:service=JaasSecurityManager">
| <!-- A flag which indicates whether the SecurityAssociation server mode
| is set on service creation. This is true by default since the
| SecurityAssociation should be thread local for multi-threaded server
| operation.
| -->
| <attribute name="ServerMode">true</attribute>
| <attribute name="SecurityManagerClassName">org.jboss.security.plugins.JaasSecurityManager</attribute>
| <attribute name="DefaultUnauthenticatedPrincipal">anonymous</attribute>
| <!-- DefaultCacheTimeout: Specifies the default timed cache policy timeout
| in seconds.
| If you want to disable caching of security credentials, set this to 0 to
| force authentication to occur every time. This has no affect if the
| AuthenticationCacheJndiName has been changed from the default value.
| -->
| <attribute name="DefaultCacheTimeout">1800</attribute>
| <!-- DefaultCacheResolution: Specifies the default timed cache policy
| resolution in seconds. This controls the interval at which the cache
| current timestamp is updated and should be less than the DefaultCacheTimeout
| in order for the timeout to be meaningful. This has no affect if the
| AuthenticationCacheJndiName has been changed from the default value.
| -->
| <attribute name="DefaultCacheResolution">60</attribute>
| <attribute name="CallbackHandlerClassName">org.jboss.web.tomcat.security.AdvancedWebCallbackHandler</attribute>
| </mbean>
|
| </server>
|
I also had to set the login auth-method in my web.xml to BASIC, Negotiate was not recognised.
| <login-config>
| <auth-method>BASIC</auth-method>
| <realm-name>Domain Login</realm-name>
| </login-config>
|
When I try to login from a client, the login failes but I get no errors in the logs. I can see Security logs on my server and PDC that reference a kerberos login, but thats as far as I get.
Has anyone successfully gotten kerberos login to work from the NegotiateKerberos documentation? Is there something I'm missing?
I'm using JBoss 4.0.4.GA and Windows 2003/XP
Thanks, David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963895#3963895
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963895
19 years, 9 months
[JBossCache] - Problems migrating from JBCache 1.3.0.GA to JBCache 1.4.0.GA
by yudivian
I have an application that runs fine using JBCache 1.3.0.GA but when I replace the libraries I need to use JBCache 1.4.0.GA then I get this exceptions when I run the applications. I appreciate any help on this.
org.jgroups.ChannelException: failed to start protocol stack
at org.jgroups.JChannel.connect(JChannel.java:393)
at org.jboss.cache.TreeCache.startService(TreeCache.java:1423)
at maf.services.JBCacheAMSAgentList.(JBCacheAMSAgentList.java:41)
at maf.services.AMS.(AMS.java:138)
at maf.base.PlatformNode.start(PlatformNode.java:125)
at maf.Boot.start(Boot.java:105)
at maf.Boot.main(Boot.java:133)
Caused by: java.lang.Exception: exception caused by UDP.start(): java.net.BindException: Cannot assign requested address
at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:600)
at org.jgroups.stack.DownHandler.run(Protocol.java:117)
org.jgroups.ChannelException: failed to start protocol stack
at org.jgroups.JChannel.connect(JChannel.java:393)
at org.jboss.cache.TreeCache.startService(TreeCache.java:1423)
at maf.services.JBCacheKB.(JBCacheKB.java:40)
at maf.services.DFJBCacheKB.(DFJBCacheKB.java:30)
at maf.services.DF.(DF.java:127)
at maf.base.PlatformNode.start(PlatformNode.java:126)
at maf.Boot.start(Boot.java:105)
at maf.Boot.main(Boot.java:133)
Caused by: java.lang.Exception: exception caused by UDP.start(): java.net.BindException: Cannot assign requested address
at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:600)
at org.jgroups.stack.DownHandler.run(Protocol.java:117)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963894#3963894
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963894
19 years, 9 months