When Muse creates a new resource instance, it defines the resource's wsa:Address using the machine's IP. However, when EPRs are resolved, the host/port in the wsa:Address is not used as part of the resolution process - so if you get back an EPR with an IP and want to change the IP to a host name (using EndpointReference.setAddress()), you can do that and the EPR will still work.
Dan "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 02/28/2007 08:04:59 PM: > I seem to be running into a similar issue. So pertaining to design, > what should getResource().getEndpointReference() return? Should it be > the fully-qualified host name, or the local IP? > > For testing, I'm currently running both the server and client on the > same local machine. First, the client invokes an operation using > something like "http://localhost/TestApp/services/TestResource";. The > operation dynamically creates an instance of another resource, calls > getResource().getEndpointReference() to get the EPR, and then returns > the EPR with the URI appearing like > "http://123.45.6.7/TestApp/services/AnotherResource";. The 123.45.6.7 > happens to be the local machine's IP. The client then attempts to > invoke an operation on the new resource using the new EPR, but it fails > to find the application. I suspect this is because my JBoss server was > started using host=localhost, so it doesn't recognize 123.45.6.7 even > though that's the machine's IP. > > I think that if my server app returns an EPR to a remote client, it > probably can't rely on getResource().getEndpointReference(). Instead, > it may need to manually create a URI containing an external-facing IP. > Most likely, Muse would not always know how to get this IP. Is this > right? > > > -----Original Message----- > From: Christian Ewers [mailto:[EMAIL PROTECTED] > Sent: Friday, February 02, 2007 11:21 AM > To: [email protected] > Subject: RE: Local-EPR with axis2 platform > > > Hi, > thanks for your replies. I could solve the problem by mapping the > full-qualified hostname to the external IP-adress in the /etc/hosts > file. > Thanks for your help. I think it was just a server configuration rather > than a muse/axis problem. > Regards, > Christian > > Although, is the dns-lookup so "expensive" that we use the IP-adress? > In long-running processes IP adresses could get changed and messages > could get lost.... perhaps that would be a good thing to be configurable > at deployment-time? > > > .Freitag, 2. Februar 2007 18:40 > To: <[email protected]> > cc: > From: "Srinivasan Packirisamy \(spackiri\)" <[EMAIL PROTECTED]> > Subject: RE: Local-EPR with axis2 platform > > > I believe the issue is because localhost maps to 127.0.0.1. I have tried > mapping the localhost to the ethernetIP (etc/hosts) of my machine and > things work fine. But, not sure whether that's the right thing to do. > > > > Thank You, > > ~Srini > > > > -----Original Message----- > From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] > Sent: Friday, February 02, 2007 9:24 AM > To: [email protected] > Subject: Re: Local-EPR with axis2 platform > > > > one more thing - yes, you can access AxisEnvironment programmatically > and > > call setDefaultURI() to hack around this. that will allow you to keep > > working while I study the problem. > > > > Dan > > > > > > > > Christian Ewers <[EMAIL PROTECTED]> wrote on 02/02/2007 08:25:44 AM: > > > > > > > > Hi, > > > > > > I'm trying to switch from the mini to the axis2 environment. I still > > have > > > one problem. > > > When calling "getResource().getEndpointReference()" > > > within a capability I get a full qualified hostname as adress when > using > > > the mini-plattform, but under axis2 I always get the local IP > > (127.0.0.1) > > > as adress. > > > > > > Can I change that behavior by any axis2 or server configuration? Or > can > > I > > > access the AxisEnvironment class programmatically to change the > > defaultURI? > > > > > > thanks, > > > Christian > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
