Hi James HigginBotham, I remember too about this list discussing about JXTA where I remember you had your own apprehensions then. I too had some mixed opinions then. Things have changed and are changing with JXTA now. I am still figuring out how to use JXTA as a invoker base in JBoss given my inexperience with JBoss Development which was discussed with Marc and Dain. May be someone may implement it while I am still lurking around this list , But then I am happy as it would be beneficial for both JXTA, JBoss and the end user.
Quoting a latest mail about the possibilities of JXTA with J2EE from James Todd for the benefit of list users.
<--Quoting James Todd--> as i see it, jxta is completely compatible with j2ee ÂÂÂÂÂÂÂÂ depending on what one means by "jxta for j2ee." can ÂÂÂÂÂÂÂÂ one mix j2ee and jxta, absolutely. should one mix j2ee ÂÂÂÂÂÂÂÂ and jxta, depends on one's objectives and context. how ÂÂÂÂÂÂÂÂ can one mix j2ee and jxta, simply treat each as a lib ÂÂÂÂÂÂÂÂ and invoke the api's of interest accordingly.
ÂÂÂÂÂÂÂÂ j2ee is comprised of many api's that can stand alone ÂÂÂÂÂÂÂÂ yet are designed to work very well together. jxta can ÂÂÂÂÂÂÂÂ be introduced into a j2ee env in multiple ways, eg:
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ a jxta app can access an ldap directory via ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ jndi (myjxta2 has code supporting this model)
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ a jxta peer could act as a web service client ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ by invoking, for example, jaxm or jaxrpc api's ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ to an existing jaxm/jax-rpc backend
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ conversely, a jaxm/jax-rpc servlet implementation ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ could sit on top of a jxta peer repurposing the ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ services and/or resources it has access to
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ a jxta peer could invoke jdbc to store/access ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ rdbms data to repurpose via a jxta service
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ etc
ÂÂÂÂÂÂÂÂ i'm fairly certain this and related topics on how best ÂÂÂÂÂÂÂÂ to mix'n match jxta with other technologies has both a ÂÂÂÂÂÂÂÂ subjective perspective that would likely involve never ÂÂÂÂÂÂÂÂ ending dialog as to the merits of each ... and a purely ÂÂÂÂÂÂÂÂ api compatibilty perspective. to the later, jxta is very ÂÂÂÂÂÂÂÂ compatible with almost every java api (and very likely ÂÂÂÂÂÂÂÂ more) that i am familiar with. they, j2ee and jxta, bring ÂÂÂÂÂÂÂÂ alot of capabilities to the table.
<--End of James Quote-->
Hopefully things can move further now.
Rajesh.
morning? I seem to recall someone saying something about using JXTA with> JBoss, but I'm not sure which tier they were planning on using this for.>
Thoughts?!> James
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
James Higginbotham 7 August 2002 20:52:42 [ permanent link ]
Good luck in your endeavors to merge j2ee and JXTA.. If I were going to do it, I would definitely choose Jboss as my platform to try it on first, esp with the JMX extensions that make it even more powerful than the standard j2ee platform.
I haven't looked at JXTA is sometime, but hopefully some of the big issues that prevent it from being used effectively have been solved (please, no flamewar on this comment, I'm tired and moving on). I still believe peer networks will continue to mature and start to make us think differently of how we work, find data, and perform tasks. Hopefully, JXTA will be the leader in this soon!
A framework we started to work on just before we closed our doors was called jockey, and its purpose was to enable services to be located and invoked over a peer network (JXTA). We did this not only to enable a client to talk to multikple peer networks using a standard API, but to overcome some of the deficiencies found in the early JXTA APIs surrounding the definition of a service and how you locate and invoke it. A colleague of mine has moved the code to sourceforge, though the JXTA impl hasn't been plugged in yet AFAIK.. Take a look and see what you think - maybe you could use this to abstract out JXTA and plug in BEEP and many other peer networks over time if JXTA isn't ready or you want to branch out.
-----Original Message-----> From: Rajesh Acharya [mailto:rajesh@infoglyptic.com] > Sent: Wednesday, August 07, 2002 11:46 AM> To: jboss-user@lists.sourceforge.net; James Higginbotham> Cc: discuss@jxta.org> Subject: Re: [JBoss-user] JXTA as an invoker in JBoss>
Hi James HigginBotham,> I remember too about this list discussing about JXTA where I > remember you had > your own apprehensions then. I too had some mixed opinions > then. Things have changed and are changing with JXTA now. I > am still figuring out how to use JXTA as a invoker base in > JBoss given my > inexperience with JBoss Development which was discussed with > Marc and Dain. > May be someone may implement it while I am still lurking > around this list > , But then I am happy as it would be beneficial for both > JXTA, JBoss and > the end user.>
Quoting a latest mail about the possibilities of JXTA with > J2EE from James > Todd for the benefit of list users.>
<--Quoting James Todd-->> as i see it, jxta is completely compatible with j2ee> ÂÂÂÂÂÂÂÂ depending on what one means by "jxta for j2ee." can> ÂÂÂÂÂÂÂÂ one mix j2ee and jxta, absolutely. should one mix j2ee> ÂÂÂÂÂÂÂÂ and jxta, depends on one's objectives and context. how> ÂÂÂÂÂÂÂÂ can one mix j2ee and jxta, simply treat each as a lib> ÂÂÂÂÂÂÂÂ and invoke the api's of interest accordingly.>
ÂÂÂÂÂÂÂÂ j2ee is comprised of many api's that can stand alone> ÂÂÂÂÂÂÂÂ yet are designed to work very well together. jxta can> ÂÂÂÂÂÂÂÂ be introduced into a j2ee env in multiple ways, eg:>
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ a jxta app can access an ldap directory via> ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ jndi (myjxta2 has code supporting this model)>
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ a jxta peer could act as a web service client> ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ by invoking, for example, jaxm or jaxrpc api's> ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ to an existing jaxm/jax-rpc backend>
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ conversely, a jaxm/jax-rpc servlet implementation> ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ could sit on top of a jxta peer repurposing the> ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ services and/or resources it has access to>
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ a jxta peer could invoke jdbc to store/access> ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ rdbms data to repurpose via a jxta service>
ÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂ etc>
ÂÂÂÂÂÂÂÂ i'm fairly certain this and related topics on how best> ÂÂÂÂÂÂÂÂ to mix'n match jxta with other technologies has both a> ÂÂÂÂÂÂÂÂ subjective perspective that would likely involve never> ÂÂÂÂÂÂÂÂ ending dialog as to the merits of each ... and a purely> ÂÂÂÂÂÂÂÂ api compatibilty perspective. to the later, jxta is very> ÂÂÂÂÂÂÂÂ compatible with almost every java api (and very likely> ÂÂÂÂÂÂÂÂ more) that i am familiar with. they, j2ee and jxta, bring> ÂÂÂÂÂÂÂÂ alot of capabilities to the table.>
<--End of James Quote-->>
Hopefully things can move further now.>
Rajesh.>
morning? I seem to recall someone saying something about using JXTA > > with JBoss, but I'm not sure which tier they were planning on using > > this for.> >
Thoughts?!> > James>
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
+1^1000 on the "no flame wars" proposal ... been there, done that, complete waste of time.
it looks to me that jms and jxta have some pretty significant synergies and would likely be an interesting place to start "panning for gold."
- james
James Higginbotham wrote:> Good luck in your endeavors to merge j2ee and JXTA.. If I were going to do it, I would definitely choose Jboss as my platform to try it on first, esp with the JMX extensions that make it even more powerful than the standard j2ee platform. >
I haven't looked at JXTA is sometime, but hopefully some of the big issues that prevent it from being used effectively have been solved (please, no flamewar on this comment, I'm tired and moving on). I still believe peer networks will continue to mature and start to make us think differently of how we work, find data, and perform tasks. Hopefully, JXTA will be the leader in this soon!>
A framework we started to work on just before we closed our doors was called jockey, and its purpose was to enable services to be located and invoked over a peer network (JXTA). We did this not only to enable a client to talk to multikple peer networks using a standard API, but to overcome some of the deficiencies found in the early JXTA APIs surrounding the definition of a service and how you locate and invoke it. A colleague of mine has moved the code to sourceforge, though the JXTA impl hasn't been plugged in yet AFAIK.. Take a look and see what you think - maybe you could use this to abstract out JXTA and plug in BEEP and many other peer networks over time if JXTA isn't ready or you want to branch out. >
-----Original Message----->>From: Rajesh Acharya [mailto:rajesh@infoglyptic.com] >>Sent: Wednesday, August 07, 2002 11:46 AM>>To: jboss-user@lists.sourceforge.net; James Higginbotham>>Cc: discuss@jxta.org>>Subject: Re: [JBoss-user] JXTA as an invoker in JBoss>>
Hi James HigginBotham,>>I remember too about this list discussing about JXTA where I >>remember you had >>your own apprehensions then. I too had some mixed opinions >>then. Things have changed and are changing with JXTA now. I >>am still figuring out how to use JXTA as a invoker base in >>JBoss given my >>inexperience with JBoss Development which was discussed with >>Marc and Dain. >>May be someone may implement it while I am still lurking >>around this list >>:-), But then I am happy as it would be beneficial for both >>JXTA, JBoss and >>the end user.>>
Quoting a latest mail about the possibilities of JXTA with >>J2EE from James >>Todd for the benefit of list users.>>
<--Quoting James Todd-->>> as i see it, jxta is completely compatible with j2ee>> depending on what one means by "jxta for j2ee." can>> one mix j2ee and jxta, absolutely. should one mix j2ee>> and jxta, depends on one's objectives and context. how>> can one mix j2ee and jxta, simply treat each as a lib>> and invoke the api's of interest accordingly.>>
j2ee is comprised of many api's that can stand alone>> yet are designed to work very well together. jxta can>> be introduced into a j2ee env in multiple ways, eg:>>
a jxta app can access an ldap directory via>> jndi (myjxta2 has code supporting this model)>>
a jxta peer could act as a web service client>> by invoking, for example, jaxm or jaxrpc api's>> to an existing jaxm/jax-rpc backend>>
conversely, a jaxm/jax-rpc servlet implementation>> could sit on top of a jxta peer repurposing the>> services and/or resources it has access to>>
a jxta peer could invoke jdbc to store/access>> rdbms data to repurpose via a jxta service>>
i'm fairly certain this and related topics on how best>> to mix'n match jxta with other technologies has both a>> subjective perspective that would likely involve never>> ending dialog as to the merits of each ... and a purely>> api compatibilty perspective. to the later, jxta is very>> compatible with almost every java api (and very likely>> more) that i am familiar with. they, j2ee and jxta, bring>> alot of capabilities to the table.>>
<--End of James Quote-->>>
Hopefully things can move further now.>>
Rajesh.>>
morning? I seem to recall someone saying something about using JXTA >>>with JBoss, but I'm not sure which tier they were planning on using >>>this for.>>>
Thoughts?!>>>James>>
---------------------------------------------------------------------> To unsubscribe, e-mail: discuss-unsubscribe@jxta.org> For additional commands, e-mail: discuss-help@jxta.org>
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
James Higginbotham 7 August 2002 22:09:37 [ permanent link ]
Right on the money. We had considered locating a small footprint JMS server some time ago and using it to store and forward requests to other peers based on the needs of our application at the time. Not sure what you and others may plan to do with it, but throwing this out for those interested.
I now monitor jboss-users more due to the work I am involved with now. If you do an integration, please be sure to post it to this list, as I and others would be interested to see how they go together.
I can't believe its been almost 16 months since JXTA came out.. Wow! How time flies!
James
-----Original Message-----> From: James Todd [mailto:jwtodd@pacbell.net] > Sent: Wednesday, August 07, 2002 1:15 PM> To: discuss@jxta.org> Cc: rajesh@infoglyptic.com; jboss-user@lists.sourceforge.net; > john@gardner.net> Subject: Re: [JXTA discuss] RE: [JBoss-user] JXTA as an > invoker in JBoss>
+1^1000 on the "no flame wars" proposal ... been there, done that,> complete waste of time.>
it looks to me that jms and jxta have some pretty significant > synergies and would likely be an interesting place to start > "panning for gold.">
- james>
James Higginbotham wrote:> > Good luck in your endeavors to merge j2ee and JXTA.. If I > were going > > to do it, I would definitely choose Jboss as my platform to > try it on first, esp with the JMX extensions that make it > even more powerful than the standard j2ee platform.> >
I haven't looked at JXTA is sometime, but hopefully some of the big > > issues that prevent it from being used effectively have been solved > > (please, no flamewar on this comment, I'm tired and moving on). I > > still believe peer networks will continue to mature and > start to make > > us think differently of how we work, find data, and perform tasks. > > Hopefully, JXTA will be the leader in this soon!> >
A framework we started to work on just before we closed our > doors was > > called jockey, and its purpose was to enable services to be > located and invoked over a peer network (JXTA). We did this > not only to enable a client to talk to multikple peer > networks using a standard API, but to overcome some of the > deficiencies found in the early JXTA APIs surrounding the > definition of a service and how you locate and invoke it. A > colleague of mine has moved the code to sourceforge, though > the JXTA impl hasn't been plugged in yet AFAIK.. Take a look > and see what you think - maybe you could use this to abstract > out JXTA and plug in BEEP and many other peer networks over > time if JXTA isn't ready or you want to branch out.> >
-----Original Message-----> >>From: Rajesh Acharya [mailto:rajesh@infoglyptic.com]> >>Sent: Wednesday, August 07, 2002 11:46 AM> >>To: jboss-user@lists.sourceforge.net; James Higginbotham> >>Cc: discuss@jxta.org> >>Subject: Re: [JBoss-user] JXTA as an invoker in JBoss> >>
Hi James HigginBotham,> >>I remember too about this list discussing about JXTA where I> >>remember you had > >>your own apprehensions then. I too had some mixed opinions > >>then. Things have changed and are changing with JXTA now. I > >>am still figuring out how to use JXTA as a invoker base in > >>JBoss given my > >>inexperience with JBoss Development which was discussed with > >>Marc and Dain. > >>May be someone may implement it while I am still lurking > >>around this list > >>:-), But then I am happy as it would be beneficial for both > >>JXTA, JBoss and > >>the end user.> >>
Quoting a latest mail about the possibilities of JXTA with> >>J2EE from James > >>Todd for the benefit of list users.> >>
<--Quoting James Todd-->> >> as i see it, jxta is completely compatible with j2ee> >> depending on what one means by "jxta for j2ee." can> >> one mix j2ee and jxta, absolutely. should one mix j2ee> >> and jxta, depends on one's objectives and context. how> >> can one mix j2ee and jxta, simply treat each as a lib> >> and invoke the api's of interest accordingly.> >>
j2ee is comprised of many api's that can stand alone> >> yet are designed to work very well together. jxta can> >> be introduced into a j2ee env in multiple ways, eg:> >>
a jxta app can access an ldap directory via> >> jndi (myjxta2 has code supporting this model)> >>
a jxta peer could act as a web service client> >> by invoking, for example, jaxm or jaxrpc api's> >> to an existing jaxm/jax-rpc backend> >>
conversely, a jaxm/jax-rpc servlet implementation> >> could sit on top of a jxta peer repurposing the> >> services and/or resources it has access to> >>
a jxta peer could invoke jdbc to store/access> >> rdbms data to repurpose via a jxta service> >>
i'm fairly certain this and related topics on how best> >> to mix'n match jxta with other technologies has both a> >> subjective perspective that would likely involve never> >> ending dialog as to the merits of each ... and a purely> >> api compatibilty perspective. to the later, jxta is very> >> compatible with almost every java api (and very likely> >> more) that i am familiar with. they, j2ee and jxta, bring> >> alot of capabilities to the table.> >>
<--End of James Quote-->> >>
Hopefully things can move further now.> >>
Rajesh.> >>
morning? I seem to recall someone saying something about using JXTA> >>>with JBoss, but I'm not sure which tier they were planning > on using > >>>this for.> >>>
Thoughts?!> >>>James> >>
---------------------------------------------------------------------> > To unsubscribe, e-mail: discuss-unsubscribe@jxta.org> > For additional commands, e-mail: discuss-help@jxta.org> >
-------------------------------------------------------> This sf.net email is sponsored by:ThinkGeek> Welcome to geek heaven.> http://thinkgeek.com/sf > _______________________________________________> JBoss-user mailing list> JBoss-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/j> boss-user>
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
Holger Baxmann 7 August 2002 22:31:52 [ permanent link ]
i am very interested to substitute the proprietary jms product with a open protocol - i am working on dallas semiconductor tini and looking for an mom protocol higher then xml-rpc, have had a look at jabber, but ... if you are on the way to implement a mbean - let me know. i'll be the first who tries it on tini, because there is a jxta impl.
bax ----- Original Message ----- From: "James Higginbotham" <jhigginbotham@betweenmarkets.com> To: <jboss-user@lists.sourceforge.net>; <discuss@jxta.org> Cc: <rajesh@infoglyptic.com>; <john@gardner.net> Sent: Wednesday, August 07, 2002 9:09 PM Subject: RE: [JXTA discuss] RE: [JBoss-user] JXTA as an invoker in JBoss
Right on the money. We had considered locating a small footprint JMS server some time ago and using it to store and forward requests to other peers based on the needs of our application at the time. Not sure what you and others may plan to do with it, but throwing this out for those interested.
I now monitor jboss-users more due to the work I am involved with now. If you do an integration, please be sure to post it to this list, as I and others would be interested to see how they go together.
I can't believe its been almost 16 months since JXTA came out.. Wow! How time flies!
James
-----Original Message-----> From: James Todd [mailto:jwtodd@pacbell.net]> Sent: Wednesday, August 07, 2002 1:15 PM> To: discuss@jxta.org> Cc: rajesh@infoglyptic.com; jboss-user@lists.sourceforge.net;> john@gardner.net> Subject: Re: [JXTA discuss] RE: [JBoss-user] JXTA as an> invoker in JBoss>
+1^1000 on the "no flame wars" proposal ... been there, done that,> complete waste of time.>
it looks to me that jms and jxta have some pretty significant> synergies and would likely be an interesting place to start> "panning for gold.">
- james>
James Higginbotham wrote:> > Good luck in your endeavors to merge j2ee and JXTA.. If I> were going> > to do it, I would definitely choose Jboss as my platform to> try it on first, esp with the JMX extensions that make it> even more powerful than the standard j2ee platform.> >
I haven't looked at JXTA is sometime, but hopefully some of the big> > issues that prevent it from being used effectively have been solved> > (please, no flamewar on this comment, I'm tired and moving on). I> > still believe peer networks will continue to mature and> start to make> > us think differently of how we work, find data, and perform tasks.> > Hopefully, JXTA will be the leader in this soon!> >
A framework we started to work on just before we closed our> doors was> > called jockey, and its purpose was to enable services to be> located and invoked over a peer network (JXTA). We did this> not only to enable a client to talk to multikple peer> networks using a standard API, but to overcome some of the> deficiencies found in the early JXTA APIs surrounding the> definition of a service and how you locate and invoke it. A> colleague of mine has moved the code to sourceforge, though> the JXTA impl hasn't been plugged in yet AFAIK.. Take a look> and see what you think - maybe you could use this to abstract> out JXTA and plug in BEEP and many other peer networks over> time if JXTA isn't ready or you want to branch out.> >
-----Original Message-----> >>From: Rajesh Acharya [mailto:rajesh@infoglyptic.com]> >>Sent: Wednesday, August 07, 2002 11:46 AM> >>To: jboss-user@lists.sourceforge.net; James Higginbotham> >>Cc: discuss@jxta.org> >>Subject: Re: [JBoss-user] JXTA as an invoker in JBoss> >>
Hi James HigginBotham,> >>I remember too about this list discussing about JXTA where I> >>remember you had> >>your own apprehensions then. I too had some mixed opinions> >>then. Things have changed and are changing with JXTA now. I> >>am still figuring out how to use JXTA as a invoker base in> >>JBoss given my> >>inexperience with JBoss Development which was discussed with> >>Marc and Dain.> >>May be someone may implement it while I am still lurking> >>around this list> >>:-), But then I am happy as it would be beneficial for both> >>JXTA, JBoss and> >>the end user.> >>
Quoting a latest mail about the possibilities of JXTA with> >>J2EE from James> >>Todd for the benefit of list users.> >>
<--Quoting James Todd-->> >> as i see it, jxta is completely compatible with j2ee> >> depending on what one means by "jxta for j2ee." can> >> one mix j2ee and jxta, absolutely. should one mix j2ee> >> and jxta, depends on one's objectives and context. how> >> can one mix j2ee and jxta, simply treat each as a lib> >> and invoke the api's of interest accordingly.> >>
j2ee is comprised of many api's that can stand alone> >> yet are designed to work very well together. jxta can> >> be introduced into a j2ee env in multiple ways, eg:> >>
a jxta app can access an ldap directory via> >> jndi (myjxta2 has code supporting this model)> >>
a jxta peer could act as a web service client> >> by invoking, for example, jaxm or jaxrpc api's> >> to an existing jaxm/jax-rpc backend> >>
conversely, a jaxm/jax-rpc servlet implementation> >> could sit on top of a jxta peer repurposing the> >> services and/or resources it has access to> >>
a jxta peer could invoke jdbc to store/access> >> rdbms data to repurpose via a jxta service> >>
i'm fairly certain this and related topics on how best> >> to mix'n match jxta with other technologies has both a> >> subjective perspective that would likely involve never> >> ending dialog as to the merits of each ... and a purely> >> api compatibilty perspective. to the later, jxta is very> >> compatible with almost every java api (and very likely> >> more) that i am familiar with. they, j2ee and jxta, bring> >> alot of capabilities to the table.> >>
<--End of James Quote-->> >>
Hopefully things can move further now.> >>
Rajesh.> >>
morning? I seem to recall someone saying something about using JXTA> >>>with JBoss, but I'm not sure which tier they were planning> on using> >>>this for.> >>>
Thoughts?!> >>>James> >>
---------------------------------------------------------------------> > To unsubscribe, e-mail: discuss-unsubscribe@jxta.org> > For additional commands, e-mail: discuss-help@jxta.org> >
-------------------------------------------------------> This sf.net email is sponsored by:ThinkGeek> Welcome to geek heaven.> http://thinkgeek.com/sf> _______________________________________________> JBoss-user mailing list> JBoss-user@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/j> boss-user>
