-
75. Re: Integration with AS6
timfox Feb 23, 2010 5:13 AM (in response to timfox)Can someone give a revised estimate for completion of this task?
It seems to be turning into another one of those "tasks without end"
-
76. Re: Integration with AS6
ataylor Feb 23, 2010 5:40 AM (in response to timfox)for my part, sorting the messaging test suite, i should be done for tomorrow. I am not sure of what other tasks need doing. Clebert can you summarize whate else is left, we should try and get this done this week. -
77. Re: Integration with AS6
jason.greene Feb 23, 2010 9:16 AM (in response to timfox)timfox wrote:
Can someone give a revised estimate for completion of this task?
It seems to be turning into another one of those "tasks without end"
Also, I need to know if this can make AS6 M3. The cutoff is March 22.
Thanks!
-
78. Re: Integration with AS6
timfox Feb 23, 2010 9:19 AM (in response to jason.greene)Well, if we can't get in done by March 22 we should all look for different jobs
The original estimate for the task was 2-3 weeks. That was about 6 weeks ago.
I'm assuming it will take another week at the most.
Clebert/Andy can you confirm?
-
79. Re: Integration with AS6
clebert.suconic Feb 23, 2010 9:28 AM (in response to timfox)If this new profile services thing (that appeared now at the end) doesn't drag us more time, I expect to finish cleaning tests by tomorrow or Thursday early in the morning.. and have it merged on AS6/trunk by the end of the week. And i will need another week for TCK.
That's well beyond my expectations also. I can't move on the AS codebase very well.. everything is heavy... lots of new/old things not well documented.. so it wasn't being very clean how to do things.
Even at the worse case scenario it would be done before March-22.
-
80. Re: Integration with AS6
timfox Feb 23, 2010 9:30 AM (in response to clebert.suconic)Can Andy/Jeff start on the TCK in parallel? -
81. Re: Integration with AS6
clebert.suconic Feb 24, 2010 11:10 PM (in response to timfox)There's one thing that was true already for JBoss Messaging 1.4.
DLQ handlging is done at HornetQ at the server, not on the resource adapter.
There are a few tests with configs like this:
<invoker-proxy-bindings> <invoker-proxy-binding> <name>my-message-driven-bean</name> <invoker-mbean>default</invoker-mbean> <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> <proxy-factory-config> <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> <MaximumSize>1</MaximumSize> <MaxMessages>1</MaxMessages> <!--ForceClearOnShutdown>true</ForceClearOnShutdown> <ForceClearAttempts>5</ForceClearAttempts> <ForceClearInterval>500</ForceClearInterval--> <MDBConfig> <ReconnectIntervalSec>10</ReconnectIntervalSec> <DLQConfig> <DestinationQueue>queue/DLQ</DestinationQueue> <MaxTimesRedelivered>10</MaxTimesRedelivered> <TimeToLive>0</TimeToLive> </DLQConfig> </MDBConfig> </proxy-factory-config> </invoker-proxy-binding> </invoker-proxy-bindings>
That's doesn't make sense any more. How should we proceed? -
82. Re: Integration with AS6
timfox Feb 25, 2010 4:55 AM (in response to clebert.suconic)Those tests won't be valid then. -
83. Re: Integration with AS6
timfox Feb 25, 2010 4:56 AM (in response to timfox)Do we even use that config at all? Isn't that just old stuff used with the old JCA adapter? -
84. Re: Integration with AS6
clebert.suconic Feb 25, 2010 8:26 AM (in response to timfox)Yes.. that's old stuff and I'm removing from the 10 tests I found this.
What I'm referring to them is:
- Should AS remove support for this on the proxy at all and throw an exception if this is used
- Or should we then just ignore this and throw a big warning on the logs.
That's a question more for AS guys.
-
85. Re: Integration with AS6
timfox Feb 25, 2010 8:35 AM (in response to clebert.suconic)I don't think this is stuff is used at all in HornetQ, so how could we throw a warning? -
86. Re: Integration with AS6
timfox Feb 25, 2010 8:36 AM (in response to timfox)The old DLQ functionality would still be applicable if the user was using the generic JCA adapter to interface with some other messaging system, it's just not used by HornetQ. -
87. Re: Integration with AS6
clebert.suconic Feb 25, 2010 8:52 AM (in response to timfox)I said this question is for AS guys...
So, this question is.. should the AS guys throw an exception if this used? (I said we as we're all JBoss )
This is set on the proxy anyway which is somewhat weird.
In regard to what affect HornetQ, I am removing this from the testsuite.
-
88. Re: Integration with AS6
timfox Feb 25, 2010 9:07 AM (in response to clebert.suconic)clebert.suconic@jboss.com wrote:
I said this question is for AS guys...
So, this question is.. should the AS guys throw an exception if this used? (I said we as we're all JBoss )
I don't think so.
The old JCA adaptor is still usable in JBoss AS, that's what you'd often use if you were integrating other non HornetQ messaging systems.
Like I say, it's just not used by HornetQ. But can be used for other reasons.
-
89. Re: Integration with AS6
brian.stansberry Feb 25, 2010 10:32 AM (in response to clebert.suconic)Please don't just remove these; please disable them (by including them in the badtest.excludes patternset in testsuite/build.xml). And then create a critical M3 JIRA for us to sort them out.