Hi All,
I have planned to Implement EJB Connector for WSO2 ESB. Currently, EJB
mediator supports EJB3 Stateless Session Beans and Stateful Session Beans.
Since EJB mediator have some isues EJB Connector will include the
Functionality of EJB mediator which calls an external Enterprise JavaBean
(EJB
On Wed, Sep 16, 2015 at 2:04 PM, Rajjaz Mohammed wrote:
> Hi All,
> I have planned to Implement EJB Connector for WSO2 ESB. Currently, EJB
> mediator supports EJB3 Stateless Session Beans and Stateful Session Beans.
> Since EJB mediator have some isues EJB Connector will include the
> Functionali
Hi Rajjaz,
Well, if you see any issue with the EJB mediator, please report them and
help us to improve the existing mediator. It is not required to repeat the
functionality of the EJB mediator in the new connector which you are going
to develop. Could you elaborate on a use case for this EJB conne
Hi
I guess there are many improvements to be made if you writing connector,
and would certainly looking forward to see new design rather what we
currently have in EJB mediator [1] (it seems original doc is corrupted)
Existing problems
- EJB mediator binds with Bean mediator when we need to
Hi Chanaka/Dushan,
Thank you to add some ideas on this Thread. I’m Currently searching on
implement new EJB Connector with Current EJB Mediator Functions and
possibilities to add more features. So i will add your ideas also in the
development.
On Wed, Sep 16, 2015 at 10:27 PM, Dushan Abeyruwan wr
Hi,
There is an EJB mediator that ships with ESB. But the mediator only
supports esb 3.0.
IMO users who have the interest to integrate with ejb may have the
requirement of integrating with legacy systems.
So in this systems they may not be using the latest ejb version. I had some
experience of a
Hi All,
Thank you for your Suggestions. Since EJB Mediator also have some issues in
working as Discussed in Yesterday meeting first i stared to get more domain
knowledge and then i plan to start the development. EJB 3.X is light
weighted and more features then EJB 2.X but since as malaka mentioned
Hi All,
For the EJB Connector Development which EJB-Container is Recommenced ? and
Which version?
as a first step i would like to develop a EJB 3.x connector because its
have more features and light weighted. after i can develop a connector for
EJB 2.x. is it OK or am i need to implement connector
Hi Rajjaz,
We don't need to write a connector for EJB 3.0 since this is already
supported with ESB EJB mediator.
+1 for the connector with EJB 2.1 support.
On Wed, Oct 7, 2015 at 11:52 AM, Rajjaz Mohammed wrote:
> Hi All,
> For the EJB Connector Development which EJB-Container is Recommenced ?
Noted Malaka,
i need to know which EJB-Container is mostly used by the client? or which
is recommended one? because development will be based on that (later will
try Generalized format).
On Wed, Oct 7, 2015 at 11:55 AM, Malaka Silva wrote:
> Hi Rajjaz,
>
> We don't need to write a connector for
Hi Rajjaz,
i need to know which EJB-Container is mostly used by the client? or which
> is recommended one? because development will be based on that (later will
> try Generalized format).
All EJB containers implements EJB 2.x/3.0/3.1/3.2
specifications. Theoretically all should support it.
You
Hi All,
Since I’m adding server libraries for Connector the size of the connector
zip file is increasing (now 65 MB) so is there any limitation for Connector
file? or do we have any other solution?
On Sat, Oct 24, 2015 at 6:15 PM, Rasika Perera wrote:
> Hi Rajjaz,
>
> i need to know which EJB-Co
Can you list down the libraries you are using?
On Wed, Oct 28, 2015 at 10:42 AM, Rajjaz Mohammed wrote:
> Hi All,
> Since I’m adding server libraries for Connector the size of the connector
> zip file is increasing (now 65 MB) so is there any limitation for Connector
> file? or do we have any ot
Rajjaz as we discussed offline this implementation should be generic and
should not tightly coupled to a container.
On Wed, Oct 28, 2015 at 10:45 AM, Rasika Perera wrote:
> Can you list down the libraries you are using?
>
> On Wed, Oct 28, 2015 at 10:42 AM, Rajjaz Mohammed wrote:
>
>> Hi All,
>
yes malaka,
i got the point. development will be based on that.
@Rasika
Thanks Rasika for the Reply.
On Wed, Oct 28, 2015 at 10:57 AM, Malaka Silva wrote:
> Rajjaz as we discussed offline this implementation should be generic and
> should not tightly coupled to a container.
>
> On Wed, Oct 28,
HI all,
currently the behaviour of ejb2 connector[1]. if is there any suggestion
to this approach please advice me to improve.
init
#
we can add any number of arguments and with any name but want to follow the
approach i added here(need to add key and value name also start with key).
met
Rajjaz
better we can rename key to arg.key. Also output is always written to
out
property
? If so we have to pass the variable name where output should be set IMO.
Don't we need to capture argument type also?
eg :-
HelloBean
sayHello
i will change key to arg.key and other then void method output's are
directly add to property name with response . since message contest
contain objects as string and we are getting the argument type from remote
interface we are dynamically casting the values so we no need to get
argument type fro
Rajjaz I guess you are currently using java reflection in EJB connector.
Worth checking is we can do this via Invokedynamic as well. [1]
[1]
http://www.javaworld.com/article/2860079/scripting-jvm-languages/invokedynamic-101.html
On Mon, Nov 16, 2015 at 9:32 AM, Rajjaz Mohammed wrote:
> i will
Hi Malkaa,
i will check on that.
On Sat, Nov 28, 2015 at 6:30 PM, Malaka Silva wrote:
> Rajjaz I guess you are currently using java reflection in EJB connector.
>
> Worth checking is we can do this via Invokedynamic as well. [1]
>
> [1]
> http://www.javaworld.com/article/2860079/scripting-jvm-la
Hi,
since ejb2 connector work fine with glassfish libraries and getting error
with jboss libraries i removed java reflection and creating method directly
[1] and its work with both jboss and glassfish. so i think i no need to
use Invokedynamic[2]. WDYT?
[1] Method method =ejbObj.getClass().getDe
Rajjaz may be it's not required for this connector. But worth checking it
to find what are the benefits over reflection?
On Thu, Dec 3, 2015 at 6:04 PM, Rajjaz Mohammed wrote:
> Hi,
> since ejb2 connector work fine with glassfish libraries and getting error
> with jboss libraries i removed jav
Hi all,
EJB2.0 connector published[1] in store and Documentation[2] also moved to
public space. as dushan mentioned its tested with Jboss5.0 and glashfish 4.
integration test added for jboss5.0.
[1]
https://store.wso2.com/store/assets/esbconnector/b04683e3-2c04-49a1-b408-9b5eb620798c
[2] https://
Hi
How to deal with complex objects, it is not clear Can we build
comprehensive sample just like in ESB, EJB mediator (if you follow my
documentation).
Also, connector documentation should have all the third party artifacts
downloadable (services that you used to describe the scenario),
Meantime
Hi Dushan,
i will write an comprehensive sample and currently it will support for
below data types[1](EJB Mediator also support with this SimpleTypeMapper
class types). in case of third party artifacts it will server dependent so
user should aware to use client library for there own server.
[1]
25 matches
Mail list logo
