Error Deploying Sample Portal from Development Guide

Question

I am going through creating a New Portal from WebLogic Portal 7 Development
Guide and I am running into the following problem.
After completing Step 2: Create the New Portal, when I try to Hot Deploy the
application, I get the following error.
Hot deploy failed with the following message:
Unable to add module: NewPortalWebApp to application descriptor for:
portalApp.
The log has the following information..
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
portlets\Portlet1.portlet to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\tools.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\webflow-extensions.wfx to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\user_account.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\portal.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\security.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\NewPortal.portal to sync list.
Attempting sync...
Sync complete.
Searching for portalApp application descriptor...
Found it.
Error - please check log for details.

Answer 1

That's great, Mike, you're welcome. I'm glad it's working for you. Thanks for letting me know.
-Scott
Mike Friesen wrote:
I'm sorry you were right.. I tried it and everything works... thanks..
Mike
"Scott Ellis" <[email protected]> wrote in message
news:[email protected]...
Hi Mike,
I hear what you are saying and I believe you. But the error you describedis the known issue related to Internet access
(down to the exact line numbers in the stack trace). Is it possible yourconnection was down last time you attempted
hot-deploy?
If you are sure your Internet connection is up, I would recommend tryinghot-deploy again. If it still does not work,
something very strange is going on. At that point I would recommendtrying the workaround anyway or escalating the issue
to BEA Support.
Now my curiosity is piqued so I hope you'll let me know either way.
Best Regards,
Scott Ellis
BEA Systems
Mike Friesen wrote:
yes..
"Scott Ellis" <[email protected]> wrote in message
news:[email protected]...
Can you please try something for me? Paste the following URL into abrowser:
http://java.sun.com/dtd/application_1_3.dtd
Does it come up?
Thanks,
Scott
Mike Friesen wrote:
Actually, my computer does have internet access, so I don't think that
is
the problem.
Mike
"Scott Ellis" <[email protected]> wrote in message
news:[email protected]...
Hi Mike,
I would bet that you are working on a machine that doesn't have
Internet
access, correct?
The problem is that the EBCC is trying and failing to access the J2EEapplication descriptor
dtd from Sun's website.
If you can't get Internet access, here is the workaround:
- save the attached file to your harddrive (just save it to c:\)
- edit the application.xml file for your project as follows:
- first copy the entire DOCTYPE declaration and save it somewhere
in
a
separate text file (in case want to revert back to it later)
- edit the DOCTYPE declaration so that it looks like this:
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN' 'file:///application_1_3.dtd'>
( notice that the java.sun.com web address is replaced with the URI
to
the file on your harddrive)
- save your changes and hotdeploy will work with or without Internetaccess
Thanks,
Scott Ellis
BEA Systems
Mike Friesen wrote:
I am going through creating a New Portal from WebLogic Portal 7
Development
Guide and I am running into the following problem.
After completing Step 2: Create the New Portal, when I try to Hot
Deploy
the
application, I get the following error.
Hot deploy failed with the following message:
Unable to add module: NewPortalWebApp to application descriptor for:
portalApp.
The log has the following information..
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
portlets\Portlet1.portlet to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\tools.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\webflow-extensions.wfx to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\user_account.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\portal.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\security.wf to sync list.
Adding file:
C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
webapps\PortalWebApp\NewPortal.portal to sync list.
Attempting sync...
Sync complete.
Searching for portalApp application descriptor...
Found it.
Error - please check log for details.
<!--
Copyright (c) 2000 Sun Microsystems, Inc.,
901 San Antonio Road,
Palo Alto, California 94303, U.S.A.
All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to
technology embodied in the product that is described in this document.
In particular, and without limitation, these intellectual property
rights may include one or more of the U.S. patents listed at
http://www.sun.com/patents and one or more additional patents or
pending patent applications in the U.S. and in other countries.
This document and the product to which it pertains are distributed
under licenses restricting their use, copying, distribution, and
decompilation. This document may be reproduced and distributed but
may
not be changed without prior written authorization of Sun and its
licensors, if any.
Third-party software, including font technology, is copyrighted and
licensed from Sun suppliers.
Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
Naming and Directory Interface, JDBC, JDK, JavaMail and and
Enterprise JavaBeans are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries.
Federal Acquisitions: Commercial Software - Government Users Subjectto
Standard License Terms and Conditions.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright (c) 2000 Sun Microsystems, Inc.,
901 San Antonio Road,
Palo Alto, California 94303, E'tats-Unis.
Tous droits re'serve's.
Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
relatants a` la technologie incorpore'e dans le produit qui est
de'crit
dans ce document. En particulier, et sans la limitation, ces droits de
proprie'te' intellectuels peuvent inclure un ou plus des brevets
ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
brevets plus supple'mentaires ou les applications de brevet en attente
dans les E'tats-Unis et dans les autres pays.
Ce produit ou document est prote'ge' par un copyright et distribue'
avec des licences qui en restreignent l'utilisation, la copie, la
distribution, et la de'compilation. Ce documention associe n peut
e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
licence, le cas e'che'ant.
Le logiciel de'tenu par des tiers, et qui comprend la technologie
relative aux polices de caracte`res, est prote'ge' par un copyright et
licencie' par des fournisseurs de Sun.
Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
Naming and Directory Interface, JDBC, JDK, JavaMail et and
Enterprise JavaBeans sont des marques de fabrique ou des marques
de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
pays.
LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
CONTREFAC,ON.
-->
<!--
This is the XML DTD for the J2EE 1.3 application deployment
descriptor. All J2EE 1.3 application deployment descriptors
must include a DOCTYPE of the following form:
<!DOCTYPE application PUBLIC
"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
-->
<!--
The following conventions apply to all J2EE deployment descriptor
elements unless indicated otherwise.
- In elements that contain PCDATA, leading and trailing whitespace
in the data may be ignored.
- In elements whose value is an "enumerated type", the value is
case sensitive.
- In elements that specify a pathname to a file within the same
JAR file, relative filenames (i.e., those not starting with "/")
are considered relative to the root of the JAR file's namespace.
Absolute filenames (i.e., those starting with "/") also specify
names in the root of the JAR file's namespace. In general, relative
names are preferred. The exception is .war files where absolute
names are preferred for consistency with the servlet API.
-->
<!--
The application element is the root element of a J2EE application
deployment descriptor.
-->
<!ELEMENT application (icon?, display-name, description?, module+,
security-role*)>
<!--
The alt-dd element specifies an optional URI to the post-assembly
version of the deployment descriptor file for a particular J2EEmodule.
The URI must specify the full pathname of the deployment descriptor
file relative to the application's root directory. If alt-dd is not
specified, the deployer must read the deployment descriptor from the
default location and file name required by the respective component
specification.
Used in: module
-->
<!ELEMENT alt-dd (#PCDATA)>
<!--
The connector element specifies the URI of a resource adapter archive
file, relative to the top level of the application package.
Used in: module
-->
<!ELEMENT connector (#PCDATA)>
<!--
The context-root element specifies the context root of a web
application.
Used in: web
-->
<!ELEMENT context-root (#PCDATA)>
<!--
The description element is used to provide text describing the parent
element. The description element should include any information that
the application ear file producer wants to provide to the consumer of
the application ear file (i.e., to the Deployer). Typically, the tools
used by the application ear file consumer will display the description
when processing the parent element that contains the description.
Used in: application, security-role
-->
<!ELEMENT description (#PCDATA)>
<!--
The display-name element contains a short name that is intended to be
displayed by tools. The display name need not be unique.
Used in: application
Example:
<display-name>Employee Self Service</display-name>
-->
<!ELEMENT display-name (#PCDATA)>
<!--
The ejb element specifies the URI of an ejb-jar, relative to the top
level of the application package.
Used in: module
-->
<!ELEMENT ejb (#PCDATA)>
<!--
The icon element contains small-icon and large-icon elements that
specify the file names for small and a large GIF or JPEG icon images
used to represent the parent element in a GUI tool.
Used in: application
-->
<!ELEMENT icon (small-icon?, large-icon?)>
<!--
The java element specifies the URI of a java application clientmodule,
relative to the top level of the application package.
Used in: module
-->
<!ELEMENT java (#PCDATA)>
<!--
The large-icon element contains the name of a file
containing a large (32 x 32) icon image. The file
name is a relative path within the application's
ear file.
The image may be either in the JPEG or GIF format.
The icon can be used by tools.
Used in: icon
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
-->
<!ELEMENT large-icon (#PCDATA)>
<!--
The module element represents a single J2EE module and contains a
connector, ejb, java, or web element, which indicates the module type
and contains a path to the module file, and an optional alt-ddelement,
which specifies an optional URI to the post-assembly version of the
deployment descriptor.
The application deployment descriptor must have one module element for
each J2EE module in the application package.
Used in: application
-->
<!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
<!--
The role-name element contains the name of a security role.
The name must conform to the lexical rules for an NMTOKEN.
Used in: security-role
-->
<!ELEMENT role-name (#PCDATA)>
<!--
The security-role element contains the definition of a security
role. The definition consists of an optional description of the
security role, and the security role name.
Used in: application
Example:
<security-role>
<description>
This role includes all employees who are authorized
to access the employee service application.
</description>
<role-name>employee</role-name>
</security-role>
-->
<!ELEMENT security-role (description?, role-name)>
<!--
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the application's
ear file.
The image may be either in the JPEG or GIF format.
The icon can be used by tools.
Used in: icon
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
-->
<!ELEMENT small-icon (#PCDATA)>
<!--
The web element contains the web-uri and context-root of a web
application module.
Used in: module
-->
<!ELEMENT web (web-uri, context-root)>
<!--
The web-uri element specifies the URI of a web application file,
relative to the top level of the application package.
Used in: web
-->
<!ELEMENT web-uri (#PCDATA)>
<!--
The ID mechanism is to allow tools that produce additional deployment
information (i.e., information beyond the standard deployment
descriptor information) to store the non-standard information in a
separate file, and easily refer from these tool-specific files to the
information in the standard deployment descriptor.
Tools are not allowed to add the non-standard information into the
standard deployment descriptor.
-->
<!ATTLIST alt-dd id ID #IMPLIED>
<!ATTLIST application id ID #IMPLIED>
<!ATTLIST connector id ID #IMPLIED>
<!ATTLIST context-root id ID #IMPLIED>
<!ATTLIST description id ID #IMPLIED>
<!ATTLIST display-name id ID #IMPLIED>
<!ATTLIST ejb id ID #IMPLIED>
<!ATTLIST icon id ID #IMPLIED>
<!ATTLIST java id ID #IMPLIED>
<!ATTLIST large-icon id ID #IMPLIED>
<!ATTLIST module id ID #IMPLIED>
<!ATTLIST role-name id ID #IMPLIED>
<!ATTLIST security-role id ID #IMPLIED>
<!ATTLIST small-icon id ID #IMPLIED>
<!ATTLIST web id ID #IMPLIED>
<!ATTLIST web-uri id ID #IMPLIED>