[Tomcat Integration] - Tomcat encoding
by jidehem
I'm using JBoss on a server with french locale.
All the pages displayed (JSP, servlets) are displaying correctly.
However, the error pages have a strange encoding (it is (correctly) interpreted by firefox as UTF-8).
For example, the 404 error page displays:
anonymous wrote : Etat HTTP 404 - /SIT/index.j
|
| type Rapport d'�tat
|
| message /SIT/index.j
|
| description La ressource demand�e (/SIT/index.j) n'est pas disponible.
| JBoss Web/2.1.3.GA
Thus it seems all pages directly generated by tomcat have the wrong encoding (encoded twice ?).
The logs from JBoss about tomcat shows the same behaviour:
anonymous wrote :
| 13:53:11,780 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-localhost%2F127.0.0.1-8080
| 13:53:11,858 INFO [Http11Protocol] D�marrage de Coyote HTTP/1.1 sur http-localhost%2F127.0.0.1-8443
Note: previewing this post, the special characters are re-interpreted and doesn't look the same as displayed in firefox.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252039#4252039
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252039
15 years, 3 months
[JBoss Web Services Users] - Cannot change the context root for web service
by seamyong
Hi all,
I would like to seek for help how to change the context root for the webservices. From my http://localhost:8080/jbossws/services, two wsdl[s] are shown with the following URL.
1.**************************************************************
Endpoint Name jboss.ws:context=amslogin-amslogin, endpoint=WSUserServiceImpl
Endpoint Address http://AMS-WS-007:8180/amslogin-amslogin/WSUserServiceImpl?wsdl
***************************************************************
2.************************************************************
Endpoint Name jboss.ws:context=amslogin,endpoint=WSUserService
Endpoint Address http://AMS-WS-007:8180/amslogin/ws/WSUserService?wsdl
*************************************************************
However, only the first link works; the second cant be accessed. The following error messages showed whenever i tried to run my web applicaton.
*************************************************************
Exceptions:
*************************************************************
org.jboss.ws.WSException: Cannot obtain config: SOAP Request Handler
at org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(JBossWSConfigFactory.java:148)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfig(EndpointMetaData.java:704)
at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigNameInternal(EndpointMetaData.java:695)
at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigName(EndpointMetaData.java:679)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.processEndpointConfig(JAXWSServerMetaDataBuilder.java:76)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:137)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
19:07:01,500 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Helps are needed!!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252035#4252035
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252035
15 years, 3 months
[JBoss Portal Users] - How to use<!--<restrict>#{s:hasRole('ACCOUNTANT')}</restrict
by guenther.herndl＠softcon.de
PostPosted: Thu Aug 27, 2009 05:56 AM Post subject: How to use<!--#{s:hasRole('ACCOUNTANT')}</restrict Reply with quote
If I use SEAM directly without the PortalBridge I can use Roles defined via our application like:
<!--
#{s:hasRole('ACCOUNTANT')}
-->
In component.xml is via security defined how do deal with login and what to do. But via the PortletBridge I have to use SSO of JBoss Portal. I found the folowing coment:
public boolean authenticate()
{
//This code is not used in portal environment when utilitizing the PortalIdentity bridgelet.
To get the UserDate to have added instead:
@In
private Credentials credentials;
So I have to define all user and relates Roles via the AdminPart of the Portal. I tried to use the s.hasRole('ssss') also via the PortalBridge but I allways got false. All SEAM DemoExamples offered for the Bridge do not use this hasRole Part. How is it possible to work with the Roles via the PortletBridge?
Kind Regards
Günther Herndl
softcon
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252024#4252024
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252024
15 years, 3 months