Web service not accessible after changing application name in Grails - web-services

I have a SOUP web service in my Grails application. It was accessible before changing application name in application.properties from localhost:8080/appName/Services/ but now this gives page not found error after changing the appName. I don't know why this is happening.

Are you providing the same appName in the url as in application.properties ?

Related

The application, MyEAR, is trying to modify a cookie which matches a pattern in the restricted programmatic session cookies list

I am getting below exception while deploying my application on WebSphere Application Server 8.5.5
java.lang.RuntimeException: SRVE8111E: The application, MyEAR, is trying to modify a cookie which matches a pattern in the restricted programmatic session cookies list [domain=*, name=JSESSIONID, path=/].
I found that if I remove below entry from my web.xml [session-config], then no error is shown with deployment and every things works fine.
<cookie-config>
<http-only>true</http-only>
</cookie-config>
<tracking-mode>COOKIE</tracking-mode>
The same ear is able to deploy and run perfectly with JBOSS and WebLogic server.
Please let me know what configuration change I have to do in which xml file to overcome this issue.
My application has application.xml, jboss-deployment-structure.xml and weblogic-application.xml.
Thanks in advance.
If you want the server to allow you to modify the session cookie it's using for HTTP Sessions, you can remove the cookie from Security > Global security > Programmatic session cookie configuration. in the WAS Admin Console.
But you shouldn't modify the session cookie.
I had the same issue in Websphere App Server and this was fixed after I changed the cookie path to the context root instead of the path =/. You could try the same.
Well, removing them from Global security is a solution, but this will impact other application also.
How I fixed this.
Changed the name of sessionId from default jsessionid to something else.

Error registering REST service in ColdFusion 10

I'm having a problem registering a REST web service in the ColdFusion Administrator. I'm using ColdFusion 10 on a Windows server, and the error I get after trying to register a REST web service is:
Error registering REST service. Please ensure that you have entered a proper mapping and path.
Application CA could not be initialized.
Reason: class "com.sun.xml.bind.Util"'s signer information does not match signer information of other classes in the same package
class "com.sun.xml.bind.Util"'s signer information does not match signer information of other classes in the same package
I've tried registering a service on both a remote CF instance as well as my local instance. Locally I've tried just a real basic service - basically one CFC in an application all by itself, but still get the error. I am putting in both the Root path and the Service Mapping, as I do not have an Application.cfc in the application.
Any ideas?
This problem was caused by some custom JARs I was referencing in the ColdFusion Class Path in the Java and JVM settings in the CF Admin utility. I removed the references to the JARs and restarted the CF instance. Then I was able to successfully add the REST WS. I then re-added the JARs in the class path and restarted the instance. The proper solution is probably to recompile those JARs with the same certificate, but if you don't have access to the source code, this may be the only workaround.

Unable to load wsdl file from android browser

I Develop a webservice from a java class using JDeveloper.and deploy it on my local weblogic server. i can access the wsdl directly from my browser . but when i try to access it from my android phone web browser it is not loading it.however i can connect to my local weblogic server via phone. here is the url of mywsdl
http://xxx.xxx.x.xxx:7101/WebServices-Services-context-root/BooksPort?WSDL
Error Message
You tried to access the address which is currently unavailable.make sure that the web address is correctly spelt and punctuated then try reloading again.
Is 7101 is the right port for you wsdl?
Try 7001 and let me know
Are other sites like google.com opening up on your mobile browser? You may require proxy settings to access the WSDL.

Identifying dynamic host and port for ATG Web Service created through Create Web Service Wizard

I am using ATG 10.2 with Weblogic server. I have created a Repository web service (getRepositoryItem) using the Web Services Wizard through dyn admin. I left the host and port empty during the EAR creation. My service is up with the EAR now, but according to the documentation for ATG web services, it says the host and port would be provided on run time. I have not provided any security setting for the webservice but it shows me a 403 if I try to hit the context for the servlet for the service.
I am struggling to access the web service. In the Manage Web services through dyn admin I see my WebApp deployed. But its Instance Running and Registered is displayed as false.
Documentation tells that if the service has been executed Instance Running and Registered displays as true.
Could somebody please help in answering, How to access the web service?
You can use the url as follows it will work. I just had to use the name twice.
http://host:port/serviceName/serviceName?WSDL

tomcat soapui mock web services

I have a .war file which was created from a soapui mock service via the 'deployaswar' option and deployed to Tomcat 5.5. I can successfully view the WSDL in firefox but noticed the the schemaLocation attribute for my xsd import is invalid. Here is the current URL format:
http://localhost:8080/?WSDL&interface=UserServicePortBinding&part=User.xsd
It's missing the web application name in tomcat. I verified this by constructing the correct URL and viewing the xsd:
http://localhost:8080/wartest?WSDL&interface=UserServicePortBinding&part=User.xsd
I also noticed the other references in the xsd have the same issue. How can I correct this?
thanks.
I figured this out for myself. It was a matter of using "Deploy directory or WAR file located on server" to deploy the war and setting the context path to: /
That allowed everything to work correctly.