To chime in: it's a really, really, bad idea for non-file URLs, as it
can violate stringprep.
For file URLs, it is an attempt to deal, with non-NFC (or NFKC)
strings in the URL failing to match the file system. However, file
system normalization is platform-dependendent. Linux does none at all,
fo
org.apache.cxf.endpoint.ServerImpl - Setting the server's publish
address to be /Extraction
Jul 31, 2010 7:54:31 AM
org.springframework.beans.GenericTypeAwarePropertyDescriptor
getWriteMethodForActualAccess
WARNING: Invalid JavaBean property 'serviceBeans' being accessed!
Ambiguous write methods f
Hi Sergey,
Referring to commit r981073, I introduce as fallows changes (include
your comments):
- Added word wrap to entry content;
- Added fancy exception handler;
- Hided security fields in "add/edit endpoint" dialog box;
- Added Customer service and client (for easy interact) to sample -
servi
What might be a similar issue
(https://jaxb.dev.java.net/issues/show_bug.cgi?id=774) came up recently on
the JAXB issue tracker, I believe the decision there was *not* to normalize;
however, I'm not sure how related Jim's simplification here is to that
issue.
Glen
Benson Margulies wrote:
>
> T
Team, our org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine uses
Eclipse's wrapper of the Jetty server (org.eclipse.jetty.server.Server)
instead of the actual object (org.mortbay.jetty.Server). Out of curiosity,
is there a reason for that--is the Eclipse wrappered version more useful or
mo
On Saturday 31 July 2010 4:02:11 pm Glen Mazza wrote:
> Team, our org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine uses
> Eclipse's wrapper of the Jetty server (org.eclipse.jetty.server.Server)
> instead of the actual object (org.mortbay.jetty.Server). Out of curiosity,
> is there a reason
