[jira] [Commented] (FEDIZ-15) Support the publish of the WS-Federation Metadata document
[ https://issues.apache.org/jira/browse/FEDIZ-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294245#comment-13294245 ] Alex Sarafian commented on FEDIZ-15: On the WIF/ADFS world there are two kinds of automation for the configuration of both passive and active profiles. First FedUtil is used to consume the Metadata of the STS (ADFS) from a url like this https://sts_host/federationmetadata/2007-06/federationmetadata.xml. The result of this action is a web.config file properly modified to consume the sts and a FederationMetadata.xml that can be used from the STS to configure the Relying Party as a second step. It is my understanding that the first step (FederationMetadata.xml export from the STS) is not yet supported but consuming a Service provider's FederationMetadata.xml to configure the STS is. If I am correct then yes I'm referring to the IDP/STS to export the WS-Federation Metadata documents. > Support the publish of the WS-Federation Metadata document > -- > > Key: FEDIZ-15 > URL: https://issues.apache.org/jira/browse/FEDIZ-15 > Project: CXF-Fediz > Issue Type: Wish >Reporter: Alex Sarafian > > It would be really good if Fediz supporter WS-Federation Metadata documents > like ADFS does. > It is really helpful for the .NET stack using the Windows Identity Foundation > Federation Utility (FedUtil) for configuration of the WIF stack for Passive > and Active profiles. -- 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-4374) JSONProvider blocks namespace prefixes set in package-info.java
Sergey Beryozkin created CXF-4374: - Summary: JSONProvider blocks namespace prefixes set in package-info.java Key: CXF-4374 URL: https://issues.apache.org/jira/browse/CXF-4374 Project: CXF Issue Type: Bug Components: JAX-RS Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Priority: Minor Fix For: 2.5.5, 2.6.2, 2.7.0 -- 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] [Resolved] (CXF-4374) JSONProvider blocks namespace prefixes set in package-info.java
[ https://issues.apache.org/jira/browse/CXF-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-4374. --- Resolution: Fixed > JSONProvider blocks namespace prefixes set in package-info.java > --- > > Key: CXF-4374 > URL: https://issues.apache.org/jira/browse/CXF-4374 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin >Priority: Minor > Fix For: 2.5.5, 2.6.2, 2.7.0 > > -- 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-4375) Archetypes are broken
Lars Heinemann created CXF-4375:
---
Summary: Archetypes are broken
Key: CXF-4375
URL: https://issues.apache.org/jira/browse/CXF-4375
Project: CXF
Issue Type: Bug
Affects Versions: 2.6.1
Reporter: Lars Heinemann
The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some
of the contained xml files (not only the pom.xml) are invalid as they contain
comment lines like
{noformat}
## this is a sample comment line
{noformat}
which are not surrounded by a xml comment tag and also the notation of property
placeholders in the pom files are sometimes written in a wrong way. ( for
example: $version instead of ${version} )
--
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-4376) STS encryptIssuedToken with the SymmetricKey KeyType does not work
Colm O hEigeartaigh created CXF-4376: Summary: STS encryptIssuedToken with the SymmetricKey KeyType does not work Key: CXF-4376 URL: https://issues.apache.org/jira/browse/CXF-4376 Project: CXF Issue Type: Bug Components: Services Affects Versions: 2.6.1, 2.5.4 Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.5.5, 2.6.2 The scenario where the STS is configured to encrypt an IssuedToken does not work when the client sends a SymmetricKey KeyType request. This is because the STS encrypts the entropy to the service provider, and the STSClient can't decrypt them as a result. This task also involves a system test for this issue. -- 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] [Resolved] (CXF-4376) STS encryptIssuedToken with the SymmetricKey KeyType does not work
[ https://issues.apache.org/jira/browse/CXF-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CXF-4376. -- Resolution: Fixed > STS encryptIssuedToken with the SymmetricKey KeyType does not work > -- > > Key: CXF-4376 > URL: https://issues.apache.org/jira/browse/CXF-4376 > Project: CXF > Issue Type: Bug > Components: Services >Affects Versions: 2.5.4, 2.6.1 >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 2.5.5, 2.6.2 > > > The scenario where the STS is configured to encrypt an IssuedToken does not > work when the client sends a SymmetricKey KeyType request. This is because > the STS encrypts the entropy to the service provider, and the STSClient can't > decrypt them as a result. This task also involves a system test for this > issue. -- 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] [Assigned] (CXF-4375) Archetypes are broken
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza reassigned CXF-4375:
---
Assignee: Glen Mazza
> Archetypes are broken
> -
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some
> of the contained xml files (not only the pom.xml) are invalid as they contain
> comment lines like
> {noformat}
> ## this is a sample comment line
> {noformat}
> which are not surrounded by a xml comment tag and also the notation of
> property placeholders in the pom files are sometimes written in a wrong way.
> ( for example: $version instead of ${version} )
--
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-4375) Archetypes are broken
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294491#comment-13294491
]
Glen Mazza commented on CXF-4375:
-
Hi, I need more information as I can't find the problem you're referring to
(I'm doing a grep on the pom.xml's and it's returning nothing):
gmazza@gmazza-work:~/.../CXF-TRNK/maven-plugins/archetypes$ grep -r "sample
comment" . --include "*.xml"
returns nothing; I switch "sample comment" to "name" and get tons of results.
Here's the 2.6.x branch:
http://svn.apache.org/viewvc/cxf/branches/2.6.x-fixes/maven-plugins/archetypes/
Could you please point me to a pom.xml file that has "## this is a sample
comment line" *and* a pom.xml file that uses $version instead of ${version}?
Thanks!
> Archetypes are broken
> -
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some
> of the contained xml files (not only the pom.xml) are invalid as they contain
> comment lines like
> {noformat}
> ## this is a sample comment line
> {noformat}
> which are not surrounded by a xml comment tag and also the notation of
> property placeholders in the pom files are sometimes written in a wrong way.
> ( for example: $version instead of ${version} )
--
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-4375) Archetypes are broken
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294496#comment-13294496
]
Glen Mazza commented on CXF-4375:
-
On second thought, you may be referring *not* to the archetype source code
itself but the code it generates. To help me replicate, what are the steps
you're following (command-line archetype generation or with m2eclipse?) And
what's your Maven (and if you have it) maven-archetype version? Thanks!
> Archetypes are broken
> -
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some
> of the contained xml files (not only the pom.xml) are invalid as they contain
> comment lines like
> {noformat}
> ## this is a sample comment line
> {noformat}
> which are not surrounded by a xml comment tag and also the notation of
> property placeholders in the pom files are sometimes written in a wrong way.
> ( for example: $version instead of ${version} )
--
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-3722) Generic interface and Implementation
[
https://issues.apache.org/jira/browse/CXF-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294530#comment-13294530
]
Sergey Beryozkin commented on CXF-3722:
---
create an adapter such as
{code:java}
public class NamedObjectAdapter extends XmlAdapter {
public Book marshal(NamedObject v) throws Exception {
return (Book)v;
}
public NamedObject unmarshal(Book v) throws Exception {
return v;
}
}
{code}
you may need to tweak it a bit for it to handle different NamedObjects and add
link to it from NamedObject:
{code:java}
@XmlType
@XmlJavaTypeAdapter(NamedObjectAdapter.class)
public interface NamedObject {
@XmlAttribute
public String getName();
}
{code}
that should work
> Generic interface and Implementation
>
>
> Key: CXF-3722
> URL: https://issues.apache.org/jira/browse/CXF-3722
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2
> Environment: CXF 2.2.6
> JAVA 6
> Windows XP
> Tomcat 6
> Code First
>Reporter: Deboschère Tony
>Assignee: Daniel Kulp
>Priority: Minor
> Fix For: Invalid
>
>
> I ve createad a Generic interface, let say IGenericInterface MyAbstracTypeOne, TYPE2 extends MyAbstractTypeTwo>
> In this interface are some méthode like :
> public TYPE getTypeFromType2(TYPE2);
> In another interface I extends IGenericInterface
> and add some specific methods
> ex :
> @WebService
> ISpecificInterface extends IgenericInterface {
> @WebMethod
> public MySubTypeOne getTest();
> }
> When I implement ISpecificInterface in an implementation class, then add the
> @Webservice @WebResult and other @WebParam and launch my server
> I do see a web service with two methods in the wsdl
> getTest and getTypeFromType2.
> But the second method returns xml corresponding to the abstractType
> MyAbstracTypeOne and not MySubTypeOne
> PS : I launch the webservice serverside via :
> Object webServiceImpl = webServiceClass.newInstance();
> Endpoint endpoint = Endpoint.create(webServiceImpl);
> endpoint.publish("/" + name);
--
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] [Resolved] (CXF-3799) Update to Jetty 8.0.1
[ https://issues.apache.org/jira/browse/CXF-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3799. -- Resolution: Fixed Fix Version/s: 2.7.0 Assignee: Daniel Kulp We've dropped Java5 for CXF 2.7. I've now updated trunk to use Jetty 8 by default. > Update to Jetty 8.0.1 > - > > Key: CXF-3799 > URL: https://issues.apache.org/jira/browse/CXF-3799 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.3.6, 2.4.2 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) > Maven home: C:\Java\apache-maven-3.0.3\bin\.. > Java version: 1.6.0_24, vendor: Sun Microsystems Inc. > Java home: C:\Program Files\Java\jdk1.6.0_24\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Travis Schneeberger >Assignee: Daniel Kulp > Fix For: 2.7.0 > > > Update to Jetty 8.0.1. -- 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-4375) Archetypes are broken
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294558#comment-13294558
]
Lars Heinemann commented on CXF-4375:
-
Hi Glen,
the ## lines do mostly contain license stuff. I only wrote "this is a sample
comment line" as symbol here.
Currently trying to fix that issue so I can deliver a patch to you. The
comments are easily removed but the other
issue with the property placeholders is more complicated as you use resource
filtering for having always the current
cxf release version in one dependency (${project.version}).
If you for example try to generate a module out of one of the two archetypes
from the shell specifying the artifactId, groupId and version
of the new module then you will recognize that those values don't get included
in the generated pom. It will still say $artifactId etc.
You also can't correct the notation to ${artifactId} for example as it will
otherwise replace those in the archetype resources pom and so you
have again the wrong data in the pom.
I am currently trying to create a patch for that. Will attach it here when
finished.
> Archetypes are broken
> -
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some
> of the contained xml files (not only the pom.xml) are invalid as they contain
> comment lines like
> {noformat}
> ## this is a sample comment line
> {noformat}
> which are not surrounded by a xml comment tag and also the notation of
> property placeholders in the pom files are sometimes written in a wrong way.
> ( for example: $version instead of ${version} )
--
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-4375) Archetypes are broken
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294567#comment-13294567
]
Glen Mazza commented on CXF-4375:
-
Cool, patches most welcome. :)
> Archetypes are broken
> -
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some
> of the contained xml files (not only the pom.xml) are invalid as they contain
> comment lines like
> {noformat}
> ## this is a sample comment line
> {noformat}
> which are not surrounded by a xml comment tag and also the notation of
> property placeholders in the pom files are sometimes written in a wrong way.
> ( for example: $version instead of ${version} )
--
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-4377) Allow CXF "servlets" to be used as Filters
Daniel Kulp created CXF-4377: Summary: Allow CXF "servlets" to be used as Filters Key: CXF-4377 URL: https://issues.apache.org/jira/browse/CXF-4377 Project: CXF Issue Type: Improvement Reporter: Daniel Kulp Assignee: Daniel Kulp Fix For: 2.7.0 To allow services to be deployed "anywhere" within a context (instead of /services/*) and co-exist with other servlets and such, it would be good if CXF could provide a Filter in addition to the current Servlets. -- 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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294602#comment-13294602
]
Lars Heinemann commented on CXF-4375:
-
Hi Glen,
I figured out that one of the issues is not a problem on CXF side but on ours.
But still the invalid XML files should be fixed.
Apologize for the confusion. :)
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann updated CXF-4375:
Attachment: archetype.patch
Attached patch for trunk but should be fixed on 2.5 and 2.6 if possible as well.
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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] [Resolved] (CXF-4377) Allow CXF "servlets" to be used as Filters
[ https://issues.apache.org/jira/browse/CXF-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4377. -- Resolution: Fixed > Allow CXF "servlets" to be used as Filters > -- > > Key: CXF-4377 > URL: https://issues.apache.org/jira/browse/CXF-4377 > Project: CXF > Issue Type: Improvement >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 2.7.0 > > > To allow services to be deployed "anywhere" within a context (instead of > /services/*) and co-exist with other servlets and such, it would be good if > CXF could provide a Filter in addition to the current Servlets. -- 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] [Comment Edited] (CXF-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294558#comment-13294558
]
Lars Heinemann edited comment on CXF-4375 at 6/13/12 6:16 PM:
--
Hi Glen,
the ## lines do mostly contain license stuff. I only wrote "this is a sample
comment line" as symbol here.
Currently trying to fix that issue so I can deliver a patch to you.
I am currently trying to create a patch for that. Will attach it here when
finished.
was (Author: lhein):
Hi Glen,
the ## lines do mostly contain license stuff. I only wrote "this is a sample
comment line" as symbol here.
Currently trying to fix that issue so I can deliver a patch to you. The
comments are easily removed but the other
issue with the property placeholders is more complicated as you use resource
filtering for having always the current
cxf release version in one dependency (${project.version}).
If you for example try to generate a module out of one of the two archetypes
from the shell specifying the artifactId, groupId and version
of the new module then you will recognize that those values don't get included
in the generated pom. It will still say $artifactId etc.
You also can't correct the notation to ${artifactId} for example as it will
otherwise replace those in the archetype resources pom and so you
have again the wrong data in the pom.
I am currently trying to create a patch for that. Will attach it here when
finished.
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann updated CXF-4375:
Description:
The archetype for cxf-jaxws-javafirst contain invalid xml files as they contain
comment lines like
{noformat}
##
{noformat}
which are not surrounded by a xml comment tag.
was:
The archetypes for cxf-jaxrs-service and cxf-jaxws-javafirst are broken. Some
of the contained xml files (not only the pom.xml) are invalid as they contain
comment lines like
{noformat}
## this is a sample comment line
{noformat}
which are not surrounded by a xml comment tag and also the notation of property
placeholders in the pom files are sometimes written in a wrong way. ( for
example: $version instead of ${version} )
Affects Version/s: 2.5.4
Summary: Invalid XML files in the archetype cxf-jaxws-javafirst
(was: Archetypes are broken)
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann updated CXF-4375:
Affects Version/s: 2.7.0
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1, 2.7.0
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294633#comment-13294633
]
Glen Mazza commented on CXF-4375:
-
Thanks, I'll check it next.
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1, 2.7.0
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294634#comment-13294634
]
Daniel Kulp commented on CXF-4375:
--
Lars,
I'm failing to reproduce this issue. If I run:
{code}
mvn archetype:generate
{code}
(maven 3.0.4)
Filter to cxf-jaxws-javafirst.
Select version 2.6.1
Set groupId to "com.dkulp", artifactId to cxf-test, version to 1.0-SNAPSHOT,
and defaults for rest, it generates a proper project with usable pom.xml,
web.xml, and beans.xml.
I'm against your patch as that would result in the apache header being written
out into the resulting beans.xml and web.xml, which would be wrong.
Can I get COMPLETE steps to reproduce the issue?
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1, 2.7.0
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294657#comment-13294657
]
Lars Heinemann commented on CXF-4375:
-
Hi Daniel,
mvn archetype:create seems to work fine. Though those files are not valid xml
files and in my environment using m2e they make problems.
So my proposal is to fully remove the license text (we also did that in
ServiceMix archetypes). It makes really no sense to have those
license texts if they are not wanted in the created files and if they
invalidate the xml.
What do you think?
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1, 2.7.0
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294662#comment-13294662
]
Daniel Kulp commented on CXF-4375:
--
So this is a bug in m2e only? Is a bug logged with them?
Per Apache policy, any files that have creative content SHOULD have that
license header. Thus, it would really be against Apache policy to remove them.
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1, 2.7.0
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294663#comment-13294663
]
Daniel Kulp commented on CXF-4375:
--
Actually, I just tried with m2e in my eclipse install and it also worked fine
there. beans.xml and web.xml come out completely fine and usable without any
license header or anything.
Thus, I really need instructions on how to reproduce this.
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1, 2.7.0
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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-4378) Refactor HttpURLConnection out of JAX-RS AbstractClient.setResponseBuilder()
Chris Dolan created CXF-4378:
Summary: Refactor HttpURLConnection out of JAX-RS
AbstractClient.setResponseBuilder()
Key: CXF-4378
URL: https://issues.apache.org/jira/browse/CXF-4378
Project: CXF
Issue Type: Improvement
Components: JAX-RS
Affects Versions: 2.6.1
Reporter: Chris Dolan
Priority: Minor
First off, I realized this is a bit of a wacky request. My use case may be an
abomination, but my specific request is modest. :-)
My current project experimentally bridges JAX-RS request/response over a JMS
bus. Services are declared with JAX-RS annotations on Java interfaces. Clients
are created with JAXRSClientFactory, but with a proprietary URL schema instead
of "http://"; and I have registered a proprietary Conduit implementation instead
of the usual HTTPConduit.
So far, so good. The request side of the JAX-RS client code is actually very
nicely abstracted from the conduit, so there's no assumption about HTTP. On the
response side, however, the AbstractClient.setResponseBuilder() method assumes
that there must be an HttpURLConnection attached to the message. If the message
already has its own InputStream (mine does) then this URLConnection is used
just to get the header values back out.
To work around this, I had to make a hack like this in my Conduit
implementation:
{code}
MockHttpURLConnection conn = new MockHttpURLConnection(url);
conn.putHeader("Yada", "yada-yada-yada");
message.put(HTTPConduit.KEY_HTTP_CONNECTION, conn);
{code}
where MockHttpURLConnection basically just wraps a Map for header values.
I request that AbstractClient be altered so it expects either a
KEY_HTTP_CONNECTION or a new type of KEY_HTTP_HEADERS, which is perhaps a
simple MultiMap or an actual Headers instance.
--
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-4378) Refactor HttpURLConnection out of JAX-RS AbstractClient.setResponseBuilder()
[
https://issues.apache.org/jira/browse/CXF-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294788#comment-13294788
]
Daniel Kulp commented on CXF-4378:
--
Aren't the headers already in the Message via the Message.PROTOCOL_HEADERS key?
> Refactor HttpURLConnection out of JAX-RS AbstractClient.setResponseBuilder()
>
>
> Key: CXF-4378
> URL: https://issues.apache.org/jira/browse/CXF-4378
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 2.6.1
>Reporter: Chris Dolan
>Priority: Minor
>
> First off, I realized this is a bit of a wacky request. My use case may be an
> abomination, but my specific request is modest. :-)
> My current project experimentally bridges JAX-RS request/response over a JMS
> bus. Services are declared with JAX-RS annotations on Java interfaces.
> Clients are created with JAXRSClientFactory, but with a proprietary URL
> schema instead of "http://"; and I have registered a proprietary Conduit
> implementation instead of the usual HTTPConduit.
> So far, so good. The request side of the JAX-RS client code is actually very
> nicely abstracted from the conduit, so there's no assumption about HTTP. On
> the response side, however, the AbstractClient.setResponseBuilder() method
> assumes that there must be an HttpURLConnection attached to the message. If
> the message already has its own InputStream (mine does) then this
> URLConnection is used just to get the header values back out.
> To work around this, I had to make a hack like this in my Conduit
> implementation:
> {code}
> MockHttpURLConnection conn = new MockHttpURLConnection(url);
> conn.putHeader("Yada", "yada-yada-yada");
> message.put(HTTPConduit.KEY_HTTP_CONNECTION, conn);
> {code}
> where MockHttpURLConnection basically just wraps a Map for header values.
> I request that AbstractClient be altered so it expects either a
> KEY_HTTP_CONNECTION or a new type of KEY_HTTP_HEADERS, which is perhaps a
> simple MultiMap or an actual Headers instance.
--
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-4378) Refactor HttpURLConnection out of JAX-RS AbstractClient.setResponseBuilder()
[
https://issues.apache.org/jira/browse/CXF-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294791#comment-13294791
]
Chris Dolan commented on CXF-4378:
--
Daniel, perhaps but the setResponseBuilder method looks like this:
{code}
HttpURLConnection conn =
(HttpURLConnection)outMessage.get(HTTPConduit.KEY_HTTP_CONNECTION);
if (conn == null) {
throw new ClientWebApplicationException("HTTP Connection is null");
}
...
for (Map.Entry> entry : conn.getHeaderFields().entrySet())
{
...
}
{code}
So, the HttpURLConnection is currently unavoidable.
> Refactor HttpURLConnection out of JAX-RS AbstractClient.setResponseBuilder()
>
>
> Key: CXF-4378
> URL: https://issues.apache.org/jira/browse/CXF-4378
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 2.6.1
>Reporter: Chris Dolan
>Priority: Minor
>
> First off, I realized this is a bit of a wacky request. My use case may be an
> abomination, but my specific request is modest. :-)
> My current project experimentally bridges JAX-RS request/response over a JMS
> bus. Services are declared with JAX-RS annotations on Java interfaces.
> Clients are created with JAXRSClientFactory, but with a proprietary URL
> schema instead of "http://"; and I have registered a proprietary Conduit
> implementation instead of the usual HTTPConduit.
> So far, so good. The request side of the JAX-RS client code is actually very
> nicely abstracted from the conduit, so there's no assumption about HTTP. On
> the response side, however, the AbstractClient.setResponseBuilder() method
> assumes that there must be an HttpURLConnection attached to the message. If
> the message already has its own InputStream (mine does) then this
> URLConnection is used just to get the header values back out.
> To work around this, I had to make a hack like this in my Conduit
> implementation:
> {code}
> MockHttpURLConnection conn = new MockHttpURLConnection(url);
> conn.putHeader("Yada", "yada-yada-yada");
> message.put(HTTPConduit.KEY_HTTP_CONNECTION, conn);
> {code}
> where MockHttpURLConnection basically just wraps a Map for header values.
> I request that AbstractClient be altered so it expects either a
> KEY_HTTP_CONNECTION or a new type of KEY_HTTP_HEADERS, which is perhaps a
> simple MultiMap or an actual Headers instance.
--
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] [Closed] (CXF-4375) Invalid XML files in the archetype cxf-jaxws-javafirst
[
https://issues.apache.org/jira/browse/CXF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann closed CXF-4375.
---
Resolution: Not A Problem
Found a suitable way to work around those invalid header comments. No need to
fix that in cxf code any longer.
> Invalid XML files in the archetype cxf-jaxws-javafirst
> --
>
> Key: CXF-4375
> URL: https://issues.apache.org/jira/browse/CXF-4375
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.5.4, 2.6.1, 2.7.0
>Reporter: Lars Heinemann
>Assignee: Glen Mazza
> Labels: archetype, cxf
> Attachments: archetype.patch
>
>
> The archetype for cxf-jaxws-javafirst contain invalid xml files as they
> contain comment lines like
> {noformat}
> ##
> {noformat}
> which are not surrounded by a xml comment tag.
--
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
