[steven.hicks@bt.com]

When I add a weblogic.xml to a web app (to be deployed in WebLogic 9.1), MyEclipse does not recognise this. When I checked the XML Catalogue it did not have anything present for WebLogic 9 (only 8.1 and below)

I tried to add the xsd files myself but since these are nested it did not work:

My file is:
<?xml version=”1.0″ encoding=”UTF-8″?>

<weblogic-web-app xmlns=”http://www.bea.com/ns/weblogic/90″&gt;
<description>WebLogic Extentions required for MyMusic App</description>
<security-role-assignment>
<role-name>MyMusicUser</role-name>
<principal-name>MyMusicUser</principal-name>
</security-role-assignment>
</weblogic-web-app>

Additions to XML Catalogue:
URI: file:/d:/opt/MyEclipse/XSD/schemacom_bea_xml/src/weblogic-web-app.xsd
Key Type: Namespace Name
Key: http://www.bea.com/ns/weblogic/90
URI: file:/d:/opt/MyEclipse/XSD/schemacom_bea_xml/src/weblogic-application.xsd
Key Type: Namespace Name
Key: http://www.bea.com/ns/weblogic/90/weblogic-application.xsd

[Riyad Kalla]

Steven,
You already emailed this question to support@genuitec.com and we asked you for the weblogic-web-app.xsd file.

[steven.hicks@bt.com]

Thanks 😀

[steven.hicks@bt.com]

@steven.hicks@bt.com wrote:

Fixed in 4.1.1 – Thanks 😀

[Riyad Kalla]

Hey guys is this working for everyone now? I installed WebLogic 9.2 and imported some of the sample weblogic.xml files as defined by the app server, like the following:

<?xml version="1.0" encoding="UTF-8"?>

<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
  <security-role-assignment>
    <role-name>PrivilegedUser</role-name>
    <principal-name>Administrators</principal-name>
  </security-role-assignment>
  <jsp-descriptor>
    <page-check-seconds>1</page-check-seconds>
    <verbose>true</verbose>
  </jsp-descriptor>
  <!--
  Use the virtual-directory-mapping element to specify document roots other
  than the default document root of the Web application for certain kinds of
  requests, such as image requests. All images for a set of Web applications
  can be stored in a single location, and need not be copied to the document
  root of each Web application that uses them. For an incoming request, if a
  virtual directory has been specified servlet container will search for the
  requested resource first in the virtual directory and then in the
  Web application's original document root.
  -->
  <virtual-directory-mapping>
    <local-path>/home/rkalla/Applications/bea-weblogic-9.2/weblogic92/samples</local-path>
    <url-pattern>server/*</url-pattern>
  </virtual-directory-mapping>
  <virtual-directory-mapping>
    <local-path>/home/rkalla/Applications/bea-weblogic-9.2/weblogic92/samples</local-path>
    <url-pattern>domains/*</url-pattern>
  </virtual-directory-mapping>
  <virtual-directory-mapping>
    <local-path>/home/rkalla/Applications/bea-weblogic-9.2/weblogic92/samples/server/</local-path>
    <url-pattern>/examples/*</url-pattern>
  </virtual-directory-mapping>
  <virtual-directory-mapping>
    <local-path>/home/rkalla/Applications/bea-weblogic-9.2/weblogic92/samples/server/</local-path>
    <url-pattern>docs/*</url-pattern>
  </virtual-directory-mapping>
  <virtual-directory-mapping>
    <local-path>/home/rkalla/Applications/bea-weblogic-9.2/weblogic92/samples/server/</local-path>
    <url-pattern>medrec/*</url-pattern>
  </virtual-directory-mapping>
  <virtual-directory-mapping>
    <local-path>/home/rkalla/Applications/bea-weblogic-9.2/weblogic92/samples/server/examples/build</local-path>
    <url-pattern>images/*</url-pattern>
  </virtual-directory-mapping>
</weblogic-web-app>

And validation and autocomplete worked fine because we ship the 9.0 schemas in our catalog. We had this as a bug in our database and I’m following up to make sure everything is working.

[Author]

Posts