[jira] Commented: (AMQCPP-83) Integration tests fail for openwire

    [
https://issues.apache.org/activemq/browse/AMQCPP-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38939
] 

Nathan Mittler commented on AMQCPP-83:
--------------------------------------

When the broker warning appears, I was seeing that we were getting in a message before the message listener
was set.  This appears to be a timing issue, as if I add a nominal sleep before we ack the message, no warning appears.

I've reorganized the way consumers acknowledge messages to be more in keeping with the Java code.  We now do
not acknowledge the message until it's been delivered to the client (so until they setMessageListener is
called in the case of the durable test).

This seems to adjust the timing so that the warning does not appear at the broker (at least for OS X).

> Integration tests fail for openwire
> -----------------------------------
>
>                 Key: AMQCPP-83
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-83
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Openwire
>    Affects Versions: 2.0
>            Reporter: Nathan Mittler
>         Assigned To: Nathan Mittler
>             Fix For: 2.0
>

Re: Command and DataStructure

That's because the transport layer in general can transport any kind
of Object.  This generalization is being taken advantage by our AMQP
implementation.  It allows our transport layer to work with AMQP
command packets which do NOT extend from the DataStructure class.

What might be useful is if we use generics in the Transport interface
so that it can become more type safe without loosing the current
flexibility.

On 3/31/07, Allesmallachen <Spammails@...> wrote:
>
> Hi,
> I was wondering why you don't use the Command and the DataStructure
> interfaces directly in the method signatures of the parts of ActiveMQ that
> are concerend with sending and receiving commands and marshalling data. All
> signatures use the generic Object type. In the implementations that are
> available, those objects get cast into Commands or Datastructres anyway. So
> why not making this explicit in the interface definitions as well?
>
> best regards,
> Christian
> --
> View this message in context: http://www.nabble.com/Command-and-DataStructure-tf3497340s2354.html#a9768534
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>

--

-- 
Regards,
Hiram

Re: [VOTE] Release Apache ActiveMQ 4.1.1 (RC 2)

On Mar 31, 2007, at 1:49 PM, Jason Dillon wrote:

> Is the crypto legal stuff handled?  I see that there is an entry on
> the crypto page ( http://www.apache.org/licenses/exports/ ) now for
> AMQ.

Yep, should be set on that front.

-Brian

Parameters in request get lost when using servlet: protocol

[result][vote] Move CachingSource to cocoon-core

Reinhard Poetz wrote:
> 
> Because of dependencies on the event-cache block, the caching source was 
> added to the repository block when it moved out from scratchpad. After 
> some refactorings I should be able now to move it to cocoon-core without 
> having to add any new depenendencies there.
> 
> As a caching source is of general interest for many of our users (see 
> several requests on the users list) I want to propose to move it to 
> cocoon-core.

The proposal has been accepted. It got 7 binding +1 votes and no -1. I will move 
  the CachingSource to core as soon as time permits.

--

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

[results][vote] Make status code attribute of seriailzers expandable

Reinhard Poetz wrote:

> I propose making the status code attribute of serializers expandable. 
> This makes it easier to provide REST style services with Cocoon that 
> make use of the different meanings of status codes.

The proposal has been accepted. It got 9 binding +1 votes and no -1. I will 
implement it as soon as time permits.

--

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Cocoon bylaws (was Re: svn commit: r524734 - in /cocoon/trunk/commons/bylaws: ./ bylaws.txt)

As this commit message shows, I have started to collect notes about what should 
become part of our bylaws (project guidelines or whatever we will call them). In 
the past we had many dicussions that would not have been necessary if we had had 
  them. With this mail I want to invite everybody else to add her or his ideas 
to it!

The aim of my effort is not to invent new rules, but to make the rules, which 
are already in use, explicit.

My personal plan is to start the brainstorming and discussions now and create 
the actual Bylaws document and vote on it at Q3.

Reinhard

reinhard <at> apache.org wrote:
> Author: reinhard
> Date: Sun Apr  1 23:55:50 2007
> New Revision: 524734
> 
> URL: http://svn.apache.org/viewvc?view=rev&rev=524734
> Log:
> some ideas what should go into more specific Bylaws than we have today
> 
> Added:
>     cocoon/trunk/commons/bylaws/
>     cocoon/trunk/commons/bylaws/bylaws.txt   (with props)
> 
> Added: cocoon/trunk/commons/bylaws/bylaws.txt
> URL: http://svn.apache.org/viewvc/cocoon/trunk/commons/bylaws/bylaws.txt?view=auto&rev=524734
> ==============================================================================
> --- cocoon/trunk/commons/bylaws/bylaws.txt (added)
> +++ cocoon/trunk/commons/bylaws/bylaws.txt Sun Apr  1 23:55:50 2007
> @@ -0,0 +1,64 @@
> +(Note: This is a summary of ideas about what could/should be part of our bylaws some time in the future. 
> +Of course a vote is required to make them official.)
> +
> +BYLAWS
> +********************************************************************************
> +
> +MISSION
> + - XML pipelines (narrow sense)
> + - web application framework (broader sense)
> +
> +ROLES AND RESPONSIBILITIES
> + - see http://www.apache.org/foundation/how-it-works.html
> + - each Cocoon committer is invited to join the PMC membership. There is NO vote required.
> + - each committer/PMC member can request to change into an emeritus status. coming back does NOT require a
further vote
> +   sending a message to private <at> cocoon.apache.org is enough
> +
> +GIVING CREDIT TO CONTRIBUTORS
> + - http://marc.info/?l=xml-cocoon-dev&m=117394069331060&w=2
> + - non committers: changes docs
> +
> +RELEASING
> + - procedure
> + - formal technical requirements (binaries, sources, javadocs, checksums, gpg singed, license,
license header)
> +
> +STATUS
> + - each project has a changes.xml
> +   * detailed log about what has changed
> +   * give credit to contributors
> +   
> +COMMIT RIGHTS
> + - (of course) all Cocoon committers
> + - additionally all Excalibur, Forrest and Lenya committers too
> + - Cocoon committers have commit  rights for: Forrest, Lenya
> +
> +VERSIONING
> + - meaning of major, minor, patch level
> + - block compatibility
> + - library upgrades
> + 
> +SUB PROJECTS AND BLOCKS
> + - what is a sub project
> + - what's the difference of a block and a sub project
> + - voting rules for setting up sub projects
> +
> +VOTING
> + - committer votings: consensus, at least three +1
> + - release votings: majority, at least three +1
> + - vetoes
> + - a vote has to stay open for at least 72 hours
> + - votes have to be done in public. The only exception is security issues.
> + 
> + -> copying what Ant/Forrest developed?
> + 
> + Questions:
> + - What happens in the case of three +3 and two -1? Is this enough for
> + - What happens in the case of a tie? (chair decision?)
> +  
> + 
> +COMMUNICATION
> + - purpose of dev/users/private/doc/commits 
> +
> +REPORTING
> + - PMC chair drafts the report and sends it to private@, 48 hours for review before
> +   sending it to the board
> \ No newline at end of file

[2.2] Logging

Vadim Gritsenko wrote:
> the only thing which is 'broken' compared with 2.1 
> is logging.

... which forces the user to recompile. Do we want or do we have to accept this? 
  Although the change is a very simple one, it would be better to have a 
deprecation period to give our users some more time.

Is there any chance to make the Spring beanfactory acknowledging the 
LoggingEnabled interface?

Second question: Do we consider component implementations (EHCacheStore, 
CachingImpl, etc.) being public API or their interfaces only?

--

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Re: [VOTE] Release Apache ActiveMQ 4.1.1 (RC 2)

Cool, so _official_ release soonish then?

Help get G 1.2 out... release AMQ 4.1.1 

--jason

On Apr 1, 2007, at 9:09 PM, Brian McCallister wrote:

>
> On Mar 31, 2007, at 1:49 PM, Jason Dillon wrote:
>
>> Is the crypto legal stuff handled?  I see that there is an entry on
>> the crypto page ( http://www.apache.org/licenses/exports/ ) now for
>> AMQ.
>
> Yep, should be set on that front.
>
> -Brian
>
>
>

poll on jcr query usage

Hi all,

my apologies for cross posting, but I'd like to get as many responses as 
possible from any kind of jackrabbit users on this topic.

I'd like to know what the preferred query language is that you are using, just 
to get a feeling where further development should go regarding query support in 
jackrabbit and JCR in general.

[ ] I primarily use XPath
[ ] I primarily use SQL
[ ] I use both XPath and SQL

and on a related topic:

If there was an API to construct a query I would ...

[ ] ... use it /instead/ of the existing XPath or SQL languages.
[ ] ... use it only for occasionally.
[ ] ... not use it at all.

Thank you for participating.

regards
  marcel