[jira] [Resolved] (CXF-4266) Cannot add CXF Karaf Features due to typo in features.xml
[
https://issues.apache.org/jira/browse/CXF-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CXF-4266.
---
Resolution: Fixed
Fix Version/s: 2.6.1
Just updated the feature file with thanks to
> Cannot add CXF Karaf Features due to typo in features.xml
> -
>
> Key: CXF-4266
> URL: https://issues.apache.org/jira/browse/CXF-4266
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.6
> Environment: Building Karaf 2.2.6 derivative with Apache CXF 2.6.0.
>Reporter: Scott Parkerson
>Assignee: Willem Jiang
> Labels: features, karaf
> Fix For: 2.6.1
>
>
> {noformat}
> [INFO] Copying bundle:
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.oauthprovider:jar:20100527_1
> .
> .
> .
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:features-maven-plugin:2.2.6:add-features-to-repo
> (add-features-to-repo) on project com.ateb.myx.kernel: Can't resolve bundle
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.oauthprovider:jar:20100527_1:
> Could not find artifact
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.oauthprovider:jar:20100527_1
> in ateb-maven-releases (http://maven.ateb.com/archiva/repository/internal)
> {noformat}
> I think the correct artifact is
> [org.apache.servicemix.bundles:org.apache.servicemix.bundles.oauth-provider|http://search.maven.org/#artifactdetails%7Corg.apache.servicemix.bundles%7Corg.apache.servicemix.bundles.oauth-provider%7C20100527_1%7Cbundle].
--
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-4267) A NPE in AttatchmentDataSource could be guarded.
Stefan E. Funk created CXF-4267:
---
Summary: A NPE in AttatchmentDataSource could be guarded.
Key: CXF-4267
URL: https://issues.apache.org/jira/browse/CXF-4267
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 2.5.2
Reporter: Stefan E. Funk
Priority: Trivial
If I do a release a hold on a DataSource like this:
void release(DataSource ds) throws IOException {
AttachmentDataSource ads = getAttachmentDataSource(ds);
if (ads != null) {
// tell attachment to hold the temporary file;
ads.release();
}
}
and the ads.isCached() is false, I get a NPE. I know that without a hold()
there should be no release(), but sometimes it may happen anyway (e.g. in
finally blocks), and then it would not be necesarry to check isCahced() before.
--
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
Re: [jira] [Resolved] (CXF-4240) CXF WSN cannot run offline in Karaf
Hi Dan,
thank's for your support.
I guess there might be a second option for enabling offline capabilities.
We tried to solve the issue by patching the component which is using WSN (e.g.
Talend SAM Server).
(1) We placed the catalog into the consuming project
(2) Ran a rebuild
(3) The OSGi bundle class loading seemed to work fine.
I am not quite sure which way is the better (fixing the WSN using component or
embedding a Require-Bundle statement) way of resolving this issue, I can only
say, both work.
Many greets and kind regards,
Christoph
On 24.04.2012, at 23:00, Daniel Kulp (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/CXF-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Daniel Kulp resolved CXF-4240.
> --
>
> Resolution: Fixed
>Fix Version/s: 2.5.4
> 2.6.1
> Assignee: Daniel Kulp
>
>> CXF WSN cannot run offline in Karaf
>> ---
>>
>>Key: CXF-4240
>>URL: https://issues.apache.org/jira/browse/CXF-4240
>>Project: CXF
>> Issue Type: Bug
>> Components: Services
>> Affects Versions: 2.5.2, 2.6
>>Environment: jdk 1.6, Karaf 2.2.5
>> Reporter: Zsolt Beothy-Elo
>> Assignee: Daniel Kulp
>>Fix For: 2.6.1, 2.5.4
>>
>>
>> I am running cxf within Karaf. If am without connection to Maven Central and
>> try to install and start the feature cxf-wsn I get the following exception:
>> {noformat}
>> org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to
>> intialize bean createPullPoint
>> at
>> org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:638)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:724)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintRepository.createInstance(BlueprintRepository.java:198)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintRepository.create(BlueprintRepository.java:137)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.ServiceRecipe.createRecipe(ServiceRecipe.java:370)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:278)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:248)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.ServiceRecipe.internalCreate(ServiceRecipe.java:140)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:64)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:219)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:147)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:640)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:331)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:227)[10:org.apache.aries.blueprint:0.3.1]
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_31]
>> at
>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_31]
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_31]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[:1.6.0_31]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[:1.6.0_31]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_31]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPo
[jira] [Commented] (CXF-4251) Error when calling methods with the similar parameters
[
https://issues.apache.org/jira/browse/CXF-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262516#comment-13262516
]
Jury Litvinoff commented on CXF-4251:
-
Yes!
@WebService(name="Xxx")
@SOAPBinding(style=SOAPBinding.Style.DOCUMENT, parameterStyle =
SOAPBinding.ParameterStyle.BARE)
public interface Xx {
...
> Error when calling methods with the similar parameters
> --
>
> Key: CXF-4251
> URL: https://issues.apache.org/jira/browse/CXF-4251
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 2.6
> Environment: Tomcat 6.0.26
>Reporter: Jury Litvinoff
>Priority: Critical
> Labels: similar_parameters
> Fix For: NeedMoreInfo
>
>
> Two methods with similar parameters - Example code:
> @WebMethod(operationName="saveCosts", action="costs")
> public String saveCosts(@WebParam(name = "way")String way,
> @WebParam(name = "item")String item,
> @WebParam(name = "project")String proj,
> @WebParam(name = "period")String period,
> @WebParam(name = "val")String val);
>
> @WebMethod(operationName="saveBalance", action="balance")
> public String saveBalance(@WebParam(name = "way")String way,
> @WebParam(name = "item")String item,
> @WebParam(name = "project")String proj,
> @WebParam(name = "period")String period,
> @WebParam(name = "val")String val);
> When I run "saveCosts", Web service transfers control to another method -
> "saveBalance"!!!
> Why???
--
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-4267) A NPE in AttatchmentDataSource could be guarded.
[
https://issues.apache.org/jira/browse/CXF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp reassigned CXF-4267:
Assignee: Daniel Kulp
> A NPE in AttatchmentDataSource could be guarded.
>
>
> Key: CXF-4267
> URL: https://issues.apache.org/jira/browse/CXF-4267
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 2.5.2
>Reporter: Stefan E. Funk
>Assignee: Daniel Kulp
>Priority: Trivial
>
> If I do a release a hold on a DataSource like this:
> void release(DataSource ds) throws IOException {
> AttachmentDataSource ads = getAttachmentDataSource(ds);
> if (ads != null) {
> // tell attachment to hold the temporary file;
> ads.release();
> }
> }
> and the ads.isCached() is false, I get a NPE. I know that without a hold()
> there should be no release(), but sometimes it may happen anyway (e.g. in
> finally blocks), and then it would not be necesarry to check isCahced()
> before.
--
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-4118) org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testResourceWithEPR breaks when run offline
[ https://issues.apache.org/jira/browse/CXF-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp reassigned CXF-4118: Assignee: Daniel Kulp > org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testResourceWithEPR > breaks when run offline > > > Key: CXF-4118 > URL: https://issues.apache.org/jira/browse/CXF-4118 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.5.3 > Environment: OpenSuse Linux 11.4 32 bit, Java(TM) SE Runtime > Environment (build 1.6.0_23-b05) >Reporter: Dennis Sosnoski >Assignee: Daniel Kulp >Priority: Minor > Labels: build-failure, offline > > NPE after SourceGenerator.createCodeModel() call to compiler.bind() returns > null. -- 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-4268) WADL 2 Java doesn't respect catalogs
Daniel Kulp created CXF-4268: Summary: WADL 2 Java doesn't respect catalogs Key: CXF-4268 URL: https://issues.apache.org/jira/browse/CXF-4268 Project: CXF Issue Type: Bug Components: Tooling Affects Versions: 2.6, 2.5.3 Reporter: Daniel Kulp Assignee: Daniel Kulp Fix For: 2.6.1, 2.5.4 The WADL 2 java tools does not allow use of the catalogs for resolving schemas. -- 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-4268) WADL 2 Java doesn't respect catalogs
[ https://issues.apache.org/jira/browse/CXF-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4268. -- Resolution: Fixed Fix Version/s: 2.4.8 > WADL 2 Java doesn't respect catalogs > > > Key: CXF-4268 > URL: https://issues.apache.org/jira/browse/CXF-4268 > Project: CXF > Issue Type: Bug > Components: Tooling >Affects Versions: 2.5.3, 2.6 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 2.6.1, 2.5.4, 2.4.8 > > > The WADL 2 java tools does not allow use of the catalogs for resolving > schemas. -- 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-4267) A NPE in AttatchmentDataSource could be guarded.
[
https://issues.apache.org/jira/browse/CXF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-4267.
--
Resolution: Fixed
Fix Version/s: 2.3.11
2.4.8
2.5.4
2.6.1
> A NPE in AttatchmentDataSource could be guarded.
>
>
> Key: CXF-4267
> URL: https://issues.apache.org/jira/browse/CXF-4267
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 2.5.2
>Reporter: Stefan E. Funk
>Assignee: Daniel Kulp
>Priority: Trivial
> Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11
>
>
> If I do a release a hold on a DataSource like this:
> void release(DataSource ds) throws IOException {
> AttachmentDataSource ads = getAttachmentDataSource(ds);
> if (ads != null) {
> // tell attachment to hold the temporary file;
> ads.release();
> }
> }
> and the ads.isCached() is false, I get a NPE. I know that without a hold()
> there should be no release(), but sometimes it may happen anyway (e.g. in
> finally blocks), and then it would not be necesarry to check isCahced()
> before.
--
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-4118) org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testResourceWithEPR breaks when run offline
[ https://issues.apache.org/jira/browse/CXF-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4118. -- Resolution: Fixed Fix Version/s: 2.5.4 2.6.1 > org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testResourceWithEPR > breaks when run offline > > > Key: CXF-4118 > URL: https://issues.apache.org/jira/browse/CXF-4118 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 2.5.3 > Environment: OpenSuse Linux 11.4 32 bit, Java(TM) SE Runtime > Environment (build 1.6.0_23-b05) >Reporter: Dennis Sosnoski >Assignee: Daniel Kulp >Priority: Minor > Labels: build-failure, offline > Fix For: 2.6.1, 2.5.4 > > > NPE after SourceGenerator.createCodeModel() call to compiler.bind() returns > null. -- 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-4267) A NPE in AttatchmentDataSource could be guarded.
[
https://issues.apache.org/jira/browse/CXF-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262745#comment-13262745
]
Stefan E. Funk commented on CXF-4267:
-
Boy, are you guys fast! Glad we switched from Axis2 to CXF :-)
> A NPE in AttatchmentDataSource could be guarded.
>
>
> Key: CXF-4267
> URL: https://issues.apache.org/jira/browse/CXF-4267
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 2.5.2
>Reporter: Stefan E. Funk
>Assignee: Daniel Kulp
>Priority: Trivial
> Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11
>
>
> If I do a release a hold on a DataSource like this:
> void release(DataSource ds) throws IOException {
> AttachmentDataSource ads = getAttachmentDataSource(ds);
> if (ads != null) {
> // tell attachment to hold the temporary file;
> ads.release();
> }
> }
> and the ads.isCached() is false, I get a NPE. I know that without a hold()
> there should be no release(), but sometimes it may happen anyway (e.g. in
> finally blocks), and then it would not be necesarry to check isCahced()
> before.
--
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-4269) In some cases, the javascript client will not output the ns declaration for wrapper element of an rpc/lit method
Daniel Kulp created CXF-4269: Summary: In some cases, the javascript client will not output the ns declaration for wrapper element of an rpc/lit method Key: CXF-4269 URL: https://issues.apache.org/jira/browse/CXF-4269 Project: CXF Issue Type: Bug Components: JavaScript Client Affects Versions: 2.6, 2.5.3, 2.4.7 Reporter: Daniel Kulp Assignee: Daniel Kulp Fix For: 2.6.1, 2.5.4, 2.4.8 The javascript generator collects the namespace prefix for the RPC wrapper element AFTER the list of prefixes has been written out. Thus, if something else hasn't happened to add the namespace to the list, the resulting XML is invalid. -- 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-4269) In some cases, the javascript client will not output the ns declaration for wrapper element of an rpc/lit method
[ https://issues.apache.org/jira/browse/CXF-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4269. -- Resolution: Fixed Fix Version/s: 2.3.11 > In some cases, the javascript client will not output the ns declaration for > wrapper element of an rpc/lit method > > > Key: CXF-4269 > URL: https://issues.apache.org/jira/browse/CXF-4269 > Project: CXF > Issue Type: Bug > Components: JavaScript Client >Affects Versions: 2.4.7, 2.5.3, 2.6 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11 > > > The javascript generator collects the namespace prefix for the RPC wrapper > element AFTER the list of prefixes has been written out. Thus, if something > else hasn't happened to add the namespace to the list, the resulting XML is > invalid. -- 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-4251) Error when calling methods with the similar parameters
[ https://issues.apache.org/jira/browse/CXF-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4251. -- Resolution: Won't Fix Fix Version/s: (was: NeedMoreInfo) Invalid Assignee: Daniel Kulp Unless someone else steps up to supply a patch, we really have no plans or desire to fix this. The resulting service is not WSI-BasicProfile compliant and is thus not interopable and outside our target. Specifically, it would violate: R9981 An ENVELOPE MUST have exactly zero or one child elements of the soap11:Body element. CORE TESTABLE BP1881 R2210 If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a wsoap11:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts. CORE TESTABLE BP2119 > Error when calling methods with the similar parameters > -- > > Key: CXF-4251 > URL: https://issues.apache.org/jira/browse/CXF-4251 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6 > Environment: Tomcat 6.0.26 >Reporter: Jury Litvinoff >Assignee: Daniel Kulp >Priority: Critical > Labels: similar_parameters > Fix For: Invalid > > > Two methods with similar parameters - Example code: > @WebMethod(operationName="saveCosts", action="costs") > public String saveCosts(@WebParam(name = "way")String way, > @WebParam(name = "item")String item, > @WebParam(name = "project")String proj, > @WebParam(name = "period")String period, > @WebParam(name = "val")String val); > > @WebMethod(operationName="saveBalance", action="balance") > public String saveBalance(@WebParam(name = "way")String way, > @WebParam(name = "item")String item, > @WebParam(name = "project")String proj, > @WebParam(name = "period")String period, > @WebParam(name = "val")String val); > When I run "saveCosts", Web service transfers control to another method - > "saveBalance"!!! > Why??? -- 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-4270) Store bus-id with the endpoint name in WS-RM's RMTxStore to correctly recover two endpoints with the same endpoint name
Aki Yoshida created CXF-4270: Summary: Store bus-id with the endpoint name in WS-RM's RMTxStore to correctly recover two endpoints with the same endpoint name Key: CXF-4270 URL: https://issues.apache.org/jira/browse/CXF-4270 Project: CXF Issue Type: Improvement Components: WS-* Components Reporter: Aki Yoshida Assignee: Aki Yoshida Priority: Minor Fix For: 2.6.1 In WS-RM's RMTxStore, currently no bus information is stored along the endpoint name (i.e., endpoint's port name + its service name). And this causes a problem when, for example, two endpoints, each configured at its own bus, have the same endpoint name, as the stored RM sequences cannot be uniquely associated with the original endpoints at the system recovery. Storing the bus-id as a separate column requires a change in the RMStore's API, either in its existing sequences retrieval method (the sequence storing method needs no change as the bus ID can be obtained from its sequence argument) or adding a new setBus(Bus) method to associate a store instance to a specific bus. These are significant disadvantages. Therefore, in this improved implementation, the bus-id will be stored with the current endpoint name in that same column. Note that the default buses (those with auto-generated "cxfx" bus Ids) will use simply the bus identifier "cxf" so that they can find their sequences, including possibly of others, but this behavior is identical to the current limitation. In other words, the new RMStore will distinguish two endpoints having the same endpoint name that are assigned to two buses that have explicitly configured unique busId values. -- 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-4258) Disabling WS-Policy feature fails
[
https://issues.apache.org/jira/browse/CXF-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263358#comment-13263358
]
Frank Cornelis commented on CXF-4258:
-
I'm afraid that was about the entire stack trace:
{code}
Fault string, and possibly fault code, not set
org.apache.cxf.jaxws.JaxWsClientProxy.invoke:156
$Proxy43.requestSecurityToken:-1
...
Caused by: null - java.lang.NullPointerException
org.apache.cxf.jaxws.JaxWsClientProxy.invoke:156
$Proxy43.requestSecurityToken:-1
...
{code}
> Disabling WS-Policy feature fails
> -
>
> Key: CXF-4258
> URL: https://issues.apache.org/jira/browse/CXF-4258
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
>Affects Versions: 2.6
>Reporter: Frank Cornelis
> Fix For: NeedMoreInfo
>
>
> When disabling the WS-Policy support by configuring the cxf.xml as follows:
> {code:title=cxf.xml|borderStyle=solid}
>
> http://www.springframework.org/schema/beans";
> xmlns:cxf="http://cxf.apache.org/core";
> xmlns:p="http://cxf.apache.org/policy";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://cxf.apache.org/core
> http://cxf.apache.org/schemas/core.xsd
> http://cxf.apache.org/policy http://cxf.apache.org/schemas/policy.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd";>
>
>
>
>
>
>
> {code}
> I get an exception when invoking my web service
> {code}
> Caused by: null - java.lang.NullPointerException
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke:156
> {code}
--
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
