[
https://jira.jboss.org/browse/JBDS-1103?page=com.atlassian.jira.plugin.sy...
]
Rob Stryker commented on JBDS-1103:
-----------------------------------
Rob, still does not explain why it works for Tomcat but not for Tomcat
when it runs in AS.
If the server has loaded a deployment, and I copy a jar into that exploded deployment, the
runtime does not pick it up. I would need to force the application to restart if a jar or
similar extension file that I know the runtime won't pick up is changed. However
I've so far hesitated to do this because I don't like the idea of restarting the
module all the time.
I'm sure I can add this in for unzipped wtp-based deployments but it may require some
digging how to do properly based on the current codebase.
Creating simple Axis Web Service fails running
----------------------------------------------
Key: JBDS-1103
URL:
https://jira.jboss.org/browse/JBDS-1103
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: SOA Platform
Affects Versions: 3.0.0.CR2
Environment: Sun JDK 1.6.0_17, x86_64, JBDS-H7-CR3, Jboss-AS 5.1-GA
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.0.x
Attachments: axis_ws_run_error.log, workspace.zip
It seems like JDBS wrongly creates axis-based web service. In comparsion to Eclipse 3.5
WTP, where everything goes OK as well as deploying and running od jboss-as 5.1
Can be reproduced by following this tutorial
http://www.eclipse.org/webtools/jst/components/ws/1.5/tutorials/BottomUpW...
Notes:
Eclipse 3.5 WTP creating, deploying, running - OK
Opening workspace created by Eclipse 3.5 WTP by JBDS and deploying+running Axis WS - OK
See attached log and workspace
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira