jboss7.x

问题 I deployed a simple war file (vivek.war) which contains a simple index.jsp file successfully in Jboss-5.X.X and Jboss-6.X.X. I simply placed the war file in server\default\deploy And then went to localhost:8080/vivek/index.jsp and everything was fine. But Similarly, for Jboss-as-7.1.1, I deployed the war file in standalone standalone\deployments and started \bin\standalone.sh and then went to localhost:8080/Hello/index.jsp does not display the file. it shows HTTP Status 404-/vivek/

问题 Is there a way to make web application context case in-sensitive? Basically i'm doing the following in jboss-web.xml <jboss-web> <context-root>cap</context-root> </jboss-web> I'm able to access the app via localhost:8080/cap, but trying to make it accessible via localhost:8080/Cap or localhost:8080/CAP. Any ideas please? 回答1: Put apache+mod_proxy in front of jboss and use url-rewriting or redirection (easier option). Example of rewrite: RewriteEngine on RewriteRule ^/Cap$ /cap/ [R]

问题 I am newbee to JBOSS developement and tring to run a project from eclipse but I am getting "Empty name segment is not allowed for java" error. I know such error comes when our jndi resource name is empty but in such case it specifies as "env" and not "java" which is in my case. Posting my stacktrace below. I am using JBOSS 7.1 version. 14:34:04,440 WARN [org.jboss.as.ee] (MSC service thread 1-5) JBAS011001: Could not resolve resource-env-ref java:/TransactionManager 14:34:04,440 ERROR [org

问题 A client installed on jBOSS is trying to access a secured website configured on DataPower xi50v6.0.0.2 appliance. The connection is getting failed at SSL handshake. I have taken a packet capture at DataPower and observed that SSL Handshake is failing with the Description:Handshake failure(40) . However, at the Client Hello step, I have observed that, only one Cipher Suite is specified which is : TLS_EMPTY_RENEGOTIATION_INFO_SCSV . The TLS protocol used ( as per packet capture) is TLS1.1. Can

问题 Can anyone please give me the main difference between JBoss AS 7 and WildFly 8? I'm going to start a very important project and I have to choose between JBoss AS 7 and WildFly 8 (for this project I'm going to use GWT, JPA/Hibernate and jBPM 6). 回答1: WildFly 8 is the next iteration of the JBoss application server after JBoss AS 7 / EAP 6. Basically: JBoss AS 7.x = JEE6 JBoss EAP 6.x = JEE6 WildFly 8.x = JEE7 Red Hat typically backports security fixes from newer versions into older versions,

问题 I have the following configuration in my standalone.xml : <subsystem xmlns="urn:jboss:domain:datasources:1.1"> <datasources> <datasource jta="true" jndi-name="java:/jdbc/myds" pool-name="CADS" enabled="true" use-java-context="true" use-ccm="true"> <connection-url>jdbc:postgresql://db.host/name</connection-url> <driver>postgresql</driver> <new-connection-sql>select 1</new-connection-sql> <pool> <min-pool-size>20</min-pool-size> <max-pool-size>100</max-pool-size> <flush-strategy>IdleConnections

问题 We are in the process of upgrading from JBoss 6 to JBoss 7. The nature of our application has a separate database instance per customer, as well as a core configuration database common to all customers. We often have EJB code which will at least reference the core database plus the individual customer's data in one call, and even some general background processes that go through all customers. In JBoss 6 this was handled without issue by setting the method with a NOT_SUPPORTED transaction

问题 I have a very strange problem where a bean is not resolved but ONLY on submit. It works fine on view but on submit, it errors out saying that the identifier is null My JSF <h:form id="edit" styleClass="form"> <rich:panel> <f:facet name="header"> <h:outputText value="Edit Data" /> </f:facet> <rich:graphValidator value="#{myModel}" id="gv"> <rich:messages for="gv" /> <rich:messages id="goal-messages" globalOnly="true" /> <!-- form fields that reference #{myModel.fields} --> <h:commandButton id=

问题 Now I am using Jboss-seam 2.1.2 ,jsf 2.0 ,richfaces and jpa till now i am used jboss-as 4.2.2 now I want to migrate jboss-as-7.1.1.Final. so now i am make sampleDemo project using seam-gen using jboss- seam 2.1.2 and deplyed in jboss 7 finally I got one issue in jboss 7 its not allow <jta-data-source>sampleDemoDatasource</jta-data-source> its not allow in jboss7 changed to persistence.xml <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema

问题 I get the following error message when trying to connect a web app running on EAP6 to MySQL in OpenShift. javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: Communications link failure How do I fix this? 回答1: The same issue was discussed at https://community.jboss.org/thread/202318. The solution is to append "?autoReconnect=true" to the connection URL. You do this in the standalone.xml file, found in the .openshift/config folder in your OpenShift Maven