I upgraded XFire and MyEclipse as well yesterday.
I was not talking about eclipse's web service explorer when accessing
that URL, I know about all that (UDDI, WSIL and WSDL main) and as a
matter of fact I mentioned in my previous email, I think,that this
particular approach is working fine. My question was for when using the
"Client Service" generation GUI/option where you have to provide the URL
in that popup GUI and it has to be validated...
How you generated the client code? you said buy using plugin + Eclipse;
same thing, I tried it and in that popup GUI you have to provide the URL
and the validation of that wsdl location URL times out in my case.
Sorry for the delay I debugged the JAXB2 project and by doing the schema
first approach I discovered that artifacts are the same as previously in
the wsdl first scenario, what happened is that the generated skeleton
for the services.xml using the top-down toolkit from MyEclipse was not
correct! So I created my own services.xml instead to modify the template
created by MyEclipse and now the generated schema is absolutely correct
in my opinion. No need for that workaround.
BUT I ran into another issue when trying to access my method in the web
service from the client test code:
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.setParams(Lorg/apache/commons/httpclient/params/HttpConnectionManagerParams;)V
at
org.codehaus.xfire.transport.http.CommonsHttpMessageSender.createClient
(CommonsHttpMessageSender.java:228)
at org.codehaus.xfire.transport.http.CommonsHttpMessageSender.open
(CommonsHttpMessageSender.java:129)
at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient
(HttpChannel.java:121)
at org.codehaus.xfire.transport.http.HttpChannel.send
(HttpChannel.java:48)
at org.codehaus.xfire.handler.OutMessageSender.invoke
(OutMessageSender.java:26)
at org.codehaus.xfire.handler.HandlerPipeline.invoke
(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
at org.codehaus.xfire.client.Client.invoke(Client.java:336)
at org.codehaus.xfire.client.XFireProxy.handleRequest
(XFireProxy.java:77)
at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
at $Proxy12.putDeviceStatus(Unknown Source)
at lixar.ServiceClient.main(ServiceClient.java:473)
And I don't really grasp the root cause of this error.
Anybody any idea ? Please I know the weekend is comming but I would
appreciate a feedback on this before that ...
Regarding the marshall/unmarshall code I don't know I am sorry...
Beside this forum you can look as well to this one for possible answers.
http://osdir.com/ml/java.xfire.user/2007-01/threads.html
I think you should look into TransportManager and Transport components
of XFire.
Regards and Many Thanks,
Dragos
On Fri, 2007-18-05 at 09:36 -0400, Daniel King wrote:
> I created the POJOs using Hibernate. Whenever I put in the path to the
> WSDL in Firefox it brings up the WSDL and shows the XML.
>
> If I put the same URL in eclipse's web service explorer under WSDL main
> then it shows the operations available and their respective inputs. If
> you notice there is UDDI, WSIL and WSDL main in the web service explorer
> so you have to choose WSDL main.
>
> When you generate your client using the WSDL URL, are parts of your
> schema missing? If so check for places where minOccurs="0" and
> nillable="true" and change it to nillable="false". I had missing parts
> of my schema and when I did that they reappeared. What exactly is wrong
> with the generated schema?
>
> What's the URL of your WSDL that you put into eclipse's web service
> explorer? I use
> http://localhost/webAppContext/services/ServiceName?wsdl.
>
> I did all the development from my machine ie created service and
> generated the client. After I got it working I deployed the war that
> has the web service to my machine and had someone from another machine
> test the client.
>
> I also upgrade my XFire eclipse plugin to 1.2.6 yesterday.
>
> I'm still having trouble with the response objects from our Remedy Web
> Service having no data yet I see the xml data came across the wire fine.
> Any idea where the marshalling code is? I went through the debugger but
> didn't see where it grabbed the xml and tried to marshall/unmarshall it.
>
> Thanks,
> Daniel
>
> 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.
>
>
> -----Original Message-----
> From: Dragos Pavel [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 17, 2007 9:48 PM
> To: [email protected]
> Subject: RE: [xfire-user] Different behavior of wsgen in command
> lineandanttask
>
> Hi Daniel and All,
>
> You mentioned:
> "For one service I created, I wrote the service using POJOs with an
> interface. Then I created a services.xml file for the service. Then I
> used the XFire eclipse plugin to generate code from the generated WSDL
> using the "http://myWebAppContext/services/MyService?wsdl"; format to
> generate the client. The web service is in one project and another
> project houses the client. I had no trouble sending/receiving data with
> this client/service as far as input/output."
>
> You created the POJO's yourself or did you use XJC to generate them ?
>
> You encouraged me to try this approach with the Schema First
> Development. Mainly because I understand better all XMLBeans binding now
> and I still prefer to make the JAXB2 bindings to work.
> Problem comes when you say = generating the client = you said "The web
> service is in one project and another project houses the client."
> I did exactly the same too trying both with XFire eclipse plugin, or
> with the XFire from within MyEclipse to generate the client code using
> the URL for the wsdl location from the other project and deployed on
> local JBoss AS. I can access that URL fine in the browser but using the
> XFire plugin (or MyEclipse XFire) I run into this errror and times out
> when accessing the URL in order to validate the wsdl:
>
> ----------------------
> Server returned HHTP response code: 504 for URL :
> http:?//correct_path/Service?wsdl
> ----------------------
>
> Looking at HTTP error codes definitions:
>
> 504 Gateway Timeout
> The server, while acting as a gateway or proxy, did not receive a timely
> response from the upstream server specified by the URI (e.g. HTTP, FTP,
> LDAP) or some other auxiliary server (e.g. DNS) it needed to access in
> attempting to complete the request.
> Note: Note to implementors: some deployed proxies are known to
> return 400 or 500 when DNS lookups time out.
>
> DNS is good in my case, I can access that URL fine in the firefox
> browser or in the MyEclipse browser.
> Further on my hostname is resolved correctly by DHCP.
> BTW I checked the URL spelling etc ...
>
> Normally the packets for http should never leave my computer because
> they have to go to the loop back interface when running locally on same
> computer. I don't understand why from MyEclipse I can't access that URL
> but from the browser is fine.
>
> If I implement this approach now I will have to create all the client
> myself... cause I can't use the plugin + Eclipse or the MyEclipse (who
> has XFire integrated).
> Did you deployed the war on another computer then you generated code
> from the generated WSDL using XFire eclipse plugin on your dev computer?
>
> Aside: what I did before was creating first the wsdl which contained the
> schema. Then using top-down scenario I used MyEclipse-XFire to generate
> all artifacts from the original wsdl. Then introduced the logic for
> service implementation and test client. Problem is that the dynamically
> generated wsdl contains wrong schema. XFire & JAXB2 bindings are
> responsible for creating the generated schema. So I tried to reset force
> XFire to use my original schema, which is not easy to implement in
> certain environment like mine.
> Hope that using XJC to generate correct code and the wsdl in the end to
> contain correct schema ...
>
> Thanks,
> Dragos
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
