[JBoss JIRA] (JBWS-3879) Convention / implementation for interceptor and feature parameters declaration through properties
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3879:
-------------------------------------
Summary: Convention / implementation for interceptor and feature parameters declaration through properties
Key: JBWS-3879
URL: https://issues.jboss.org/browse/JBWS-3879
Project: JBoss Web Services
Issue Type: Feature Request
Components: jbossws-cxf, jbossws-integration
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.0
JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below:
||Property||Value||
|cxf.features|org.jboss.ws.cxf.DelegateFeature.foo, org.apache.cxf.DelegateFeature.bar|
|org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.GZIPFeature|
|org.jboss.ws.cxf.DelegateFeature.foo.threshold|0|
|org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.RMFeature|
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3879) Convention / implementation for interceptor and feature parameters declaration through properties
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3879?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3879:
----------------------------------
Description:
JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below:
||Property||Value||
|cxf.features|org.jboss.ws.cxf.DelegateFeature.foo, org.apache.cxf.DelegateFeature.bar|
|org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.GZIPFeature|
|org.jboss.ws.cxf.DelegateFeature.foo.threshold|0|
|org.jboss.ws.cxf.DelegateFeature.bar.class|org.apache.cxf.feature.RMFeature|
was:
JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below:
||Property||Value||
|cxf.features|org.jboss.ws.cxf.DelegateFeature.foo, org.apache.cxf.DelegateFeature.bar|
|org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.GZIPFeature|
|org.jboss.ws.cxf.DelegateFeature.foo.threshold|0|
|org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.RMFeature|
> Convention / implementation for interceptor and feature parameters declaration through properties
> -------------------------------------------------------------------------------------------------
>
> Key: JBWS-3879
> URL: https://issues.jboss.org/browse/JBWS-3879
> Project: JBoss Web Services
> Issue Type: Feature Request
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0
>
>
> JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below:
> ||Property||Value||
> |cxf.features|org.jboss.ws.cxf.DelegateFeature.foo, org.apache.cxf.DelegateFeature.bar|
> |org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.GZIPFeature|
> |org.jboss.ws.cxf.DelegateFeature.foo.threshold|0|
> |org.jboss.ws.cxf.DelegateFeature.bar.class|org.apache.cxf.feature.RMFeature|
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3878) Deal with javadoc warnings
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3878:
-------------------------------------
Summary: Deal with javadoc warnings
Key: JBWS-3878
URL: https://issues.jboss.org/browse/JBWS-3878
Project: JBoss Web Services
Issue Type: Task
Components: jbossws-cxf
Reporter: Alessio Soldano
Fix For: jbossws-cxf-5.0
Fix all javadoc warnings printed out when building jbossws components (especially with JDK8)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3877) EndpointRegistry SPI cleanup
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3877:
-------------------------------------
Summary: EndpointRegistry SPI cleanup
Key: JBWS-3877
URL: https://issues.jboss.org/browse/JBWS-3877
Project: JBoss Web Services
Issue Type: Task
Components: jbossws-cxf, jbossws-integration
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.0
Currently all implementors of EndpointRegistry are internally baked by the MSC ServiceRegistry. This means we can remove the register/unregister methods from the EndpointRegistry SPI and drop the other implementations of EndpointRegistry living in JBossWS-Common, which are not needed anymore.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3876) Build failures with JDK 1.8
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3876?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3876:
----------------------------------
Description:
Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
( from http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-21563... )
{quote}
Area: Tools / javac
Synopsis
Interfaces need to be present when compiling against their implementations
Description
When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
{quote}
in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
was:
Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
from *http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html#A999387*
{quote}
Area: Tools / javac
Synopsis
Interfaces need to be present when compiling against their implementations
Description
When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
{quote}
in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
> Build failures with JDK 1.8
> ---------------------------
>
> Key: JBWS-3876
> URL: https://issues.jboss.org/browse/JBWS-3876
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0
>
>
> Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
> ( from http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-21563... )
> {quote}
> Area: Tools / javac
> Synopsis
> Interfaces need to be present when compiling against their implementations
> Description
> When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
> {quote}
> in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3876) Build failures with JDK 1.8
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3876?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3876:
----------------------------------
Description:
Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
from *http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html#A999387*
{quote}
Area: Tools / javac
Synopsis
Interfaces need to be present when compiling against their implementations
Description
When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
{quote}
in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
was:
Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
*from http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-21563...
{quote}
Area: Tools / javac
Synopsis
Interfaces need to be present when compiling against their implementations
Description
When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
{quote}
in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
> Build failures with JDK 1.8
> ---------------------------
>
> Key: JBWS-3876
> URL: https://issues.jboss.org/browse/JBWS-3876
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0
>
>
> Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
> from *http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html#A999387*
> {quote}
> Area: Tools / javac
> Synopsis
> Interfaces need to be present when compiling against their implementations
> Description
> When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
> {quote}
> in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3876) Build failures with JDK 1.8
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3876?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3876:
----------------------------------
Description:
Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
*from http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-21563...
{quote}
Area: Tools / javac
Synopsis
Interfaces need to be present when compiling against their implementations
Description
When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
{quote}
in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
was:
Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
{quote}
Area: Tools / javac
Synopsis
Interfaces need to be present when compiling against their implementations
Description
When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
{quote}
in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
> Build failures with JDK 1.8
> ---------------------------
>
> Key: JBWS-3876
> URL: https://issues.jboss.org/browse/JBWS-3876
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0
>
>
> Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
> *from http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-21563...
> {quote}
> Area: Tools / javac
> Synopsis
> Interfaces need to be present when compiling against their implementations
> Description
> When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
> {quote}
> in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3876) Build failures with JDK 1.8
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3876?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3876:
----------------------------------
Description:
Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
{quote}
Area: Tools / javac
Synopsis
Interfaces need to be present when compiling against their implementations
Description
When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
{quote}
in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
> Build failures with JDK 1.8
> ---------------------------
>
> Key: JBWS-3876
> URL: https://issues.jboss.org/browse/JBWS-3876
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0
>
>
> Using JDK 1.8, JBossWS API and SPI builds fail with javadoc errors. JBossWS-CXF build fails because of new compile requirement on interfaces availability:
> {quote}
> Area: Tools / javac
> Synopsis
> Interfaces need to be present when compiling against their implementations
> Description
> When compiling a class against another class implementing an interface which is defined in yet another class file, such class file (where interface is defined) must be available in the class path used by javac during compilation. This is a new requirement as of JDK 8 - a failure to do so will result in a compilation error
> {quote}
> in our it's org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec artifact which is not exported by PicketBox that is causing problems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (JBWS-3876) SPI build failure with JDK 1.8
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3876:
-------------------------------------
Summary: SPI build failure with JDK 1.8
Key: JBWS-3876
URL: https://issues.jboss.org/browse/JBWS-3876
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf, jbossws-integration
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.0
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months