[AMARIS]

… but missing some functionality.
Or maybe I’m just overlooking it.

1. Start an application server from within the console view.
I can stop the server but not start it.

2. Add application context to Tomcat server.xml.
It would be easy to just add the context to the webapplication under development to the server.xml, otherwise I have to redeploy my webapp each time I make a minor adjustment.

3. Create WAR file from application.

4. Monitor SOAP messages with TCP/IP monitor.
When developing a client which talks to a webservice, I would like to be able to monitor the traffic between my client and the webservice. I though the TCP/IP monitor could just do that, but it doesn’t seem to work (maybe my configuration of the monitor is wrong?).

5. Configure the formating of JSP’s.
I prefer that each tag is on a new line, but the current formatter doesn’t allow me configure this.

Otherwise your product looks fine.
Jeroen.

[Riyad Kalla]

1. Start an application server from within the console view.
I can stop the server but not start it.

Starting and stopping are done via the same button in the toolbar (right click on your tool bar > Customize… > and make sure all the “MyEclipse” options are checked to see it).

2. Add application context to Tomcat server.xml.
It would be easy to just add the context to the webapplication under development to the server.xml, otherwise I have to redeploy my webapp each time I make a minor adjustment.

We support more than 20 application servers, the down side is that our connectors are more ‘generic’ in the sense that they do not perform any application server-specific tasks like this.

3. Create WAR file from application.

When setting up a project deployment, selected “Packaged deployment”, it will create a WAR file for you.

4. Monitor SOAP messages with TCP/IP monitor.

The monitor is used like a proxy, you tell it what to connect to and then YOU connect to it.

5. Configure the formating of JSP’s.

The JSP formatter is currently disabled because of some problems with it mangling valid JSP pages. We will address this in a future release (its incredibly complex).

I hope that feedback helped!

[AMARIS]

Riyad,

Thanks for your answer.
We will further look into the product.

One more question about the tcp/ip monitor.
How do I configure it to see my messages?
Let’s say my client as at: http://localhost:8080/myClient
The webservice runs at: http://myserver:8080/webservice
Both in tomcat containers.
What are the settings of the tcp/ip monitor to see the SOAP from and to myClient?

Thanks,
Jeroen.

[Riyad Kalla]

Jeroen,
The HTTP monitor is currently used for analyzing get/post and the headers (IIRC) not the payloads (SOAP data).

[Author]

Posts