Over here, we've added entities in the header of struts-config.xml like
this:

<?xml version="1.0" encoding="ISO-8859-1" ?>

<!DOCTYPE struts-config PUBLIC
  "-//Apache Software Foundation//DTD Struts Configuration 1.0//EN"
  "http://jakarta.apache.org/struts/dtds/struts-config_1_0.dtd"; [

  <!-- General -->
  <!ENTITY global_forwards                  SYSTEM
"file:package/path/globalforwards.xml">
  <!ENTITY general_actionmappings           SYSTEM
"file:package/path/actionmappings.xml">
  <!-- Part1 -->
  <!ENTITY part1_formbeans       SYSTEM
"file:other/package/strutsconf/formbeans.xml">
  <!ENTITY part1_actionmappings  SYSTEM
"file:other/package/strutsconf/actionmappings.xml">

  <!-- Part 2 -->
  ......
]>

and then the appropriate entries under form-beans and <action-mappings>,
like this:

  <form-beans>
    &part1_formbeans;
    &part2_formbeans;
  </form-beans>

   .....
  <action-mappings>
    &part1_actinomappings;
    &part2_actionmappings;
  </action-mappings>

The only problem was getting the parser to read the entries with a relative
path.
Our solution was to always start the servlet engine (tomcat) from a
directory at the
top of the package hierarchy. I've seen in Ted Husted's pages that other
approach was to 
change the DTD to allow repeated <form-beans> and <action-mappings> entries
in the struts-config
file and build this file as with ant (concatenation).

Ronaldo

-----Ursprüngliche Nachricht-----
Von: Yee Keat [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 13. November 2001 10:45
An: Struts Users Mailing List
Betreff: Bloated struts-config.xml


After developing around 200+ jsp and 600+ java files, the struts-config.xml 
is getting around 3000 lines. 

Is there anyway to better organize the contents of the file? Like can 
organiza by java path or something like that.
-- 
Cheers,

Yee Keat

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to