March 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: Move Interceptors and Tests back into AS5 Workspace

by wolfc

"anil.saldhana(a)jboss.com" wrote : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135044 | | Rather than hijacking ALR's thread, this thread contains my suggestions. | | a) the ejb3 interceptors need to be back in AS/trunk/ejb3 module. | b) the ejb3 tests that require AS should ideally be in AS/trunk/testsuite or AS/trunk/ejb3 | | Why? You have already answered the 'why not (move back)?' yourself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135567#4135567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135567

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: iCalendar wrapper

by koen.aers＠jboss.com

Damn, I should learn to use preview... :-s "fady.matar" wrote : I must say this is a very useful feature | [snip] | Posting the code wouldn't be harmful can you do that? | I agree. It would be good to create a JIRA issue for this that we can use as a vehicle to attach code and maybe some design overview document. Adrian, would you mind creating this and explain a bit more the overall architecture of your work? Is there a place where we can already play with it? Tom, how do you think we could include this work in our project? Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135559#4135559 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135559

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: iCalendar wrapper

by koen.aers＠jboss.com

"fady.matar" wrote : I must say this is a very useful feature | | Posting the code wouldn't be harmful can you do that? | /quote] | | I agree. It would be good to create a JIRA issue for this that we can use as a vehicle to attach code and maybe some design overview document. | | Adrian, would you mind creating this and explain a bit more the overall architecture of your work? Is there a place where we can already play with it? | | Tom, how do you think we could include this work in our project? | | Regards, | Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135558#4135558 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135558

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : Third identified problem is ESB integration with JBossWS. | This will be fixed in next JBossWS versions through SPI, see: http://jira.jboss.org/jira/browse/JBWS-2024 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135557#4135557 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135557

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : Second identified problem is HA WS-RM in combination with WS-Security. | | WS-Security processing must be the last/first thing in client and endpoint | outgoing/incoming processing chain. | | HA WS-RM must reside on top of transport layer This will not be the problem anymore. WS-Security will be decoupled from handlers and will provide standard interface to handle WS-Security from other system components. On client side both WSRM-Handler and WS-Security handler will be moved to the transport layer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135555#4135555 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135555

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : First identified problem is HA itself. Imagine the following usecase: | | Client sends WS-RM message to a webservice endpoint that is not available. | | The default AS behaviour in such case is 404 (resource N/A). | | To overcome this problem here are the potential solutions that comes into my mind: | | 1) Deploy a special servlet that would do the following steps: | * will match all http(s) requests that would result in 404 on running AS instance (is it doable?) | * will ignore all http(s) POST requests that wouldn't contain SOAP envelope with WS-RM 1.0/1.1 protocol elements (quite performance issue but realizable) | | 2) Deploy a special servlet that would do the following steps: | * will reside on /wsrm/* web context | * all "GET WSDL" http(s) requests would return a modified WSDL document to reference the endpoint using /wsrm prefix for web context. (Of course only if such WSDL exists - otherwise it would return 404.) | | Example: | | | | client request GET .../wsrm/ctx/endpoint?wsdl | | special servlet request GET .../ctx/endpoint?wsdl | | RETURN modified WSDL or 404 (if above WSDL isn't available) | | | * will ignore all http(s) POST requests that wouldn't contain SOAP envelope with WS-RM 1.0/1.1 protocol elements (quite performance issue but realizable) | | For both above approaches it is supposed to use ServletContext.getContext() method to gain access to the context for various parts of the server, and as needed obtain RequestDispatcher objects from the context. We (JBossWS team) brainstormed new and better HA solution ;) The solution is the following: Server side: * we will provide two types of RMProxy (secured/unsecured) * this RMProxy will implement Provider and MBean * the secured RMProxy will have WS-Security handler in the handlers chain * each RMEnabled endpoint must register itself to the RMProxy (using JMX) * RMProxy will handle only registered endpoints * RMProxy will use RMReceiver internally to ensure HA and QoS * RMReceiver will forward endpoint invocations to RMEndpointInvoker * RMEndpointInvoker will do endpoint invocations according to message addr. headers Client side: * WS-Security will move to the transport layer * WS-RM handler will move to the transport layer Both server and client side will survive and recover from restarts in next RM versions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135553#4135553 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135553

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : It's not possible to move WS-Security to the transport layer. | | We decided to decouple WS-Security from handlers and provide generic interace for accessing WS-Security from other system components. Related bug is: | | http://jira.jboss.org/jira/browse/JBWS-2022 | | When this bug will be fixed there's no problem with WS-Security anymore. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135549#4135549 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135549

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM With Seam

by fady.matar

You need to explore further more Seam's functionality. Seam has a very useful class which is the ManagedJbpmContext that can be used to retrieve the current jBPM context. Make sure you have jBPM enabled in your components.xml a workaround might need to take place to expose the jBPM database without having any process deployed. The next versions of the console are based on Seam, there's already work in progress in CVS. Cheers, Fady View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135542#4135542 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135542

18 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: iCalendar wrapper

by fady.matar

I must say this is a very useful feature that we planned to do as a notification engine where by task notifications would be one feature of it, other notification types could be initiated on process instantiation, process termination, bam notifications, etc... Regarding mobile notification , I believe you're talking about SMS notification you can have a look at the SNMP protocol a number of messaging gateways have been implemented there. Posting the code wouldn't be harmful can you do that? Cheers, Fady View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135540#4135540 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135540

18 years

1
0
0 / 0

[Design of JBoss Portal] - Inter portlet communication between two portlets in differen

by msbrijesh1

Hi, I am using JBoss portal server 2.6.4. Our requirement is : I have portlet A in one page and Portlet B in the second page. Can we achieve inter portlet communication between these two portlets using event mechanism? How can we achieve this? Thanks Brijesh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135529#4135529 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135529

18 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2008