Member Avatar for satish.paluvai

I am using weblogic workshop 8.1 if anybody is familiar with this plz tell me.how to write the deployment descriptor in that?

  • 4 Contributors
  • 3 Replies
  • 88 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by jwenting

Dani AI

Generated

As and hinted, the deployment descriptor for a Workshop 8.1 project is just the usual J2EE descriptors plus WebLogic-specific descriptors. That means for a web module you use WEB-INF/web.xml (standard servlet descriptors) and WEB-INF/weblogic.xml (WebLogic-specific overrides). For an EAR you use META-INF/application.xml and META-INF/weblogic-application.xml; EJB jars can use weblogic-ejb-jar.xml. Workshop often creates basic descriptors for you, but you can and should edit them directly when you need custom behavior.

Practical steps inside Workshop 8.1:

  • In the Project/Explorer view expand your web or EAR project.
  • Open WEB-INF (web) or META-INF (EAR) and edit the *.xml files. Workshop provides a descriptor editor and a Source view — use Source for precise control.
  • Save, build/publish, and deploy from Workshop (or Export a WAR/EAR and install it through the Admin Console) so the updated descriptors end up in the deployed archive.

Minimal example skeletons (edit to match your servlet names and mappings):

<!-- WEB-INF/web.xml (very small skeleton) -->
<web-app>
  <servlet>
    <servlet-name>MyServlet</servlet-name>
    <servlet-class>com.example.MyServlet</servlet-class>
  </servlet>
  <servlet-mapping>
    <servlet-name>MyServlet</servlet-name>
    <url-pattern>/app/*</url-pattern>
  </servlet-mapping>
</web-app>

Troubleshooting and tips:

  • Make sure the descriptor XML matches the expected schema/version for the target runtime; wrong schema causes deployment errors.
  • If Workshop auto-generates parts when you add servlets, prefer editing the descriptor file itself so your changes persist.
  • After edits, do a clean build and redeploy; check server logs for XML validation or class-not-found errors.
  • If context-root or classloader behavior is unexpected, verify both web.xml and the WebLogic descriptor rather than only one file.

Yes, the docs are heavy (as noted), but editing these few files directly solves most descriptor needs.

Recommended Answers

All 3 Replies

Member Avatar for masijade

By reading the documentation, maybe?

Member Avatar for Ezzaral

By reading the documentation, maybe?

Yep, sounds like a good bet to me. They put that documentation in there for a reason :)

Member Avatar for jwenting

yep. WebLogic docpacks make great monitor stands (I know from experience).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.