[JBoss Portal] - saving admin portlet-based config as default portal config
by vinguye2
Currently, the admin portlet is used to configure the portal at runtime. Instead of having the info saved to the db, is there a way to make it output to actual descriptor files that can be used to replace the original JBoss Portal descriptors, to make it the default configuration of the Portal itself?
I'd like to configure the portal per customer, so each distribution will have its own default configuration. I was wondering if I can take advantage of the admin portlet as the "IDE" to customize the portal since it can already do this at runtime...instead of me needing to directly update the descriptor files to have the same end result. I don't want to distribute a product to a customer with data already in the db, requiring me to also distribute the db.
It would be nice if the admin portlet could also be a stand-alone app by itself somehow, to configure the portal at design time instead of runtime. Could this be something supported by the Portal team in the future?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094767#4094767
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094767
18Â years, 9Â months
[JBossWS] - Re: jbossws-2.0.1 released
by ptenn10
Richard,
Thanks very much for your response.
I downloaded a pure copy of the JBoss AS 4.0.4GA and compared default/conf/standardjboss.xml to our /conf/standardjboss.xml.
It appears that in the pure 4.0.4GA, the interceptor is: org.jboss.ws.server.ServiceEndpointInterceptor
and we had changed this to
org.jboss.ws.integration.jboss.ServiceEndpointInterceptor
when we upgraded to jbossws-1.4. Although I wasn't the person on our team who did this upgrade to jbossws-1.4, this is what I can gather based on subversion revision messages.
So, as you suggested, I changed the interceptor to org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor in our /conf/standardjboss.xml:
| <container-configuration>
| <container-name>Standard Stateless SessionBean</container-name>
| <call-logging>false</call-logging>
| <invoker-proxy-binding-name>stateless-rmi-invoker</invoker-proxy-binding-name>
| <container-interceptors>
| <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
| <!-- CMT -->
| <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
| <!-- BMT -->
| <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor</interceptor>
| <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
| </container-interceptors>
| <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool>
| <instance-cache></instance-cache>
| <persistence-manager></persistence-manager>
| <container-pool-conf>
| <MaximumSize>100</MaximumSize>
| </container-pool-conf>
| </container-configuration>
|
| <container-configuration>
| <container-name>Clustered Stateless SessionBean</container-name>
| <call-logging>false</call-logging>
| <invoker-proxy-binding-name>clustered-stateless-rmi-invoker</invoker-proxy-binding-name>
| <container-interceptors>
| <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
| <!-- CMT -->
| <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor </interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
| <!-- BMT -->
| <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor </interceptor>
| <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
| </container-interceptors>
| <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool>
| <instance-cache></instance-cache>
| <persistence-manager></persistence-manager>
| <container-pool-conf>
| <MaximumSize>100</MaximumSize>
| </container-pool-conf>
| <cluster-config>
| <partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
| </cluster-config>
| </container-configuration>
|
However, this class is not found either. I get the exception
2007-10-12 15:40:44,728 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor interceptor
| java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor
|
Could you tell me which JAR this class (org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor) is supposed to reside in? I've tried going through the JARs inside the jbossws.sar directory, but have not been able to find it.
Thanks again for your help!
Philip Tenn
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094763#4094763
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094763
18Â years, 9Â months