yeah I have a log4j.xml file in my src/main/resources directory. Maven2 picks it up fine from that location, but it doesn't appear to enable logging for the WsdlllGenerator (I think that's the class off the top of my head) like I was trying to do.
On 7/9/07, Daniel King <[EMAIL PROTECTED]> wrote:
Are you using log4j.xml and log4j.dtd files? Daniel King, R2D2, C3P0 Application Engineer Web Team Nemours Office: (904) 288-5643 Fax: (904) 288-5758 *** Call me Daniel *** NOTICE…This electronic transmission is intended only for the person(s) named. It may contain information that is (i) proprietary to the sender, and/or (ii) privileged, confidential and/or otherwise exempt from disclosure under applicable State and Federal law, including, but not limited to, privacy standards imposed pursuant to the federal Health Insurance Portability and Accountability Act of 1996 (HIPAA). Receipt by anyone other than the named recipient(s) is not a waiver of any applicable privilege. If you received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message from your system. ------------------------------ *From:* Ryan Moquin [mailto:[EMAIL PROTECTED] *Sent:* Monday, July 09, 2007 12:05 PM *To:* [email protected] *Subject:* Re: [xfire-user] How to get logging from XFire during generation? Sorry, missed your reply. I didn't try that, I have other services that I run xfire on that work fine, This is a common problem I run into when XFire doesn't like a wsdl, but it's rare that I ever get any useful information from XFire. I did put the xsd file into my classpath along with the wsdl. The funny thing is, the original wsdl doesn't mention this xsd, when I try to run the generation on the original wsdl, it mentions missing types. I added the import statement myself manually for the xsd file, and hence get this error. I'm not sure why their original wsdl doesn't mention the xsd file. I actually have another wsdl that WAS working correctly in my maven build, but since I made some changes to it to incorporate new features, I now get the same error when trying to generate that one (it worked before my changes). I get this log4j error: [ERROR]log4j:WARN No appenders could be found for logger ( org.codehaus.xfire.gen.Wsdl11Generator). I put a log4j file into my build classpath, but still get it to pick up the log4j. Does the log4j go into the plugins classpath? I'm hoping if I can get the logging to work, I can get a message that will help me to understand where the problem is. Thanks, Ryan On 6/25/07, *Conor MacMahon* <[EMAIL PROTECTED]> wrote: Hi Ryan, Have you tried to build the jaxb2 webapp under the examples folder of the latest xfire download? Might be an idea to get that working, so that you know that your environment is all fine for generating jaxb, before moving onto something else? Assuming you have done that, then I suspect it's because you might need to manually download the schema, v01-types-messaging.xsd, to your hard drive and reference it in your classpath as you attempt to run jaxb via maven? This is how the jaxb2 example works in xfire example apps. Also note that another xfire example webapp, jaxws-spring, does a wsgen on a given wsdl file. Again, might be of help to you to get that working, before moving on? To possibly get more information on your maven build, you might want to run the build with the -e switch, gives you more information about what maven is attempting to do before it faults out. Also add a log4j configuration file, and add category(s) on jaxb so that the build spits out more information (e.g. javax.xml.bind)? To conclude, my 'gut feel' is that your trying to run jaxb over another company's wsdl? That wsdl refers to a schema that is probably hosted by them? Hence, you might require some proxy configuration to be setup for maven to allow that schema to be accessed/downloaded? If that's the case, then have a look at this url: http://maven.apache.org/guides/mini/guide-proxies.html I'll leave it at that, as what we're talking about above is more jaxb and maven, rather than xfire. Hoping the above is of some help to you Ryan. Best of luck, Conor ------------------------------ *From:* Ryan Moquin [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, 26 June 2007 5:16 AM *To:* [email protected] *Subject:* [xfire-user] How to get logging from XFire during generation? I'm using the XFire Maven plugin to generate jaxb classes for a wsdl. I keep getting cryptic errors that aren't letting the process finish. I was hoping that someone could tell me if there is a way to get logging to find out what the actual error is so I can fix it. This is the error I'm getting: [INFO]Executing XFire WsGen task with url: file:/messaging.wsdl Retrieving schema at 'v01-types-messaging.xsd', relative to 'file:/messaging.wsdl'. [INFO]------------------------------------------------------------------------ [ERROR]BUILD ERROR [INFO]------------------------------------------------------------------------ [INFO]command execution failed Embedded error: org.codehaus.xfire.gen.GenerationException: Error generating JAXB model. That's all I get about the error... how does one normally troubleshoot this? The wsdl itself is one to a service that we need to consume, we don't have any control over their wsdl, but cannot generate an object model from it... so I'm not sure if we are out of luck using xfire for this? Any help would be appreciated! Thanks! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This email (including any attached files) is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email. The views and opinions are the originator's and do not necessarily reflect those of the Queensland Studies Authority. All reasonable precautions have been taken to ensure that this email contained no viruses at the time it was sent.
