Ok, that is true, but it doesn't tell me why this change was required, what it means, or really how to fix an interface to work properly (like it once did) again. Just fixing the topmost class doesn't do it. Also, searching for responseType in the Help menu takes me to a place that has a graphic that isn't correct. I mean, you don't really want to subclass for something like this. You probably want to instantiate the ui:responseType property. I did that (and with other ui-specific classes) but still don't have the thing working. So a 'real' tutorial would be clear enough that most questions would be answered at least in terms of logistics of making something work. Although your reply is most certainly appreciated, the questions remain mostly unanswered. So I'll try to load the workspace into 4.2 and see what happens. Now that I have changed a bunch of classes I hope the whole thing doesn't break completely, but that is my problem.
Jack On Monday, June 30, 2014 10:45:08 AM UTC-7, Scott Henninger wrote: > > In http://www.topquadrant.com/docs/versions/changes-4.3.0.txt > > - Change: Any SWP view that shall be callable from the outside via the swp > servlet must declare a property > ui:responseType - either directly or indirectly via a superclass. > Otherwise, the request will > be rejected. This change may require adjustments to your own > applications, although SWA has been > adjusted to make the transition as smooth as possible. > > > -- Scott > > On 6/30/2014, 12:37 PM, Jack Hodges wrote: > > Thank you Scott. This is exactly the kind of thing that would be very > useful to see in release notes. When I was reading the release notes from > 4.2 to 4.4 I saw nothing about this (important) change. Did I just miss it? > > Jack > > On Monday, June 30, 2014 9:20:41 AM UTC-7, Scott Henninger wrote: >> >> Jack, the error message states what you need to do. For each SWP class >> you want to expose as a Web service, you need to provide a response type. >> In addition to assisting the mime type of the response, this serves as a >> way to control access to the SWP classes you generate - i.e. only those >> that have a responseType can be access from outside of a TopBraid SWP >> context. >> >> To assign the response type, go to the class definition you want to >> expose as a service and choose "add existing: from the context menu. The >> set of types supported will be displayed. Choose one and commit the >> choice, and you service should work as before. >> >> There is a section on this that can be found by searching for >> "responseType" in Composer help. See Help > TopBraid Composer > >> Application Development Tools > Web Services. >> >> -- Scott >> >> On 6/30/2014, 11:12 AM, Jack Hodges wrote: >> >> I suppose I should clarify 'why' I want to do this but thank you for the >> link (I'll try it out). The reason I want to go to 4.2 is that I am getting >> a load error in the browser (see trace below). This is from Windows 64-bit >> TBCME version 4.4. I have already run System->Refresh Topbraid system >> registries (SPIN etc). I would rather use the current version if I can >> figure out what the differences are in 4.4 that produce this result that >> don't occur in 4.2. Thanks for any pointers. >> >> Jack >> >> Operation failed. >> >> On: Jun 30, 2014 9:05:38 AM >> >> Reason: >> java.lang.IllegalArgumentException: View class >> http://siemens.com/swa/doc#SymptomsIndex has no ui:responseType and >> therefore cannot be called from a web service >> >> at >> org.topbraid.spin.swp.servlet.SWPServletUtil.runUncached(SWPServletUtil.java:691) >> >> at >> org.topbraid.spin.swp.servlet.SWPServletUtil.run(SWPServletUtil.java:502) >> >> at org.topbraidlive.swp.servlet.SWPServlet.run(SWPServlet.java:169) >> >> at org.topbraidlive.swp.servlet.SWPServlet.run(SWPServlet.java:150) >> >> at org.topbraidlive.swp.servlet.SWPServlet.run(SWPServlet.java:132) >> >> at org.topbraidlive.swp.servlet.SWPServlet.doGet(SWPServlet.java:61) >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) >> >> at >> org.topbraid.auth.servlet.TBAuthEnabledServlet.service(TBAuthEnabledServlet.java:38) >> >> at >> org.topbraid.eclipsex.servlet.TBHttpServlet.service(TBHttpServlet.java:125) >> >> at >> org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) >> >> at >> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) >> >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) >> >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60) >> >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) >> >> at >> org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:386) >> >> at >> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) >> >> at >> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501) >> >> at >> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229) >> >> at >> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) >> >> at >> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) >> >> at >> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) >> >> at >> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) >> >> at >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) >> >> at >> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) >> >> at org.eclipse.jetty.server.Server.handle(Server.java:370) >> >> at >> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494) >> >> at >> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971) >> >> at >> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033) >> >> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) >> >> at >> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) >> >> at >> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) >> >> at >> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667) >> >> at >> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) >> >> at >> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) >> >> at >> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) >> >> at java.lang.Thread.run(Unknown Source) >> >> >> >> On Monday, June 30, 2014 8:09:10 AM UTC-7, Jack Hodges wrote: >>> >>> I need to find a copy of 64 bit TBCME for Windows, version 4.2. I am >>> having a problem loading up a SWP page on 4.4 and it is working fine on 4.2 >>> (albeit on a Mac). Thanks. >>> >> -- >> -- You received this message because you are subscribed to the Google >> Group "TopBraid Suite Users", the topics of which include Enterprise >> Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid >> Insight, SPARQLMotion, SPARQL Web Pages and SPIN. >> To post to this group, send email to >> [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/topbraid-users?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "TopBraid Suite Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > -- You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid > Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > [email protected] <javascript:> > To unsubscribe from this group, send email to > [email protected] <javascript:> > For more options, visit this group at > http://groups.google.com/group/topbraid-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
