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 for 2.x first?

can anyone have experience with client can guide me on this? what is the
client requirement?


On Wed, Sep 23, 2015 at 12:24 PM, Rajjaz Mohammed <[email protected]> wrote:

> 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 our
> clients are prefer EJB 2.X  first connector will be for EJB 2.X.
>
> On Fri, Sep 18, 2015 at 10:40 AM, Malaka Silva <[email protected]> wrote:
>
>> 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 requirement to integrate with EJB 2.1.
>>
>> So the integration requirement resides to integrate with different ejb
>> versions. So if we follow the current approach we need to write a mediator
>> for each or parameter it.
>>
>> In this case best solution is to have different connectors for different
>> ejb versions. I think we can start with ejb 2.1 (since ejb mediator is
>> already there to support 3.0)
>>
>> In long term we can deprecate EJB mediator and write connectors for
>> these. WDYT?
>>
>> @Rajjaz - To start better we discuss the high level architecture of your
>> development.
>>
>> On Wed, Sep 16, 2015 at 11:09 PM, Rajjaz Mohammed <[email protected]>
>> wrote:
>>
>>> 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 <[email protected]>
>>> wrote:
>>>
>>>> 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 initialize
>>>>    instances for binding responses or requests for complex object IMV its 
>>>> too
>>>>    much overhead and feels we need to normalize this.
>>>>    -  We need to get rid from 'beanstalks' way of communicating via
>>>>    synapse.propertis (it is must) it should be flexible.
>>>>    - Then we must test this with least multiple application servers
>>>>    (Jboss, Glassfish) there are tons of class loader issues (and we had to
>>>>    create split packages to get rid)
>>>>
>>>>  With all above concerns please do come up with the design we can
>>>> continue to discuss.
>>>>
>>>>
>>>> [1] http://www.dushantech.com/search?q=ejb
>>>>
>>>>
>>>> Cheers,
>>>> Dushan
>>>>
>>>> On Wed, Sep 16, 2015 at 10:42 AM, Chanaka Fernando <[email protected]>
>>>> wrote:
>>>>
>>>>> 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 
>>>>> connector?
>>>>>
>>>>> On Wed, Sep 16, 2015 at 2:04 PM, Rajjaz Mohammed <[email protected]>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 16, 2015 at 2:04 PM, Rajjaz Mohammed <[email protected]>
>>>>>> 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
>>>>>>> Functionality of  EJB mediator which calls an external Enterprise 
>>>>>>> JavaBean
>>>>>>> (EJB) and stores the result in the message payload or in a message 
>>>>>>> context
>>>>>>> property.
>>>>>>>
>>>>>>> This is my Basic Idea so If you have anything  to add/change in EJB
>>>>>>> Connector please add in this Thread. and Connector will be Separate for 
>>>>>>> EJB
>>>>>>> 2.0 & 3.0.
>>>>>>>
>>>>>>> --
>>>>>>> Thank you
>>>>>>> Best Regards
>>>>>>>
>>>>>>> *Rajjaz HM*
>>>>>>> Associate Software Engineer
>>>>>>> WSO2 Inc. <http://wso2.com/>
>>>>>>> lean | enterprise | middleware
>>>>>>> Mobile | +94752833834
>>>>>>> Email   | [email protected]
>>>>>>> LinkedIn | Blogger | WSO2 Profile
>>>>>>> <http://wso2.com/about/team/mohammer_rajjaz/>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thank you
>>>>>> Best Regards
>>>>>>
>>>>>> *Rajjaz HM*
>>>>>> Associate Software Engineer
>>>>>> WSO2 Inc. <http://wso2.com/>
>>>>>> lean | enterprise | middleware
>>>>>> Mobile | +94752833834
>>>>>> Email   | [email protected]
>>>>>> LinkedIn | Blogger | WSO2 Profile
>>>>>> <http://wso2.com/about/team/mohammer_rajjaz/>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Architecture mailing list
>>>>>> [email protected]
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Chanaka Fernando
>>>>> Senior Technical Lead
>>>>> WSO2, Inc.; http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> mobile: +94 773337238
>>>>> Blog : http://soatutorials.blogspot.com
>>>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>>>> Twitter:https://twitter.com/chanakaudaya
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> [email protected]
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Dushan Abeyruwan | Technical Lead
>>>> Technical Support-Bloomington US
>>>> PMC Member Apache Synpase
>>>> WSO2 Inc. http://wso2.com/
>>>> Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>*
>>>> Mobile:(001)812-391-7441
>>>>
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Thank you
>>> Best Regards
>>>
>>> *Rajjaz HM*
>>> Associate Software Engineer
>>> WSO2 Inc. <http://wso2.com/>
>>> lean | enterprise | middleware
>>> Mobile | +94752833834
>>> Email   | [email protected]
>>> LinkedIn | Blogger | WSO2 Profile
>>> <http://wso2.com/about/team/mohammer_rajjaz/>
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. <http://wso2.com/>
> lean | enterprise | middleware
> Mobile | +94752833834
> Email   | [email protected]
> LinkedIn | Blogger | WSO2 Profile
> <http://wso2.com/about/team/mohammer_rajjaz/>
>



-- 
Thank you
Best Regards

*Rajjaz HM*
Associate Software Engineer
WSO2 Inc. <http://wso2.com/>
lean | enterprise | middleware
Mobile | +94752833834
Email   | [email protected]
LinkedIn | Blogger | WSO2 Profile
<http://wso2.com/about/team/mohammer_rajjaz/>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to