[
https://issues.apache.org/jira/browse/PROTON-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143282#comment-14143282
]
Hiram Chirino commented on PROTON-694:
--
Seems ok to me.
> splitting
Hiram Chirino created PROTON-518:
Summary: Add SASL hostname getter/setter
Key: PROTON-518
URL: https://issues.apache.org/jira/browse/PROTON-518
Project: Qpid Proton
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893586#comment-13893586
]
Hiram Chirino commented on PROTON-474:
--
Any thoughts how to resolve those outb
Hiram Chirino created PROTON-509:
Summary: Proton build fails on OS X 10.9
Key: PROTON-509
URL: https://issues.apache.org/jira/browse/PROTON-509
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-474:
-
Attachment: (was: PROTON-474.patch)
> Incorrect mapping of TTL to JMSExpiration in
[
https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-474:
-
Attachment: PROTON-474-v2.patch
Attaching new patch that incorporates Robbie Gemmell's com
[
https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889734#comment-13889734
]
Hiram Chirino commented on PROTON-474:
--
Linking to an AMQ issue that depends on
[
https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-474:
-
Attachment: PROTON-474.patch
Attaching updated patch that also does a similar mapping on the
[
https://issues.apache.org/jira/browse/PROTON-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-507:
-
Comment: was deleted
(was: Attaching update version of the patch that also does a similar
[
https://issues.apache.org/jira/browse/PROTON-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-507:
-
Attachment: (was: PROTON-507.patch)
> [proton-c] Idle time out should advertise half
[
https://issues.apache.org/jira/browse/PROTON-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-507:
-
Attachment: PROTON-507.patch
Attaching update version of the patch that also does a similar
[
https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841318#comment-13841318
]
Hiram Chirino commented on PROTON-474:
--
Looks good to me.
> Incorrect map
[
https://issues.apache.org/jira/browse/PROTON-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795462#comment-13795462
]
Hiram Chirino commented on PROTON-440:
--
Works for me on OS X now.
> Messen
[
https://issues.apache.org/jira/browse/PROTON-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-440:
-
Attachment: PROTON-440.patch
Attaching patch that fixes the issue. Seems like blocking selects
[
https://issues.apache.org/jira/browse/PROTON-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792723#comment-13792723
]
Hiram Chirino commented on PROTON-440:
--
Test fails
Hiram Chirino created PROTON-440:
Summary: MessengerImpl tests fail on OSX
Key: PROTON-440
URL: https://issues.apache.org/jira/browse/PROTON-440
Project: Qpid Proton
Issue Type: Bug
cent API
> call.
>
>
> I would be happy to submit a patch to make it work this way, and see what
> people think - but not if I am merely exhibiting my own philosophical
> ignorance here.
>
>
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fuseso
if we're going to expect people to compile against it. I'm not
> sure what the right answers to these questions are, but propose that we
> resolve this Proton/ProtonJ/ProtonC stuff first.
>
>
> Phil
>
>
>
> On 8 August 2013 17:45, Hiram Chirino wrote:
>
[
https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-396:
-
Attachment: PROTON-396-v2.patch
Attaching simpler fix.
> Proton Messen
[
https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-396:
-
Attachment: (was: PROTON-396.patch)
> Proton Messenger should configure the SNI head
[
https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733772#comment-13733772
]
Hiram Chirino commented on PROTON-396:
--
calling pn_ssl_set_peer_hostname after
ays detrimental as it creates a
>> barrier to entry for all users when most don't care about the flexibility
>> it offers (at least right now) and if they do care about that flexibility
>> it is easy enough for them to build their own. In fact modulo exception
>> handling it is really just one extra line of code:
>>
>> Class impl = Class.forName(System.getProperty("blah"));
>> Proton p = (Proton) impl.newInstance();
>>
>> So I'd personally say go for the simple interface/impl split pattern that
>> everyone knows and is used to and don't worry about a generic discovery
>> mechanism until we actually have enough implementations for it to be
>> warranted.
>>
>> --Rafael
>>
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
blog: Hiram Chirino's Bit Mojo
decision of choosing a particular
> implementation after weighing the pros and cons of it.
>
> Rajith
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
blog: Hiram Chirino's Bit Mojo
[
https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-396:
-
Attachment: PROTON-396.patch
Attaching a patch that fixes this issue.
> Pro
[
https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733564#comment-13733564
]
Hiram Chirino commented on PROTON-396:
--
If you want to keep pn_ssl_t opaque, th
Hiram Chirino created PROTON-396:
Summary: Proton Messenger should configure the SNI headers on it's
TLS connections so that those connections can be routed by SNI aware proxies.
Key: PROTON-396
URL:
Hiram Chirino created PROTON-392:
Summary: proton-jni build fails
Key: PROTON-392
URL: https://issues.apache.org/jira/browse/PROTON-392
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-390:
-
Description:
openssl.c produces lots of warnings.
/Users/chirino/sandbox/qpid-proton/proton-c
Hiram Chirino created PROTON-390:
Summary: Suppress or Fix the warnings openssl.c produce
Key: PROTON-390
URL: https://issues.apache.org/jira/browse/PROTON-390
Project: Qpid Proton
Issue
on p = new ProtonJ();
or
Proton p = new ProtonC();
where ProtonJ and ProtonC are in the respective implementation jars.
if folks really want to make it configurable, they can easily build an
if statement to pick the impl that they desire.
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@
[
https://issues.apache.org/jira/browse/PROTON-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-361:
-
Attachment: PROTON-361.patch
attaching patch to fix issue.
> [proto
Hiram Chirino created PROTON-361:
Summary: [proton-j][hawtdispatch] transport is silently discarding
errors while connecting
Key: PROTON-361
URL: https://issues.apache.org/jira/browse/PROTON-361
[
https://issues.apache.org/jira/browse/PROTON-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-360:
-
Attachment: PROTON-360.patch
attaching patch that resolves this issue
Hiram Chirino created PROTON-360:
Summary: [proton-j][hawtdispatch] Add support for ANONYMOUS SASL
Key: PROTON-360
URL: https://issues.apache.org/jira/browse/PROTON-360
Project: Qpid Proton
situation with transactions (local
> and distributed) in proton?
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Local-transactions-support-tp7594523p7594550.html
> Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
--
Hir
[
https://issues.apache.org/jira/browse/PROTON-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-340:
-
Attachment: PROTON-340.patch
Attaching fix for the bug.
> AMQP to
Hiram Chirino created PROTON-340:
Summary: AMQP to JMS transformer fails to properly map AMQP
specific property types like UnsignedInteger
Key: PROTON-340
URL: https://issues.apache.org/jira/browse/PROTON-340
;> > On 23 May 2013 14:45, Phil Harvey wrote:
>> >
>> > > Hi Hiram,
>> > >
>> > > Did you ever get a reply about this (e.g. on the IRC channel)?
>> > >
>> > > I think Rafi created the 0.4 release candidate but I don't know if
>> &
I don't see the 0.4 release in maven central:
http://repo2.maven.org/maven2/org/apache/qpid/proton-api/
Can you guy make sure that a maven deployment is part of the release process?
--
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
[
https://issues.apache.org/jira/browse/PROTON-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631728#comment-13631728
]
Hiram Chirino commented on PROTON-292:
--
yep.
> [proton-hawtd
[
https://issues.apache.org/jira/browse/PROTON-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-293:
-
Attachment: PROTON-293.patch
attaching fix.
> [proton-hawtdispatch] Use m
[
https://issues.apache.org/jira/browse/PROTON-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-292:
-
Attachment: PROTON-293.patch
> [proton-hawtdispatch] avoid printing debug info to
[
https://issues.apache.org/jira/browse/PROTON-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-292:
-
Attachment: (was: PROTON-293.patch)
> [proton-hawtdispatch] avoid printing debug info
Hiram Chirino created PROTON-293:
Summary: [proton-hawtdispatch] Use more conservative initial
message size estimates.
Key: PROTON-293
URL: https://issues.apache.org/jira/browse/PROTON-293
Project
[
https://issues.apache.org/jira/browse/PROTON-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-292:
-
Attachment: PROTON-292.patch
attaching fix.
> [proton-hawtdispatch] av
Hiram Chirino created PROTON-292:
Summary: [proton-hawtdispatch] avoid printing debug info to the
console.
Key: PROTON-292
URL: https://issues.apache.org/jira/browse/PROTON-292
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-271:
-
Attachment: PROTON-271.patch
Attaching patch that fixes the issue.
> pro
Hiram Chirino created PROTON-271:
Summary: proton-hawtdispatch transport not properly encoding PLAIN
sasl user/password.
Key: PROTON-271
URL: https://issues.apache.org/jira/browse/PROTON-271
Project
alked about recently --
> looking forward to reviews.
>
>
>
> Phil - thanks for the markdown idea -- it's extremely cool.
>
>
>
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchir...@redhat.com | fusesource.com | redhat.com*
*skype: hiramchirino | twitter:
[
https://issues.apache.org/jira/browse/PROTON-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582225#comment-13582225
]
Hiram Chirino commented on PROTON-244:
--
Hi, could you post how you were using
[
https://issues.apache.org/jira/browse/PROTON-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino reopened PROTON-126:
--
So you don't agree that it should return void?
> Sender.send should ret
ld be a useful addition to the current "unit" test
> framework - I don't believe we do any canned interopt testing yet.
>
> Thoughts?
>
> -K
>
>
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchir...@redhat.com | fusesource.com | redhat.com*
*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*
*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
;
>
> On 28 January 2013 11:40, Rafael Schloming wrote:
>
> > Would it be better if we were to deprecate the constructors and remove
> them
> > in a future release?
> >
> > --Rafael
> >
> > On Fri, Jan 25, 2013 at 6:25 PM, Hiram Chirino > >w
n 25, 2013 at 6:25 PM, Hiram Chirino >wrote:
>
> > I was hoping I could upgrade to newer proton versions without having to
> > change my client code, since I was not planning on using the JNI impl
> > anyways.
> >
> >
> > On Fri, Jan 25, 2013 at 4:
flection, I'm coming round to the idea that keeping these
> constructors
> >> public will place unreasonable restrictions on our ability to evolve the
> >> implementation whilst keeping the API stable.
> >>
> >> Phil
> >>
> >>
> >>
[
https://issues.apache.org/jira/browse/PROTON-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-156:
-
Attachment: PROTON-156.patch
attaching patch that fixes this issue.
> [proto
t()
> > > {
> > > return new TransportImpl();
> > > }
> > >
> > >
> > > ... etc
> > >
> > > Code that requires the extended functionality offered by the pure Java
> > > implementation can thus instanti
>
> https://svn.apache.org/repos/asf/qpid/proton/branches/jni-binding/proton-c/bindings/java/jni/src/main/java/org/apache/qpid/proton/engine/jni/JNIEngineFactory.java
>
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchir...@redhat.com | fusesource.com | redhat.com*
*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*
*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
n-j. Does anyone object to
> >> putting one in the proton-c directory as well?
> >>
> >> -Ted
> >>
> >>
>
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchir...@redhat.com | fusesource.com | redhat.com*
*skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino>
*
*blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>*
+1
On Mon, Dec 17, 2012 at 6:08 PM, Ted Ross wrote:
> We've added a contrib directory under proton-j. Does anyone object to
> putting one in the proton-c directory as well?
>
> -Ted
>
>
--
**
*Hiram Chirino*
*Engineering | Red Hat, Inc.*
*hchir...@redha
[
https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-186:
-
Attachment: (was: PROTON-186.patch)
> Message encode should always return the number
[
https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-186:
-
Attachment: PROTON-186v2.patch
> Message encode should always return the number of by
[
https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-186:
-
Attachment: PROTON-186v2.patch
Attaching updated patch that does not change the current encode
[
https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-186:
-
Attachment: (was: PROTON-186v2.patch)
> Message encode should always return the num
[
https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-186:
-
Attachment: PROTON-186.patch
Attaching patch which implements this for proton-j
Hiram Chirino created PROTON-186:
Summary: Message encode should always return the number of bytes
needed to fully encode the message
Key: PROTON-186
URL: https://issues.apache.org/jira/browse/PROTON-186
[
https://issues.apache.org/jira/browse/PROTON-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-186:
-
Issue Type: Improvement (was: Bug)
> Message encode should always return the number
[
https://issues.apache.org/jira/browse/PROTON-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-182:
-
Attachment: PROTON-182.patch
Attaching patch which generates the keys using java so that they
Hiram Chirino created PROTON-182:
Summary: [proton-j] SSL tests fail with
org.bouncycastle.openssl.PEMException: problem parsing ENCRYPTED PRIVATE KEY:
java.security.InvalidKeyException: Illegal key size
Key: PROTON-182
-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:
>
> >
[
https://issues.apache.org/jira/browse/PROTON-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-175:
-
Attachment: PROTON-175.patch
attaching patch that removed them
Hiram Chirino created PROTON-175:
Summary: engine.Outcome and sub interfaces not used by proton-j,
they should be deleted.
Key: PROTON-175
URL: https://issues.apache.org/jira/browse/PROTON-175
[
https://issues.apache.org/jira/browse/PROTON-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-174:
-
Attachment: PROTON-174.patch
Attaching patch to fix the issue.
> [proto
Hiram Chirino created PROTON-174:
Summary: [proton-j contrib] Ehance the JMS mapping logic to
support carrying type info for the JMSDestination and JMSReplyTo, also support
mapping the JMSX properties in AMQP Application properties
Hiram Chirino created PROTON-173:
Summary: Message annotations not properly encoded
Key: PROTON-173
URL: https://issues.apache.org/jira/browse/PROTON-173
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-173:
-
Attachment: PROTON-173.patch
Attaching patch with fix.
> Message annotati
[
https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-168:
-
Attachment: deprecate-pragma.patch
Attaching a patch that uses a pragma to disable the ssl
[
https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506767#comment-13506767
]
Hiram Chirino commented on PROTON-168:
--
Hi Andrew,
Warnings would still be on,
[
https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506551#comment-13506551
]
Hiram Chirino commented on PROTON-168:
--
OS X is generating too many warnings to
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/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-168:
-
Attachment: SO_NOSIGPIPE.patch
Attaching patch that sets the SO_NOSIGPIPE socket option when on
[
https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-168:
-
Attachment: nowerror.patch
and here's a patch to disable -Werror o
[
https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-168:
-
Attachment: clock.patch
Here's a patch that incorporates Mr Goldstein's OS X cloc
[
https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505963#comment-13505963
]
Hiram Chirino commented on PROTON-168:
--
Running cmake on OS X now result
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505576#comment-13505576
]
Hiram Chirino edited comment on PROTON-154 at 11/28/12 3:5
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505576#comment-13505576
]
Hiram Chirino commented on PROTON-154:
--
Hi Rafael, that's a different is
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-154:
-
Attachment: PROTON-154-test.patch
Attaching test case to demonstrates the error
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-154:
-
Component/s: proton-c
> link attach, detach, attach sequence on single session does
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505388#comment-13505388
]
Hiram Chirino commented on PROTON-154:
--
Python test case also verifies that this
[
https://issues.apache.org/jira/browse/PROTON-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-168:
-
Attachment: PROTON-168-v2.patch
Attaching a slightly updated version of the proton-168.patch so
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-154:
-
Attachment: PROTON-154.patch
attaching possible fix.
> link attach, det
[
https://issues.apache.org/jira/browse/PROTON-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved PROTON-35.
-
Resolution: Fixed
Fix Version/s: 0.3
PROTON-140 implemented the multi-module build
[
https://issues.apache.org/jira/browse/PROTON-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-22:
Attachment: PROTON-22-v5.patch
Attaching new impl.. it now lands in the contrib dir
[
https://issues.apache.org/jira/browse/PROTON-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503819#comment-13503819
]
Hiram Chirino commented on PROTON-22:
-
Ok now that PROTON-140 has been impleme
[
https://issues.apache.org/jira/browse/PROTON-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-22:
Attachment: (was: PROTON-22-v4.patch)
> Add optional module that provides HawtDispa
[
https://issues.apache.org/jira/browse/PROTON-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-22:
Attachment: (was: PROTON-22-v3.patch)
> Add optional module that provides HawtDispa
[
https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-65:
Attachment: PROTON-65.patch
Attaching new re-worked impl. It now lands under the contrib dir
[
https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503802#comment-13503802
]
Hiram Chirino commented on PROTON-65:
-
Now that PROTON-140 has been applied,
[
https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-65:
Attachment: (was: PROTON-65.patch)
> Provide a AMQP 1.0 Message to JMS Message mapp
[
https://issues.apache.org/jira/browse/PROTON-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-140:
-
Attachment: PROTON-140.patch
Attaching patch to tweak the new poms a bit. Child poms don't
1 - 100 of 246 matches
Mail list logo
