[
https://issues.apache.org/jira/browse/QPIDJMS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218834#comment-15218834
]
Hiram Chirino commented on QPIDJMS-164:
---
PR available for this at h
Hiram Chirino created QPIDJMS-164:
-
Summary: Provide an OSGi bundle for the Qpid JMS client
Key: QPIDJMS-164
URL: https://issues.apache.org/jira/browse/QPIDJMS-164
Project: Qpid JMS
Issue
voidable.
>> > We can make exception for slf4j, but even then my preference is to use
>> JDK
>> > logging.
>> >
>>
>> If only JDK logging weren't so horrible :-)
>>
>
> Agreed, hence my reason to make an exception for slf4j :D
The Acti
ect. Then again, ActiveMQ also has dup detection logic, a subsequent
send /w the same message id would get dropped.
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchir...@redhat.com | fusesource.com | redhat.com*
*skype: hiramchirino | twitter: @hiramchirino<http://twitt
have a configurable way to
> ensure the send-impl doesn't override the message id.
> I think we will be seeing such use cases in the near future.
>
> ---------
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
t; >
> > This addresses bug PROTON-121.
> > https://issues.apache.org/jira/browse/PROTON-121
> >
> >
> > Diffs
> > -
> >
> > /proton/trunk/proton-c/src/codec/codec.c 1417656
> > /proton/trunk/proton-c/src/framing/framing.c 1417656
&
-c, but there's definitely fixes/improvements I'd like to get out. I
> think kicking off 0.3 sometime in the next couple of weeks would be good to
> shoot for and doable from my side.
>
> --Rafael
>
> On Thu, Nov 29, 2012 at 9:16 AM, Hiram Chirino >wrote:
>
> >
e/QPID-4483:
> Commit: http://svn.apache.org/viewvc?rev=1415148&view=rev
>
> Alex and I worked on the tests together and have indicated our review to
> that effect on the JIRAs.
>
> Thanks,
> Robbie
>
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchi
[
https://issues.apache.org/jira/browse/QPID-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4454:
Attachment: (was: QPID-4454.patch)
> [AMQP 1.0 JMS Client] getJMSReplyTo() != the value
[
https://issues.apache.org/jira/browse/QPID-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4454:
Attachment: QPID-4454-v2.patch
Updating patch. Was missing a new file.
> [A
[
https://issues.apache.org/jira/browse/QPID-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4454:
Attachment: QPID-4454.patch
Attaching patch which implements a fix.
> [AMQP
Hi guys,
proton-j has really mad some major advancements in stability/correctness
since the 0.2 release. I'm really happy with the current state of proton's
trunk. What are the chances we can cut a 0.3 release soon?
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchir...@
[
https://issues.apache.org/jira/browse/QPID-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4457:
Attachment: QPID-4457.patch
Attaching patch file the adds the joram test suite. Still needs work
Hiram Chirino created QPID-4457:
---
Summary: Test the against Joram JMS test suite.
Key: QPID-4457
URL: https://issues.apache.org/jira/browse/QPID-4457
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4455:
Attachment: QPID-4455.patch
attaching possible fix.
> Queue browsers were
Hiram Chirino created QPID-4455:
---
Summary: Queue browsers were not returning jms messages
Key: QPID-4455
URL: https://issues.apache.org/jira/browse/QPID-4455
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4454:
Component/s: Java Client
> getJMSReplyTo() != the value set with setJMSRepl
Hiram Chirino created QPID-4454:
---
Summary: getJMSReplyTo() != the value set with setJMSReplyTo()
Key: QPID-4454
URL: https://issues.apache.org/jira/browse/QPID-4454
Project: Qpid
Issue Type
[
https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4453:
Attachment: QPID-4453.patch
attaching possible fix.
> ObjectMessage /w no b
Hiram Chirino created QPID-4453:
---
Summary: ObjectMessage /w no body improperly converted to an AMQP
message.
Key: QPID-4453
URL: https://issues.apache.org/jira/browse/QPID-4453
Project: Qpid
I see that the binaries have been staged to nexus at:
https://repository.apache.org/content/repositories/orgapacheqpid-028/org/apache/qpid/qpid-proton/0.2/
Are you guys planning on holding a vote and releasing them?
On Tue, Nov 6, 2012 at 9:43 AM, Hiram Chirino wrote:
> Hi,
>
> Now
[
https://issues.apache.org/jira/browse/QPID-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4411:
Attachment: (was: QPID-4411-v2.patch)
> QPID JMS QueueBrowser should defer getting messa
[
https://issues.apache.org/jira/browse/QPID-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4411:
Attachment: QPID-4411-v3.patch
Updated patch so that we make sure the server validate selector on
[
https://issues.apache.org/jira/browse/QPID-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4412:
Attachment: (was: QPID-4412.patch)
> QPID Java: ReceivingLinkEndpoint.isDrained result
[
https://issues.apache.org/jira/browse/QPID-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4412:
Attachment: QPID-4412-v2.patch
Better fix.
> QPID J
[
https://issues.apache.org/jira/browse/QPID-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4412:
Description: the delivery count was not being updated when a Flow was
received.
Summary
Hiram Chirino created QPID-4412:
---
Summary: QPID Java: ReceivingLinkEndpoint.isDrained should check
against the _remoteTransferCount instead of the local delivery count.
Key: QPID-4412
URL: https://issues.apache.org
[
https://issues.apache.org/jira/browse/QPID-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4412:
Attachment: QPID-4412.patch
> QPID Java: ReceivingLinkEndpoint.isDrained should check agai
[
https://issues.apache.org/jira/browse/QPID-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4411:
Attachment: QPID-4411-v2.patch
attaching cleaned up version of the patch.
> Q
[
https://issues.apache.org/jira/browse/QPID-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4411:
Attachment: (was: QPID-4411.patch)
> QPID JMS QueueBrowser should defer getting messa
[
https://issues.apache.org/jira/browse/QPID-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4411:
Attachment: QPID-4411.patch
Attaching patch that resolves this issue.
> QPID
Hiram Chirino created QPID-4411:
---
Summary: QPID JMS QueueBrowser should defer getting messages until
getEnumeration() is called.
Key: QPID-4411
URL: https://issues.apache.org/jira/browse/QPID-4411
[
https://issues.apache.org/jira/browse/QPID-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4365:
Attachment: QPID-4365.patch
Attaching patch that implements.
> Support setting
Hiram Chirino created QPID-4365:
---
Summary: Support setting the client-id after the JMS connection
has been created.
Key: QPID-4365
URL: https://issues.apache.org/jira/browse/QPID-4365
Project: Qpid
old-style config).
> >>>> I've used maven (involuntarily) for a while now, and will avoid it at
> >>>> all costs in the future.
> >>>>
> >>>> Full disclosure: I'm old enough to wish everything was just done with
> >>>> gm
> > For additional commands, e-mail: dev-h...@qpid.apache.org
> >
>
>
>
> --
> Joseph B. Ottinger
> http://enigmastation.com
> Ça en vaut la peine.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>
>
--
**
*Hiram Chirino*
*Software Fellow | FuseSource Corp.*
*chir...@fusesource.com | fusesource.com*
*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*
*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
*
*
*
*
; Yes, my one concern would be that we could offer 'full' AMQP support,
> including any extensions such as filters, or transaction coordination
> protocols, management mechanisms that may be defined in ongoing standards
> work.
Yep. Apollo would be happy to pulled in t
On Thu, Jul 19, 2012 at 11:14 AM, Gordon Sim wrote:
> On 07/19/2012 03:48 PM, Hiram Chirino wrote:
>
>> I'm interested in using Proton in the ActiveMQ's Apollo message broker.
>>
>
> Great!
>
> I don't know how closely you are following this thread,
27;s or Tibco's protocol to AMQP. The NMS apis
already kinda popular in the .NET world when folks are interested in
maintaining some vender neutrality.
[1]: http://activemq.apache.org/nms/
Yes this probably one of those projects like Proton which would
have benefitted from being a T
n't imply you are the one making the silly argument.
> Rather I used your point about growing the community and deciding
> later, as a basis for addressing the community in general.
>
> ---------
> To unsubscribe, e-mail: de
lidate
> the C codec against the files you posted. If you have any interest in
> donating the test data and java version of the dump utility, I could
> wire it all into the test suite so that we can make sure there are no
> regressions.
>
> --Rafael
>
> On Tue, 2012-07-03 at 15
[
https://issues.apache.org/jira/browse/QPID-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated QPID-4106:
Attachment: QPID-4106.patch
Attaching patch which contains the protocol dump utility and also some
Hiram Chirino created QPID-4106:
---
Summary: Add a protocol dump utility for java
Key: QPID-4106
URL: https://issues.apache.org/jira/browse/QPID-4106
Project: Qpid
Issue Type: New Feature
199945912
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>
>
--
**
*Hiram Chirino*
*Software Fellow | FuseSource Corp.*
*chir...@fu
un the same frames
> >> through proton-c you might get more of a clue what's going on, and I
> >> could definitely help out a bit more. Otherwise Rob should be back at
> >> work late Tuesday/early Wednesday.
> >>
> >> --Rafael
> >>
> >> On Mon, 20
ckout the
test case, just my git branch from github:
https://github.com/chirino/proton
and then run maven in the base directory using:
mvn compile exec:java
--
**
*Hiram Chirino*
*Software Fellow | FuseSource Corp.*
*chir...@fusesource.com | fusesource.com*
*skype: hiramchirino | tw
Jun 11, 2010 at 3:53 PM, Hiram Chirino wrote:
>
>> Picking Github also means picking a more decentralized collaboration
>> model where there is no 'owner' or group of owners that folks have to
>> get blessing from to start contributing in a meaningful way.
Picking Github also means picking a more decentralized collaboration
model where there is no 'owner' or group of owners that folks have to
get blessing from to start contributing in a meaningful way. Any one
can fork at any time and contribute. Worthy contributions will be
merged by the other fork
On Fri, Jun 11, 2010 at 9:17 AM, Marnie McCormack
wrote:
> The starting point for this discussion centred on the development of core
> libraries that the Qpid/ActiveMQ projects could use for 1-0. (Clearly I'm
> interested in how this might work for the Qpid implementation of AMQP.)
>
I think bruc
BTW, I've created the mailing list on google groups that was suggested
on earlier posts:
Group home page: http://groups.google.com/group/amqp-client-dev
I think it would be a good idea to move this discussion there since
this thread is getting cross posted across a couple groups who's
interest le
I personally think that the incubator is one of the worst places to
build a project/community. Apache has recognized this.. that's why
there's Apache Labs. The incubator works when you have an existing
project and are working towards transitioning it to a full fledged
project.
On Thu, Jun 10, 20
BTW.. I do hope that once the project gets established and stabilizes,
we take the time to re-evaluate if the community that has formed is
large and diverse enough to thrive in as an Apache standalone
project... and then at that time figure out how to bring it back..
perhaps into qpid.
On Thu, Jun
My preference would be Github + Google Groups. Since the point of
taking it outside of Apache is to encourage external folks to more
easily participate, using Git as the SCM is a no brainer since anyone
can fork and contribute at anytime without needing to 'earn commit
karma'. And naturally, I'd
Hi,
I'm interested in using the python qpid client with jython. I've
gotten pretty far but I've had to make some slight modifications to
get it to run.
Basically,
1) a couple of "from __future__ import generators" were needed.
2) socket.SSLType is not defined so a try .. except AttributeError wa
54 matches
Mail list logo
