Hello, I was thinking about have a generic backend (models) that returns XML, this XML is then transformed in to XHTML, SOAP, RSS depending on what is required by the client, using XSLT templates. Can SOAP be constructed in this way? Or do I need I need specific fuctionality to deliver web services? I know of Rails web services which now seem to be defunct in place of the more RESTful way of doing things... But I already have a requirment for XML output so I was thinking of going down the above route. Any pitfalls? Many thanks, K. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Kris wrote:> Hello, I was thinking about have a generic backend (models) that returns > XML, this XML is then transformed in to XHTML, SOAP, RSS depending on > what is required by the client, using XSLT templates. Can SOAP be > constructed in this way? Or do I need I need specific fuctionality to > deliver web services? > > I know of Rails web services which now seem to be defunct in place of > the more RESTful way of doing things... But I already have a requirment > for XML output so I was thinking of going down the above route. > > Any pitfalls? > > Many thanks, K.Is this more suited for asking on the Ruby forum, since it is not exactly Rails specific? Maybe it does not fit in with the Rails way of doing things. I would however modify/extend the basic Rails setup to allow XSLT and a XML backend... -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
You could do things this way, but it''s not clear to me why you wouldn''t just use Rails'' Web services. As I understand it, AWS isn''t going to disappear - it just may turn into an add-on rather than remaining part of the core Rails package. For those (apparently few) of us who use it, AWS is a really powerful, elegant way of working; REST makes it simpler to create simple XML documents, but the effort involved in turning those documents into SOAP or XML-RPC is pretty painful if you code it yourself. Regards Dave M. On 30/10/06, Kris <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > Hello, I was thinking about have a generic backend (models) that returns > XML, this XML is then transformed in to XHTML, SOAP, RSS depending on > what is required by the client, using XSLT templates. Can SOAP be > constructed in this way? Or do I need I need specific fuctionality to > deliver web services? > > I know of Rails web services which now seem to be defunct in place of > the more RESTful way of doing things... But I already have a requirment > for XML output so I was thinking of going down the above route. > > Any pitfalls? > > Many thanks, K. > > -- > Posted via http://www.ruby-forum.com/. > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
You can certainly use rails to generate XML instead of XHTML. We did exactly that, and had an after_filter that ran it through Xalan to turn it into XHTML. No idea about whether you can do it with soap though, I don''t know enough about the details of SOAP. ActionWebService is pretty easy to work with though and you should be able to share almost all of the code. Fred -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---