Thanks Christophe. Will try
Dak

On Thu, May 26, 2016 at 2:48 PM, Christophe Marchand
cmarchand@xxxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi [unnamed] !
>
> This subject is out of topic, but you could think to pre-compile your .sch
> files at a project build level and not in your application. In a maven
> script, for example, as you are in a java env.
> Something like
> <build>
>    <plugins>
>       <plugin>
>          <groupId>...</groupId>
>          <artifactId>your-artifact</artifactId>
>           ...
>           <configuration>
>              <sources>
>                  <source dir="src/main/sch" recurse="true"
include="*.sch"/>
>              </sources>
>           </configuration>
>        </plugin>
>     </plugins>
> </build>
>
> should not be very difficult to implement. Just a maven plugin to write.
And
> you package only the compiled version of your schematron.
>
> But Wendell solution is much simpler.
>
> Best regards,
> Christophe
>
>
> Le 26/05/2016 20:57, Mailing Lists Mail daktapaal@xxxxxxxxx a C)crit :
>>
>> Dear all,
>> I am sure people would have had this issue before. want to know how to
>> resolve the issue of schematron that needs to import another
>> schematron ..
>>
>> The issue is when a common set of rules are in many schematrons. I
>> dont see a way I can do this ..
>> So I did the following.. Invented a new element with the following
>> structure
>> <includesch document = "../common.sch" rule-name = "common1"/>
>>
>> The <includesch> can be added anywhere you want in the main schematron
>> document..
>>
>> and I wrote a compiler that should be run before the first compilation
>> / THis precompiler will bring the rule from the common document and
>> append it into my main document, where I had added the <includesch>
>>
>> This works fine within the altova environment but fails within my Java
>> environment , as my environment comes up with issues with class path
>> etc, and it does not find the common.sch.. I have asked the Java
>> developers to look into the class path and why common.sch is being
>> looked in a different location. In the meantime, I wanted to know, if
>> this is the right approach, or if there is some element within the
>> schematron library that I can use.
>>
>> May be there is and I am not finding it, may be I am not looking in
>> the right place.
>>
>> May be there is any other approach for this?
>>
>> Your help will be appreciated.