[jira] [Assigned] (CXF-4278) Karaf features.xml for CXF wants to load EhCache for cxf-sts-ws and cxf-ws-security
[
https://issues.apache.org/jira/browse/CXF-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CXF-4278:
-
Assignee: Freeman Fang
> Karaf features.xml for CXF wants to load EhCache for cxf-sts-ws and
> cxf-ws-security
> ---
>
> Key: CXF-4278
> URL: https://issues.apache.org/jira/browse/CXF-4278
> Project: CXF
> Issue Type: Bug
> Components: OSGi
>Affects Versions: 2.6, 2.6.1
> Environment: Apache Karaf 2.2.6 + Felix OSGi Container
>Reporter: Scott Parkerson
>Assignee: Freeman Fang
>Priority: Minor
>
> According to the [migration
> guide|http://cxf.apache.org/docs/26-migration-guide.html]:
> {quote}
> EhCache is now a compile time dependency of the cxf-rt-ws-security module to
> support caching and replay detection. It can be safely excluded downstream,
> at the expense of weakening the caching support.
> {quote}
> If that is the case, then why force a user to load a specific version of
> EhCache in the features.xml file for CXF? This breaks cases where, for
> instance, a user wants to use an EhCache compatible with old-school Hibernate
> (3.3.2) which requires net.sf.ehcache;version=[1.2.3, 2.0.0).
> Furthermore, it appears that there is no version bounding on the optional
> import of net.sf.ehcache in cxf-ws-security, so theoretically, my
> already-loaded version of EhCache should work just fine with CXF. :D
> Note: Setting this to a minor issue as it can be worked around by installing
> the features with {{--no-clean}} in Karaf and then removing the EhCache
> provided by CXF's features.
--
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
[jira] [Commented] (CXF-4281) uribuilder from null?
[
https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268219#comment-13268219
]
Sergey Beryozkin commented on CXF-4281:
---
The following test works for me locally, we have few of tests like this one:
{code:java}
@Test
public void testFromEncodedDuplicateVar3() {
String expected = "http://localhost:8080/1/2/3/1";;
URI uri = UriBuilder.fromPath("http://localhost:8080";)
.path("/{a}/{b}/{c}/{a}")
.buildFromEncoded("1", "2", "3");
assertEquals(expected, uri.toString());
}
{code}
Can you get a breakpoint inside UriBuilderImpl.doPath(...) ? You should hit a
block specifically checking if a given path represents a URI and if yes then it
gelegates to a uri handler. May be also ping me on IRC ?
> 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[
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
[jira] [Commented] (CXF-4281) uribuilder from null?
[
https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268232#comment-13268232
]
Romain Manni-Bucau commented on CXF-4281:
-
I think it should produce a getRawSchemeSpecificPart() == null
@Test
public void testFromEncodedDuplicateVar3() {
String expected = "http://localhost:8080/1/2/3/1";;
URI uri = UriBuilder.fromPath("http://localhost:8080";)
.path("/{a}/{b}/{c}/{a}")
.buildFromEncoded("1", "2", "3");
assertEquals(expected, uri.toString());
}
doesn't pass for me. I'm using the snapshot.
i'm on irc (rmb/rmannibucau) if you want
> 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[
https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268249#comment-13268249
]
Sergey Beryozkin commented on CXF-4281:
---
Lets see how CXF 2.5.x build reacts to
http://svn.apache.org/viewvc?rev=1333860&view=rev :-)
As for the
'UriBuilder.fromUri("http://foo:1234";).scheme(null).build().getRawSchemeSpecificPart()
!= null', I think that setting the scheme to 'null' should only affect the
'http' part from the original URI which would leave the scheme specific part as
'foo:1234'.
Write now I can see CXF printing "//localhost:8080" in this case which is
useless. I think the right outcome should be either "http://foo:1234"; where
UriBuilder detects that scheme specific part is set but the actual scheme is
not and thus defaults to 'http' or throw IllegalArgumentException at
scheme(null)
> 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
[jira] [Issue Comment Edited] (CXF-4281) uribuilder from null?
[
https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268249#comment-13268249
]
Sergey Beryozkin edited comment on CXF-4281 at 5/4/12 10:36 AM:
Lets see how CXF 2.5.x build reacts to
http://svn.apache.org/viewvc?rev=1333860&view=rev :-)
As for the
'UriBuilder.fromUri("http://foo:1234";).scheme(null).build().getRawSchemeSpecificPart()
!= null', I think that setting the scheme to 'null' should only affect the
'http' part from the original URI which would leave the scheme specific part as
'foo:1234'.
Right now I can see CXF printing "//localhost:8080" in this case which is
useless. I think the right outcome should be either "http://foo:1234"; where
UriBuilder detects that scheme specific part is set but the actual scheme is
not and thus defaults to 'http' or throw IllegalArgumentException at
scheme(null)
was (Author: sergey_beryozkin):
Lets see how CXF 2.5.x build reacts to
http://svn.apache.org/viewvc?rev=1333860&view=rev :-)
As for the
'UriBuilder.fromUri("http://foo:1234";).scheme(null).build().getRawSchemeSpecificPart()
!= null', I think that setting the scheme to 'null' should only affect the
'http' part from the original URI which would leave the scheme specific part as
'foo:1234'.
Write now I can see CXF printing "//localhost:8080" in this case which is
useless. I think the right outcome should be either "http://foo:1234"; where
UriBuilder detects that scheme specific part is set but the actual scheme is
not and thus defaults to 'http' or throw IllegalArgumentException at
scheme(null)
> 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
[jira] [Created] (FEDIZ-1) WS-Federation Metadata document published at runtime in RP
Oliver Wulff created FEDIZ-1: Summary: WS-Federation Metadata document published at runtime in RP Key: FEDIZ-1 URL: https://issues.apache.org/jira/browse/FEDIZ-1 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff plugins/core should be enhanced to generate a WS-Federation Metadata document -- 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
[jira] [Created] (FEDIZ-2) Support encrypted tokens in plugin
Oliver Wulff created FEDIZ-2: Summary: Support encrypted tokens in plugin Key: FEDIZ-2 URL: https://issues.apache.org/jira/browse/FEDIZ-2 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff -- 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
[jira] [Created] (FEDIZ-3) Support the role "Resource IDP" in IDP
Oliver Wulff created FEDIZ-3: Summary: Support the role "Resource IDP" in IDP Key: FEDIZ-3 URL: https://issues.apache.org/jira/browse/FEDIZ-3 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff -- 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
[jira] [Created] (FEDIZ-4) Support SAML token with Holder-Of-Key SubjectConfirmationMethod
Oliver Wulff created FEDIZ-4: Summary: Support SAML token with Holder-Of-Key SubjectConfirmationMethod Key: FEDIZ-4 URL: https://issues.apache.org/jira/browse/FEDIZ-4 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff -- 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
[jira] [Created] (FEDIZ-5) Provide adapter for Jetty
Oliver Wulff created FEDIZ-5: Summary: Provide adapter for Jetty Key: FEDIZ-5 URL: https://issues.apache.org/jira/browse/FEDIZ-5 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff -- 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
[jira] [Created] (FEDIZ-8) Add support for OAuth
Oliver Wulff created FEDIZ-8: Summary: Add support for OAuth Key: FEDIZ-8 URL: https://issues.apache.org/jira/browse/FEDIZ-8 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff -- 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
[jira] [Created] (FEDIZ-6) Provide adapter for JBoss
Oliver Wulff created FEDIZ-6: Summary: Provide adapter for JBoss Key: FEDIZ-6 URL: https://issues.apache.org/jira/browse/FEDIZ-6 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff -- 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
[jira] [Created] (FEDIZ-7) Add support for SAML-P
Oliver Wulff created FEDIZ-7: Summary: Add support for SAML-P Key: FEDIZ-7 URL: https://issues.apache.org/jira/browse/FEDIZ-7 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff -- 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
[jira] [Created] (FEDIZ-9) Add plugin for CXF
Oliver Wulff created FEDIZ-9: Summary: Add plugin for CXF Key: FEDIZ-9 URL: https://issues.apache.org/jira/browse/FEDIZ-9 Project: CXF-Fediz Issue Type: New Feature Reporter: Oliver Wulff Provide thread local storage for token and STS Client callback handler which is required for on-behalf-of STS use case. Support CXF JAX-RS -- 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
[jira] [Updated] (FEDIZ-9) Provide plugin for CXF
[ https://issues.apache.org/jira/browse/FEDIZ-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-9: - Summary: Provide plugin for CXF (was: Add plugin for CXF) > Provide plugin for CXF > -- > > Key: FEDIZ-9 > URL: https://issues.apache.org/jira/browse/FEDIZ-9 > Project: CXF-Fediz > Issue Type: New Feature >Reporter: Oliver Wulff > > Provide thread local storage for token and STS Client callback handler which > is required for on-behalf-of STS use case. > Support CXF JAX-RS -- 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
[jira] [Updated] (FEDIZ-3) Support the role "Resource IDP" in IDP
[ https://issues.apache.org/jira/browse/FEDIZ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-3: - Component/s: IDP > Support the role "Resource IDP" in IDP > -- > > Key: FEDIZ-3 > URL: https://issues.apache.org/jira/browse/FEDIZ-3 > Project: CXF-Fediz > Issue Type: New Feature > Components: IDP >Reporter: Oliver Wulff > -- 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
[jira] [Updated] (FEDIZ-1) WS-Federation Metadata document published at runtime in RP
[ https://issues.apache.org/jira/browse/FEDIZ-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-1: - Component/s: Plugin > WS-Federation Metadata document published at runtime in RP > -- > > Key: FEDIZ-1 > URL: https://issues.apache.org/jira/browse/FEDIZ-1 > Project: CXF-Fediz > Issue Type: New Feature > Components: Plugin >Reporter: Oliver Wulff > > plugins/core should be enhanced to generate a WS-Federation Metadata document -- 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
[jira] [Updated] (FEDIZ-2) Support encrypted tokens in plugin
[ https://issues.apache.org/jira/browse/FEDIZ-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-2: - Component/s: Plugin IDP > Support encrypted tokens in plugin > -- > > Key: FEDIZ-2 > URL: https://issues.apache.org/jira/browse/FEDIZ-2 > Project: CXF-Fediz > Issue Type: New Feature > Components: IDP, Plugin >Reporter: Oliver Wulff > -- 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
[jira] [Updated] (FEDIZ-4) Support SAML token with Holder-Of-Key SubjectConfirmationMethod
[ https://issues.apache.org/jira/browse/FEDIZ-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-4: - Component/s: Plugin IDP > Support SAML token with Holder-Of-Key SubjectConfirmationMethod > --- > > Key: FEDIZ-4 > URL: https://issues.apache.org/jira/browse/FEDIZ-4 > Project: CXF-Fediz > Issue Type: New Feature > Components: IDP, Plugin >Reporter: Oliver Wulff > -- 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
[jira] [Updated] (FEDIZ-5) Provide adapter for Jetty
[ https://issues.apache.org/jira/browse/FEDIZ-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-5: - Component/s: Plugin > Provide adapter for Jetty > - > > Key: FEDIZ-5 > URL: https://issues.apache.org/jira/browse/FEDIZ-5 > Project: CXF-Fediz > Issue Type: New Feature > Components: Plugin >Reporter: Oliver Wulff > -- 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
[jira] [Updated] (FEDIZ-9) Provide plugin for CXF
[ https://issues.apache.org/jira/browse/FEDIZ-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-9: - Component/s: Plugin > Provide plugin for CXF > -- > > Key: FEDIZ-9 > URL: https://issues.apache.org/jira/browse/FEDIZ-9 > Project: CXF-Fediz > Issue Type: New Feature > Components: Plugin >Reporter: Oliver Wulff > > Provide thread local storage for token and STS Client callback handler which > is required for on-behalf-of STS use case. > Support CXF JAX-RS -- 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
[jira] [Updated] (FEDIZ-6) Provide adapter for JBoss
[ https://issues.apache.org/jira/browse/FEDIZ-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-6: - Component/s: Plugin > Provide adapter for JBoss > - > > Key: FEDIZ-6 > URL: https://issues.apache.org/jira/browse/FEDIZ-6 > Project: CXF-Fediz > Issue Type: New Feature > Components: Plugin >Reporter: Oliver Wulff > -- 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[
https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268265#comment-13268265
]
Glen Mazza commented on CXF-4281:
-
Testing with Jersey 1.12:
testing:
System.out.println(UriBuilder.fromUri("http://foo:1234";).scheme(null).build().toString())"
returns //foo:1234
testing:
System.out.println(UriBuilder.fromPath("").replacePath("http://localhost:8080";).path("/{a}/{b}/{c}/{a}").buildFromEncoded("1",
"2", "3").toString());
returns http://localhost:8080/1/2/3/1
> 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268268#comment-13268268 ] Sergey Beryozkin commented on CXF-4281: --- Hi Glen, thanks for the help, next time I'll run Jersey tests myself :-) So, the way Jersey manages scheme(null) is consistent with the way CXF does it so I guess we can not worry about it. Minor update to the way CXF handles UriBuilder.replacePath when the http based URIs are provided is on the way > 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268272#comment-13268272 ] Romain Manni-Bucau commented on CXF-4281: - @Glen what does return jersey for uri.getRawSchemeSpecificPart() when scheme(null) was called? > 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268284#comment-13268284 ] Sergey Beryozkin commented on CXF-4281: --- Romain - it would return the same value you see with CXF given that UriBuilder.build produces 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268298#comment-13268298 ] Glen Mazza commented on CXF-4281: - Romain, to do your own testing on Jersey, very simple, just download the Jersey samples (http://maven.java.net/service/local/artifact/maven/redirect?r=releases&g=com.sun.jersey.samples&a=jersey-samples&v=1.12&e=zip&c=project), navigate to the helloworld sample and alter its Main.getBaseURI() method adding in a System.out.println(UriBuilder...whatever you want.toString()) and then run mvn compile exec:java from that sample (as stated in its README). You'll see the results from a terminal window. > 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268339#comment-13268339 ] Sergey Beryozkin commented on CXF-4281: --- UriBuilder.replacePath now delegates to the uri handler when it sees absolute http uris > 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268355#comment-13268355 ] Romain Manni-Bucau commented on CXF-4281: - doesnt work with jersey too for me > 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268497#comment-13268497 ] Romain Manni-Bucau commented on CXF-4281: - just tried the trunk it is really better but i got one issue: UriBuilder.fromPath(null) doesn't throw any exception. It should throw a IllegalArgumentException, no? > 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
[jira] [Created] (CXF-4288) SecureAnnotationsInterceptor maps roles only based on method name
Daniel Kulp created CXF-4288: Summary: SecureAnnotationsInterceptor maps roles only based on method name Key: CXF-4288 URL: https://issues.apache.org/jira/browse/CXF-4288 Project: CXF Issue Type: Bug Components: Core Affects Versions: 2.6 Reporter: Daniel Kulp Assignee: Daniel Kulp Fix For: 2.6.1 The SecureAnnotationsInterceptor maps the roles into the method map only based on the method name. If the class in question is using overloaded methods with different roles for each method, this can result in the wrong roles being applied to the authorization. The map needs to take into account the params/returns as well. -- 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
[jira] [Updated] (CXF-4277) STSClient does not use returned KeyInfo size when creating a secret key
[ https://issues.apache.org/jira/browse/CXF-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CXF-4277: - Description: The STSClient does not use the returned KeyInfo size when creating a secret key. This means that it creates an incorrect secret key in the case where an STS rejects the submitted KeySize, and returns a different KeySize to the client. (was: The STSClient does not use the returned KeyInfo size when creating a secret key. This means that it creates an incorrect secret key in the case where an STS rejects the submitted KeySize, and returns a different KeySize to the client.) Fix Version/s: 2.3.11 > STSClient does not use returned KeyInfo size when creating a secret key > --- > > Key: CXF-4277 > URL: https://issues.apache.org/jira/browse/CXF-4277 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 2.4.7, 2.5.3, 2.6 >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11 > > > The STSClient does not use the returned KeyInfo size when creating a secret > key. This means that it creates an incorrect secret key in the case where an > STS rejects the submitted KeySize, and returns a different KeySize to the > client. -- 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
[jira] [Updated] (CXF-4288) SecureAnnotationsInterceptor maps roles only based on method name
[ https://issues.apache.org/jira/browse/CXF-4288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp updated CXF-4288: - Description: The SecureAnnotationsInterceptor maps the roles into the method map only based on the method name. If the class in question is using overloaded methods with different roles for each method, this can result in the wrong roles being applied to the authorization. The map needs to take into account the params/returns as well. (was: The SecureAnnotationsInterceptor maps the roles into the method map only based on the method name. If the class in question is using overloaded methods with different roles for each method, this can result in the wrong roles being applied to the authorization. The map needs to take into account the params/returns as well.) Affects Version/s: 2.3.10 2.4.7 2.5.3 Fix Version/s: 2.3.11 2.4.8 2.5.4 > SecureAnnotationsInterceptor maps roles only based on method name > - > > Key: CXF-4288 > URL: https://issues.apache.org/jira/browse/CXF-4288 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 2.3.10, 2.4.7, 2.5.3, 2.6 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11 > > > The SecureAnnotationsInterceptor maps the roles into the method map only > based on the method name. If the class in question is using overloaded > methods with different roles for each method, this can result in the wrong > roles being applied to the authorization. The map needs to take into > account the params/returns as well. -- 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268694#comment-13268694 ] Sergey Beryozkin commented on CXF-4281: --- Hi, I think > UriBuilder.fromPath(null) doesn't throw any exception. It should throw a > IllegalArgumentException, no? Yes - which actually highlights the problem with the API implementation that you use, recall you mentioning URIBuilder.fromPath() calls replacePath() [1] on the newly created UriBuilder, where supplying 'null' is perfectly valid. Effectively we are talking about the API in question breaking the 'negative' part of the UriBuilder.fromPath contract [1] http://docs.oracle.com/javaee/6/api/javax/ws/rs/core/UriBuilder.html#replacePath%28java.lang.String%29 > 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268777#comment-13268777 ] Romain Manni-Bucau commented on CXF-4281: - i'll open a geronimo jira > 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
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268779#comment-13268779 ] Romain Manni-Bucau commented on CXF-4281: - opened GERONIMO-6344 > 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
