Skip to content

RETS 1.8 Spec compliance - and other resuscitations #14

Description

@GoogleCodeExporter
I can see everyone standing around going should I shouldn't I, someone has to 
say it.

When are we applying the 1.8 specification?
I guess this has to be addressed at some point. 

Do we have any roadmap or are you aware of any major obstacles perhaps?

+1 on the 1.5 deprecation and move to 1.7 \o/

Latest tomcat 6.0.x stands on 6.0.37 or if we take on Servlet 3.0 jsp 2.2 then 
the 7.0.x release would be 7.0.41. But that is merely the most obvious of the 
dependencies and lots has changed over the last 3 years. Do we even want to 
hold on to some of these dependencies like hibernate, king of the crop back 
then but now theres JCA and several new kids on the block. It even seems odd 
not to find lucene in the mix which has became common place on these stacks, am 
I wrong?

@Mark I picked up from your discussions that you are weary of breaking anything 
but by the look of things that might be just what we need. I can assure you 
things will break if we replace the stack but isn't that the best thing to do 
at this junction. What says yous?


LOL Yes they say when it rains it pours =) it's been quiet foc so long and I 
for one am relieved to see some action since I am new to the party. Colour me 
impressed Mark you've managed to keep tabs on things all this time. Kudos!  
Well done!

Original issue reported on code.google.com by n...@jigsoft.co.za on 4 Jul 2013 at 12:23

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions