>-----Original Message-----
>From: rsal [mailto:rsal@;mb.sympatico.ca]
>Sent: Friday, October 11, 2002 3:01 PM
>To: xdoclet-user
>Subject: Re: [Xdoclet-user] help with merge points?
>
>
>I'll try to give an example:
>
>In our project, we're using a open source component called SiteMesh. 
>SiteMesh contains a filter that we are using. We didn't create this 
>filter, so therefore, we can't generate a filter mapping for it using 
>XDoclet.
>
>To overcome this, XDoclet gives you the ability to merge files into 
>deployment descriptors. What we did, was create a filter-mappings.xml 
>file (take a look in the generate xml files to see what to 
>name certain 

Rick,

Thanks for the help, but I'm still not there yet:

What files do you refer to with "the generate xml files"?

>From the 1.2 beta 1 docs:

"The problem is that you will need to change your code when the url 
changes. Several merge points exist in ejb-body.xdt. This file is the 
template for ejb-jar.xml, you can see the merge point we need: 
<XDtMerge:merge file="ejb-env-entries-{0}.xml">.
Every line between this tag and its closing tag will be replaced in the 
generated ejb-jar.xml file by the content of 
ejb-env-entries-SessionBean.xml, found under the directory given by the 
mergeDir attribute you specify for the task or the subtask and a 
directory structure given by the package of the class."

What does the notation "{0}" mean in "ejb-env-entries-{0}.xml"? I had 
not encountered this notation prior to looking into XDoclet.

How do you know which *.xdt files are templates for which deployment 
descriptors?

How was the file name "ejb-env-entries-SessionBean.xml" arrived at?

Thanks a lot for your help. Some of the XDoclet functionality is 
difficult to crack into but very useful once you figure it out.

Chuck


>files for merging) and added the following to it:
>
><filter>
>    <filter-name>sitemesh</filter-name>
>    
><filter-class>com.opensymphony.module.sitemesh.filter.PageFilte
>r</filter-class>
></filter>
>
><filter-mapping>
>      <filter-name>sitemesh</filter-name>
>      <url-pattern>/*</url-pattern>
></filter-mapping>
>
>When xdoclet creates the web.xml, it will look in the merge directory 
>we've specified, and add the above in the appropriate spot.
>
>That's the jist of it. Hopefully, I haven't missed something. 
>If I have 
>could someone please point it out. ;)
>
>HTH,
>/rick
>
>[EMAIL PROTECTED] wrote:
>
>>I trying to understand xdoclet merging. I've read the 1.2 
>beta docs on 
>>the subject, but am not fully understanding it yet. I make 
>good use of 
>>the sample project, but it doesn't seem to utilize merge 
>functionality. 
>>Can anyone provide me with pointers to any relevant examples or 
>>documentation not included with the 1.2 beta? Thanks.
>>
>>Chuck
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Welcome to geek heaven.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>Xdoclet-user mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>>
>>  
>>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Xdoclet-user mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to