Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 4 May 2012 09:40:48 +0000 (UTC)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <6689059.26330.1336124448996.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1436216626.15189.1335911093943.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CXF-4281) uribuilder from null?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268226#comment-13268226 ] 

Sergey Beryozkin commented on CXF-4281:
---------------------------------------

> UriBuilder.fromUri("http://foo:1234").scheme(null).build().getRawSchemeSpecificPart() != null

I don't even know what that is supposed to produce, but UriBuilder does allow it.  
I can imagine using UriBuilder.scheme() in combination with UriBuilder.schemeSpecificPart, when building a uri from scratch. 

What do you think

UriBuilder.fromUri("http://foo:1234").scheme(null).build()

should produce ? I'd consider throwing IllegalArgumentException in cases where the scheme and schemeSpecificParts have already been initialized from the existing URI
                
> uribuilder from null?
> ---------------------
>
>                 Key: CXF-4281
>                 URL: https://issues.apache.org/jira/browse/CXF-4281
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Romain Manni-Bucau
>
> in tomee/openejb we need to patch the uri builder to be able to satisfied some cases (UriBuilder.fromPath(null) for instance)
> here is the patched builder working for us: http://svn.apache.org/repos/asf/openejb/trunk/openejb/server/openejb-cxf-rs/src/main/java/org/apache/openejb/server/cxf/rs/OpenEJBRuntimeDelegateImpl.java
> any way to get it merged with cxf?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira