Nabble - lingo - dev

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-08-13T02:02:46Z

This e-mail address has been disabled because of spam. Please contact us via a different e-mail address. Thanks.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-08-13T02:00:30Z

Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-08-13T01:58:22Z

Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-08-13T01:56:13Z

Re: Re: Re: Re: Re: Re: Re: Active?

2008-08-13T01:54:04Z

Re: Re: Re: Re: Re: Re: Active?

2008-08-13T01:51:54Z

Re: Re: Re: Re: Re: Active?

2008-08-13T01:49:47Z

Re: Re: Re: Re: Active?

2008-08-13T01:47:39Z

Re: Re: Re: Active?

2008-08-13T01:45:28Z

Re: Re: Active?

2008-08-13T01:43:19Z

Re: Active?

2008-08-13T01:41:01Z

Sure! Wanna submit a patch to a JIRA?

BTW I've been adding most of the Lingo features to Apache Camel recently...
http://activemq.apache.org/camel/spring-remoting.html
http://activemq.apache.org/camel/using-exchange-pattern-annotations.html

2008/5/27 Andy Malakov <nabblespam@...>:

>
> Hi James,
>
> Is it possible to submit bugfixes to Lingo?
>
> For example, it seems that MultiplexingRequestor does not shutdown
> ScheduledThreadPoolExecutor on close().
>
> Regards,
> Andy Malakov
>
> <code>
> @Override
> public void close () throws JMSException {
> super.close();
>
> if (executor != null)
> executor.shutdown();
> }
> </code>
>
>
> James.Strachan wrote:
>>
>> On 30/10/2007, SynapticFire <apache@...> wrote:
>>
>> Its kinda finished really - it does what it says on the tin :). I know
>> of lots of folks using Lingo in production today.
>> ....
>>
>
> --
> View this message in context: http://www.nabble.com/Active--tp13497072p17493431.html
> Sent from the lingo - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

--
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:45Z

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:33Z

Re: Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:26Z

Re: Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:55:13Z

Re: Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:52:33Z

Re: Re: Re: Re: Re: Re: Active?

2008-05-27T10:49:55Z

Re: Re: Re: Re: Re: Active?

2008-05-27T10:42:22Z

Re: Re: Re: Re: Active?

2008-05-27T10:24:11Z

Re: Re: Re: Active?

2008-05-27T09:54:11Z

Re: Re: Active?

2008-05-27T09:27:50Z

Re: Active?

2008-05-27T08:42:54Z

Hi James,

Is it possible to submit bugfixes to Lingo?

For example, it seems that MultiplexingRequestor does not shutdown ScheduledThreadPoolExecutor on close().

Regards,
Andy Malakov

<code>
@Override
public void close () throws JMSException {
super.close();

if (executor != null)
executor.shutdown();
}
</code>

James.Strachan wrote:

On 30/10/2007, SynapticFire <apache@synapticfire.net> wrote:

Its kinda finished really - it does what it says on the tin :). I know
of lots of folks using Lingo in production today.
....

Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:29:40Z

Re: Re: Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:28:54Z

Re: Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:27:49Z

Re: Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:26:51Z

Re: Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:24:23Z

Re: Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:23:03Z

Re: Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:22:37Z

Re: Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:22:08Z

Re: Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:21:30Z

Re: [jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:20:23Z

[jira] Updated: (LINGO-10) Add support for JMS 1.0.2

2008-02-27T00:18:29Z

[ http://jira.codehaus.org/browse/LINGO-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radek Porazil updated LINGO-10:
-------------------------------

Attachment: MultiplexingRequestor102.java
JmsProducerConfig102.java

I had to use JMS 1.0.2 for one of my projects on WLS8.1 and I somehow solved the issue (it is not particularly well documented and it even might not be complete as my application uses Lingo just as infrastructure).
However, I believe, that attached files might be good start for people facing the same problem. Add the attached files to your project, do some refactoring if you need to and of course modify your Spring application context :

<bean id="producerConfig" class="org.lingo102.JmsProducerConfig102"/>

<bean id="jmsRequestor" class="org.lingo102.MultiplexingRequestor102" factory-method="newInstance">
<constructor-arg ref="jmsFactory"/>
<constructor-arg ref="requestDestination"/>
</bean>

> Add support for JMS 1.0.2
> -------------------------
>
> Key: LINGO-10
> URL: http://jira.codehaus.org/browse/LINGO-10
> Project: Lingo
> Issue Type: New Feature
> Affects Versions: 1.0
> Reporter: James Webster
> Fix For: 1.4
>
> Attachments: JmsProducerConfig102.java, MultiplexingRequestor102.java
>
>
> Lingo does not support JMS 1.0.2; or at least, the DefaultJmsProducer doesn't.
> DefaultJmsProducer.newInstance(ConnectionFactory) will only work with a 1.1 version ConnectionFactory .
> Maybe there should be a DefaultJms102Producer as well?

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jira] Commented: (LINGO-44) MultiplexingRequestor leaves lingering threads after close() called

2007-12-07T10:55:57Z

[ http://jira.codehaus.org/browse/LINGO-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116196 ]

elan commented on LINGO-44:
---------------------------

Which release will have this critical bug fix?

> MultiplexingRequestor leaves lingering threads after close() called
> -------------------------------------------------------------------
>
> Key: LINGO-44
> URL: http://jira.codehaus.org/browse/LINGO-44
> Project: Lingo
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: ActiveMQ 4.1.1, Windows XP
> Reporter: Jason Koch
> Priority: Critical
> Attachments: MultiplexingRequestor.java
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The MultiplexingRequestor class does not have a close() method to close the ScheduledThreadPoolExecutor. This leaves non-daemon threads hanging around and thus applications will not quit until System.exit() is called (causing Tomcat applications exporting Lingo services and standard Java apps calling Lingo services to hang forever on shutdown).
> Attached is an updated MultiplexingRequestor class that fixes the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Active?

2007-10-31T03:44:57Z

On 30/10/2007, SynapticFire <apache@...> wrote:
> Is this project still active? I've not seen any activity for some time.
> The last commit was 12 months ago (except for a minor pom change).

Its kinda finished really - it does what it says on the tin :). I know
of lots of folks using Lingo in production today.

As it happens we've mostly been working on a different project that
focusses on more general integration of POJOs to different middleware
transports
http://activemq.apache.org/camel/

which implements the Enterprise Integration Patterns...
http://activemq.apache.org/camel/enterprise-integration-patterns.html

Often the out-of-the-box Lingo is fine; but if you want something more
complex (e.g. smart routing, transformations or to use in memory v JMS
v other transports) then Camel becomes more compelling.

We've actually managed to implement most of the features of Lingo in
Camel so far; so I guess long term, Camel is probably a replacement
for Lingo - though we're not quite there yet in terms of replicating
all of Lingo's features. (e.g. Camel doesn't yet support async method
invocations or async conversations using listeners etc).

But certainly, if you want a Spring Remoting implementation for JMS,
Lingo does what it says on the tin. (But then increasingly Camel does
too - and a whole lot more besides).
--
James
-------
http://macstrac.blogspot.com/

Open Source SOA
http://open.iona.com

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email