[jira] Commented: (DAYTRADER-1) [Daytrader] ejb module should not depend on wsappclient module
[ http://issues.apache.org/jira/browse/DAYTRADER-1?page=comments#action_12437912 ] Christopher James Blythe commented on DAYTRADER-1: -- Just out of curiousity, is anyone using the web services app client? Was wondering if we could simply remove it along with the TradeWebSoapProxy? These two are actually independent. The web services app client was created to test web service invocations of the Daytrader web services from a standalone J2EE client. The TradeWebSoapProxy, was added as a means of testing web services and driving the transactions via a browser and the basic servlets/JSPs. Consequently, a request to the action servlet would coordinate with the WebSoapProxy to invoke the target web service. Given the interest in AJAX, I think the AJAX-based interface that is currently in POC would remove the need for these items. [Daytrader] ejb module should not depend on wsappclient module -- Key: DAYTRADER-1 URL: http://issues.apache.org/jira/browse/DAYTRADER-1 Project: DayTrader Issue Type: Bug Components: EJB Tier Reporter: Vincent Massol Assigned To: Matt Hogstrom There is dependency on the wsappclient jar in the ejb module. That doesn't look right. Does it mean the wsappclient should be split into 2 modules? I haven't investigated more but it smells like a circular depdency somewhere. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DAYTRADER-1) [Daytrader] ejb module should not depend on wsappclient module
[ http://issues.apache.org/jira/browse/DAYTRADER-1?page=comments#action_12437972 ] Matt Hogstrom commented on DAYTRADER-1: --- I did not expose it Chris because it required some additional scrubbing and wasn't my primary concern. I think the standalone app could easily disappear. I['m not sure about the SoapProxy as there is no good way to test WS that I'm aware of. Personally though, I'm not big on WS anyway. Perhaps DJencks has some opinion here. [Daytrader] ejb module should not depend on wsappclient module -- Key: DAYTRADER-1 URL: http://issues.apache.org/jira/browse/DAYTRADER-1 Project: DayTrader Issue Type: Bug Components: EJB Tier Reporter: Vincent Massol Assigned To: Matt Hogstrom There is dependency on the wsappclient jar in the ejb module. That doesn't look right. Does it mean the wsappclient should be split into 2 modules? I haven't investigated more but it smells like a circular depdency somewhere. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DAYTRADER-1) [Daytrader] ejb module should not depend on wsappclient module
[ http://issues.apache.org/jira/browse/DAYTRADER-1?page=comments#action_12437978 ] David Jencks commented on DAYTRADER-1: -- I recently got the ws app client to work against g. trunk and the jee5-jetty6 integration. I would strongly prefer that we leave it in place since it works and we have really few examples especially non-trivial examples of anything. If there's a code dependency from the ejb module to the wsappclient module that is definitely something we need to fix. Vincents original comments look reasonable to me, but I'm not that familiar with daytrader. [Daytrader] ejb module should not depend on wsappclient module -- Key: DAYTRADER-1 URL: http://issues.apache.org/jira/browse/DAYTRADER-1 Project: DayTrader Issue Type: Bug Components: EJB Tier Reporter: Vincent Massol Assigned To: Matt Hogstrom There is dependency on the wsappclient jar in the ejb module. That doesn't look right. Does it mean the wsappclient should be split into 2 modules? I haven't investigated more but it smells like a circular depdency somewhere. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
