try using a charles or fiddler and debug the packets back and forth from the server.
a lot of times it would help to figure out the problem. Charles: http://www.charlesproxy.com/index.php Fiddler: http://www.fiddlertool.com/fiddler/ regards, Varun Shetty 2008/10/14 ararat avşaroğlu <[EMAIL PROTECTED]> > First of all thanks for your suggestions. I tried something about > crossdomain.xml and achieved to reach the web service, but still cannot > login. The busy cursor appears when i click the login button but nothing > happens after that. When I look access logs of tomcat i can see my flex app > reaches the web service, but gets error 500. When i look to stdout logs of > tomcat there is an exception like this. Have you ever seen this before?: > > <SOAP-ENV:Envelope xmlns:SOAP-ENV=" > http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd=" > http://www.w3.org/2001/XMLSchema"; xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance";> > <SOAP-ENV:Body> > <tns:verifyUser xmlns:tns="http://www.myurl.com";> > <tns:user> > <created xsi:nil="true"/> > <description xsi:nil="true"/> > <groups xsi:nil="true"/> > <id>0</id> > <password></password> > <username></username> > </tns:user> > </tns:verifyUser> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope>-------------------- > ====[server:request]==== > java.lang.IllegalStateException: Method getLocalName() cannot be called for > CHARACTERS event. > at > com.sun.xml.stream.XMLReaderImpl.getLocalName(XMLReaderImpl.java:344) > at > com.sun.xml.ws.util.xml.XMLStreamReaderFilter.getLocalName(XMLStreamReaderFilter.java:128) > at > com.sun.xml.ws.message.stream.StreamMessage.copy(StreamMessage.java:347) > at com.sun.xml.ws.util.pipe.DumpTube.dump(DumpTube.java:82) > at com.sun.xml.ws.util.pipe.DumpTube.processRequest(DumpTube.java:61) > at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559) > at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518) > at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503) > at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400) > at > com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:226) > at > com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:375) > at > com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:175) > at > com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134) > at > com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:159) > at > com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:49) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:542) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) > at java.lang.Thread.run(Unknown Source) > ---[HTTP response 500]--- > <?xml version="1.0" ?><S:Envelope xmlns:S=" > http://schemas.xmlsoap.org/soap/envelope/";><S:Body><ns2:Fault xmlns:ns2=" > http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ns3=" > http://www.w3.org/2003/05/soap-envelope";><faultcode>ns2:Server</faultcode><faultstring>Method > getLocalName() cannot be called for CHARACTERS > event.</faultstring></ns2:Fault></S:Body></S:Envelope>-------------------- > > 14 Ekim 2008 Salı 13:28 tarihinde <mx:AnandVardhan/> < > [EMAIL PROTECTED]> yazdı: > > >> I think your URL delegate is not hitting the server. >> >> Try invoking the webservice directly from the browser and let us know >> what you fund. >> >> Also try to debug the entire cycle of events from clicking on the >> login button to the service layer.. i think you will find something >> broken. >> >> Anand >> >> On Oct 14, 12:14 pm, "ararat avşaroğlu" <[EMAIL PROTECTED]> >> wrote: >> > I tried this solution but there is no success. At the initialization of >> flex >> > do i need to add following codes: >> > Security.allowDomain("*"); >> > Security.loadPolicyFile(" >> http://servername:8080/MyFlexApp/crossdomain.xml";); >> > >> > 2008/10/13 Varun Shetty <[EMAIL PROTECTED]> >> > >> > > yes, you will require crossdomain.xml file on the server that has the >> > > webservice. >> > >> > > if you are hosting on tomcat and the site example is tomcat.com and >> > > webservice is on webservicetom.com >> > > you need to have a crossdomain file on the webservicetom.com root >> folder. >> > >> > > <cross-domain-policy> >> > > <allow-access-from domain="*tomcat.com"/> >> > > <allow-http-request-headers-from domain="*tomcat.com" headers="*" >> > > secure="false"/> >> > > </cross-domain-policy> >> > >> > > regards, >> > > Varun Shetty >> > >> > > On Mon, Oct 13, 2008 at 10:56 AM, ararat <[EMAIL PROTECTED] >> >wrote: >> > >> > >> I developped a flex application that communicates with java web >> > >> service. When i open my application there is a login form. It sends a >> > >> request to web service user's name and password. At my local machine >> > >> no problem with accessing to web service. But when i deploy >> customer's >> > >> server on tomcat there is a problem to reach web service. When i >> > >> lounch the flex app. there is no error on load, after entering >> > >> username and password and press the submit key, there is no action. >> > >> Also the busy cursor doesn't appear. I think flex app. cannot reach >> > >> web service. Is it a crossdomain.xml problem or other reason? Have >> > >> someone ever met this problem? (I put the crossdomain.xml to root >> > >> directory of my app) Anyone have ideas? >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex India Community" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/flex_india?hl=en -~----------~----~----~----~------~----~------~--~---
