[jira] [Assigned] (CXF-3527) NullPointer exception when interface contains generics

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang reassigned CXF-3527:
-

Assignee: Freeman Fang

> NullPointer exception when interface contains generics
> --
>
> Key: CXF-3527
> URL: https://issues.apache.org/jira/browse/CXF-3527
> Project: CXF
>  Issue Type: Bug
>  Components: Aegis Databinding
>Affects Versions: 2.3.3
> Environment: Debian GNU/Linux Tomcat6
>Reporter: Vassilis Virvilis
>Assignee: Freeman Fang
>
> The following code fails with a NULL pointer exception in deploy. Always the 
> same. In order to reproduce the problem you have to uncomment the method 
> declarations otherwise the war does not deploy.
> What I would like in case it is not possible to make it work in Aegis due to 
> other constraints is a better error mentioning the problematic method because 
> right now I have to suspect all methods and play binary search to find the 
> problematic ones.
> // fails with null pointer exception in deploy
> // public T testGeneric(Collection collection);
> // success
> public Integer testGeneric(Collection collection);
> // fails with null pointer exception in deploy
> // public  Pair testReturnGenericPair(T1 first, T2 
> second);
> // fails with null pointer exception in deploy
> // public Pair testReturnQualifiedPair(Integer first,
> // String second);
> // fails with null pointer exception in deploy
> // public  int testGenericPair(Pair pair);
> // fails with null pointer exception in deploy
> // public int testQualifiedPair(Pair pair);
> You cant find the eclipse project attached in 
> https://issues.apache.org/jira/browse/CXF-3526
> and here is the exception
> May 16, 2011 5:38:12 PM org.apache.catalina.core.StandardContext listenerStart
> SEVERE: Exception sending context initialized event to listener instance of 
> class org.springframework.web.context.ContextLoaderListener
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'test': Invocation of init method failed; nested exception is 
> java.lang.NullPointerException
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
> at 
> org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
> at 
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
> at 
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
> at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at 
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
> at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:563)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1397)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Delega

[jira] [Created] (CXF-3549) Support docLocation attribute for jaxrs endpoints

[Sergey Beryozkin (JIRA)]

Support docLocation attribute for jaxrs endpoints
-

 Key: CXF-3549
 URL: https://issues.apache.org/jira/browse/CXF-3549
 Project: CXF
  Issue Type: Task
  Components: JAX-RS
Affects Versions: 2.4.1
Reporter: Sergey Beryozkin
Assignee: Sergey Beryozkin
 Fix For: 2.4.1


It makes sense to support a docLocation attribute given an initial support for 
the wadl-first dev is now in place.
In principle it can even point to pdf or something other file, wsdl2 doc in the 
future, etc, not only WADL


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3549) Support docLocation attribute for jaxrs endpoints

[Sergey Beryozkin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Beryozkin resolved CXF-3549.
---

Resolution: Fixed

> Support docLocation attribute for jaxrs endpoints
> -
>
> Key: CXF-3549
> URL: https://issues.apache.org/jira/browse/CXF-3549
> Project: CXF
>  Issue Type: Task
>  Components: JAX-RS
>Affects Versions: 2.4.1
>Reporter: Sergey Beryozkin
>Assignee: Sergey Beryozkin
> Fix For: 2.4.1
>
>
> It makes sense to support a docLocation attribute given an initial support 
> for the wadl-first dev is now in place.
> In principle it can even point to pdf or something other file, wsdl2 doc in 
> the future, etc, not only WADL

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3527) NullPointer exception when interface contains generics

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved CXF-3527.
---

   Resolution: Fixed
Fix Version/s: 2.3.5
   2.4.1

commit fix
http://svn.apache.org/viewvc?rev=1127829&view=rev for trunk
http://svn.apache.org/viewvc?rev=1127855&view=rev for 2.3.x branch

> NullPointer exception when interface contains generics
> --
>
> Key: CXF-3527
> URL: https://issues.apache.org/jira/browse/CXF-3527
> Project: CXF
>  Issue Type: Bug
>  Components: Aegis Databinding
>Affects Versions: 2.3.3
> Environment: Debian GNU/Linux Tomcat6
>Reporter: Vassilis Virvilis
>Assignee: Freeman Fang
> Fix For: 2.4.1, 2.3.5
>
>
> The following code fails with a NULL pointer exception in deploy. Always the 
> same. In order to reproduce the problem you have to uncomment the method 
> declarations otherwise the war does not deploy.
> What I would like in case it is not possible to make it work in Aegis due to 
> other constraints is a better error mentioning the problematic method because 
> right now I have to suspect all methods and play binary search to find the 
> problematic ones.
> // fails with null pointer exception in deploy
> // public T testGeneric(Collection collection);
> // success
> public Integer testGeneric(Collection collection);
> // fails with null pointer exception in deploy
> // public  Pair testReturnGenericPair(T1 first, T2 
> second);
> // fails with null pointer exception in deploy
> // public Pair testReturnQualifiedPair(Integer first,
> // String second);
> // fails with null pointer exception in deploy
> // public  int testGenericPair(Pair pair);
> // fails with null pointer exception in deploy
> // public int testQualifiedPair(Pair pair);
> You cant find the eclipse project attached in 
> https://issues.apache.org/jira/browse/CXF-3526
> and here is the exception
> May 16, 2011 5:38:12 PM org.apache.catalina.core.StandardContext listenerStart
> SEVERE: Exception sending context initialized event to listener instance of 
> class org.springframework.web.context.ContextLoaderListener
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'test': Invocation of init method failed; nested exception is 
> java.lang.NullPointerException
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1420)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:580)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
> at 
> org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
> at 
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
> at 
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
> at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
> at 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
> at 
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
> at 
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:563)
> at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1397)
> at sun

[jira] [Resolved] (CXF-3548) EndPointImpl's hasCode value should not change when its mutable properties are changed

[Aki Yoshida (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aki Yoshida resolved CXF-3548.
--

Resolution: Fixed

Thanks Dan.
I should have used svnmerge to track the merged version.
Regards, aki

> EndPointImpl's hasCode value should not change when its mutable properties 
> are changed
> --
>
> Key: CXF-3548
> URL: https://issues.apache.org/jira/browse/CXF-3548
> Project: CXF
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.4, 2.3.4
>Reporter: Aki Yoshida
>Assignee: Aki Yoshida
> Fix For: 2.4.1, 2.3.5
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The current implementation of hashCode() simply calls HashMap's hashCode(). 
> Consequently, the hashCode changes whenever some changes occur in this 
> property table. The endpoint's hashCode should be calculated on the immutable 
> part to avoid confusion as the following abnormality can be observed:
> Endpoint ep = ...
> map = new HashMap<...>();
> map.put(ep, "A");
> assertNotNull(map.get(ep)); // okay
> ep.put(USING_ADDRESSING, b);
> assertEquals(ep, map.keySet().iterator().next()); // okay
> assertNotNull(map.get(ep)); // error
> This issue was discussed in dev@cxf:
> http://cxf.547215.n5.nabble.com/org-apache-cxf-endpoint-EndpointImpl-may-not-be-used-as-a-hash-map-key-td4393354.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-2465) WSDL2Java should create Javadoc from wsdl:documentation tags

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-2465.
--

   Resolution: Fixed
Fix Version/s: 2.3.5
   2.4.1
 Assignee: Daniel Kulp

> WSDL2Java should create Javadoc from wsdl:documentation tags
> 
>
> Key: CXF-2465
> URL: https://issues.apache.org/jira/browse/CXF-2465
> Project: CXF
>  Issue Type: New Feature
>  Components: Tooling
>Affects Versions: 2.2.4
>Reporter: Christian Schneider
>Assignee: Daniel Kulp
>Priority: Minor
> Fix For: 2.4.1, 2.3.5
>
>
> Currently Java2WS already creates wsdl:documentation tags from 
> @WsdlDocumentation annotations. These apply to portType and operation. 
> To benefit from these tags in generated code WSDL2Java should create Javadoc 
> comments from wsdl:documentation tags.
> See the thread on the mailing list for some pointers from Dan how to 
> implement this:
> http://mail-archives.apache.org/mod_mbox/cxf-users/200910.mbox/browser
> "Mostly, in the WSDLServiceBuilder thing, when processing the wsdl, you 
> would need to copy the documentation stuff out of the wsdl and into the new 
> documentation things I added into the service model to support the 
> @WSDLDocumentation things.   From there, just updating the jaxws processor 
> things in tools and maybe the velocity templates may be enough.
> Dan"

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3182) wsdl:documentation should become javadoc in generated code

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-3182.
--

   Resolution: Fixed
Fix Version/s: 2.3.5
   2.4.1
 Assignee: Daniel Kulp

> wsdl:documentation should become javadoc in generated code
> --
>
> Key: CXF-3182
> URL: https://issues.apache.org/jira/browse/CXF-3182
> Project: CXF
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: 2.2.10
>Reporter: Karl Palsson
>Assignee: Daniel Kulp
> Fix For: 2.4.1, 2.3.5
>
>
> I'd like wsdl documentation to appear as javadoc in the generated classes.  
> metro does this, at least using the following maven plugin
> {code:xml}
> org.codehaus.mojo
> jaxws-maven-plugin
> 1.12
> {code} 
> This was discussed on nabble, (attached below, nabble urls seem to be 
> outrageously fragile)
> On Tuesday 11 May 2010 8:39:17 pm Naresh Tallapelli wrote: 
> > Hi All, 
> > 
> > I have added documentation in wsdl for some of my operations. And i tried 
> > to generate the java code from wsdl using "WSDL2JAVA". But i did not find 
> > any comments in the generated code which i have added in wsdl file. Please 
> > help me to generate the java doc from wsdl documentation. 
> This isn't implemented yet.   Per JAX-WS spec, any javadoc should come from 
> custom jax-ws binding files, but that really does suck.   If you'd like to 
> tackle it, I'd me more than happy to point you in the right directions.   :-) 
> Dan 
> -
> Apparently a ticket was never filed for this :(

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CXF-3182) wsdl:documentation should become javadoc in generated code

[Karl Palsson (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039866#comment-13039866
 ] 

Karl Palsson commented on CXF-3182:
---



Ég hef látið af störfum hjá Vodafone, vinsamlegast hafið samband við Fannar Örn 
Þorbjörnsson, fanna...@vodafone.is

Kv.
Karl Jóhann Pálsson


> wsdl:documentation should become javadoc in generated code
> --
>
> Key: CXF-3182
> URL: https://issues.apache.org/jira/browse/CXF-3182
> Project: CXF
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: 2.2.10
>Reporter: Karl Palsson
>Assignee: Daniel Kulp
> Fix For: 2.4.1, 2.3.5
>
>
> I'd like wsdl documentation to appear as javadoc in the generated classes.  
> metro does this, at least using the following maven plugin
> {code:xml}
> org.codehaus.mojo
> jaxws-maven-plugin
> 1.12
> {code} 
> This was discussed on nabble, (attached below, nabble urls seem to be 
> outrageously fragile)
> On Tuesday 11 May 2010 8:39:17 pm Naresh Tallapelli wrote: 
> > Hi All, 
> > 
> > I have added documentation in wsdl for some of my operations. And i tried 
> > to generate the java code from wsdl using "WSDL2JAVA". But i did not find 
> > any comments in the generated code which i have added in wsdl file. Please 
> > help me to generate the java doc from wsdl documentation. 
> This isn't implemented yet.   Per JAX-WS spec, any javadoc should come from 
> custom jax-ws binding files, but that really does suck.   If you'd like to 
> tackle it, I'd me more than happy to point you in the right directions.   :-) 
> Dan 
> -
> Apparently a ticket was never filed for this :(

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CXF-3182) wsdl:documentation should become javadoc in generated code

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp updated CXF-3182:
-

Comment: was deleted

(was: 

Ég hef látið af störfum hjá Vodafone, vinsamlegast hafið samband við Fannar Örn 
Þorbjörnsson, fanna...@vodafone.is

Kv.
Karl Jóhann Pálsson
)

> wsdl:documentation should become javadoc in generated code
> --
>
> Key: CXF-3182
> URL: https://issues.apache.org/jira/browse/CXF-3182
> Project: CXF
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: 2.2.10
>Reporter: Karl Palsson
>Assignee: Daniel Kulp
> Fix For: 2.4.1, 2.3.5
>
>
> I'd like wsdl documentation to appear as javadoc in the generated classes.  
> metro does this, at least using the following maven plugin
> {code:xml}
> org.codehaus.mojo
> jaxws-maven-plugin
> 1.12
> {code} 
> This was discussed on nabble, (attached below, nabble urls seem to be 
> outrageously fragile)
> On Tuesday 11 May 2010 8:39:17 pm Naresh Tallapelli wrote: 
> > Hi All, 
> > 
> > I have added documentation in wsdl for some of my operations. And i tried 
> > to generate the java code from wsdl using "WSDL2JAVA". But i did not find 
> > any comments in the generated code which i have added in wsdl file. Please 
> > help me to generate the java doc from wsdl documentation. 
> This isn't implemented yet.   Per JAX-WS spec, any javadoc should come from 
> custom jax-ws binding files, but that really does suck.   If you'd like to 
> tackle it, I'd me more than happy to point you in the right directions.   :-) 
> Dan 
> -
> Apparently a ticket was never filed for this :(

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-2766) @Webparam name not honoured

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-2766.
--

   Resolution: Fixed
Fix Version/s: 2.4.1
 Assignee: Daniel Kulp

> @Webparam name not honoured
> ---
>
> Key: CXF-2766
> URL: https://issues.apache.org/jira/browse/CXF-2766
> Project: CXF
>  Issue Type: Bug
>  Components: JAXB Databinding
>Affects Versions: 2.2.6, 2.2.7
> Environment: Mac OS-X, Windows XP, Spring Configured CXF Client
>Reporter: John Friar
>Assignee: Daniel Kulp
> Fix For: 2.4.1
>
>
> I have imported a wsdl (using the wsdl2java tool) from a service provider. A 
> snippet of the generated webservice interface is:
> @WebResult(name = "return-response", targetNamespace = 
> "http://sp.com/service.wsdl/types";, partName = "returnResponse")
> @WebMethod(action = "http://sp.com/doReturn";)
> public ReturnResponseType doReturn(
> @WebParam(partName = "returnTrx", name = "return-request", 
> targetNamespace = "http://sp.com/service.wsdl/types";)
> ReturnRequestType returnTrx
> ) throws ErrorMessages;
> However, the soap message that is created does not honour the name of the 
> @WebParam (return-request) and instead uses doReturn as the name of the 
> method and parameter. If any other name is used then behaviour is as 
> expected. I cannot find anything in the spec. that specifies that 'return' 
> should not be used at the start of a @WebParam name but that appears to be 
> the issue.
> Thanks,
> John

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-1714) ASM package are not stated as optional imports in the bundle's MANIFEST

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-1714.
--

   Resolution: Fixed
Fix Version/s: 2.4.1
 Assignee: Daniel Kulp

> ASM package are not stated as optional imports in the bundle's MANIFEST
> ---
>
> Key: CXF-1714
> URL: https://issues.apache.org/jira/browse/CXF-1714
> Project: CXF
>  Issue Type: Wish
>  Components: OSGi
>Affects Versions: 2.1.1, 2.0.7
> Environment: OW2 JOnAS , using CXF in an OSGi gateway (Felix)
>Reporter: Guillaume Sauthier
>Assignee: Daniel Kulp
> Fix For: 2.4.1
>
>
> I've found that the package 'org.objectweb.asm' was in the list of 
> Import-Package of the bundle.
> It's not described as optional, even if in the code (I looked at the 
> WrapperHelper class) it seems to handle the case where ASM is not present, so 
> I cannot deploy the CXF bundle if the gateway do not have the 
> 'org.objectweb.asm' package available.
> So it seems logical to add a resolution:=optional statement in the bnd file.
> I have described that issue as a wish because there is a simple workaround: 
> simply provide a bundle exporting the right package; but I don't really like 
> this solution because, I know, from experience, that ASM is not a easily 
> shareable library, because of API incompatibilities, it far more easier to 
> embed its privatized version of ASM (using jarjar or the "new" 
> maven-shadow-plugin its easy) in a private package: org.apache.cxf.asm. So 
> that you don't have to describe the imports because ASM is now part of the 
> distribution + you are sure to never have ASM version incompatibilities 
> issue. Moreover, the ASM core is really lightweight...
> So to sum up, I have 2 solutions:
> 1. add resolution:=optional to the import statement
> 2. or privatize ASM automatically
> My preference goes to #2 :)
> BTW, does that make sens to have a "Bundle" component in JIRA, or the OSGi 
> issues will go to the "Build system" component ?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3500) Make more packages optional in the CXF JAX-RS OSGI bundle to reduce runtime dependencies

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-3500.
--

Resolution: Fixed
  Assignee: Daniel Kulp


Patches applied.  Thanks!

> Make more packages optional in the CXF JAX-RS OSGI bundle to reduce runtime 
> dependencies
> 
>
> Key: CXF-3500
> URL: https://issues.apache.org/jira/browse/CXF-3500
> Project: CXF
>  Issue Type: Improvement
>  Components: Build system, JAX-RS, OSGi
>Affects Versions: 2.4, 2.3.4
> Environment: JDK 1.6
> Eclipse Equinox 3.6.2
>Reporter: Ka-Lok Fung
>Assignee: Daniel Kulp
>Priority: Minor
> Fix For: 2.4.1, 2.3.5
>
> Attachments: cxf-jaxrs-bundle-pom-23.diff, 
> cxf-jaxrs-bundle-pom-24.diff
>
>
> The Import-Package line in the CXF JAX-RS bundle has packages which are 
> required but are actually optional. 
> Here's a list of packages that should be optional in the 2.3.x stream:
> {quote}
> org.apache.neethi;resolution:=optional,
> org.apache.ws.commons.schema*;resolution:=optional,
> org.apache.xml.resolver*;resolution:=optional,
> org.objectweb.asm;resolution:=optional,
> javax.mail*;version="[0.0,2)";resolution:=optional,
> {quote}
> Here's a list of packages that should be optional in the trunk (2.4.x) stream:
> {quote}
> org.apache.ws.commons.schema*;resolution:=optional,
> org.apache.xml.resolver*;resolution:=optional,
> org.objectweb.asm;resolution:=optional,
> org.osgi.service.blueprint*;resolution:=optional,
> javax.mail*;version="[0.0,2)";resolution:=optional,
> javax.wsdl*;resolution:=optional,
> {quote}
> Proposed patches to both streams attached.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3078) Encoding warning with Maven 2.2.1 while building CXF sample projects.

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-3078.
--

   Resolution: Fixed
Fix Version/s: 2.4
 Assignee: Daniel Kulp


This was actually fixed in 2.4.

> Encoding warning with Maven 2.2.1 while building CXF sample projects.
> -
>
> Key: CXF-3078
> URL: https://issues.apache.org/jira/browse/CXF-3078
> Project: CXF
>  Issue Type: Improvement
>  Components: Build system
>Affects Versions: 2.3
>Reporter: Robert Liguori
>Assignee: Daniel Kulp
>Priority: Minor
> Fix For: 2.4
>
>
> I see an encoding warning when building CXF samples with Maven 2.2.1.
> [INFO] 
> 
> [INFO] Building Apache CXF Code Generation Maven2 Plugins
> [INFO]task-segment: [clean, install]
> [INFO] 
> 
> ...
> [WARNING] Using platform encoding (Cp1252 actually) to read mojo metadata, 
> i.e. build is platform dependent!
> ...
> This blog entry is close to what I am seeing:
> ([WARNING] Using platform encoding (Cp1252 actually) to copy filtered 
> resources, i.e. build is platform dependent!)
> http://blog.vinodsingh.com/2009/04/encoding-warning-with-maven-210.html
> I think it's best to remove warnings where possible... as such, should the 
> CXF POM files be updated with something similar to this:
> 
> UTF-8
>   
> Or would this affect backwards compatibility?
> Thanks!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CXF-3070) add a LoadBalanceFeature for CXF

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp updated CXF-3070:
-

Fix Version/s: NeedMoreInfo

This may be a duplicate of CXF-3424 which was added in 2.3.4/2.4.   Can this be 
marked resolved?

> add a LoadBalanceFeature for CXF
> 
>
> Key: CXF-3070
> URL: https://issues.apache.org/jira/browse/CXF-3070
> Project: CXF
>  Issue Type: Wish
>  Components: Core
>Affects Versions: 2.3
>Reporter: scud
>Assignee: Christian Schneider
> Fix For: NeedMoreInfo
>
>
> I write some code to implement the LoadBalanceFeature upon FailOverFeatuer. 
> (many code is from FailoverFeature and realted classes)
> I hope someone can merge the feature into CXF, it need some review and 
> improve for merge.
> please check here for it: 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/src/main/java/org/javascud/extensions/cxf/LoadBalanceFeature.java
>   
> you can find the project in 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CXF-3070) add a LoadBalanceFeature for CXF

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider closed CXF-3070.



> add a LoadBalanceFeature for CXF
> 
>
> Key: CXF-3070
> URL: https://issues.apache.org/jira/browse/CXF-3070
> Project: CXF
>  Issue Type: Wish
>  Components: Core
>Affects Versions: 2.3
>Reporter: scud
>Assignee: Christian Schneider
> Fix For: NeedMoreInfo
>
>
> I write some code to implement the LoadBalanceFeature upon FailOverFeatuer. 
> (many code is from FailoverFeature and realted classes)
> I hope someone can merge the feature into CXF, it need some review and 
> improve for merge.
> please check here for it: 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/src/main/java/org/javascud/extensions/cxf/LoadBalanceFeature.java
>   
> you can find the project in 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3070) add a LoadBalanceFeature for CXF

[Christian Schneider (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider resolved CXF-3070.
--

Resolution: Duplicate

> add a LoadBalanceFeature for CXF
> 
>
> Key: CXF-3070
> URL: https://issues.apache.org/jira/browse/CXF-3070
> Project: CXF
>  Issue Type: Wish
>  Components: Core
>Affects Versions: 2.3
>Reporter: scud
>Assignee: Christian Schneider
> Fix For: NeedMoreInfo
>
>
> I write some code to implement the LoadBalanceFeature upon FailOverFeatuer. 
> (many code is from FailoverFeature and realted classes)
> I hope someone can merge the feature into CXF, it need some review and 
> improve for merge.
> please check here for it: 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/src/main/java/org/javascud/extensions/cxf/LoadBalanceFeature.java
>   
> you can find the project in 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CXF-3070) add a LoadBalanceFeature for CXF

[Christian Schneider (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039961#comment-13039961
 ] 

Christian Schneider commented on CXF-3070:
--

@scud: Could you take a look at the solution from the other ticket and report 
if that works for you? Also feel free to propose improvements.

> add a LoadBalanceFeature for CXF
> 
>
> Key: CXF-3070
> URL: https://issues.apache.org/jira/browse/CXF-3070
> Project: CXF
>  Issue Type: Wish
>  Components: Core
>Affects Versions: 2.3
>Reporter: scud
>Assignee: Christian Schneider
> Fix For: NeedMoreInfo
>
>
> I write some code to implement the LoadBalanceFeature upon FailOverFeatuer. 
> (many code is from FailoverFeature and realted classes)
> I hope someone can merge the feature into CXF, it need some review and 
> improve for merge.
> please check here for it: 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/src/main/java/org/javascud/extensions/cxf/LoadBalanceFeature.java
>   
> you can find the project in 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CXF-3070) add a LoadBalanceFeature for CXF

[Daniel Kulp (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp updated CXF-3070:
-

Fix Version/s: (was: NeedMoreInfo)
   2.3.4

> add a LoadBalanceFeature for CXF
> 
>
> Key: CXF-3070
> URL: https://issues.apache.org/jira/browse/CXF-3070
> Project: CXF
>  Issue Type: Wish
>  Components: Core
>Affects Versions: 2.3
>Reporter: scud
>Assignee: Christian Schneider
> Fix For: 2.3.4
>
>
> I write some code to implement the LoadBalanceFeature upon FailOverFeatuer. 
> (many code is from FailoverFeature and realted classes)
> I hope someone can merge the feature into CXF, it need some review and 
> improve for merge.
> please check here for it: 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/src/main/java/org/javascud/extensions/cxf/LoadBalanceFeature.java
>   
> you can find the project in 
> http://code.google.com/p/cnscud/source/browse/trunk/extensions/cxf/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang reassigned CXF-3421:
-

Assignee: Freeman Fang

> HTTP conduit settigs not used fro downloading WSDL
> --
>
> Key: CXF-3421
> URL: https://issues.apache.org/jira/browse/CXF-3421
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 2.3.3
> Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM 
> secured.
>Reporter: frantisek.ko...@gmail.com
>Assignee: Freeman Fang
>Priority: Critical
>
> I have WS on server with NTLM secured HTTP connection. If wsdlLocation is 
> set, CXF tries to download WSDL but does not take HTTP conduit settings into 
> account. Server returned HTTP response code: 401 for URL: 
> http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl
> WSDL is on location
>  wsdlLocation="http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl";
> And I use service address as http-conduit name like 
>  name="http://172.16.55.55:555/WebServices/WebServiceABC.asmx";
> This does not work
>  serviceClass="SERVICE_CLASS"
> wsdlLocation="WSDL_LOCATION"
> serviceName="s:SERVICE_NAME"
> xmlns:s="SERVICE_NAMESPACE"
> >
> 
>  name="SERVICE_ADDRESS">
>  ConnectionTimeout="31234" />
> 
> NAME
> PASSWORD
> 
> 
> This works (but does not try to download WSDL)
>  name="SERVICE_NAME"
> address="SERVICE_ADDRESS"
> serviceClass="SERVICE_CLASS"
> >
> 
>  name="SERVICE_ADDRESS">
>  ConnectionTimeout="31234" />
> 
> NAME
> PASSWORD
> 
> 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL

[Freeman Fang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CXF-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved CXF-3421.
---

Resolution: Won't Fix

> HTTP conduit settigs not used fro downloading WSDL
> --
>
> Key: CXF-3421
> URL: https://issues.apache.org/jira/browse/CXF-3421
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 2.3.3
> Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM 
> secured.
>Reporter: frantisek.ko...@gmail.com
>Assignee: Freeman Fang
>Priority: Critical
>
> I have WS on server with NTLM secured HTTP connection. If wsdlLocation is 
> set, CXF tries to download WSDL but does not take HTTP conduit settings into 
> account. Server returned HTTP response code: 401 for URL: 
> http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl
> WSDL is on location
>  wsdlLocation="http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl";
> And I use service address as http-conduit name like 
>  name="http://172.16.55.55:555/WebServices/WebServiceABC.asmx";
> This does not work
>  serviceClass="SERVICE_CLASS"
> wsdlLocation="WSDL_LOCATION"
> serviceName="s:SERVICE_NAME"
> xmlns:s="SERVICE_NAMESPACE"
> >
> 
>  name="SERVICE_ADDRESS">
>  ConnectionTimeout="31234" />
> 
> NAME
> PASSWORD
> 
> 
> This works (but does not try to download WSDL)
>  name="SERVICE_NAME"
> address="SERVICE_ADDRESS"
> serviceClass="SERVICE_CLASS"
> >
> 
>  name="SERVICE_ADDRESS">
>  ConnectionTimeout="31234" />
> 
> NAME
> PASSWORD
> 
> 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CXF-3421) HTTP conduit settigs not used fro downloading WSDL

[Freeman Fang (JIRA)]

[ 
https://issues.apache.org/jira/browse/CXF-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040089#comment-13040089
 ] 

Freeman Fang commented on CXF-3421:
---

Hi,

Could you use something like
https://172.16.55.55:555/.*";>
instead? the "https" prefix here is important, it should work, we actually have 
a testcase[1] which demonstrate using https download remote wsdl, take a look 
at the testHttpsWrappedContinuations method.
And the configuration file with that test[2]
[1]https://svn.apache.org/repos/asf/cxf/trunk/systests/transports/src/test/java/org/apache/cxf/systest/http_jetty/continuations/ClientServerWrappedContinuationTest.java
[2]https://svn.apache.org/repos/asf/cxf/trunk/systests/transports/src/test/java/org/apache/cxf/systest/http_jetty/continuations/cxf_https.xml

Freeman

> HTTP conduit settigs not used fro downloading WSDL
> --
>
> Key: CXF-3421
> URL: https://issues.apache.org/jira/browse/CXF-3421
> Project: CXF
>  Issue Type: Bug
>  Components: Transports
>Affects Versions: 2.3.3
> Environment: CXF client on Jetty, Java 6. WS server in .NET NTLM 
> secured.
>Reporter: frantisek.ko...@gmail.com
>Assignee: Freeman Fang
>Priority: Critical
>
> I have WS on server with NTLM secured HTTP connection. If wsdlLocation is 
> set, CXF tries to download WSDL but does not take HTTP conduit settings into 
> account. Server returned HTTP response code: 401 for URL: 
> http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl
> WSDL is on location
>  wsdlLocation="http://172.16.55.55:555/WebServices/WebServiceABC.asmx?wsdl";
> And I use service address as http-conduit name like 
>  name="http://172.16.55.55:555/WebServices/WebServiceABC.asmx";
> This does not work
>  serviceClass="SERVICE_CLASS"
> wsdlLocation="WSDL_LOCATION"
> serviceName="s:SERVICE_NAME"
> xmlns:s="SERVICE_NAMESPACE"
> >
> 
>  name="SERVICE_ADDRESS">
>  ConnectionTimeout="31234" />
> 
> NAME
> PASSWORD
> 
> 
> This works (but does not try to download WSDL)
>  name="SERVICE_NAME"
> address="SERVICE_ADDRESS"
> serviceClass="SERVICE_CLASS"
> >
> 
>  name="SERVICE_ADDRESS">
>  ConnectionTimeout="31234" />
> 
> NAME
> PASSWORD
> 
> 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira