> -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: 06 March 2013 06:52
> I could recreate the invalid xlink:href problems without joining. > With joining, I couldn't recreate the problem. It would be faster with > joining too. > I guess it's about time I make joining the default behaviour. > Also, I think the problem with your filters should be solved with > joining. > Please let me know otherwise. I didn't have joining enabled so I tried enabling it (now using 2.3-RC1) and can confirm this fixes both the xlink:href problem and getting the correct results with my filters (for WFS 1.1.0 requests). The documentation notes some restrictions on capabilities with joining set. These don't affect anything I'm currently doing but I don't know whether they affect anyone else. So I don't know whether an issue should still be raised to get correct behaviour without joining set or instead to make joining always be set. Marcus This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
