[jira] Created: (CXF-2929) Allow programmatic initialisation of RMManager
Allow programmatic initialisation of RMManager -- Key: CXF-2929 URL: https://issues.apache.org/jira/browse/CXF-2929 Project: CXF Issue Type: Improvement Components: WS-* Components Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 2.3, 2.2.10 It is currently possible to create and stop a RMManager using the API. The instance can't be properly initialised though, as the two methods for that are currently package protected and just called by the injection fw being @PostConstruct annotated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2930) Simple frontend + generics list type + XmlAdapter
Simple frontend + generics list type + XmlAdapter - Key: CXF-2930 URL: https://issues.apache.org/jira/browse/CXF-2930 Project: CXF Issue Type: Bug Affects Versions: 2.2.9 Environment: simple frontend, JAXB, generics, XmlAdapter Reporter: Tamas KIS Simple frontend does not seem to support a generics list type with XmlAdapter. Adapters work fine until they try to map some generics data (e.g. a generics list like MyGenericsList, see attached project). (JAX-WS frontend works). There is warning message at startup, should it mean that JAXWS is the preferred frontend for CXF in general, or only until some better Adapter support is implemented (is it planned?) ? " org.apache.cxf.service.factory.ReflectionServiceFactoryBean checkServiceClassAnnotations WARNING: A JAX-WS Annotation was found on demo.hw.server.HelloWorldImpl while using the Simple frontend. For better results, use the JAX-WS frontend. " I attach a demo project.. (if there is some way to do it..) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2930) Simple frontend + generics list type + XmlAdapter
[ https://issues.apache.org/jira/browse/CXF-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas KIS updated CXF-2930: --- Attachment: MyGenericsTestWS.jar demo project for XmlAdapter problem with JAXB databinding. > Simple frontend + generics list type + XmlAdapter > - > > Key: CXF-2930 > URL: https://issues.apache.org/jira/browse/CXF-2930 > Project: CXF > Issue Type: Bug >Affects Versions: 2.2.9 > Environment: simple frontend, JAXB, generics, XmlAdapter >Reporter: Tamas KIS > Attachments: MyGenericsTestWS.jar > > > Simple frontend does not seem to support a generics list type with XmlAdapter. > Adapters work fine until they try to map some generics data (e.g. a generics > list like MyGenericsList, see attached project). > (JAX-WS frontend works). > There is warning message at startup, should it mean that JAXWS is the > preferred frontend for CXF in general, or only until some better Adapter > support is implemented (is it planned?) ? > " > org.apache.cxf.service.factory.ReflectionServiceFactoryBean > checkServiceClassAnnotations > WARNING: A JAX-WS Annotation was found on demo.hw.server.HelloWorldImpl > while using the Simple frontend. For better results, use the JAX-WS frontend. > " > I attach a demo project.. (if there is some way to do it..) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2931) Add configurable pretty printing to the CXF logging in/out interceptors
Add configurable pretty printing to the CXF logging in/out interceptors --- Key: CXF-2931 URL: https://issues.apache.org/jira/browse/CXF-2931 Project: CXF Issue Type: Improvement Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.3, 2.2.10 Currently the logging in/out interceptors only print the raw message without any additional formatting, in many cases making it difficult to read requests/replies in the logging. We should have ability in these interceptors to turn on a flag and have messages logged with proper indentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2931) Add configurable pretty printing to the CXF logging in/out interceptors
[ https://issues.apache.org/jira/browse/CXF-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-2931. --- Resolution: Fixed committed the patch in CXF trunk and CXF 2.2.x-fixing branch. > Add configurable pretty printing to the CXF logging in/out interceptors > --- > > Key: CXF-2931 > URL: https://issues.apache.org/jira/browse/CXF-2931 > Project: CXF > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.3, 2.2.10 > > > Currently the logging in/out interceptors only print the raw message without > any additional formatting, in many cases making it difficult to read > requests/replies in the logging. We should have ability in these interceptors > to turn on a flag and have messages logged with proper indentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2929) Allow programmatic initialisation of RMManager
[ https://issues.apache.org/jira/browse/CXF-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessio Soldano resolved CXF-2929. -- Resolution: Fixed I've added another (public) method for initialising the RMManager given a Bus instance > Allow programmatic initialisation of RMManager > -- > > Key: CXF-2929 > URL: https://issues.apache.org/jira/browse/CXF-2929 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Reporter: Alessio Soldano >Assignee: Alessio Soldano > Fix For: 2.3, 2.2.10 > > > It is currently possible to create and stop a RMManager using the API. The > instance can't be properly initialised though, as the two methods for that > are currently package protected and just called by the injection fw being > @PostConstruct annotated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2932) no way to specify default value with aegis
no way to specify default value with aegis -- Key: CXF-2932 URL: https://issues.apache.org/jira/browse/CXF-2932 Project: CXF Issue Type: Improvement Components: Aegis Databinding Affects Versions: 2.2.9 Environment: All Reporter: Michenaud Laurent Hi, At this time, it is not possible to specify the default value of an element with Aegis. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CXF-2929) Allow programmatic initialisation of RMManager
[ https://issues.apache.org/jira/browse/CXF-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glen Mazza reopened CXF-2929: - Are you sure you want the public API to be using British English? Neither Spring nor the JDK uses that. initialise() is real Britain-specific, not even the Canadians use that (http://www3.telus.net/linguisticsissues/BritishCanadianAmerican.htm) See also here: http://www.mail-archive.com/avalon-...@jakarta.apache.org/msg07094.html > Allow programmatic initialisation of RMManager > -- > > Key: CXF-2929 > URL: https://issues.apache.org/jira/browse/CXF-2929 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Reporter: Alessio Soldano >Assignee: Alessio Soldano > Fix For: 2.3, 2.2.10 > > > It is currently possible to create and stop a RMManager using the API. The > instance can't be properly initialised though, as the two methods for that > are currently package protected and just called by the injection fw being > @PostConstruct annotated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2929) Allow programmatic initialisation of RMManager
[ https://issues.apache.org/jira/browse/CXF-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895686#action_12895686 ] Alessio Soldano commented on CXF-2929: -- oh, well... I've no problems at all renaming that to initialize(), really. Doing that.. > Allow programmatic initialisation of RMManager > -- > > Key: CXF-2929 > URL: https://issues.apache.org/jira/browse/CXF-2929 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Reporter: Alessio Soldano >Assignee: Alessio Soldano > Fix For: 2.3, 2.2.10 > > > It is currently possible to create and stop a RMManager using the API. The > instance can't be properly initialised though, as the two methods for that > are currently package protected and just called by the injection fw being > @PostConstruct annotated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-2933) Can't find the request for service's Observer
Can't find the request for service's Observer - Key: CXF-2933 URL: https://issues.apache.org/jira/browse/CXF-2933 Project: CXF Issue Type: Task Components: JAX-WS Runtime Affects Versions: 2.2.8 Environment: Windows XP, JDK 1.6, Weblogic application server 10.3 Reporter: amit rathi Hi, I have developed a webservice using CXF2.2.8, when I deployed it on weblogic application server & try to access the WSDL url in IE its throwing exception. Below are the various files I am using. Kindly help me, its urgent. Let me know if you need anything more from my side. cxf.xml - http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:jaxws="http://cxf.apache.org/jaxws"; xmlns:context="http://www.springframework.org/schema/context"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd";> - cxf-servlet.xml - http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:foo="http://cxf.apache.org/configuration/foo"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd";> http://cxf.apache.org/bindings/xformat http://schemas.xmlsoap.org/soap/http http://schemas.xmlsoap.org/wsdl/http/ http://schemas.xmlsoap.org/wsdl/soap/http http://www.w3.org/2003/05/soap/bindings/HTTP/ http://cxf.apache.org/transports/http/configuration - cxf-extension-soap.xml - http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:foo="http://cxf.apache.org/configuration/foo"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd";> http://schemas.xmlsoap.org/soap/ http://schemas.xmlsoap.org/wsdl/soap/ http://schemas.xmlsoap.org/wsdl/soap12/ http://www.w3.org/2003/05/soap/bindings/HTTP/ http://schemas.xmlsoap.org/wsdl/soap/http http://schemas.xmlsoap.org/soap/ http://schemas.xmlsoap.org/wsdl/soap/ http://schemas.xmlsoap.org/wsdl/soap12/
[jira] Commented: (CXF-2929) Allow programmatic initialisation of RMManager
[ https://issues.apache.org/jira/browse/CXF-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895692#action_12895692 ] Glen Mazza commented on CXF-2929: - Yeah, I've long suggested that Java developers should switch to fattenUp() to avoid the initialise() vs. initialize() argument, but have seen limited adoption of that. :) > Allow programmatic initialisation of RMManager > -- > > Key: CXF-2929 > URL: https://issues.apache.org/jira/browse/CXF-2929 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Reporter: Alessio Soldano >Assignee: Alessio Soldano > Fix For: 2.3, 2.2.10 > > > It is currently possible to create and stop a RMManager using the API. The > instance can't be properly initialised though, as the two methods for that > are currently package protected and just called by the injection fw being > @PostConstruct annotated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2927) Missing ConfiguredBeanLocator in bus created by org.apache.cxf.bus.CXFBusFactory
[ https://issues.apache.org/jira/browse/CXF-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895716#action_12895716 ] Daniel Kulp commented on CXF-2927: -- The other option is in the ExtensionBus that you get when you don't have spring is to have it have a special ConfiguredBeanLocator that does smart things with the loaded extensions. Thus, the "get by class" things could iterator through the extensions for those that implement the class and such. That MAY be a first step in getting some of the policy things auto loaded when not using Spring. If the SecPolLoader bean is in the extension array, when the policy engine starts up and need the extensions, it would ask the locator for all the PolicyLoaders and this would then find them. > Missing ConfiguredBeanLocator in bus created by > org.apache.cxf.bus.CXFBusFactory > > > Key: CXF-2927 > URL: https://issues.apache.org/jira/browse/CXF-2927 > Project: CXF > Issue Type: Bug > Components: Bus >Reporter: Alessio Soldano > Fix For: 2.3 > > > On the current trunk (2.3-SNAPSHOT) a ConfiguredBeanLocator instance is only > installed when the Spring based Bus factory is used. Unfortunately not all > the retrieval of that bus extensions are followed by a check for the > extension being actually available, hence it's possible to get NPE. > I've reproduced this issue when manually enabling WS-Policy engine after > building the Bus with the CXFBusFactory as well as using the wsdl2java > tooling (without spring available). > In the latter, for instance, the BindingFactoryManagerImpl throws NPE when > finding the BindingFactory for a wsdl segement like this: > > > > > > > As a temporary workaround I've succesfully verified adding a dummy locator to > the bus solves the problem. That would implement ConfiguredBeanLocator > returning null/empty collections. > However, I'm worndering what we want to do here, we can either go and protect > every access to this locator or install a default one that does nothing in > the CXFBusFactory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2929) Allow programmatic initialisation of RMManager
[ https://issues.apache.org/jira/browse/CXF-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895717#action_12895717 ] Daniel Kulp commented on CXF-2929: -- That's why I ususally just user: public void init(); Everyone is happy, including my fingers. :-) > Allow programmatic initialisation of RMManager > -- > > Key: CXF-2929 > URL: https://issues.apache.org/jira/browse/CXF-2929 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Reporter: Alessio Soldano >Assignee: Alessio Soldano > Fix For: 2.3, 2.2.10 > > > It is currently possible to create and stop a RMManager using the API. The > instance can't be properly initialised though, as the two methods for that > are currently package protected and just called by the injection fw being > @PostConstruct annotated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CXF-2931) Add configurable pretty printing to the CXF logging in/out interceptors
[ https://issues.apache.org/jira/browse/CXF-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp reopened CXF-2931: -- I'm reopening this as I have two issues with the code that was committed: 1) Please do not create a transformer or parser or anything directly. Make sure you go through XMLUtils or StaxUtils to do so. I learned from the security issue that having all of that in one place makes changing things if needed MUCH MUCH easier. 2) If this is configured on a Bus level (common for logging) but a non XML request goes through, what happens?For example, a JAXRS JSON thing or similar? I think this needs to check the content type or something to make sure it really is XML before doing an XML transform on it. > Add configurable pretty printing to the CXF logging in/out interceptors > --- > > Key: CXF-2931 > URL: https://issues.apache.org/jira/browse/CXF-2931 > Project: CXF > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.3, 2.2.10 > > > Currently the logging in/out interceptors only print the raw message without > any additional formatting, in many cases making it difficult to read > requests/replies in the logging. We should have ability in these interceptors > to turn on a flag and have messages logged with proper indentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
NullPointerException on code generation
One project of mine gives a stacktrace given at the end. It is quite strange as
it loads lots of bean definitions, my plugin configuration has only two plugins:
org.apache.felix
maven-bundle-plugin
true
${pom.artifactId}
javax.jws,
javax.wsdl,
javax.xml.bind,
javax.xml.bind.annotation,
javax.xml.namespace,
javax.xml.ws,
META-INF.cxf,
META-INF.cxf.osgi,
META-INF.cxf.transport.nmr,
org.apache.camel,
org.apache.camel.osgi,
org.apache.cxf.binding,
org.apache.cxf.binding.soap,
org.apache.cxf.binding.soap.spring,
org.apache.cxf.bus,
org.apache.cxf.bus.spring,
org.apache.cxf.bus.resource,
org.apache.cxf.buslifecycle,
org.apache.cxf.catalog,
org.apache.cxf.configuration.spring,
org.apache.cxf.endpoint,
org.apache.cxf.headers,
org.apache.cxf.phase,
org.apache.cxf.resource,
org.apache.cxf.jaxws,
org.apache.cxf.transport,
org.apache.cxf.transport.http,
org.apache.cxf.transport.http.policy,
org.apache.cxf.transport.http_jetty,
org.apache.cxf.transport.http_osgi,
org.apache.cxf.workqueue,
org.apache.cxf.wsdl11,
org.apache.servicemix.camel.nmr,
org.apache.servicemix.cxf.transport.nmr,
org.apache.servicemix.nmr.api,
org.springframework.beans.factory.config,
*
pl.edu.uw.dsk.esb.integration.come
org.apache.cxf.bundle
org.apache.cxf
cxf-codegen-plugin
${cxf.version}
generate-sources
generate-sources
${project.build.directory}/generated-sources/cxf
${basedir}/../../../../../data-exchange/trunk/someservice.wsdl
SomeService
wsdl2java
[INFO] [cxf-codegen:wsdl2java {execution: generate-sources}]
Aug 5, 2010 6:04:01 PM org.apache.cxf.tools.wsdlto.core.PluginLoader loadPlugin
INFO: Replaced default frontend jaxws
Aug 5, 2010 6:04:01 PM org.apache.cxf.tools.wsdlto.core.PluginLoader loadPlugin
INFO: Replaced default databinding jaxb
Aug 5, 2010 6:04:02 PM
org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO: Refreshing org.apache.cxf.bus.spring.busapplicationcont...@164a8c:
display name [org.apache.cxf.bus.spring.busapplicationcont...@164a8c]; startup
date [Thu Aug 05 18:04:02 CEST 2010]; root of context hierarchy
Aug 5, 2010 6:04:02 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf.xml]
Aug 5, 2010 6:04:02 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-camel.xml]
Aug 5, 2010 6:04:02 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-corba.xml]
Aug 5, 2010 6:04:02 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-jaxws.xml]
Aug 5, 2010 6:04:02 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-soap.xml]
Aug 5, 2010 6:04:02 PM
org.springframework
[jira] Resolved: (CXF-2929) Allow programmatic initialisation of RMManager
[ https://issues.apache.org/jira/browse/CXF-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessio Soldano resolved CXF-2929. -- Resolution: Fixed > Allow programmatic initialisation of RMManager > -- > > Key: CXF-2929 > URL: https://issues.apache.org/jira/browse/CXF-2929 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Reporter: Alessio Soldano >Assignee: Alessio Soldano > Fix For: 2.3, 2.2.10 > > > It is currently possible to create and stop a RMManager using the API. The > instance can't be properly initialised though, as the two methods for that > are currently package protected and just called by the injection fw being > @PostConstruct annotated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2931) Add configurable pretty printing to the CXF logging in/out interceptors
[ https://issues.apache.org/jira/browse/CXF-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895920#action_12895920 ] Willem Jiang commented on CXF-2931: --- Hi Dan, I just committed the patch as you suggested , please review it if you have time. Thanks, Willem > Add configurable pretty printing to the CXF logging in/out interceptors > --- > > Key: CXF-2931 > URL: https://issues.apache.org/jira/browse/CXF-2931 > Project: CXF > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.3, 2.2.10 > > > Currently the logging in/out interceptors only print the raw message without > any additional formatting, in many cases making it difficult to read > requests/replies in the logging. We should have ability in these interceptors > to turn on a flag and have messages logged with proper indentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
