[JBoss Seam] - HTML source codes has some characters like "&# 30416", but I
by chicochen
HTML source codes has some characters like "&# 30416", but IE display these native words rightly.
I use jboss seam and facelet, and there must not has "&# 30416" charater, which is not supported by google search engine.
I even tried to solve this problem in jsf level, here are some codes, but still not work:
webpage:
<?xml version="1.0" encoding="UTF-8"?>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
web.xml
<filter>
| <filter-name>Set Character Encoding</filter-name>
| <filter-class>com.eastidea.px0515.util.SetCharacterEncodingFilter</filter-class>
| <init-param>
| <param-name>encoding</param-name>
| <param-value>UTF-8</param-value>
| </init-param>
| </filter>
| <filter-mapping>
| <filter-name>Set Character Encoding</filter-name>
| <url-pattern>/*</url-pattern>
| </filter-mapping>
DB conection string:
<connection-url>jdbc:mysql://127.0.0.1:3306/px0515?useUnicode=true&characterEncoding=UTF-8</connection-url>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090466#4090466
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090466
17Â years
[EJB 3.0] - JBoss 4.2.1 and EJB 3.0 Redeployment
by nhelder
I have a stateless session bean that I'd like to make available to a number of war applications.
I'd like to (occasionally) update that session bean and have the changes be immediately made available to those war applications.
But it seems that no matter what I do, the redeploying of the session bean results in ClassCastExceptions being encountered when the web applications look up the session bean's interface. These exceptions persist until either the server is stopped/started or the war file is redeployed.
My best guess is that there's a disconnect between the Tomcat and JBoss class cache... the EJB is undeployed from JBoss and JBoss clears it's cache. Then the EJB comes back, JBoss loads those classes, and is ready to go. But Tomcat still has a reference to the old class files, and thus when it does its JBoss lookup of the EJB's interface it gets what appears to be a "different" class than what it has cached (even though nothing in the interface has changed) and dies.
...is that a (somewhat) accurate description of what's happening? If so, is there some way to avoid the class conflict?
A serialVersionUID seems like it would be a slick solution, but of course those can't be placed on interfaces. Another (crude) solution would be to catch the ClassCastException, somehow tell Tomcat to flush it's cache for that particular context, then try the lookup again... but perhaps there's a more standard solution out there...?
Thanks in advance,
- Nathan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090465#4090465
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090465
17Â years
[JBoss Seam] - Why would adding the following to pages.xml give me: No acti
by samdoyle
Here is the exception as I've seen before. As usual the exception doesn't give any indication of the true problem.
| 4541-a253-1f80ffbdb7c7;|Error Rendering View[/login.xhtml]
| java.lang.IllegalStateException: No active conversation context
|
Here are the two new entries in the pages.xml. Without these it works fine.
| <page view-id="*" login-required="true">
|
| // several more navigation rules before this
|
| <navigation>
| <rule if-outcome="NotificationAdmin">
| <redirect view-id="/notificationAdmin.xhtml"/>
| /rule>
| </navigation>
|
| </page>
|
| // several more of the same type of entry before this one.
| <page view-id="/notificationAdmin.xhtml" login-required="true">
| <restrict>#{s:hasRole('ultra-user')}</restrict>
| </page>
|
I have commented out the notificationAdmin.xhtml so it is bare bones and not doing any form of Seam Component access and I still get this error.
Any help would be great since there is no real indication why this would happen.
Thanks, S.D.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090462#4090462
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090462
17Â years
[JBoss Seam] - Re: How can I integrate CAS client into Seam?
by wuhaixing
This is what in my web.xml
| <filter>
| <filter-name>CAS Filter</filter-name>
| <filter-class>edu.yale.its.tp.cas.client.filter.CASFilter</filter-class>
| <init-param>
| <param-name>edu.yale.its.tp.cas.client.filter.loginUrl</param-name>
| <param-value>https://localhost:8443/cas/login</param-value>
| </init-param>
| <init-param>
| <param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name>
| <param-value>https://localhost:8443/cas/proxyValidate</param-value>
| </init-param>
| <init-param>
| <param-name>edu.yale.its.tp.cas.client.filter.serviceUrl</param-name>
| <param-value>http://localhost:8080/epass/login.seam</param-value>
| </init-param>
| </filter>
|
and this is in the page.xml
| <page view-id="/login.xhtml" action="#{identity.login}">
| <navigation from-action="#{identity.login}">
| <rule if="#{identity.loggedIn}">
| <redirect view-id="/home.xhtml"></redirect>
| </rule>
| <rule if="#{not identity.loggedIn}">
| <redirect view-id="/users/register.xhtml"></redirect>
| </rule>
| </navigation>
| </page>
|
and then in the components.xml ,I have this
| <security:identity authenticate-method="#{authenticator.authenticate}"/>
|
In the authenticator...
| public boolean authenticate()
| {
| String username = (String)Contexts.getSessionContext().get(CASFilter.CAS_FILTER_USER);
| if(username != null) {
| identity.setUsername(username);
| }
| log.info("authenticating #0", identity.getUsername());
| //write your authentication logic here,
| identity.addRole("admin");
| return true;
| }
|
the log told me
anonymous wrote :
| 09:18:11,085 INFO [Contexts] starting up: org.jboss.seam.security.identity
| 09:18:11,092 WARN [RuleBasedIdentity] no security rule base available - please install a RuleBase with the name 'securityRules' if permission checks are required.
| 09:18:11,095 INFO [Contexts] starting up: org.jboss.seam.web.session
| 09:18:13,283 INFO [STDOUT] 2007-10-02 09:18:13,282 INFO [org.jasig.cas.web.flow.InitialFlowSetupAction] - <Setting ContextPath for cookies to: /cas>
| 09:18:19,535 INFO [STDOUT] 2007-10-02 09:18:19,534 INFO [org.jasig.cas.authentication.AuthenticationManagerImpl] - <AuthenticationHandler: org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler successfully authenticated the user which provided the following credentials
| >
| 09:18:19,572 INFO [STDOUT] 2007-10-02 09:18:19,572 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - <Granted service ticket [ST-1-lHKcFO0JY3WxO3lLJrx0a17yhjDhF5fhUmD-20] for service [http://localhost:8080/epass/login.seam] for user [wuhaixing]>
| 09:18:19,709 INFO [Contexts] starting up: org.jboss.seam.security.identity
| 09:18:19,715 WARN [RuleBasedIdentity] no security rule base available - please install a RuleBase with the name 'securityRules' if permission checks are required.
| 09:18:19,718 INFO [Contexts] starting up: org.jboss.seam.web.session
| 09:18:20,054 WARN [SkinFactoryImpl] Init parameter for a skin name changed to org.richfaces.SKIN
| 09:18:20,177 INFO [Authenticator] authenticating null
|
What's wrong?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090456#4090456
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090456
17Â years
[Installation, Configuration & DEPLOYMENT] - Deployment Issues
by ashok_av
Deployment issues.
Currently i am using jboss 3.2.7 version and deploying .ear package with 3 war files inside the .ear file. Everything works just fine. I am currently
looking into upgrading to jboss 4.2.1.GA. I intalled jboss 4.2.1.GA and jdk version 1.5. When i tried to deploy the .ear package, the deployment fails.The
ear file is exploded, but none of the war packages are getting deployed. The WARDeployer (WebSerivce) fails to start and i see these error in the jboss log.
Any help is greatly appreciated.
2007-10-02 08:14:15,584 DEBUG [org.jboss.system.ServiceCreator] About to create xmbean object: jboss.web:service=WebServer with code: org.jboss.web.tomcat.service.JBossWeb with descriptor: META-INF/webserver-xmbean.xml
2007-10-02 08:14:15,717 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.web:service=WebServer
2007-10-02 08:14:15,926 INFO [STDOUT] 08:14:15,902 ERROR [Util] Failed to create schema loader.
java.lang.ClassCastException: org.apache.xerces.dom.DOMXSImplementationSourceImpl
at org.w3c.dom.bootstrap.DOMImplementationRegistry.newInstance(DOMImplementationRegistry.java:144)
at org.jboss.xb.binding.Util$5.run(Util.java:512)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.xb.binding.Util.getXSImplementation(Util.java:488)
at org.jboss.xb.binding.Util.loadSchema(Util.java:387)
at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:168)
at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.java:139)
at org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver.resolve(DefaultSchemaResolver.java:247)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:187)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:323)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:188)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:140)
at org.jboss.system.ServiceConfigurator.parseJbxbSerialData(ServiceConfigurator.java:643)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:327)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
2007-10-02 08:14:15,930 INFO [STDOUT] 08:14:15,927 INFO [ServiceConfigurator] Problem configuring service jboss.web:service=WebServer
org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to create schema loader: org.apache.xerces.dom.DOMXSImplementationSourceImpl
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:192)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:140)
at org.jboss.system.ServiceConfigurator.parseJbxbSerialData(ServiceConfigurator.java:643)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:327)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
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:585)
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.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
2007-10-02 08:14:25,994 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.EARDeployer@1144ba2
2007-10-02 08:14:25,994 INFO [STDOUT] 08:14:25,994 INFO [EARDeployer] Init J2EE application: file:/opt/janus/jboss-4.2.1.GA/server/default/deploy/application.ear
2007-10-02 08:14:25,994 INFO [org.jboss.deployment.EARDeployer] Init J2EE application: file:/opt/janus/jboss-4.2.1.GA/server/default/deploy/application.ear
2007-10-02 08:14:26,009 DEBUG [org.jboss.deployment.EARDeployer] Extracted non-deployable content: META-INF/MANIFEST.MF
2007-10-02 08:14:26,025 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: ejb-db.jar
2007-10-02 08:14:26,104 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: gui.war
2007-10-02 08:14:26,112 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: unprotected.war
2007-10-02 08:14:26,113 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: upload.war
2007-10-02 08:14:26,207 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: communication.war
2007-10-02 08:14:27,089 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/ejb-db.jar
2007-10-02 08:14:27,089 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/communication.war
2007-10-02 08:14:27,089 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for url: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/communication.war
2007-10-02 08:14:27,089 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/communication.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/gui.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for url: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/gui.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/gui.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/unprotected.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for url: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/unprotected.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/unprotected.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/upload.war
2007-10-02 08:14:27,090 DEBUG [org.jboss.deployment.MainDeployer] No deployer found for url: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/upload.war
2007-10-02 08:14:27,091 DEBUG [org.jboss.deployment.MainDeployer] deployment waiting for deployer: file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/upload.war
2007-10-02 08:14:27,091 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/opt/janus/jboss-4.2.1.GA/server/default/deploy/application.ear
2007-10-02 08:14:27,091 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/opt/janus/jboss-4.2.1.GA/server/default/deploy/application.ear
2007-10-02 08:14:27,091 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/opt/janus/jboss-4.2.1.GA/server/default/tmp/deploy/tmp41094application.ear-contents/ejb-db.jar
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.web:service=WebServer
State: FAILED
Reason: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to create schema loader: org.apache.xerces.dom.DOMXSImplementationSourceImpl
Depends On Me:
jboss.mq:service=InvocationLayer,type=HTTP
2007-10-02 08:14:29,185 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090454#4090454
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090454
17Â years