Re: How to adjust the logging properties and or command to execute Calabash 0.9.17

Thanks Norman,

That solved my first error related to logging however now I get

SEVERE: XS0062:XS0062
SEVERE: Pipeline failed: err:XS0062: XS0062  It is a static error if a
required version attribute is not present.

I went through and added some version="1.0" in places in the xproc were the
schema was letting me add version number such as

cx:message
p:store
p:xslt


I'm not using a pipeline

Any thoughts on this one?

Regards
Alex




On Mon, Mar 1, 2010 at 2:17 PM, Norman Walsh <ndw@nwalsh.com> wrote:

> Alex Muir <alex.g.muir@gmail.com> writes:
> > I haven't figured out what I should do to adjust the logging
> > properties file and or the batch file command I'm using with the
> > earlier version of Calabash to run with 0.9.17. I played around with
> > it and got some different error messages however not certain the
> > solution.
>
> Here's what I have in my logging.properties file:
>
> ############################################################
> # Logging Configuration File
> #
> # You can use a different file by specifying a filename
> # with the java.util.logging.config.file system property.
> # For example java -Djava.util.logging.config.file=myfile
> ############################################################
>
> ############################################################
> #       Global properties
> ############################################################
>
> # "handlers" specifies a comma separated list of log Handler
> # classes.  These handlers will be installed during VM startup.
> # Note that these classes must be on the system classpath.
> # By default we only configure a ConsoleHandler, which will only
> # show messages at the INFO and above levels.
> handlers=java.util.logging.ConsoleHandler
>
> # To also add the FileHandler, use the following line instead.
> #handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler
>
> # Default global logging level.
> # This specifies which kinds of events are logged across
> # all loggers.  For any given facility this global level
> # can be overriden by a facility specific level
> # Note that the ConsoleHandler also has a separate level
> # setting to limit messages printed to the console.
> .level = FINEST
>
> ############################################################
> # Handler specific properties.
> # Describes specific configuration info for Handlers.
> ############################################################
>
> # default file output is in user's home directory.
> java.util.logging.FileHandler.pattern = %h/java%u.log
> java.util.logging.FileHandler.limit = 50000
> java.util.logging.FileHandler.count = 1
> java.util.logging.FileHandler.formatter = java.util.logging.XMLFormatter
>
> # Limit the message that are printed on the console to INFO and above.
> java.util.logging.ConsoleHandler.level = INFO
> java.util.logging.ConsoleHandler.formatter =
> com.xmlcalabash.util.LogFormatter
> #java.util.logging.SimpleFormatter
>
> ############################################################
> # Facility specific properties.
> # Provides extra control for each logger.
> ############################################################
>
> # For example, set the com.xyz.foo logger to only log SEVERE
> # messages:
> #com.xmlcalabash.level = ALL
> #org.xmlresolver.level = ALL
>
> I don't tend to use much except the ConsoleHandler and I just turn
> the level up and down depending on what I want to see.
>
> Hope that helps.
>
>                                        Be seeing you,
>                                          norm
>
> --
> Norman Walsh <ndw@nwalsh.com> | The years teach us much which the days
> http://nwalsh.com/            | never knew.-- Emerson
>



-- 
Alex
https://sites.google.com/a/utg.edu.gm/alex

Some Good Music
http://sites.google.com/site/greigconteh/