[Design of EJB 3.0] - Feature: MC Equivalent of @Service
by ALRubinger
Want to address a future feature and get a feel for how much work would be required.
We've currently got @Service, which deploys a Singleton EJB and exposes a JMX View. Oftentimes this is used strictly to get a hook into a Lifecycle (ie. "I want a callback for when my JAR is deployed"). And JMX exposure is not necessarily desired.
I'd like to introduce the notion of an MC EJB, which would have the following features:
* Full EJB (Tx, Security, etc)
* @Singleton (Same model following EJB3.1 with regards to concurrency)
* POJO w/ annotations to denote Callbacks (@Service requires Management interface)
* Proxy is installed into MC and therefore becomes a valid MC Bean; though when MC POJOs invoke on the EJB MC Bean, a typical EJB call starts.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153826#4153826
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153826
17 years, 10 months
[Design of JBoss ESB] - Error in invoking Sync call using deliveryAdapter.deliverSyn
by gopi12345
Hi All,
I am getting the following error while running the 'quickstarts\webservice_consumer1'- SendEsbMessage.java application.
root cause
javax.servlet.ServletException: org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [ ]] to Service [MyServiceCategory:WebserviceConsumer1]. Check for errors.
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:855)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:784)
org.apache.jsp.jsp.client_jsp._jspService(client_jsp.java:114)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [ ]] to Service [MyServiceCategory:WebserviceConsumer1]. Check for errors.
org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:279)
org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:155)
org.apache.jsp.jsp.client_jsp._jspService(client_jsp.java:98)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
note The full stack trace of the root cause is available in the JBossWeb/2.0.0.GA logs.
Can somebody help me resolving this?
Thanks in advance!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153809#4153809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153809
17 years, 10 months
[Design of POJO Server] - Re: profile service, farming
by scott.stark＠jboss.org
Yes, I think we'll have to add a describe/prepare method as the caller needs to be able to receive meaningful information about what is wrong if a deployment cannot be described.
In terms of being aware of cluster membership changes, that still needs to be added and how that is handled defined. There could be more interaction between the server and client side DeploymentProgress, but its possible that the DeploymentManager is not talking to live servers.
I would view the cluster as locked at the start of the deployment op, and new additions need to synchronize their repository view once the op is complete.
"bstansberry(a)jboss.com" wrote :
| BTW, will the basic profile service impl still exist in 5.0.0.GA?
|
Yes, I expect so.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153803#4153803
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153803
17 years, 10 months
[Design of POJO Server] - Re: profile service, farming
by bstansberry＠jboss.com
anonymous wrote : I need to look more at the DeploymentManager API; sounds like that's where ability to do things like "running the deployments across the cluster to the DeploymentStages.DESCRIBE phase" will be exposed.
The current DeploymentManager SPI of distribute/start/redeploy/stop/undeploy doesn't expose a method to let a client bring a deployment to DESCRIBE or PRE_REAL. Were you thinking in terms of adding such a method, e.g. a
| /**
| * Bring a previously distributed deployment through the DESCRIBE stage.
| * @param name
| * @param phase
| * @return
| * @throws Exception
| */
| public DeploymentProgress describe(String name, DeploymentPhase phase)
| throws Exception;
Another possibility is this step can be an internal detail of DeploymentManager.start() and redeploy, i.e. DeployHandler.invoke() could handle a "describe" invocation. In that case, an impl of DeploymentProgress would handle the coordination task by looping through the targets and calling "describe", "start" etc. on the DeployHandler.
A problem with all of this is a DeploymentProgress instance in a remote would have no way to know about cluster topology changes that occur in the middle of an operation (e.g. new node joins in the middle of a deploy; that node never gets the update).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153802#4153802
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153802
17 years, 10 months
[Design of JBoss Build System] - Getting aop 2.0.0.CR10 jars into AS
by kabir.khan＠jboss.com
I am trying to upgrade AS to use AOP 2.0.0.CR10, but the plugin is not recognised.
| [kabir(a)~/sourcecontrol/thirdparty/legacy/jboss/aop/2.0.0.CR10]
| $mvn org.jboss.maven.plugins:maven-buildmagic-thirdparty-plugin:maven-deploy -Durl=file:///Users/kabir/sourcecontrol/thirdparty/maven2/
| [INFO] Scanning for projects...
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] The plugin 'org.jboss.maven.plugins:maven-buildmagic-thirdparty-plugin' does not exist or no valid version could be found
| [INFO] ------------------------------------------------------------------------
| [INFO] For more information, run Maven with the -e switch
| [INFO] ------------------------------------------------------------------------
| [INFO] Total time: < 1 second
| [INFO] Finished at: Tue May 27 21:58:18 BST 2008
| [INFO] Final Memory: 1M/2M
| [INFO] ------------------------------------------------------------------------
|
Why is it not picked up? Also, if it were picked up am I entering the right command? ~/sourcecontrol/thirdparty/legacy/jboss/aop/2.0.0.CR10 is my local checkout of the version I want to add
| [kabir(a)~/sourcecontrol/thirdparty/legacy/jboss/aop/2.0.0.CR10]
| $ls -al *
| -rw-r--r--@ 1 kabir staff 1591 27 May 21:33 component-info.xml
|
| lib:
| total 5296
| drwxr-xr-x 13 kabir staff 442 27 May 21:32 .
| drwxr-xr-x 7 kabir staff 238 27 May 21:33 ..
| drwxr-xr-x 9 kabir staff 306 27 May 21:35 .svn
| -rw-r--r-- 1 kabir staff 28118 27 May 20:55 jboss-aop-as4-deployer.jar
| -rw-r--r-- 1 kabir staff 42568 27 May 20:55 jboss-aop-deployer-jdk50.jar
| -rw-r--r-- 1 kabir staff 22267 27 May 20:55 jboss-aop-jboss4-jdk50.jar
| -rw-r--r-- 1 kabir staff 192847 27 May 20:55 jboss-aop-jdk50-client.jar
| -rw-r--r-- 1 kabir staff 1256790 27 May 20:55 jboss-aop-jdk50.jar
| -rw-r--r-- 1 kabir staff 909593 27 May 20:55 jboss-aop-src.zip
| -rw-r--r-- 1 kabir staff 102049 27 May 20:55 jboss-standalone-aspect-library-jdk50.jar
| -rw-r--r-- 1 kabir staff 125814 27 May 20:55 jboss-standalone-aspects-src.zip
| -rw-r--r-- 1 kabir staff 6990 27 May 21:27 jrockit-pluggable-instrumentor.jar
| -rw-r--r-- 1 kabir staff 4761 27 May 20:55 pluggable-instrumentor.jar
|
| resources:
| total 16
| drwxr-xr-x 5 kabir staff 170 27 May 21:21 .
| drwxr-xr-x 7 kabir staff 238 27 May 21:33 ..
| drwxr-xr-x 9 kabir staff 306 27 May 21:35 .svn
| -rw-r--r-- 1 kabir staff 2441 27 May 21:21 aspect-deployer-beans.xml
| -rw-r--r-- 1 kabir staff 853 27 May 21:21 jboss-aspect-library-beans.xml
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153791#4153791
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153791
17 years, 10 months