You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Harish Krishnaswamy <hk...@comcast.net> on 2003/09/29 15:46:17 UTC
[HiveMind] Ignored parsing problems
Last night I built a proof of concept for my work with
Tapestry/HiveMind/iBatisDB. It was so much fun and the code is so clean.
Long live open source!
Now to the question. While building the proof of concept, I spent most
of the time debugging one stupid typo in the module descriptor.
Apparently I did not have the logger set up or I would have seen the
problem. I can see from a microkernel stand point why it should not
crash, but is there a way we can turn the logger on by placing a default
log properties in the distribution or something?
-Harish
Re: [HiveMind] Ignored parsing problems
Posted by Harish Krishnaswamy <hk...@comcast.net>.
Yes Tomcat was running on JDK 1.4, but I have used Log4j with this
Tomcat before so I will have to play with it. It would be nice if we
could some way force the logs like other kernels do on a console. But
not sure how though, may be it should just be a flashing, bold warning
sign in the documentation! I am sure a lot of the newbie's would face
this situation.
-Harish
Howard M. Lewis Ship wrote:
>Can't you just use Log4J and a reasonable log4j.properties? What was your environment? Probably JDK
>1.4 and I don't know what the default behavior is for it. I'd hate to package up a log4j.properties
>or JDK 1.4 logger conf (whatever that looks like) in hivemodule.jar as that might screw up real
>end-users.
>
>HiveMind is logging a few things at debug and the rest at error.
>
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>http://jakarta.apache.org/commons/sandbox/hivemind/
>http://javatapestry.blogspot.com
>
>
>
>>-----Original Message-----
>>From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
>>Sent: Monday, September 29, 2003 9:46 AM
>>To: Jakarta Commons Developers List
>>Subject: [HiveMind] Ignored parsing problems
>>
>>
>>Last night I built a proof of concept for my work with
>>Tapestry/HiveMind/iBatisDB. It was so much fun and the code
>>is so clean.
>>Long live open source!
>>
>>Now to the question. While building the proof of concept, I
>>spent most
>>of the time debugging one stupid typo in the module descriptor.
>>Apparently I did not have the logger set up or I would have seen the
>>problem. I can see from a microkernel stand point why it should not
>>crash, but is there a way we can turn the logger on by
>>placing a default
>>log properties in the distribution or something?
>>
>>-Harish
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>
RE: [HiveMind] Ignored parsing problems
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Can't you just use Log4J and a reasonable log4j.properties? What was your environment? Probably JDK
1.4 and I don't know what the default behavior is for it. I'd hate to package up a log4j.properties
or JDK 1.4 logger conf (whatever that looks like) in hivemodule.jar as that might screw up real
end-users.
HiveMind is logging a few things at debug and the rest at error.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com
> -----Original Message-----
> From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> Sent: Monday, September 29, 2003 9:46 AM
> To: Jakarta Commons Developers List
> Subject: [HiveMind] Ignored parsing problems
>
>
> Last night I built a proof of concept for my work with
> Tapestry/HiveMind/iBatisDB. It was so much fun and the code
> is so clean.
> Long live open source!
>
> Now to the question. While building the proof of concept, I
> spent most
> of the time debugging one stupid typo in the module descriptor.
> Apparently I did not have the logger set up or I would have seen the
> problem. I can see from a microkernel stand point why it should not
> crash, but is there a way we can turn the logger on by
> placing a default
> log properties in the distribution or something?
>
> -Harish
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [HiveMind] Ignored parsing problems
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Can't you just use Log4J and a reasonable log4j.properties? What was your environment? Probably JDK
1.4 and I don't know what the default behavior is for it. I'd hate to package up a log4j.properties
or JDK 1.4 logger conf (whatever that looks like) in hivemodule.jar as that might screw up real
end-users.
HiveMind is logging a few things at debug and the rest at error.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com
> -----Original Message-----
> From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> Sent: Monday, September 29, 2003 9:46 AM
> To: Jakarta Commons Developers List
> Subject: [HiveMind] Ignored parsing problems
>
>
> Last night I built a proof of concept for my work with
> Tapestry/HiveMind/iBatisDB. It was so much fun and the code
> is so clean.
> Long live open source!
>
> Now to the question. While building the proof of concept, I
> spent most
> of the time debugging one stupid typo in the module descriptor.
> Apparently I did not have the logger set up or I would have seen the
> problem. I can see from a microkernel stand point why it should not
> crash, but is there a way we can turn the logger on by
> placing a default
> log properties in the distribution or something?
>
> -Harish
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>