Warning: file_get_contents(/data/phpspider/zhask/data//catemap/9/solr/3.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181

Warning: file_get_contents(/data/phpspider/zhask/data//catemap/0/search/2.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Solr 3.1 Jboss服务器部署失败_Jboss_Solr - Fatal编程技术网

Solr 3.1 Jboss服务器部署失败

Solr 3.1 Jboss服务器部署失败,jboss,solr,Jboss,Solr,当我将Solr 3.1部署到Jboss application server(最终版本6.0)时,我收到了以下异常消息: 无法创建资源solr.war-原因:java.lang.Exception:无法启动部署[vfs:///D:/jboss-6.0.0.Final/server/default/deploy/solr.war]在部署“solr.war”期间-原因:java.lang.RuntimeException:org.jboss.deployers.client.spi.Incomple

当我将Solr 3.1部署到Jboss application server(最终版本6.0)时,我收到了以下异常消息:

无法创建资源solr.war-原因:java.lang.Exception:无法启动部署[vfs:///D:/jboss-6.0.0.Final/server/default/deploy/solr.war]在部署“solr.war”期间-原因:java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException:未完成部署的摘要(有关详细信息,请参阅以前的错误):*错误中的部署:名称->错误vfs:///D:/jboss-6.0.0.Final/server/default/deploy/solr.war->org.jboss.deployers.spi.DeploymentException:为创建托管对象时出错vfs:///D:/jboss-6.0.0.Final/server/default/deploy/solr.war错误部署:部署"vfs:///D:/jboss-6.0.0.Final/server/default/deploy/solr.war“出现错误,原因如下:org.xml.sax.SAXException:必须声明元素类型“tlibversion”。@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]->

我想知道为什么会发生这个错误

我尝试将Solr版本1.4和4.0部署到同一台服务器,但没有发现任何错误

(我的部署方法:将JBoss用作6管理控制台,并添加“solr.war”作为独立web应用程序的新资源)

感谢您的关注,并感谢您提供的任何帮助。

我再次:)……好消息,我已经修复了它,我刚刚编辑了这个文件:solr.war\WEB-INF\lib\velocity-tools-2.0-beta3.jar\META-INF\velocity-view.tld

对此(您可以按原样复制并粘贴):


1
1.2
速度
http://velocity.apache.org/velocity-view
VelocityView标签
看法
org.apache.velocity.tools.view.jsp.VelocityViewTag
标记相关
身份证件
假的
真的
变量
假的
真的
范围
假的
真的
模板
假的
真的
bodyContentKey
假的
真的

我尝试了Tomcat和weblogic,但没有出现任何问题。我相信问题是由JBoss 6.0引起的
<?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>