+1
On Wed, Aug 15, 2012 at 9:20 AM, Daniel Kulp wrote:
>
> We've resolved over 80 issues since 2.6.1 and we're a little overdue for a
> release.
>
> List of issues:
> 2.4.9
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12321666
> 2.5.5
> https://issues.apach
Hi,
If you can append a more detailed stack trace, it would be more helpful.
Also if you can append a simple wsdl which can reproduce this NPE, we can do a
quick test from our side.
Freeman
－
Freeman Fang
FuseSource
Email:ff...@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Hi,
For the CCE in JAXBDataBinding, I think it's from two
javax.xml.bind.JAXBContext object somehow loaded by different classloaders.
Most likely one is from the jaxb api bundle you installed, one from the system
bundle 0, so you can comment out javax.xml.bind* package from system bundle 0
Thanks for the info, I have used some hook methods to make the API work,
for the packages exported by the system packages, according to the wiring
rule in OSGi spec, CXF bundles will automatically wire to the latest
jaxws2.2 and jaxb 2.2 bundle.
The issue blocked me is that the JAXBDataBinding cla
Hi,
I am using the 2.6.2-SNAPSHOT:
2.6.2-20120813.071134-43
in Eclipse with m2e but I get the following error when I run package.
[ERROR] Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:2.6.2-SNAPSHOT:wsdl2java
(myproject-generate-sources) on project cope:
Execution myproject-gener
Hi,
As I mentioned, you can't simply wrap spec jar like jaxb-api, as SPI mechanism
doesn't work in OSGi container. So the spec jar need have OSGiLocator stuff, so
that it can load jaxb-impl bundles from OSGi container, servicemix already
provide such spec jars with OSGiLocator, so you better us
I noticed one of the 2.6.2 unit tests is failing under windows.
Failed tests:
testMtomWithFileName(org.apache.cxf.systest.mtom.ClientMtomXopTest):
can't get file name expected: but
was:
It seems that the file name extraction in
AttachmentsUtils.createMtomAttachmentFromDH is not working under
win
(Resending...) +1
Glen
--
View this message in context:
http://cxf.547215.n5.nabble.com/VOTE-Release-Apache-CXF-2-4-9-2-5-5-2-6-2-tp5712591p5712650.html
Sent from the cxf-dev mailing list archive at Nabble.com.
That's it.
OK, here is my +1.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weib
I use Equonix as the OSGi container, and now I have installed all the
required bundles, and all of them are resovled and started correctly. Guess
that this issue is not related to the actual container is used. even turn
to Karaf (a high level infrasture on the native OSGi runtime), the issue
may st
+1,
-- Ulhas
On 15 Aug 2012, at 02:20, Daniel Kulp wrote:
>
> We've resolved over 80 issues since 2.6.1 and we're a little overdue for a
> release.
>
> List of issues:
> 2.4.9
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12321666
> 2.5.5
> https://issu
+1
Freeman
－
Freeman Fang
FuseSource
Email:ff...@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
On 2012-8-15, at 上午9:20, Daniel Kulp wrote:
>
> We've resolved ov
Willem,
There are changes to Camel needed which I've done on trunk, but haven't yet had
the time to back port to the fixes branches.
Most notably are revs 1371861 and 1371861.
Will work on porting those back later today.
Dan
On Aug 15, 2012, at 5:53 AM, Willem jiang wrote:
> Hi,
>
> I
+1.
Colm.
On Wed, Aug 15, 2012 at 10:29 AM, Christian Schneider <
ch...@die-schneider.net> wrote:
> +1
>
> Christian
>
> Am 15.08.2012 03:20, schrieb Daniel Kulp:
>
> We've resolved over 80 issues since 2.6.1 and we're a little overdue for
>> a release.
>>
>> List of issues:
>> 2.4.9
>> https:/
+1
Christian
Am 15.08.2012 03:20, schrieb Daniel Kulp:
We've resolved over 80 issues since 2.6.1 and we're a little overdue for a
release.
List of issues:
2.4.9
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12321666
2.5.5
https://issues.apache.org/jira/secu
Hi,
Which OSGi container you are using?
To use CXF in OSGi container, a lot of effort need be done, jaxb-api and
jaxb-impl bundle is one of them, but not all. Servicemix wrap lots of
bundles(spec bundle like jaxb-api need use OSGiLocator stuff) and karaf
provide a provisioning mechanism(feat
Hi,
I ran some tests in camel with CXF 2.6.2 and 2.5.5.
All the CXF related tests are passed with CXF 2.6.2 in the Camel trunk.
But I got some error when running the test with CXF 2.5.5 and Camel 2.9.x in
camel-cxf module.
The test failures are
Failed tests:
testDispatchPayload(org.apache.ca
+1
David
On 15 August 2012 02:20, Daniel Kulp wrote:
>
> We've resolved over 80 issues since 2.6.1 and we're a little overdue for a
> release.
>
> List of issues:
> 2.4.9
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12321666
> 2.5.5
> https://issues.apache
Hi,
+1
Sergey
On 15/08/12 04:20, Daniel Kulp wrote:
We've resolved over 80 issues since 2.6.1 and we're a little overdue for a
release.
List of issues:
2.4.9
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511&version=12321666
2.5.5
https://issues.apache.org/jira/secure
I am trying to use CXF 2.6.1 in OSGi environment, as jdk 6 does not ship
the latest JAXB API and implementation, so deployed a JAXB 2.2 API and a
repackaged RI JAXB impl as bundles. While running my application, it shows
ClassCastException one line 392 of JAXBDataBinding. Think the problem is
that,
20 matches
Mail list logo
