jboss-dev-forums — The jboss development forum posts

[Jboss-dev-forums] [Design of JBossXB] - Re: Inline bindings with jbxb

[<ale...@jb...>]

> Does this sounds acceptable to you?
Yes.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879910#3879910

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879910

[Jboss-dev-forums] [Deployers on JBoss (Deployers/JBoss)] - Jboss Application server undeploys all the beans and shuts d

[<sp...@ca...>]

Hi All,
Please help me as its very critical for me. I am using JBOSS 4.0, Oracle 10G and struts for my application.
My Struts action class gets a call on a hit on the jsp page.
Then the action class makes a call to a stateless bean and then makes a call to my 
JasperReport java class. Now this JasperReport java class fills the jasper report and shows it in a new window.

It opens up properly but when i close the jasper report window, my server shuts down automatically. The server doesnt throw any error but simply undeploys the beans and shuts down.
My JasperReport code is as follows:

          JasperDesign jasperDesign = JasperManager.loadXmlDesign("C:/RFID/ReportsWS/ReportsProj/public_html/BasicReport.xml");
          JasperReport jasperReport = JasperManager.compileReport(jasperDesign);
          Map parameters = new HashMap();
          parameters.put("Title", "Basic JasperReport");
          parameters.put("MaxSalary", new Double(25000.00));
Connection conn = this.getConnection(); 
          JasperPrint jasperPrint1 = JasperManager.fillReport(jasperReport, 
             parameters, conn);
          JasperViewer.viewReport(jasperPrint1 );

Server logs is as follows:




14:04:18,158 INFO  [PropertyMessageResources] Initializing, config='org.apache.struts.taglib.logic.LocalStrings', returnNull=true
14:04:23,233 INFO  [Server] JBoss SHUTDOWN: Undeploying all packages
14:04:23,233 INFO  [TomcatDeployer] undeploy, ctxPath=/proximities, warUrl=file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28851proximities.ear-contents/proximities-exp.war/
14:04:23,249 INFO  [EJBDeployer] Undeploying: file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28851proximities.ear-contents/proximities.jar-contents/proximities-ejb.jar
14:04:23,592 INFO  [EjbModule] Undeployed ItemManageFacade
14:04:23,592 INFO  [EjbModule] Undeployed StationServiceFacade
14:04:23,592 INFO  [EjbModule] Undeployed OrderRequestFacade
14:04:23,592 INFO  [EjbModule] Undeployed ManageVenueFacade
14:04:23,592 INFO  [EjbModule] Undeployed ReportFacade
14:04:23,686 INFO  [EARDeployer] Undeploying J2EE application, destroy step: file:/C:/jboss/jboss-4.0.1sp1/server/default/deploy/proximities.ear
14:04:23,702 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28851proximities.ear restart will delete it
14:04:23,702 INFO  [TomcatDeployer] undeploy, ctxPath=/web-console, warUrl=file:/C:/jboss/jboss-4.0.1sp1/server/default/deploy/management/web-console.war/
14:04:23,717 INFO  [TomcatDeployer] undeploy, ctxPath=/jmx-console, warUrl=file:/C:/jboss/jboss-4.0.1sp1/server/default/deploy/jmx-console.war/
14:04:23,733 INFO  [ConnectionFactoryBindingService] Unbound connection factory for resource adapter for ConnectionManager 'jboss.jca:name=ProximitiesDataSource,service=DataSourceBinding from JNDI name 'java:ProximitiesDataSource'
14:04:23,733 INFO  [ConnectionFactoryBindingService] Unbound connection factory for resource adapter for ConnectionManager 'jboss.jca:name=IntellionsDataSource,service=DataSourceBinding from JNDI name 'java:IntellionsDataSource'
14:04:23,748 INFO  [ConnectionFactoryBindingService] Unbound connection factory for resource adapter for ConnectionManager 'jboss.jca:name=JmsXA,service=ConnectionFactoryBinding from JNDI name 'java:JmsXA'
14:04:23,780 INFO  [ConnectionFactoryBindingService] Unbound connection factory for resource adapter for ConnectionManager 'jboss.jca:name=DefaultDS,service=DataSourceBinding from JNDI name 'java:DefaultDS'
14:04:24,966 INFO  [HypersonicDatabase] Database standalone closed clean
14:05:31,317 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28847mail-ra.rar restart will delete it
14:05:31,317 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28846jms-ra.rar restart will delete it
14:05:31,317 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28845jboss-xa-jdbc.rar restart will delete it
14:05:31,317 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28844jboss-local-jdbc.rar restart will delete it
14:05:31,332 INFO  [MailService] Mail service 'java:/Mail' removed from JNDI
14:05:31,411 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28827uuid-key-generator.sar restart will delete it
14:05:31,411 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28826jfreechart.jar restart will delete it
14:05:31,411 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28825jcommon.jar restart will delete it
14:05:31,426 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28824console-mgr-classes.jar restart will delete it
14:05:31,426 INFO  [TomcatDeployer] undeploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/jboss/jboss-4.0.1sp1/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
14:05:31,442 WARN  [ServiceController] Ignoring request to stop nonexistent service: null
14:05:31,442 INFO  [TomcatDeployer] undeploy, ctxPath=/, warUrl=file:/C:/jboss/jboss-4.0.1sp1/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
14:05:31,457 INFO  [Http11Protocol] Pausing Coyote HTTP/1.1 on http-0.0.0.0-9090
14:05:32,472 INFO  [StandardService] Stopping service jboss.web
14:05:32,472 INFO  [StandardHost] Create Host deployer for direct deployment ( non-jmx )
14:05:32,488 INFO  [StandardHostDeployer] Removing web application at context path /ws4ee
14:05:32,488 INFO  [StandardHostDeployer] Removing web application at context path /invoker
14:05:32,488 INFO  [Http11Protocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0-9090
14:05:32,504 INFO  [TomcatDeployer] undeploy, ctxPath=/invoker, warUrl=file:/C:/jboss/jboss-4.0.1sp1/server/default/deploy/http-invoker.sar/invoker.war/
14:05:32,519 INFO  [TomcatDeployer] undeploy, ctxPath=/ws4ee, warUrl=file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28799jboss-ws4ee-exp.war/
14:05:32,597 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28823tomcat50-service.jar restart will delete it
14:05:32,597 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28822tomcat-util.jar restart will delete it
14:05:32,597 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28821tomcat-jk2.jar restart will delete it
14:05:32,597 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28820tomcat-http11.jar restart will delete it
14:05:32,597 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28819tomcat-coyote.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28818servlets-webdav.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28817servlets-invoker.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28816servlets-default.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28815servlets-common.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28814naming-resources.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28813naming-common.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28812jasper-runtime.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28811jasper-compiler.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28810jakarta-regexp-1.3.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28809commons-modeler.jar restart will delete it
14:05:32,613 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28808commons-logging.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28807commons-el.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28806commons-digester.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28805commons-collections.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28804commons-beanutils.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28803catalina.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28802catalina-optional.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28801catalina-manager.jar restart will delete it
14:05:32,629 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28800ant.jar restart will delete it
14:05:32,644 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28798wsdl4j.jar restart will delete it
14:05:32,644 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28797jboss-ws4ee.jar restart will delete it
14:05:32,644 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28796commons-logging.jar restart will delete it
14:05:32,644 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28795commons-discovery.jar restart will delete it
14:05:32,660 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28794axis-ws4ee.jar restart will delete it
14:05:32,691 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28790odmg-3.0.jar restart will delete it
14:05:32,691 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28789jboss-hibernate.jar restart will delete it
14:05:32,691 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28788hibernate2.jar restart will delete it
14:05:32,691 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28787cglib-full-2.0.1.jar restart will delete it
14:05:32,691 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28786trove.jar restart will delete it
14:05:32,707 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28785jboss-aspect-library.jar restart will delete it
14:05:32,707 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28784jboss-aop.jar restart will delete it
14:05:32,707 WARN  [DeploymentInfo] Could not delete file:/C:/jboss/jboss-4.0.1sp1/server/default/tmp/deploy/tmp28783javassist.jar restart will delete it
Shutting down
14:05:33,253 INFO  [Server] Shutdown complete
Shutdown complete
Halting VM
Press any key to continue . . .

When i close the jasper report window, the application server shuts down.
PLEASE HELP ME AS ITS VERY CRITICAL.

Thanks a ton!!!
Sandeep Pathak
Calance Cor.
Gurgaon
India`

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879906#3879906

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879906

[Jboss-dev-forums] [Design of JTA and JTS on JBoss] - Re: mt-issues with org.jboss.tm.TransactionLocal

[<dim...@jb...>]

Ok, lock()/unlock() similar to TransactionImpl was added, along with a helper SynchronizedTransactionLocal class (in the branch I'm working).

Thanks

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879852#3879852

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879852

[Jboss-dev-forums] [TODO -- DEVELOPMENT] - I have a problem with template

[janoboss <nu...@jb...>]

that is my code in de file *.xml.vm

------------------------------------------------------------------------------


      #if($TopicName)
	
	#end

		<depends optional-attribute-name="DestinationManager">$DestinationManager
		
		#if($SecurityManager)
    			<depends optional-attribute-name="SecurityManager">$SecurityManager
		#end
		
		#if($SecurityRoles)
    			
      		
			
			#foreach($role in $SecurityRoles)      
        			<role name="#firstToken($role ':')" #ifDefReplace($role "read" 'read="true"') #ifDefReplace($role "write" 'write="true"') #ifDefReplace($role "create" 'create="true"')/>
			#end        
      		
			
    		
		#end
  	


that is my code in de file template.xml

------------------------------------------------------------------------------

<template-config template="vm/jms-queue.xml.vm" extension="-service.xml"> 
	<property-list> 
		<!-- if type not specified, java.lang.String is assumed --> 
		<!-- a value must be supplied at runtime, or an exception will be thrown --> 
		
		
			
		
		<!-- if a value is not supplied at runtime, the default will be used --> 
		 
			 
				The ObjectName of the DestinationManager factory to be used
			 
			<default-value>jboss.mq:service=DestinationManager</default-value> 
		
	</property-list> 
</template-config> 

-----------------------------------------------------------------------------

my proble is the following:

Exception : java.lang.Exception: Required property missing: 'TopicName' of type 'java.lang.String'


I want to make Queue and Topic, but I have a the avobe proble, the type of property TopicName. Please Help ME!!

see soon






View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879851#3879851

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879851

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: getting the SQL out of PreparedStatement

[<bil...@jb...>]

proxy the return from prepareStatement().  The proxy can hold the SQL and then you could get it at runtime.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879850#3879850

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879850

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - getting the SQL out of PreparedStatement

[drakonis <nu...@jb...>]

I was wondering, if one can get the SQL out of a PreparedStatement.
For example the code in

public class TestClass {
 public void aMethod () {
 PreparedStatement sql=con.prepareStatement("INSERT
   INTO person(id,adress,age) VALUES(?,?,?,?)");
  sql.setInt(1,22);
  sql.setString(2,?Str. .....?);
  sql.setInt(3,24);
 sql.executeUpdate();
 }
}
We could write an interceptor, intercept prepareStatement and get the parameter, but the SQL String has those nasty ? ? ? in it.

Next we have another interceptor intercept the ..PreparedStatement->set*(..) but how would i be able to get the info extracted with the first interceptor(the SQL String with ? ? ? in it), if only i could get, that then i would use a regular expresion to parse it and add the info of that perticular set* method instead of the ?
and finally at executeUpdate() i would just have the plain clear as day SQL.

Metadata to pass the data from one Interceptor to the other is out of the question i guess cause i belive that's for chains of interceptors, right?
How about we dinamicaly add a field to the TestClass and put the partial result of all the calls in there. Could we do that?

Is it possible to make it work. Any ideas?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879848#3879848

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879848

[Jboss-dev-forums] [Design of JBoss Reporting] - Re: tools for reporting

[honey.george <nu...@jb...>]

Hi,
I am currently evaluating JasperReports for generating OLAP kind of reports. Can somebody share their experiences using the tool. How flexible it is and easy to adapt.

Thanks,
George

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879840#3879840

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879840

[Jboss-dev-forums] [Design the new POJO MicroContainer] - Re: OnDemand + another animals

[<ad...@jb...>]

Do we need any other modes? Most of the usecases I can think of
can be done with these primitives.

The only additional feature I plan to support is the "registry" type of OnDemand.
e.g. jms queue uses OnDemand jms destination manager which not only bootstraps
the destination manager (if not done so already) 
but also does manager.register/unregisterDestination() as they are undeployed.

Making this a first class notion removes the need for this boiler plate code in every
service and also allows extra semantics to be placed at this "JoinPoint" since it is described
to the controller/microcontainer.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879837#3879837

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879837

[Jboss-dev-forums] [Design the new POJO MicroContainer] - Re: OnDemand + another animals

[<ad...@jb...>]

There is no "OnUnDemand", i.e. automatically removing an unreferenced
bean when its dependencies are undeployed.

This is mainly because I don't want the OnDemand bean to bounce when its only
dependee is redeployed.
This will change when I add support for more direct/atomic redeploy.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879836#3879836

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879836

[Jboss-dev-forums] [Design the new POJO MicroContainer] - OnDemand + another animals

[<ad...@jb...>]

I've added support for different deployment modes to the controller.

* DISABLED - The context does not progress beyond the initial "Not Installed".
* MANUAL - Initially the state is "Not Installed" however the required state
can be changed with controller.change(ControllerContext, ControllerState)
* AUTOMATIC - Similar to manual except the initial requested state is "Installed"
* ON_DEMAND - The context remains at "Not Installed" until somebody introduces a dependency on it. The requested state is then changed to "Installed".

My main motivation for doing now this is the JMX ServiceController uses the MANUAL 
approach (even if it looks automatic because the SARDeployer drives it), whereas IOC
uses the AUTOMATIC approach.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879835#3879835

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879835

[Jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: requirements for connection failure callback

[<ad...@jb...>]

What is missing is that the transport could fail while there are no calls.
e.g. 
1) I register a message listener but there are no messages.
2) The server or network fails
3) JMS needs to invoke the ExceptionListener to tell the user code about the failure
otherwise onMessage will just wait forever.

Currently, JBossMQ does this by passing a regular ping/pong around the connection.

You have the same issue on the server where the client/network has failed
but you don't know about it, it just looks like the client isn't doing anything. 
The server does not want to maintain resources
(unacknowledged messages/temporary destinations/nondurable subscriptions) 
for these clients.

Currently UIL2 does this by setting an SOTimeout on the server side
to detect when it stop receiving the pings.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879832#3879832

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879832

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - FileBenchmarkReceiver Thread Model vs DatabaseBenchmarkRecei

[<cle...@jb...>]

FileBenchmarkReceiver has this piece of code for multi-threading:

   private void initServerThread()
  |    {
  |       Thread svrThread = new Thread()
  |       {
  |                 public void run()
  |                 {
  |                    while(keepRunning)
  |                    {
  |                       try
  |                       {
  |                          currentThread().sleep(1000);
  |                       }
  |                       catch(InterruptedException e)
  |                       {
  |                          log.debug("Server thread interrupted.");
  |                       }
  |                    }
  |                 }
  |       };
  |       svrThread.setDaemon(false);
  |       svrThread.start();
  |    }
  | 

For DatabaseBenchmarkReceiver I'm only using JGroups threading model.

So... should I do the same in DatabaseBenchmarkReceiver?


Clebert Suconic

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879831#3879831

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879831

[Jboss-dev-forums] [Design of JBoss's Web Services Implementation] - Re: WebServiceDeployer integration as deployment interceptor

[<sco...@jb...>]

The metadata should be created during the create step. Since the tomcat web app class loader is not available at this time, another could be created to load resources. This already exists for loading the descriptors. The web app version could add the WEB-INF/{classes,lib} to its path. The new step that is needed is to merge the annotation and xml level metadata.

A concern here is whether loading annotations as classes through a temporary class loader is going to cause problems. I guess there really should not be any annotations that would be defined by the web app class loader since these are not application level classes.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879829#3879829

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879829

[Jboss-dev-forums] [Design of JBoss's Web Services Implementation] - Re: WebServiceDeployer integration as deployment interceptor

[<dim...@jb...>]

So the xmbean interceptor idea for the deployers seems to work after all, that's great!

I see in the WebServiceInterceptor that you conditionally forward the call to a delegate mbean.

A more dynamic approach is to plugin to the xmbean-ized deployer (e.g. EJB, EJB3, ...) the DynamicInterceptor which is just a placeholder that allows the dynamic registration/unregistration of interceptors, over the MBeanServer interface.

This has the benefit of not having to alter the xmbean descriptor for every interceptor added, the interceptors attach and detach dynamically (e.g. if you don't have webservices at all) and there can be a better seperation of modules, so the WebServiceInterceptor would live in the webservices module.

That was described here:

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=57296

I might try to refactor this, now that there is a good use-case. I'll also port the DynamicInterceptor stuff to 4.0, soon I hope.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879828#3879828

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879828

[Jboss-dev-forums] [Design of JBoss's Web Services Implementation] - Re: WebServiceDeployer integration as deployment interceptor

[<bil...@jb...>]

"tho...@jb..." wrote : The deployers for EJB, EJB3, WAR have been modified to use inlined xmbean desriptors that allow for deployment interceptors. The WebServiceInterceptor delegates to the appropriate WS endpoint deployer to do the additional work to get the endpoint up and running.
  | 
  | With JSR181 a WS endpoint may be annotated with @WebService for that I need to read the annotation from the endpoint implementation class. Currently, this is done by loading the endpoint class and inspecting the annotations on java.lang.Class
  | 

EJB3 can override the annotation within XML (or provide definition for @WebService.  I hope that annotations are NOT required in J2EE 5 for web services, are they?

anonymous wrote : 
  | With java service endpoints (JSE) the web app context classloader only becomes available after the web app has started. This is too late.
  | 
  | I can see two solutions to the problem:
  | 
  | 1. the annotations are obtained from the *.class file without loading the class
  | 
Not sure if this would solve your problem as you still need a classloader to obtain Javassist structures (or any structure for that matter).  Javassist does ClassLoader.getResource() to obtain access to the raw bytecode.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879825#3879825

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879825

[Jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: requirements for connection failure callback

[<tom...@jb...>]

Ok.  I get what you want for JMS.  So what do you want from remoting that is not already there?  

Here are the possible ways to use remoting:

1. make a uni-directional, synchronous call from client to server, which will throw a CanNotConnectException if the transport can not connect to the server.
2. make a uni-directional, asynchronous call from client to server, where the client's calling thread will block until the server call is made.  This will throw a CanNotConnectException if the transport can not connect to the server.
3. make a uni-directional, asynchronous call from the client to the server, where the client's calling thread will NOT block until the server call is made, but return immediately.  Another work thread on the client will then make the call to the server.  In this case, the client will NOT BE AWARE OF ANY TRANSPORT FAILURES.  This is the case I mentioned previously where I can add an API for registering a exception listener.
4. The server has a handle to the client's callback listener and will make calls on it for callbacks.  In this case, the server (invocation handler) will get a HandleCallbackException if can not deliver the callback to the client's listener.

Other than number 3, I don't see where you would not have what you need.  

The other thing, which is on my roadmap but have not started, is a true bi-directional transport like UIL2.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879823#3879823

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879823

[Jboss-dev-forums] [Design of JBossXB] - Re: Inline bindings with jbxb

[<ad...@jb...>]

I'd like to drop the pojoserver test in the testsuite (I don't want to cross maintain
this everytime new features are added) in favour of more
clearly defined unit tests of the features I'm using in the MC (where they are not
already tested).
e.g. 
1) recursion in the value processing
2) polymorphism in the value processing
3) holders

Basically, turn each one of the patterns I use in BeanSchemaBinding
into a unit test that can be tested with both a programmatic binding and an annotated
binding.

Does this sounds acceptable to you?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879821#3879821

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879821

[Jboss-dev-forums] [Design of Mail Services] - Re: Forwarder listener

[<tom...@jb...>]

I committed to HEAD.  Class is org.jboss.mail.maillistener.ForwarderMailListener and it's interface.  

The configuration entry to jboss-service.xml would look something like:


  |   <!-- Custom listener for forwarding e-mails -->
  |   <mbean code="org.jboss.mail.maillistener.ForwarderMailListener"
  |     name="jboss.mail:type=MailServices,name=ForwarderListener">
  |      <attribute name="Configuration">
  |           <forwarding>
  |                 <forward originalAddress="ad...@ac...">bo...@ac...</forward>
  |                 <forward originalAddress="abc.org">ja...@ac...</forward>
  |                 <forward originalAddress="webadmin">ka...@ab...</forward>
  |          </forwarding>
  |      </attribute>
  |   </mbean>
  | 

The value for the orginalAddress attribute can either be the user name, domain, or a the full e-mail address to match on.  The value for the forward element has to be the full e-mail address of where to forward.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879820#3879820

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879820

[Jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: requirements for connection failure callback

[<ad...@jb...>]

What JMS wants is the following (client side description):

1) Make a bi-directional connection (could be two separate uni-directional connections that are linked in terms of state or uni-directional with polling).
2) Let the server push messages to the client back along that connection
3) If that connection fails due to unrecoverable transport failures
connection.setExceptionListener() is invoked with the failure exception.

Of course, I don't expect you to invoke the jms api directly, that mapping will
be provided by the JMS code from the remoting api.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879818#3879818

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879818

[Jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: requirements for connection failure callback

[<ad...@jb...>]

Tom,

It is a common misconception that JMS should use a "One way" invocation.
I've seen this nonsense repeated so many times. 

It can use it to optimize certain parts of the protocol, e.g. message delivery
to client only needs to be one-way since the result (both the delivery and whether it
was processed successfully) is communicated back through acknowledgements.

It is JMS that implements the "One Way" behaviour, it has other requirements to satisfy
beyond the transport (like persistence and transactions).

When a client does
producer.send(message);
in a persistent context, the client needs to know that when that method 
returns the message delivery is guaranteed.
It cannot do this if the transport is "One Way" (i.e. best effort, maybe it will get there
and you don't know the result).

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879814#3879814

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879814

[Jboss-dev-forums] [Design of JBoss's Web Services Implementation] - WebServiceDeployer integration as deployment interceptor

[<tho...@jb...>]

The deployers for EJB, EJB3, WAR have been modified to use inlined xmbean desriptors that allow for deployment interceptors. The WebServiceInterceptor delegates to the appropriate WS endpoint deployer to do the additional work to get the endpoint up and running.

With JSR181 a WS endpoint may be annotated with @WebService for that I need to read the annotation from the endpoint implementation class. Currently, this is done by loading the endpoint class and inspecting the annotations on java.lang.Class

With java service endpoints (JSE) the web app context classloader only becomes available after the web app has started. This is too late.

I can see two solutions to the problem:

1. the annotations are obtained from the *.class file without loading the class
2. the classloader is made available during the create step

Generally, at what point of the deployment lifecycle should annotation meta data be available?

This has been assigned to

http://jira.jboss.com/jira/browse/JBWS-236


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879813#3879813

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879813

[Jboss-dev-forums] [TODO -- DEVELOPMENT] - Re: Create a Topic with DeploymentService

[<dim...@jb...>]

You are in the wrong forum. I moved your question here:

http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879811#3879811

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879812#3879812

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879812

[Jboss-dev-forums] [TODO -- DEVELOPMENT] - I need to create Topic dinamic form

[janoboss <nu...@jb...>]

Hello, I am using DeploymentService for create Queue dinamic form. I installed deployment-service.sar, I maked deploy with Ant, in this moment i am doing Queue but my question is, How can I create Topic dinamic form? 

thank you.... 

see soon. 
 


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879807#3879807

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879807

[Jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Re: AntBenchmarkReceiver question

[<tom...@jb...>]

Sounds good.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879806#3879806

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879806

[Jboss-dev-forums] [TODO -- DEVELOPMENT] - Create a Topic with DeploymentService

[janoboss <nu...@jb...>]

Hello, I am using DeploymentService for create Queue dinamic form. I installed deployment-service.sar, I maked deploy with Ant, in this moment i am doing Queue but my question is, How can I create Topic dinamic form?

thank you....

see soon.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879804#3879804

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879804