[JBoss JIRA] (JBWS-3873) Web Services can't inherit a JDK8 default method
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3873?page=com.atlassian.jira.plugin.... ]
Jim Ma edited comment on JBWS-3873 at 4/15/15 2:27 AM:
-------------------------------------------------------
PR is sent for this issue : https://github.com/wildfly/wildfly-core/pull/622
It requires wildfly-core 1.0.0.Beta5 to include this fix.
was (Author: jim.ma):
PR is sent for this issue : https://github.com/wildfly/wildfly-core/pull/622
It requires 1.0.0.Beta5 to include this fix.
> Web Services can't inherit a JDK8 default method
> ------------------------------------------------
>
> Key: JBWS-3873
> URL: https://issues.jboss.org/browse/JBWS-3873
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Affects Versions: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta3
> Environment: JDK8
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Fix For: jbossws-cxf-5.0
>
> Attachments: jdk8-ws-defaultmethod.zip
>
>
> Having simple SEI and POJO webservice with JDK8 feature - default method for interface:
> {code}
> @WebService
> public interface GreeterSEI {
> default public String sayHello() {
> return "Hello, Default";
> }
> }
>
> //----------------------------------------------------------
>
> @WebService
> public class GreeterImpl implements GreeterSEI {}
> {code}
> When you try to execute sayHello method:
> {code}
> Service greeterService = Service.create(...);
> GreeterSEI g = greeterService.getPort(GreeterSEI.class);
>
> Assert.assertEquals("JBoss", greeter.sayHello());
> {code}
> You will get a message-less IllegalStateException on server.
> Expected results:
> no exception, default implementation of method is invoked.
> Or if this is considered unsupported usage, the exception should be more descriptive (ie.: "Method xx not found on implementation class")
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[JBoss JIRA] (JBWS-3873) Web Services can't inherit a JDK8 default method
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3873?page=com.atlassian.jira.plugin.... ]
Jim Ma commented on JBWS-3873:
------------------------------
PR is sent for this issue : https://github.com/wildfly/wildfly-core/pull/622
It requires 1.0.0.Beta5 to include this fix.
> Web Services can't inherit a JDK8 default method
> ------------------------------------------------
>
> Key: JBWS-3873
> URL: https://issues.jboss.org/browse/JBWS-3873
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Affects Versions: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta3
> Environment: JDK8
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Fix For: jbossws-cxf-5.0
>
> Attachments: jdk8-ws-defaultmethod.zip
>
>
> Having simple SEI and POJO webservice with JDK8 feature - default method for interface:
> {code}
> @WebService
> public interface GreeterSEI {
> default public String sayHello() {
> return "Hello, Default";
> }
> }
>
> //----------------------------------------------------------
>
> @WebService
> public class GreeterImpl implements GreeterSEI {}
> {code}
> When you try to execute sayHello method:
> {code}
> Service greeterService = Service.create(...);
> GreeterSEI g = greeterService.getPort(GreeterSEI.class);
>
> Assert.assertEquals("JBoss", greeter.sayHello());
> {code}
> You will get a message-less IllegalStateException on server.
> Expected results:
> no exception, default implementation of method is invoked.
> Or if this is considered unsupported usage, the exception should be more descriptive (ie.: "Method xx not found on implementation class")
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[JBoss JIRA] (JBWS-3899) Print warning for misconfigured contract-first endpoints
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-3899?page=com.atlassian.jira.plugin.... ]
R Searls updated JBWS-3899:
---------------------------
Assignee: R Searls
> Print warning for misconfigured contract-first endpoints
> --------------------------------------------------------
>
> Key: JBWS-3899
> URL: https://issues.jboss.org/browse/JBWS-3899
> Project: JBoss Web Services
> Issue Type: Enhancement
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: R Searls
> Priority: Minor
> Fix For: jbossws-cxf-5.0
>
>
> When user provides misconfigured contract-first endpoints as below, the stack silently ignore the request of using the specified contract and generates the wsdl (code-first).
> {noformat}
> @Stateless
> @WebService(portName = "SimpleEchoPort",wsdlLocation = "META-INF/wsdl/Echo.wsdl")
> public class SimpleEcho {
> ...
> }
> {noformat}
> (notice there's no serviceName specified, hence the stack won't know which port/service to use from the contract)
> We should likely print a warning in this scenario, asking the user if he really wants a contract-first endpoint.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[JBoss JIRA] (JBWS-3888) metadata-complete setting ignored
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-3888?page=com.atlassian.jira.plugin.... ]
R Searls commented on JBWS-3888:
--------------------------------
On evaluation I find this can not be an issue in JBossWS. For 3 reasons I
recommend this be forwarded to the undertow team for evaluation. One, "metadata-complete"
is an attribute of "web-app" in the web.xml file. Undertow handles the processing of
that information. Two, annotations @WebServlet, @WebFilter, and @WebListener are
to be ignored as well. I don't think JBossWS/CXF directly uses these or acts on them
but web apps do. Three, the sample code provided by Amit was determine not to correctly
show the issue. I would think there is a test in undertow to check this scenario.
The Java Servlet 3.0 / 3.1 Specification states.
"If metadata-complete is set to "true", the deployment tool only examines the
web.xml file and must ignore annotations such as @WebServlet, @WebFilter, and
@WebListener present in the class files of the application, and must also ignore
any web-fragment.xml descriptor packaged in a jar file in WEB-INF/lib. If the
metadata-complete attribute is not specified or is set to "false", the
deployment tool must examine the class files and web-fragment.xml files for
metadata,as previously specified."
> metadata-complete setting ignored
> ---------------------------------
>
> Key: JBWS-3888
> URL: https://issues.jboss.org/browse/JBWS-3888
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: R Searls
> Fix For: jbossws-cxf-5.0
>
>
> See https://developer.jboss.org/message/921776 . We need to check if metadata-complete setting is being properly considered and if it's not, fix it.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[JBoss JIRA] (JBWS-3873) Web Services can't inherit a JDK8 default method
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3873?page=com.atlassian.jira.plugin.... ]
Jim Ma updated JBWS-3873:
-------------------------
Assignee: Jim Ma
> Web Services can't inherit a JDK8 default method
> ------------------------------------------------
>
> Key: JBWS-3873
> URL: https://issues.jboss.org/browse/JBWS-3873
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Affects Versions: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta3
> Environment: JDK8
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Fix For: jbossws-cxf-5.0
>
> Attachments: jdk8-ws-defaultmethod.zip
>
>
> Having simple SEI and POJO webservice with JDK8 feature - default method for interface:
> {code}
> @WebService
> public interface GreeterSEI {
> default public String sayHello() {
> return "Hello, Default";
> }
> }
>
> //----------------------------------------------------------
>
> @WebService
> public class GreeterImpl implements GreeterSEI {}
> {code}
> When you try to execute sayHello method:
> {code}
> Service greeterService = Service.create(...);
> GreeterSEI g = greeterService.getPort(GreeterSEI.class);
>
> Assert.assertEquals("JBoss", greeter.sayHello());
> {code}
> You will get a message-less IllegalStateException on server.
> Expected results:
> no exception, default implementation of method is invoked.
> Or if this is considered unsupported usage, the exception should be more descriptive (ie.: "Method xx not found on implementation class")
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years
[JBoss JIRA] (JBWS-3863) @MTOM.enabled is not honored
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBWS-3863?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBWS-3863:
-----------------------------------------------
Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1178234|https://bugzilla.redhat.com/show_bug.cgi?id=1178234] from NEW to POST
> @MTOM.enabled is not honored
> ----------------------------
>
> Key: JBWS-3863
> URL: https://issues.jboss.org/browse/JBWS-3863
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.3.1
> Reporter: Kyle Lape
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0.0.Beta3
>
> Attachments: jbws3863.diff
>
>
> If you put {{@MTOM(enabled=false)}} on an endpoint, it will still send responses as if MTOM is enabled. If you remove the annotation altogether, the endpoint will end up inlining the content as you'd expect. This does not occur if you run CXF standalone -- only when using the JBossWS integration layer in JBoss.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years