Solr 3.1 Déploiement du serveur Jboss échoué

Question

Quand je Solr 3.1 à déployer le serveur d'applications Jboss (version 6.0 finale) J'ai reçu le message d'exception suivant:

Impossible de créer des ressources - Cause: java.lang.Exception: Échec du démarrage du déploiement [vfs: /// D: /jboss-6.0.0.Final/server/default/deploy/solr.war] lors du déploiement de 'solr.war' - cause: java.lang.RuntimeException: org. jboss.deployers.client.spi.IncompleteDeploymentException: Récapitulatif des déploiements incomplets (VOIR LES ERREURS PRÉCÉDENTES POUR PLUS DE DÉTAILS): * DÉPLOIEMENTS IN ERROR: Nom -> Erreur vfs: /// D: /jboss-6.0.0.Final/server /default/deploy/solr.war -> org.jboss.deployers.spi.DeploymentException: Erreur lors de la création de l'objet géré pour vfs: /// D: /jboss-6.0.0.Final/server/default/deploy/solr.w ar DEPLOIEMENTS IN ERROR: Déploiement "vfs: /// D: /jboss-6.0.0.Final/server/default/deploy/solr.war" est en erreur pour les raison (s) suivante (s): org.xml.sax .SAXException: le type d'élément "tlibversion" doit être déclaré. @ vfs: /// D: /jboss-6.0.0.Final/server/default/deploy/solr.war/WEB-INF/lib/velocity-tools-2.0-beta3.jar/META-INF/velocity-view .tld [22,16] ->

Je me demande pourquoi cette erreur est survenue.

J'ai essayé de déployer Solr version 1.4 et 4.0 sur le même serveur et aucune erreur n'a été détectée.

(Ma méthode deploy: Utiliser JBoss AS 6 Admin Console et Ajouter "solr.war" comme une nouvelle ressource pour l'application Web autonome)

Nous vous remercions de l'attention et toute aide est considérée.

Answer 1

moi encore :) .... bonnes nouvelles Je l'ai corrigé Je viens d'éditer ce fichier: solr.war \ WEB-INF \ lib \ velocity-outils-2.0-beta3.jar \ META-INF \ velocity-view .tld

à cette (vous copiez et collez comme est):

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN" "http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd"> 
<!-- 
Licensed to the Apache Software Foundation (ASF) under one 
or more contributor license agreements. See the NOTICE file 
distributed with this work for additional information 
regarding copyright ownership. The ASF licenses this file 
to you under the Apache License, Version 2.0 (the 
"License"); you may not use this file except in compliance 
with the License. You may obtain a copy of the License at 

    http://www.apache.org/licenses/LICENSE-2.0 

Unless required by applicable law or agreed to in writing, 
software distributed under the License is distributed on an 
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 
KIND, either express or implied. See the License for the 
specific language governing permissions and limitations 
under the License.  
--> 
<taglib> 
    <tlib-version>1.0</tlib-version> 
    <jsp-version>1.2</jsp-version> 
    <short-name>velocity</short-name> 
    <uri>http://velocity.apache.org/velocity-view</uri> 
    <display-name>VelocityView Tag</display-name> 
    <description><![CDATA[Support for using Velocity and VelocityTools within JSP files and tags. 
         This makes it trivial to render VTL (Velocity Template Language) 
         or process a Velocity template from within JSP using the current 
         context. This also provides the typical VelocityView support 
         for accessing and configuring both custom and provided 
         VelocityTools.]]></description> 
    <tag> 
    <name>view</name> 
    <tag-class>org.apache.velocity.tools.view.jsp.VelocityViewTag</tag-class> 
    <body-content>tagdependent</body-content> 
    <attribute> 
     <name>id</name> 
     <required>false</required> 
     <rtexprvalue>true</rtexprvalue> 
     <description><![CDATA[A id unique to this usage of the VelocityViewTag. This id is used to uniquely identify this tag in log messages and hopefully at some point serve as a key under which any body for this tag may be cached as an already-parsed template for improved performance. If no id is specified, then a unique is automatically generated, though that will understandably be less useful in log messages.]]></description> 
    </attribute> 
    <attribute> 
     <name>var</name> 
     <required>false</required> 
     <rtexprvalue>true</rtexprvalue> 
     <description><![CDATA[A variable name whose value should be set to the rendered result of this tag.]]></description> 
    </attribute> 
    <attribute> 
     <name>scope</name> 
     <required>false</required> 
     <rtexprvalue>true</rtexprvalue> 
     <description><![CDATA[This property is meaningless unless a 'var' attribute is also set. When it is, this determines the scope into which the resulting variable is set.]]></description> 
    </attribute> 
    <attribute> 
     <name>template</name> 
     <required>false</required> 
     <rtexprvalue>true</rtexprvalue> 
     <description><![CDATA[The name of a template to be requested from the configured Velocity resource loaders and rendered into the page (or variable if the 'var' attribute is set) using the current context. If this tag also has body content, then the body will be rendered first and placed into the context used to render the template as '$bodyContent'; this approximates the "two-pass render" used by the VelocityLayoutServlet.]]></description> 
    </attribute> 
    <attribute> 
     <name>bodyContentKey</name> 
     <required>false</required> 
     <rtexprvalue>true</rtexprvalue> 
     <description><![CDATA[This property is meaningless unless a 'template' attribute is set and the tag has body content in it. When it is, this changes the key under which the rendered result of the body content is placed into the context for use by the specified template. The default value is "bodyContent" and should be sufficient for nearly all users.]]></description> 
    </attribute> 
    </tag> 
</taglib>