Re: [Wonder-disc] Log4J (Unknown Source)

[Chuck H. <ch...@gl...>]

wocompile is javac.  It just extends it so whatever works for javac also works with wocompile.


On Jun 27, 2011, at 11:03 AM, Ramsey Gurley wrote:

> Hi all,
> 
> I'm looking at my logs in deployment trying to pinpoint a NPE, but I'm seeing:
> 
> at com.practicemojo.businesslogic.campaignprocessing.TransactionQueueUtilities.processSmsQueueItems(Unknown Source)
> 
> The wonder and WO stuff all print source lines just fine, it's only in our own frameworks where this is a problem, so I suspect there's a problem in the build.xml or something.  Googling presents me with
> 
> http://nileshbansal.blogspot.com/2006/08/java-exception-unknown-source.html
> 
> Which sorta supports my theory, but they're using javac, not wocompile...  Is there some flag I can set in build.properties or something to make source lines available in deployment?
> 
> Thanks,
> 
> Ramsey
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security 
> threats, fraudulent activity, and more. Splunk takes this data and makes 
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Wonder-disc mailing list
> Won...@li...
> https://lists.sourceforge.net/lists/listinfo/wonder-disc

-- 
Chuck Hill             Senior Consultant / VP Development

Come to WOWODC this July for unparalleled WO learning opportunities and real peer to peer problem solving!  Network, socialize, and enjoy a great cosmopolitan city.  See you there!  http://www.wocommunity.org/wowodc11/