- This topic has 8 replies, 2 voices, and was last updated 13 years, 2 months ago by
.
-
Posts
-
We have a web application and have been using IBM tools including WebSphere and development studio. I have been able to get the application to work in MyEclipseBlue. However, my first install indicated the rpc web services worked. I tried to create a JAX-WS service and could not get a simple example to work. After questions I posted here on the tutorials I eventually was advised to re-installed Websphere. This time I loaded WebSphere according to: Installing wepSphere 6.1, JAX-WS, EJB 3.0 and Updates. That brought my server to 6.1.0.13. Our App now doesn’t start. Deployment can run forever – but then fails. When we first ported our app to MEB, we noticed we had to leave out the .xmi files to avoid many errors. With those removed, the app did run. I have posted detailed questions and files with a few responses but not enough follow-up.
So I am including a portion of my deployment file, and then the console startup – which is now again complaining about missing a wscoor.xml file. I have been on this full time for a week and am about to jump off a cliff.
Will someone comment on these files? Can I call for additional help? Do I always have to wait a full day for a response? We have 6 licenses with the prospect for more but I am not getting a warm feeling banging my head against a wall for a week.
If you look up my posts you can see the entire scenario. What can I do to repair this installation? Why does the server window show the apps deployed when they are not?
Fastest way around this is needed.Not sure what happened. I removed a few unneeded jars, tinkered with profiles, regenerated a web service, recompiled and the dire messages went away. Both RPC and WS services are working!! What a fragile world we live in!
jamestthomas,
Apologies for the delay. Glad that it is working fine.
Do let us know if you have any other issues.While I got things working, the larger WS web service did not work, the small te4st one did?. So we are going rpc because we have no time. My question is in my Web project we have designated WebContent as the web-root folder. It seems an empty WEB-INF directory appears outside after i do a compile or 2. Does this indicate a potential error?
jamestthomas ,
1) Are you working with a web project which is created outside the MyEclipse IDE ? Did you rename the WebContent folder to Web-root?
2) Are you seeing the empty WEB-INF generated in the deployment location? Can you please give detail steps on what exactly you are doing for me to be able to replicate it at my end?
I have attached a document with some screen prints and related questions. At this point I have tried a deployment to our dev server. However please see the document and questions attached. We did not rename WebContent to Web-Root. The xmi I was opening was the bnd one and we do have another pre-existing service. Thank you.
I’ll put this back in documentation if you wish. However it is related to this discussion thread.
I have created a client on the same machine I am running the service using 2 instances of myEclipseBlue. I went through the tutorial steps for
Creating a Client for the Web Service which is in the Developing JAX-RPC Web Services for WebSphere on your site. First question – does the above scenario sound like a valid way to test?Attached is the doc showing client project and the results which is an error. Getting this to work is a critical step for us at this point (lost time due to a hurricane!). If you can help determine the reason for error and what I may have done wrong – I would be most grateful.
You must read the above to posts to follow this. MyEclipseBlue is putting in an extra slash in the URL of the service. It creates in the cachedEndpoint:
authority = “localhost:9082” which is correct.
file = “//services/Importer” which is INCORRECT!!In debugging I stopped the thread at the service invocation and changed every value that included the double slash to a single slash and guess what:
Test Call:test: Success 12 <- expected results. So now I am thinking if the tool did not add that double slash – everything would work. This looks very much like a bug. How can I make the tool understand the correct URL as localhost:9082/services/Importer and NOT localhost:9082//services/Importer? This is the kernel of my problem!!!!!!
The response time here does not match up with the real world demands of IT development. We can’t sit and wait for answers so by the time I get one – I have moved on basically plowing through all issues myself. I understand Genuitec does not want to get into a massive support expense and become a substitute for IBM. However new customers following tutorials should get a prompt response. I pointed out an annoying extra slash added to the endpoint URl of a web service on my localhost test. I will simply remove it in the generated code – a one time correction. This is what I would recommend anyone who has read any of this thread. Thank you.
