[jira] Updated: (CXF-2959) XMLBeans - XmlBeansSchemaInitializer can't support http schema location
[ https://issues.apache.org/jira/browse/CXF-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sébastien updated CXF-2959: --- Attachment: BsbXmlBeansDataBinding.java BsbXmlBeansSchemaInitializer.java I've created a patch allowing to use an XmlCatalog before resolving schema locations. This is a sample catalog: http://www.myCompany.com/schemas/"; rewritePrefix="classpath:schemaorg_apache_xmlbeans/src/com/myCompany"/> In that way, when one of our schema is encountered, we guess that it has been included by XmlBeans in a JAR. > XMLBeans - XmlBeansSchemaInitializer can't support http schema location > --- > > Key: CXF-2959 > URL: https://issues.apache.org/jira/browse/CXF-2959 > Project: CXF > Issue Type: Improvement > Components: OtherDatabindings >Affects Versions: 2.2.6 >Reporter: Sébastien > Attachments: BsbXmlBeansDataBinding.java, > BsbXmlBeansSchemaInitializer.java > > > Currently CXF doesn't seem to support schema localized on the web. For > instance if a schema have imports like these: > http://www.myCompany.com/sf/scheduler/core"; > > schemaLocation="http://www.myCompany.com/schemas/sf/scheduler/core/scheduler-core.xsd"/> > http://www.myCompany.com/sf/execution/core"; > > schemaLocation="http://www.myCompany.com/schemas/sf/execution/core-interface/execution-core.xsd"/> > CXF tries to load the local file: > schemaorg_apache_xmlbeans/src/http://www.myCompany.com/schemas/sf/scheduler/core/scheduler-core.xsd > Moreover, it could be interesting to support an XML schema catalog avoiding > to load the schema from the net. In that way the upper URL could be mapped to > the following local file: > schemaorg_apache_xmlbeans\src\com\myCompany\sf\scheduler\core\scheduler-core.xsd -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CXF-2959) XMLBeans - XmlBeansSchemaInitializer can't support http schema location
[ https://issues.apache.org/jira/browse/CXF-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907926#action_12907926 ] Sébastien edited comment on CXF-2959 at 9/10/10 4:02 AM: - I've created a patch allowing to use an XmlCatalog before resolving schema locations. This is a sample catalog: http://www.myCompany.com/schemas/"; rewritePrefix="classpath:schemaorg_apache_xmlbeans/src/com/myCompany"/> In that way, when one of our schema is encountered, we guess that it has been included by XmlBeans in a JAR. was (Author: sebge2): I've created a patch allowing to use an XmlCatalog before resolving schema locations. This is a sample catalog: http://www.myCompany.com/schemas/"; rewritePrefix="classpath:schemaorg_apache_xmlbeans/src/com/myCompany"/> In that way, when one of our schema is encountered, we guess that it has been included by XmlBeans in a JAR. > XMLBeans - XmlBeansSchemaInitializer can't support http schema location > --- > > Key: CXF-2959 > URL: https://issues.apache.org/jira/browse/CXF-2959 > Project: CXF > Issue Type: Improvement > Components: OtherDatabindings >Affects Versions: 2.2.6 >Reporter: Sébastien > Attachments: BsbXmlBeansDataBinding.java, > BsbXmlBeansSchemaInitializer.java > > > Currently CXF doesn't seem to support schema localized on the web. For > instance if a schema have imports like these: > http://www.myCompany.com/sf/scheduler/core"; > > schemaLocation="http://www.myCompany.com/schemas/sf/scheduler/core/scheduler-core.xsd"/> > http://www.myCompany.com/sf/execution/core"; > > schemaLocation="http://www.myCompany.com/schemas/sf/execution/core-interface/execution-core.xsd"/> > CXF tries to load the local file: > schemaorg_apache_xmlbeans/src/http://www.myCompany.com/schemas/sf/scheduler/core/scheduler-core.xsd > Moreover, it could be interesting to support an XML schema catalog avoiding > to load the schema from the net. In that way the upper URL could be mapped to > the following local file: > schemaorg_apache_xmlbeans\src\com\myCompany\sf\scheduler\core\scheduler-core.xsd -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2984) Added getState() method into InterceptorChain
[ https://issues.apache.org/jira/browse/CXF-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-2984. --- Resolution: Fixed Applied patch into the trunk. > Added getState() method into InterceptorChain > -- > > Key: CXF-2984 > URL: https://issues.apache.org/jira/browse/CXF-2984 > Project: CXF > Issue Type: Improvement > Components: Core >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.3 > > > We can get the InterceptorChain from message, if we can get the stats of the > InterceptorChain, that will be great. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2982) Don't throw the SuspendedInvocationException when call the suspend() method of CXF continuation
[ https://issues.apache.org/jira/browse/CXF-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-2982. --- Resolution: Fixed Applied patch with suggestion of DanKulp Here is the mail thread[1] about it. [1]http://cxf.547215.n5.nabble.com/CXF-continuation-enhancement-td2800561.html#a2800561 > Don't throw the SuspendedInvocationException when call the suspend() method > of CXF continuation > --- > > Key: CXF-2982 > URL: https://issues.apache.org/jira/browse/CXF-2982 > Project: CXF > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.3 > > Attachments: cxf-2982.patch > > > Current CXF Continuation suspend implementation is based on throw > SuspendedInvocationException, This implementation has a shortcoming which > cannot call the other framework's async API after continuation suspend is > called as Jetty7 does. > So I introduce a flag of Message.CONTINUATION_SUSPENDED to break out current > interceptor chain as the SuspendedInvocation does, but It will make CXF > continuation API more easy to use and it supports the Jetty7 continuation or > Servlet3 suspend resume semantics. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2986) sets null instead of empty List/Set/SortedSet when value isn't in query string
[
https://issues.apache.org/jira/browse/CXF-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Cupit updated CXF-2986:
Description:
when using @QueryParam on a collection and the query param is not found in the
request, CXF sets a null collection, rather than an empty collection.
The javadocs in @DefaultValue says:
If this annotation is not used and the corresponding metadata is not present in
the request, the value will be an empty collection for List, Set or SortedSet
this seems similar to CXF-1675
Example:
@GET
@Path("/stuff")
public Response get(@QueryParam("option") Set options) { ... }
and http://localhost:8080/stuff is called (and ?option=abc is not on the query
string), options will be null, but should be an empty Set
was:
when using @QueryParam on a collection and the query param is not found in the
request, CXF sets a null collection, rather than an empty collection.
The javadocs in @DefaultValue says:
If this annotation is not used and the corresponding metadata is not present in
the request, the value will be an empty collection for List, Set or SortedSet
this seems similar to CXF-1675
Example:
@GET
@Path("/stuff")
public Response get(@QueryParam("option") Set options) { ... }
and http://localhost:8080/stuff is called (and ?option=abc is not on the query
string), options will be null, rather than an empty Set
> sets null instead of empty List/Set/SortedSet when value isn't in query string
> --
>
> Key: CXF-2986
> URL: https://issues.apache.org/jira/browse/CXF-2986
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.2.10
>Reporter: Brad Cupit
>Priority: Minor
>
> when using @QueryParam on a collection and the query param is not found in
> the request, CXF sets a null collection, rather than an empty collection.
> The javadocs in @DefaultValue says:
> If this annotation is not used and the corresponding metadata is not present
> in the request, the value will be an empty collection for List, Set or
> SortedSet
> this seems similar to CXF-1675
> Example:
> @GET
> @Path("/stuff")
> public Response get(@QueryParam("option") Set options) { ... }
> and http://localhost:8080/stuff is called (and ?option=abc is not on the
> query string), options will be null, but should be an empty Set
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2987) Add search capabilities
Add search capabilities --- Key: CXF-2987 URL: https://issues.apache.org/jira/browse/CXF-2987 Project: CXF Issue Type: Sub-task Reporter: Tomasz Oponowicz -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2987) Add search capabilities
[ https://issues.apache.org/jira/browse/CXF-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Oponowicz updated CXF-2987: -- Attachment: searching_layout_v1.png searching_layout_with_popup_v1.png Sample UI for searching feature > Add search capabilities > --- > > Key: CXF-2987 > URL: https://issues.apache.org/jira/browse/CXF-2987 > Project: CXF > Issue Type: Sub-task >Reporter: Tomasz Oponowicz > Attachments: searching_layout_v1.png, > searching_layout_with_popup_v1.png > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2988) cxf-java2ws-plugin - Generating Wrapper Bean does not produce class names based on the WebMethod annotation.
cxf-java2ws-plugin - Generating Wrapper Bean does not produce class names based on the WebMethod annotation. Key: CXF-2988 URL: https://issues.apache.org/jira/browse/CXF-2988 Project: CXF Issue Type: Bug Components: Tooling Affects Versions: 2.2.10 Environment: Running on Windows 7, with JDK 1.6, in STS Reporter: Jay Blanton I have the following method in my SEI: @WebMethod(operationName = "updateContactPoint") @WebResult(targetNamespace = "http://foo.com/model";, name = "contactPoint") ContactPoint update( @WebParam(targetNamespace = "http://foo.com/model";, name = "criteria") ContactPoint cp); And when this runs through the code generator, the request wrapper class and the response wrapper class are update and updateResponse instead of updateContactPoint and updateContactPointResponse. http://cxf.547215.n5.nabble.com/Problem-with-java2ws-and-genWrapperbean-not-honoring-operationName-td2834289.html#a2834289 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2988) cxf-java2ws-plugin - Generating Wrapper Bean does not produce class names based on the WebMethod annotation.
[ https://issues.apache.org/jira/browse/CXF-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Blanton updated CXF-2988: - Attachment: sample-model-impl.zip This project is a zip file of two maven projects because this zip file is used in another JIRA issue that I will be opening up. There is a model project and a service project. In the service project is a SEI that has the fields in question. > cxf-java2ws-plugin - Generating Wrapper Bean does not produce class names > based on the WebMethod annotation. > > > Key: CXF-2988 > URL: https://issues.apache.org/jira/browse/CXF-2988 > Project: CXF > Issue Type: Bug > Components: Tooling >Affects Versions: 2.2.10 > Environment: Running on Windows 7, with JDK 1.6, in STS >Reporter: Jay Blanton > Attachments: sample-model-impl.zip > > > I have the following method in my SEI: > @WebMethod(operationName = "updateContactPoint") > @WebResult(targetNamespace = "http://foo.com/model";, name = > "contactPoint") > ContactPoint update( > @WebParam(targetNamespace = "http://foo.com/model";, name = > "criteria") ContactPoint cp); > And when this runs through the code generator, the request wrapper class and > the response wrapper class are update and updateResponse instead of > updateContactPoint and updateContactPointResponse. > http://cxf.547215.n5.nabble.com/Problem-with-java2ws-and-genWrapperbean-not-honoring-operationName-td2834289.html#a2834289 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2989) cxf-java2ws-plugin - While running the maven plugin, the wrapper beans that are generated complain when dependencies are in another jar.
cxf-java2ws-plugin - While running the maven plugin, the wrapper beans that are
generated complain when dependencies are in another jar.
Key: CXF-2989
URL: https://issues.apache.org/jira/browse/CXF-2989
Project: CXF
Issue Type: Bug
Components: Tooling
Affects Versions: 2.2.10
Environment: Running on Windows 7, with JDK 1.6, in STS
Reporter: Jay Blanton
http://cxf.547215.n5.nabble.com/java2ws-problem-td568861.html#a2653030
So here is a quick example.
1) I have a pojo called ContactPoint with some basic information and it is to
be represented as a complexType.
2) Pom file for building this into a jar.
3) ContactPointEndpoint is a simple interface that takes in a ContactPoint and
returns it.
4) Pom file that runs java2ws to generate a wsdl, wrapper bean, and client.
This produces a similar error where the ContactPointEndpoint is in its own
project with a dependency to the jar artifact that ContactPoint exists in.
The java2ws generates code and errors, but when I am in Eclipse and look at the
generated wrapper bean and client, there are no errors and it resolves the
classes.
Any thoughts as to what this might be or what I have done wrong?
Thanks a ton!!! Jay
ContactPoint.java-
package com.foo;
import javax.xml.bind.annotation.XmlAccessType;
import javax.xml.bind.annotation.XmlAccessorType;
import javax.xml.bind.annotation.XmlType;
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(namespace = "http://foo.com/model";, name = "ContactPoint", propOrder =
{
"id", "number" })
public class ContactPoint {
/** The id. */
private Long id; // NOPMD
private String number;
public Long getId() {
return id;
}
public void setId(final Long id) {
this.id = id;
}
public String getNumber() {
return number;
}
public void setNumber(final String number) {
this.number = number;
}
}
ContactPoint pom.xml-
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
foo-model
com.foo
0.0.1-SNAPSHOT
jar
ContactPointEndpoint.java-
package com.foo;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
import javax.xml.ws.RequestWrapper;
import javax.xml.ws.ResponseWrapper;
/**
* Spring service that handles CRUD requests for People entities
*
* @generated
*/
@WebService(targetNamespace = "http://foo.com/service";)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.WRAPPED, use =
SOAPBinding.Use.LITERAL, style = SOAPBinding.Style.DOCUMENT)
public interface ContactPointEndpoint {
/**
* Save an existing People entity
*
* @generated
*/
@WebMethod
@ResponseWrapper(targetNamespace = "http://foo.com/service";)
@RequestWrapper(targetNamespace = "http://foo.com/service";)
@WebResult(targetNamespace = "http://foo.com/model";, name =
"updatedContactPoint")
ContactPoint updateContactPoint(
@WebParam(targetNamespace = "http://foo.com/model";, name =
"criteria") ContactPoint cp);
}
ContactPointEndpoint pom.xml-
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
foo-service
com.foo
0.0.1-SNAPSHOT
jar
org.apache.cxf
cxf-java2ws-plugin
2.2.9
org.apache.cxf
cxf-rt-frontend-jaxws
2.2.9
org.apache.cxf
cxf-rt-frontend-simple
2.2.9
foo-model
com.foo
[jira] Updated: (CXF-2989) cxf-java2ws-plugin - While running the maven plugin, the wrapper beans that are generated complain when dependencies are in another jar.
[
https://issues.apache.org/jira/browse/CXF-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Blanton updated CXF-2989:
-
Attachment: sample-model-impl.zip
This project is a zip file of two maven projects because this zip file is used
in another JIRA issue that I will be opening up.
There is a model project and a service project.
The model is built as a jar file and the service has a dependency on that model
jar. It is defined in the pom.xml and defined in the plugin section.
When running mvn install, the generated wrapper beans will not get compiled
because they complain that they cannot resolve model references to classes that
are in the model jar.
> cxf-java2ws-plugin - While running the maven plugin, the wrapper beans that
> are generated complain when dependencies are in another jar.
>
>
> Key: CXF-2989
> URL: https://issues.apache.org/jira/browse/CXF-2989
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 2.2.10
> Environment: Running on Windows 7, with JDK 1.6, in STS
>Reporter: Jay Blanton
> Attachments: sample-model-impl.zip
>
>
> http://cxf.547215.n5.nabble.com/java2ws-problem-td568861.html#a2653030
> So here is a quick example.
> 1) I have a pojo called ContactPoint with some basic information and it is to
> be represented as a complexType.
> 2) Pom file for building this into a jar.
> 3) ContactPointEndpoint is a simple interface that takes in a ContactPoint
> and returns it.
> 4) Pom file that runs java2ws to generate a wsdl, wrapper bean, and client.
> This produces a similar error where the ContactPointEndpoint is in its own
> project with a dependency to the jar artifact that ContactPoint exists in.
> The java2ws generates code and errors, but when I am in Eclipse and look at
> the generated wrapper bean and client, there are no errors and it resolves
> the classes.
> Any thoughts as to what this might be or what I have done wrong?
> Thanks a ton!!! Jay
> ContactPoint.java-
> package com.foo;
> import javax.xml.bind.annotation.XmlAccessType;
> import javax.xml.bind.annotation.XmlAccessorType;
> import javax.xml.bind.annotation.XmlType;
> @XmlAccessorType(XmlAccessType.FIELD)
> @XmlType(namespace = "http://foo.com/model";, name = "ContactPoint", propOrder
> = {
> "id", "number" })
> public class ContactPoint {
> /** The id. */
> private Long id; // NOPMD
> private String number;
> public Long getId() {
> return id;
> }
> public void setId(final Long id) {
> this.id = id;
> }
> public String getNumber() {
> return number;
> }
> public void setNumber(final String number) {
> this.number = number;
> }
> }
> ContactPoint pom.xml-
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> foo-model
> com.foo
> 0.0.1-SNAPSHOT
> jar
>
> ContactPointEndpoint.java-
> package com.foo;
> import javax.jws.WebMethod;
> import javax.jws.WebParam;
> import javax.jws.WebResult;
> import javax.jws.WebService;
> import javax.jws.soap.SOAPBinding;
> import javax.xml.ws.RequestWrapper;
> import javax.xml.ws.ResponseWrapper;
> /**
> * Spring service that handles CRUD requests for People entities
> *
> * @generated
> */
> @WebService(targetNamespace = "http://foo.com/service";)
> @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.WRAPPED, use =
> SOAPBinding.Use.LITERAL, style = SOAPBinding.Style.DOCUMENT)
> public interface ContactPointEndpoint {
> /**
> * Save an existing People entity
> *
> * @generated
> */
> @WebMethod
> @ResponseWrapper(targetNamespace = "http://foo.com/service";)
> @RequestWrapper(targetNamespace = "http://foo.com/service";)
> @WebResult(targetNamespace = "http://foo.com/model";, name =
> "updatedContactPoint")
> ContactPoint updateContactPoint(
> @WebParam(targetNamespace = "http://foo.com/model";, name =
> "criteria") ContactPoint cp);
> }
> ContactPointEndpoint pom.xml-
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> 4.0.0
> foo-service
> com.foo
> 0.0.1-SNAPSHOT
> jar
>
>
