Hi Sergey,
Adding Dynamic-Import: * would likely resolve the issue. It also makes any
package/class name resolution a lot slower because all the OSGI bundles
will basically now be a gigantic class path. I would not be inclined to go
down this route.
I've uploaded a new version to CXF-3859. I've u
Hi Benson
On 02/12/11 22:16, Benson Margulies wrote:
On Fri, Dec 2, 2011 at 4:45 PM, Sergey Beryozkin wrote:
Hi Benson
I think we should get rid of that Class level annotation that you
introduced. It is not secure enough - the path and verb values it lists -
they can not serve as a guarantee
On Fri, Dec 2, 2011 at 4:45 PM, Sergey Beryozkin wrote:
> Hi Benson
>
> I think we should get rid of that Class level annotation that you
> introduced. It is not secure enough - the path and verb values it lists -
> they can not serve as a guarantee that the actual resource handler exists.
> They
On 02/12/11 19:56, Daniel Kulp wrote:
This is probably long overdue
I added an .htaccess file to the root of the website which will redirect the
CXF schema namespaces to the appropriate schema files on the live site.
For example, if you point your browser at:
http://cxf.apache.org/core
(
This is probably long overdue
I added an .htaccess file to the root of the website which will redirect the
CXF schema namespaces to the appropriate schema files on the live site.
For example, if you point your browser at:
http://cxf.apache.org/core
(the namespace for the cxf core obj