[jira] [Updated] (CXF-4482) AttachmentSerializer puts an extra new line

[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Kadyrko updated CXF-4482: Attachment: crlf.jpg > AttachmentSerializer puts an extra new line >

[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra new line

[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500899#comment-13500899 ] Kirill Kadyrko commented on CXF-4482: - Hi, I think we should definitely use CRLFCRLF to

[jira] [Resolved] (CXF-4482) AttachmentSerializer puts an extra new line

[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-4482. --- Resolution: Fixed Fix Version/s: (was: 2.4.10) (was: 2.5.6)

[jira] [Commented] (CXF-4482) AttachmentSerializer puts an extra new line

[ https://issues.apache.org/jira/browse/CXF-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500523#comment-13500523 ] Hagen Raab commented on CXF-4482: - This fix introduces a new problem. The LF (w/o CR) leads

[jira] [Comment Edited] (CXF-4571) javax.ws.rs.WebApplicationException when creating jaxrs:server under OSGi Blueprint

[ https://issues.apache.org/jira/browse/CXF-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500448#comment-13500448 ] Sergey Beryozkin edited comment on CXF-4571 at 11/19/12 6:10 PM: -

[jira] [Commented] (CXF-4571) javax.ws.rs.WebApplicationException when creating jaxrs:server under OSGi Blueprint

[ https://issues.apache.org/jira/browse/CXF-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500448#comment-13500448 ] Sergey Beryozkin commented on CXF-4571: --- Dan also updated jsr339 spec bundle to export

[jira] [Commented] (CXF-3898) Socket Read Timeout - Couldn't parse stream - Runtime Exception - JOnAS 5.1

[ https://issues.apache.org/jira/browse/CXF-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500423#comment-13500423 ] Anamica R commented on CXF-3898: I have similar problem but the only difference is using Tom

[jira] [Commented] (CXF-4571) javax.ws.rs.WebApplicationException when creating jaxrs:server under OSGi Blueprint

[ https://issues.apache.org/jira/browse/CXF-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500408#comment-13500408 ] Sergey Beryozkin commented on CXF-4571: --- After playing with modifying export packages

[jira] [Commented] (CXF-4571) javax.ws.rs.WebApplicationException when creating jaxrs:server under OSGi Blueprint

[ https://issues.apache.org/jira/browse/CXF-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500234#comment-13500234 ] Sergey Beryozkin commented on CXF-4571: --- Found it, never mind > javax

[jira] [Commented] (CXF-4571) javax.ws.rs.WebApplicationException when creating jaxrs:server under OSGi Blueprint

[ https://issues.apache.org/jira/browse/CXF-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500230#comment-13500230 ] Sergey Beryozkin commented on CXF-4571: --- where is patched org.joda/joda-money/0.6.solu

[jira] [Commented] (DOSGI-11) dOSGi creates new databinding instance instead of using a spring-loaded databinding if available

[ https://issues.apache.org/jira/browse/DOSGI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500201#comment-13500201 ] Christian Schneider commented on DOSGI-11: -- Sounds good .. thx Sergey

[jira] [Reopened] (DOSGI-11) dOSGi creates new databinding instance instead of using a spring-loaded databinding if available

[ https://issues.apache.org/jira/browse/DOSGI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reopened DOSGI-11: --- > dOSGi creates new databinding instance instead of using a spring-loaded > databinding if ava

[jira] [Assigned] (DOSGI-11) dOSGi creates new databinding instance instead of using a spring-loaded databinding if available

[ https://issues.apache.org/jira/browse/DOSGI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reassigned DOSGI-11: - Assignee: Sergey Beryozkin > dOSGi creates new databinding instance instead of using a

[jira] [Commented] (DOSGI-11) dOSGi creates new databinding instance instead of using a spring-loaded databinding if available

[ https://issues.apache.org/jira/browse/DOSGI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500199#comment-13500199 ] Sergey Beryozkin commented on DOSGI-11: --- User was expecting a CXF DataBinding configur

[jira] [Commented] (DOSGI-106) DSW can not get a handle to OSGI HttpService when a single-bundle distribution is installed

[ https://issues.apache.org/jira/browse/DOSGI-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500191#comment-13500191 ] Sergey Beryozkin commented on DOSGI-106: Single bundle activator runs via the activ

[jira] [Commented] (DOSGI-106) DSW can not get a handle to OSGI HttpService when a single-bundle distribution is installed

[ https://issues.apache.org/jira/browse/DOSGI-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500190#comment-13500190 ] Sergey Beryozkin commented on DOSGI-106: Yes, can confirm it is still an issue; afa

[jira] [Created] (DOSGI-145) Multiple services using HTTP Service and published from the same bundle do not work

Sergey Beryozkin created DOSGI-145: -- Summary: Multiple services using HTTP Service and published from the same bundle do not work Key: DOSGI-145 URL: https://issues.apache.org/jira/browse/DOSGI-145

[jira] [Resolved] (DOSGI-109) NullPointerException in ToloplogyManager during bundle stop

[ https://issues.apache.org/jira/browse/DOSGI-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-109. --- Resolution: Fixed Fix Version/s: 1.4 Closing the issue as it should be fixed du

[jira] [Resolved] (DOSGI-125) The dead lock in TopologyManagerImport

[ https://issues.apache.org/jira/browse/DOSGI-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-125. --- Resolution: Fixed Fix Version/s: 1.4 Assignee: Christian Schneider Res

[jira] [Resolved] (DOSGI-92) Exception : Applying intent: SOAP via binding config

[ https://issues.apache.org/jira/browse/DOSGI-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-92. -- Resolution: Fixed Fix Version/s: 1.4 Assignee: Christian Schneider This s

[jira] [Assigned] (DOSGI-10) Spring schema handling (intents) doesn't work properly for the single-bundle case

[ https://issues.apache.org/jira/browse/DOSGI-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned DOSGI-10: Assignee: Christian Schneider > Spring schema handling (intents) doesn't work pro

[jira] [Resolved] (DOSGI-10) Spring schema handling (intents) doesn't work properly for the single-bundle case

[ https://issues.apache.org/jira/browse/DOSGI-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-10. -- Resolution: Fixed This should be obsolete now as spring dm is not used anymore.

[jira] [Updated] (DOSGI-10) Spring schema handling (intents) doesn't work properly for the single-bundle case

[ https://issues.apache.org/jira/browse/DOSGI-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated DOSGI-10: - Fix Version/s: 1.4 > Spring schema handling (intents) doesn't work properly for the sin

[jira] [Resolved] (DOSGI-90) Do not use/assume that endpoint.id is an address

[ https://issues.apache.org/jira/browse/DOSGI-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-90. -- Resolution: Fixed The problem is in: org.apache.cxf.dosgi.dsw.handlers.HttpServiceConfigu

[jira] [Commented] (CXF-4571) javax.ws.rs.WebApplicationException when creating jaxrs:server under OSGi Blueprint

[ https://issues.apache.org/jira/browse/CXF-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500117#comment-13500117 ] Sergey Beryozkin commented on CXF-4571: --- Hi, I believe that either updating the spec b

[jira] [Assigned] (CXF-4571) javax.ws.rs.WebApplicationException when creating jaxrs:server under OSGi Blueprint

[ https://issues.apache.org/jira/browse/CXF-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin reassigned CXF-4571: - Assignee: Sergey Beryozkin > javax.ws.rs.WebApplicationException when creating jaxrs:se

[jira] [Updated] (DOSGI-90) Do not use/assume that endpoint.id is an address

[ https://issues.apache.org/jira/browse/DOSGI-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated DOSGI-90: - Fix Version/s: 1.4 > Do not use/assume that endpoint.id is an address > ---

[jira] [Assigned] (DOSGI-90) Do not use/assume that endpoint.id is an address

[ https://issues.apache.org/jira/browse/DOSGI-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned DOSGI-90: Assignee: Christian Schneider > Do not use/assume that endpoint.id is an address

[jira] [Resolved] (DOSGI-63) The discovery can be used be used before the connection to the server is completely established

[ https://issues.apache.org/jira/browse/DOSGI-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-63. -- Resolution: Fixed I have changed the startup to only really start the discovery once the

[jira] [Closed] (DOSGI-11) dOSGi creates new databinding instance instead of using a spring-loaded databinding if available

[ https://issues.apache.org/jira/browse/DOSGI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider closed DOSGI-11. Resolution: Incomplete Closing the issue as we did not get more informations till now. Please

[jira] [Assigned] (DOSGI-63) The discovery can be used be used before the connection to the server is completely established

[ https://issues.apache.org/jira/browse/DOSGI-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned DOSGI-63: Assignee: Christian Schneider (was: David Bosschaert) > The discovery can be use

[jira] [Updated] (DOSGI-63) The discovery can be used be used before the connection to the server is completely established

[ https://issues.apache.org/jira/browse/DOSGI-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated DOSGI-63: - Fix Version/s: 1.4 > The discovery can be used be used before the connection to the ser

[jira] [Commented] (DOSGI-106) DSW can not get a handle to OSGI HttpService when a single-bundle distribution is installed

[ https://issues.apache.org/jira/browse/DOSGI-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500093#comment-13500093 ] Christian Schneider commented on DOSGI-106: --- Is this still open? I think the sing

[jira] [Commented] (DOSGI-144) can not deploy CXF 1.3.1 on Virgo Tomcat 3.5.RELEASE

[ https://issues.apache.org/jira/browse/DOSGI-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500092#comment-13500092 ] Christian Schneider commented on DOSGI-144: --- Can you try the current trunk snapsh

[jira] [Resolved] (DOSGI-115) Use Spring DM and Eclipse Gemini Blueprint with DOSGi

[ https://issues.apache.org/jira/browse/DOSGI-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-115. --- Resolution: Fixed I will switch the loading of intents to a OSGi service aproach in DO

[jira] [Commented] (DOSGI-86) Decouple DOSGi DSW from Spring DM.

[ https://issues.apache.org/jira/browse/DOSGI-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500090#comment-13500090 ] Christian Schneider commented on DOSGI-86: -- I now replaced the spring dm loading of

[jira] [Resolved] (DOSGI-132) Switch logging at runtime to pax logging

[ https://issues.apache.org/jira/browse/DOSGI-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-132. --- Resolution: Fixed Multibundle distro now uses pax logging. For the single bundle distr

[jira] [Assigned] (DOSGI-132) Switch logging at runtime to pax logging

[ https://issues.apache.org/jira/browse/DOSGI-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider reassigned DOSGI-132: - Assignee: Christian Schneider > Switch logging at runtime to pax logging > ---

[jira] [Resolved] (DOSGI-143) Remove all repos except for apache snapshot and central

[ https://issues.apache.org/jira/browse/DOSGI-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-143. --- Resolution: Fixed 1410610 16.11.2012 23:45:47, by cschneider DOSGI-143 Removing all re

[jira] [Resolved] (DOSGI-142) Upgrade CXF to 2.7.0

[ https://issues.apache.org/jira/browse/DOSGI-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved DOSGI-142. --- Resolution: Fixed > Upgrade CXF to 2.7.0 > > >

Issues with Attachments: week of 2012-11-19

CXF - Monday, November 19, 2012 4 Issues with Attachments (sorted oldest to newest) [CXF-4530] Checkstyle 5.6 no longer supports the DoubleCheckedLocking - Created: 2012-10-01 - Updated: 2012-11-04 - Type: Bug - Fix Versions: [] - Reporter: Jason Pell