Re: [VOTE] Release Apache CXF 2.1.2

[jim ma]

+1
Jim

On Wed, Aug 13, 2008 at 2:57 PM, Ulhas Bhole <[EMAIL PROTECTED]> wrote:

> +1,
>
> --Ulhas
>
> Daniel Kulp wrote:
>
>> This is a vote to release CXF 2.1.2
>>
>> Once again, there have been a bunch of bug fixes and enhancements that
>> have been done compared to the 2.1.1 release.   Over 67 JIRA issues
>> are resolved for 2.1.2.
>> List of issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313268&styleName=Html&projectId=12310511&Create=Create
>>
>> The staging area is at:
>> http://people.apache.org/~dkulp/stage_cxf/2.1.2
>>
>> The distributions are in the "dist" directory. The "maven" directory
>> contains the stuff that will by pushed to the central repository.
>>
>> This release is tagged at:
>> http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.1.2
>>
>>
>> Here is my +1.   The vote will be open here for at least 72 hours.
>>
>>
>>
>>
>
> 
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>

Re: [VOTE] Release Apache CXF 2.1.2

[Willem Jiang]

+1

Willem
Daniel Kulp wrote:

This is a vote to release CXF 2.1.2

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.1 release.   Over 67 JIRA issues
are resolved for 2.1.2.  


List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313268&styleName=Html&projectId=12310511&Create=Create

The staging area is at:
http://people.apache.org/~dkulp/stage_cxf/2.1.2

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.1.2


Here is my +1.   The vote will be open here for at least 72 hours.


  

Re: [VOTE] Release Apache CXF 2.1.2

[Freeman Fang]

+1

Freeman

Daniel Kulp wrote:

This is a vote to release CXF 2.1.2

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.1 release.   Over 67 JIRA issues
are resolved for 2.1.2.  


List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313268&styleName=Html&projectId=12310511&Create=Create

The staging area is at:
http://people.apache.org/~dkulp/stage_cxf/2.1.2

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.1.2


Here is my +1.   The vote will be open here for at least 72 hours.


  

RE: [VOTE] Release Apache CXF 2.1.2

[Emeka Kanu]

+1 

-Original Message-
From: Freeman Fang [mailto:[EMAIL PROTECTED] 
Sent: 13 August 2008 11:34
To: dev@cxf.apache.org
Subject: Re: [VOTE] Release Apache CXF 2.1.2

+1

Freeman

Daniel Kulp wrote:
> This is a vote to release CXF 2.1.2
>
> Once again, there have been a bunch of bug fixes and enhancements that
> have been done compared to the 2.1.1 release.   Over 67 JIRA issues
> are resolved for 2.1.2.  
>
> List of issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=1231326
> 8&styleName=Html&projectId=12310511&Create=Create
>
> The staging area is at:
> http://people.apache.org/~dkulp/stage_cxf/2.1.2
>
> The distributions are in the "dist" directory. The "maven" directory 
> contains the stuff that will by pushed to the central repository.
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.1.2
>
>
> Here is my +1.   The vote will be open here for at least 72 hours.
>
>
>   

RE: [VOTE] Release Apache CXF 2.1.2

[O'Callaghan, Sean]

+1

-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: 12 August 2008 22:17
To: CXF Dev
Subject: [VOTE] Release Apache CXF 2.1.2




This is a vote to release CXF 2.1.2

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.1 release.   Over 67 JIRA issues
are resolved for 2.1.2.  

List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313268&;
styleName=Html&projectId=12310511&Create=Create

The staging area is at:
http://people.apache.org/~dkulp/stage_cxf/2.1.2

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.1.2


Here is my +1.   The vote will be open here for at least 72 hours.


-- 
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog


IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

Re: [VOTE] Release Apache CXF 2.1.2

[Eoghan Glynn]

+1

Daniel Kulp wrote:


This is a vote to release CXF 2.1.2

Once again, there have been a bunch of bug fixes and enhancements that
have been done compared to the 2.1.1 release.   Over 67 JIRA issues
are resolved for 2.1.2.  


List of issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12313268&styleName=Html&projectId=12310511&Create=Create

The staging area is at:
http://people.apache.org/~dkulp/stage_cxf/2.1.2

The distributions are in the "dist" directory. The "maven" directory
contains the stuff that will by pushed to the central repository.

This release is tagged at:
http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.1.2


Here is my +1.   The vote will be open here for at least 72 hours.





IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

Bug in handling JMS TextMessage encoding (see CXF-1668)?

[Christian Schneider]

In the issue CXF-1668 Eduard reported that CXF uses the system encoding 
for JMS Messages. This is wrong as most times messages are to be 
transmitted using UTF-8.

I want to build a patch for this issue but need some conceptional help.

When we receive a message from JMS how can we decide which encoding it 
uses? Should I try to use the   tag? Where is a good 
point to add this functionality? Should I add it in handleResponse like 
Eduard suggested?


Best regards

Christian

https://issues.apache.org/jira/browse/CXF-1668

Re: Bug in handling JMS TextMessage encoding (see CXF-1668)?

[Ulhas Bhole]

Hi Christian,
The place Eduard mentioned in Jira is correct. I was looking at this 
JIRA sometime back but had the same problem of how to determine encoding 
type. JMS TextMessage doesn't contain any encoding information so it's 
hard to know what is the encoding of the contents.


Regards,

Ulhas Bhole

Christian Schneider wrote:
In the issue CXF-1668 Eduard reported that CXF uses the system 
encoding for JMS Messages. This is wrong as most times messages are to 
be transmitted using UTF-8.

I want to build a patch for this issue but need some conceptional help.

When we receive a message from JMS how can we decide which encoding it 
uses? Should I try to use the   tag? Where is a 
good point to add this functionality? Should I add it in 
handleResponse like Eduard suggested?


Best regards

Christian

https://issues.apache.org/jira/browse/CXF-1668



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

Re: Bug in handling JMS TextMessage encoding (see CXF-1668)?

[Ulhas Bhole]

Hi Christian,
One option (bit limited though) is to use file.encoding property and if 
it's set use that for encoding. In this case the application need to 
pass in -Dfile.encoding property to the JVM. However, this doesn't 
guarantee the encoding used will always be same as the one that original 
message was encoded in.


Regards,

Ulhas Bhole

Ulhas Bhole wrote:

Hi Christian,
The place Eduard mentioned in Jira is correct. I was looking at this 
JIRA sometime back but had the same problem of how to determine 
encoding type. JMS TextMessage doesn't contain any encoding 
information so it's hard to know what is the encoding of the contents.


Regards,

Ulhas Bhole

Christian Schneider wrote:
In the issue CXF-1668 Eduard reported that CXF uses the system 
encoding for JMS Messages. This is wrong as most times messages are 
to be transmitted using UTF-8.

I want to build a patch for this issue but need some conceptional help.

When we receive a message from JMS how can we decide which encoding 
it uses? Should I try to use the   tag? Where is a 
good point to add this functionality? Should I add it in 
handleResponse like Eduard suggested?


Best regards

Christian

https://issues.apache.org/jira/browse/CXF-1668



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland



IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

mvn -Pfastinstall failure with current trunk

[Benson Margulies]

[INFO] FastInfosetting 0 resource
[INFO] [jaxb:generate {execution: default}]
[INFO] failure in the XJC task. Use the Ant -verbose switch for more details
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] unrecognized parameter -Xdv
[INFO] 
[INFO] Trace
unrecognized parameter -Xdv
at com.sun.tools.xjc.XJC2Task._doXJC(XJC2Task.java:409)
at com.sun.tools.xjc.XJC2Task.doXJC(XJC2Task.java:397)
at com.sun.tools.xjc.XJC2Task.execute(XJC2Task.java:332)
at com.sun.tools.xjc.maven2.XJCMojo.execute(XJCMojo.java:310)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: com.sun.tools.xjc.BadCommandLineException: unrecognized
parameter -Xdv
at com.sun.tools.xjc.Options.parseArguments(Options.java:664)
at com.sun.tools.xjc.XJC2Task._doXJC(XJC2Task.java:407)
... 21 more
--- Nested Exception ---
com.sun.tools.xjc.BadCommandLineException: unrecognized parameter -Xdv
at com.sun.tools.xjc.Options.parseArguments(Options.java:664)
at com.sun.tools.xjc.XJC2Task._doXJC(XJC2Task.java:407)
at com.sun.tools.xjc.XJC2Task.doXJC(XJC2Task.java:397)
at com.sun.tools.xjc.XJC2Task.execute(XJC2Task.java:332)
at com.sun.tools.xjc.maven2.XJCMojo.execute(XJCMojo.java:310)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] 
[INFO] Total time: 21 seconds
[INFO] Finished at: Wed Aug 13 20:42:26 EDT 2008
[INFO] Final Memory: 36M/64M
[INFO] 
puck%