Sandeep Raman wrote:
Hi,
I tired with 8080. Same error seems to be coming up.
Regards
Sandeep
Did you go through all the steps listed in [1]? In particular, are you
running on WebSphere 6.1.0.9? This error looks like a known problem
with WebSphere (see [2]) that is fixed in 6.1.0.9.
Hi,
I get this error:
/ExceptionError 404: SRVE0190E: File not found: /ComposerService
on touching my URL:
http://172.19.103.18:9080/LOSComposite/ComposerService
in websphere while calling up my composite application with a binding.ws
specified.
The end points are established and i get the
On Thu, Mar 27, 2008 at 12:25 PM, Sandeep Raman [EMAIL PROTECTED]
wrote:
Hi,
I get this error:
/ExceptionError 404: SRVE0190E: File not found: /ComposerService
on touching my URL:
http://172.19.103.18:9080/LOSComposite/ComposerService
in websphere while calling up my composite application
Hi Simon,
I am currently out of office and dont have my files here, i will send you across my war file once i am in office.
The JIRA issue i had raised was for a diff problem i was getting but the files are the same i am using in my war too. If you infer somthing from the files attached with the
HI,
I am using the port 9080 on websphere.
In my composite file i have only specified binding.ws/, will giving some absolute path out there help? i havent tried tht case.
I have configured WAS to use the same port 9080 for all the application deployed.
Regards
Sandeep.
=-=-=
But I think that default port for binding.ws would be 8080. Could
you give a quick try ?
Also, I'm available on IRC if this helps.
On Thu, Mar 27, 2008 at 9:37 AM, Sandeep Raman [EMAIL PROTECTED] wrote:
HI,
I am using the port 9080 on websphere.
In my composite file i have only specified
Hi,
I tired with 8080. Same error seems to be coming up.
Regards
Sandeep
Luciano Resende [EMAIL PROTECTED] wrote on 03/27/2008 10:11:55 PM:
But I think that default port for binding.ws would be 8080. Could
you give a quick try ?
Also, I'm available on IRC if this helps.
On Thu, Mar 27,
