i have used the following liberaries in the classpath as mentioned in the XFire user guide -
stax-api-1.0.1.jar wsdl4j-1.6.1.jar wstx-asl-3.2.0.jar xfire-all-1.2.5.jar xfire-jsr181-api-1.0-M1.jar XmlSchema-1.1.jar Regards, Anshumn --- Andres Bernasconi <[EMAIL PROTECTED]> wrote: > ok. Are you sure that XFire's XML libraries are > used? (stax and the > like....) > > On 5/19/07, Anshumn Sagar <[EMAIL PROTECTED]> > wrote: > > > > sure, please let me know once you try it. > > > > Regards, > > Anshumn > > > > --- Andres Bernasconi > <[EMAIL PROTECTED]> > > wrote: > > > > > mmm..interesting... thanks I will try it. > > > > > > On 5/12/07, Anshumn Sagar > <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > I did not add weblogic.xml in the ear file for > > > > Weblogic 9.2 deplyement and it works fine. > That > > > file > > > > is only required for weblogic 8.1 > > > > > > > > --- Andres Bernasconi > > > <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > mmm.. How did you make XFire work on BEA > > > WebLogic > > > > > 9.2? I was having a > > > > > problem with Classloading XML-related > classes ( > > > > > > > > > > > > > > > http://forums.bea.com/bea/message.jspa?messageID=400004159&tstart=0 > > > > > ) > > > > > > > > > > On 5/9/07, Anshumn Sagar > > > <[EMAIL PROTECTED]> > > > > > wrote: > > > > > > > > > > > > Hi Tonio, > > > > > > > > > > > > Thanks for your response. I was able to > figure > > > out > > > > > the > > > > > > problem yesterday and am sorry that could > not > > > post > > > > > it > > > > > > today. > > > > > > > > > > > > It was a very strange problem and finally > I > > > > > figured > > > > > > out that it was due to jdk > incompatibility. I > > > had > > > > > > developed the service in my local machine > on > > > > > tomcat > > > > > > and used jdk 1.4 as the production > environment > > > > > uses > > > > > > Weblogic 8.1 which uses 1.4 jvm. But > inspite > > > of > > > > > doing > > > > > > that I found out that the problem was > arising > > > due > > > > > to > > > > > > some jdk incompatibility as I was not able > to > > > > > > correctly debug the program since all the > > > debug > > > > > points > > > > > > were not reached while debugging. I knew > that > > > > > > invocationTargetException arises if the > > > invoked > > > > > method > > > > > > internally throws some exception, so I > wanted > > > to > > > > > check > > > > > > the code statement which was causing it, > but > > > due > > > > > to > > > > > > the strange behaviour arising of the jvm > > > > > > incompatibility, the debugger would > suddenly > > > jump > > > > > out > > > > > > to some other statements. > > > > > > > > > > > > I am using Eclipse as the IDE and its very > > > nice > > > > > > feature to explicitely impose the excat > jdk > > > > > > compatibility solved the entire issue(Menu > > > option > > > > > > Project -> Properties -> Java Compiler -> > Jdk > > > > > > Compliance)! > > > > > > > > > > > > Thanks again for your response! > > > > > > > > > > > > Regards, > > > > > > Anshumn > > > > > > > > > > > > --- Tonio Caputo <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > > > Hi Anshum, > > > > > > > > > > > > > > The problem here is that de stack-trace > > > > > information > > > > > > > is not good. > > > > > > > > > > > > > > You must run your code through a > debugger > > > and > > > > > stop > > > > > > > in AbstractInvoker (I'm not sure if > that's > > > the > > > > > class > > > > > > > name) > > > > > > > , and see what the TargetException is > > > > > > > (method getTargetException() in > > > > > > > InvocationTargetException class) > > > > > > > these will let you know the real cause > of > > > the > > > > > error. > > > > > > > > > > > > > > After this I'm sure you will be able to > > > detect > > > > > your > > > > > > > problem. > > > > > > > > > > > > > > I faced a similar problem a week ago, > and I > > > was > > > > > > > going to send > > > > > > > an e-mail to see if this problem (?) can > be > > > > > fixed. > > > > > > > > > > > > > > Hope it helps > > > > > > > tonio > > > > > > > > > > > > > > > > > > > > > On Mon, 2007-05-07 at 17:47 -0700, > Anshumn > > > Sagar > > > > > > > wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > I am facing a problem while calling > the > > > web > > > > > > > service > > > > > > > > which returns a list of objects. The > > > service > > > > > is > > > > > > > > written using spring+xfire. The > problem > > > occurs > > > > > > > when I > > > > > > > > deploy the service on Weblogic 8.1. If > I > > > call > > > > > the > > > > > > > > service from my client, I > > > > > > > > get InvocationTargetException. The > stack > > > trace > > > > > > > appears > > > > > > > > as - > > > > > > > > > > > > > > > > > > > > > > > > ---------------------------------------------------- > > > > > > > > > org.codehaus.xfire.XFireRuntimeException: > > > > > > > Exception > > > > > > > > while calling: > > > > > > > > > > > > > > === message truncated === ____________________________________________________________________________________Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222 --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
