Before you implement the ErroNotifier interface in this way, you may need a local email server that supports the Simple Mail Transfer Protocol (SMTP) for testing purposes.
1.True
2.False
3.none
4.all the mentoined
CronTrigger accepts a Unix cron expression for you to specify the times to run your job.
1.True
2.False
3.none
4.all the mentoined
Spring allows your beans to publish JMX notifications through:-
1.NotificationPublisher
2.Notification
3. Notify
4.all of the mentioned
The MessageCreator interface declares method:-
1.createMessage()
2.create()
3. createMsg()
4. none of the mentioned
To send a JMS message with this template, you simply call:-
1. send
2.sendTo
3. all of the mentioned
4.None of the mentioned
? should be replaced by:- <beans ...> ... <bean id="rmiRegistry" class="org.springframework.remoting.rmi.RmiRegistryFactoryBean" /> <bean id="connectorServer" class="org.springframework.jmx.support.ConnectorServerFactoryBean" depends-on="rmiRegistry"> <property name="serviceUrl" value=? /> </bean> </beans>
1.service:jmx:rmi://localhost/jndi/rmi://localhost:1099/replicator
2.service:jmx:rmi://localhost/jndi/rmi://localhost:1099/
3.service:jmx:rmi://localhost/jndi//localhost:1099/replicator
4.None of the mentioned
A JMS template helps you to obtain and release the JMS connection and session.
1.True
2.False
3.none
4.all the mentoined
Before you can send and receive JMS messages, you need to install a JMS message broker:-
1.Apache ActiveM
2.Apache Active
3.Apache MQ
4. Apache ActiveMQ
Connectors to expose your MBeans for remote access over a specific protocol by using a factory bean.
1.MBeanExporter
2.JSR-160
3.All of the mentioned
4.None of the mentioned
Endpoint Classes for dom4j:-
1. AbstractDomPayloadEndpoint
2.AbstractJDomPayloadEndpoint
3.AbstractDom4jPayloadEndpoint
4. AbstractXomPayloadEndpoint
Endpoint Classes for DOM:-
1.AbstractDomPayloadEndpoint
2.AbstractJDomPayloadEndpoint
3.AbstractDom4jPayloadEndpoint
4.AbstractXomPayloadEndpoint
Endpoint Classes for Event-based StAX:-
1.AbstractDomPayloadEndpoint
2.AbstractSaxPayloadEndpoint
3.AbstractDom4jPayloadEndpoint
4.AbstractStaxEventPayloadEndpoint
Endpoint Classes for JDOM:-
1.AbstractDomPayloadEndpoint
2. AbstractJDomPayloadEndpoint
3.AbstractDom4jPayloadEndpoint
4. AbstractXomPayloadEndpoint
Endpoint Classes for SAX:-
1. AbstractDomPayloadEndpoint
2. AbstractSaxPayloadEndpoint
3.AbstractDom4jPayloadEndpoint
4. AbstractXomPayloadEndpoint
Endpoint Classes for Streaming StAX :-
1.AbstractDomPayloadEndpoint
2. AbstractSaxPayloadEndpoint
3.AbstractStaxStreamPayloadEndpoint
4. AbstractStaxEventPayloadEndpoint
Endpoint Classes for XML marshalling :-
1.AbstractDomPayloadEndpoint
2.AbstractSaxPayloadEndpoint
3.AbstractStaxStreamPayloadEndpoint
4.AbstractMarshallingPayloadEndpoint
Endpoint Classes for XML marshalling :-
1.AbstractDomPayloadEndpoint
2.AbstractSaxPayloadEndpoint
3.AbstractStaxStreamPayloadEndpoint
4.AbstractMarshallingPayloadEndpoint
Endpoint Classes for XOM:-
1. AbstractDomPayloadEndpoint
2. AbstractJDomPayloadEndpoint
3. AbstractDom4jPayloadEndpoint
4.AbstractXomPayloadEndpoint
However, in an environment with no MBean server available, you have to create one explicitly using:-
1.MBeanServerFactoryBean
2. MBeanServerFactory
3.All of the mentioned
4.None of the mentioned
If no RMI registry has been created externally, you should create one by using:-
1.RmiRegistryFactory
2. RmiRegistryFactoryBean
3. RmiRegistry
4.RmiRegister
If you have a JavaMail session configured in your Java EE application server, you can first look it up with the help of:-
1.JndiObjectFactory
2. JndiObjectFactoryBean
3.JndiObject
4.None of the mentioned
If you need to get access to the entire SOAP message, you should write an endpoint class by implementing:-
1.org.springframework.ws.server.endpoint.MessageEndpoint
2.org.springframework.ws
3. org.springframework.ws.server.endpoint
4.All of the mentioned
In this method, you can access the request XML element, whose type is org.dom4j.Element, and the response document, whose type is org.dom4j.Document, as method arguments.
1.invoke
2. invokeInterval
3. invokeInternal
4.None of the mentioned
Method, all files in the source directory will be replicated to the destination directory.
1.replicate
2.copy
3.rep
4. none of the mentioned
MIME is supported by JavaMail through the:-
1.javax.mail.internet.Mime
2. javax.mail.internet.Message
3. javax.mail.internet.MimeMessage
4.javax.mail.internet.Mail
Quartz supports several types of triggers:-
1.SimpleTrigger
2. CronTrigger
3.All of the mentioned
4.None of the mentioned
SimpleTrigger allows you to set trigger properties:-
1.start time
2. end time
3.repeat interval
4.All of the mentioned
Spring 3.0 debuts new support for configuring:-
1.TaskExecutors
2.TaskSchedulers
3.All of the mentioned
4.None of the mentioned
Spring allows you to create a JMX connector server through:-
1.ConnectorServerFactoryBean
2.ConnectorServer
3.ConnectorServerFactory
4. all of the mentioned
Spring also offers MethodInvokingJobDetailFactoryBean for you to define a job that executes a single method of a particular object.
1. True
2. False
3.none
4.all the mentoined
Spring can also detect and export your MBeans automatically from beans declared in the IoC container and annotated with JMX-specific annotations defined by Spring.
1. True
2. False
3.none
4.all the mentoined
Spring supports JMX by allowing you to export any beans in its IoC container as model MBeans.
1.True
2.False
3.none
4.all the mentoined
Spring-WS provides various abstract endpoint classes for you to process the request.
1.org.springframework.ws.server.endpoint
2. org.springframework.ws.server
3.org.springframework.*
4.None of the mentioned
Template which can send and receive JMS messages with much less code
1. JmsTemplate
2.EMail
3.all of the mentioned
4.None of the mentioned
The core interface of Spring email support is:-
1. MailSender
2. EMail
3.All of the mentioned
4.None of the mentioned
The default port used by JavaMailSenderImpl is the:-
1. SMTP port 24
2.SMTP port 22
3.SSH port 22
4.SMTP port 25
The JavaMailSender interface is a subinterface of MailSender that includes specialized JavaMail features:-
1.Multipurpose Internet Mail Extensions
2.Multipurpose Internet Mail
3.Multipurpose Internet Extensions
4. None of the mentioned
The JavaMailSenderImpl instance you injected does implement this interface.
1.True
2.False
3.none
4.all the mentoined
The simplest MBean assembler in Spring is, which allows you to specify the names of the methods to export.
1. MethodNameBasedMBeanInfoAssembler
2.MethodNameBasedMBeanInfo
3.MethodNameBasedMBean
4.MethodNameBasedInfoAssembler
The template handles the boilerplate tasks for you and also converts the JMS API JMSException hierarchy into Spring runtime exception:-
1.org.springframework.jms.Jms
2.org.springframework.jms.JmsException
3.org.springframework.jms.JmsTemplate
4. none of the mentioned
There are several types of messages defined in the JMS API, including:-
1.TextMessage
2.MapMessage
3. BytesMessage
4. all of the mentioned
There are two main options for scheduling tasks on the Java platform:-
1. JDK Timer
2. Quartz Scheduler
3. All of the mentioned
4.None of the mentioned
To address different JMS APIs, Spring provides :-
1. JmsTemplate
2. JmsTemplate102
3. All of the mentioned
4.None of the mentioned
VM argument to enable local monitoring of this application.
1. -Dcom.sun.management.jmxremote
2. -Dcom.sun.management
3. -Dcom.sun.management.jmx
4.None of the mentioned
Web services can be invoked through the core template class:-
1.org.springframework.ws.client.core.WebServiceTemplate
2. JDBC Template
3. All of the mentioned
4.None of the mentioned
WebServiceTemplate provides a sendSourceAndReceiveToResult() method that accepts arguments:-
1.java.xml.transform.Source
2.java.xml.transform.Result
3.all of the mentioned
4.None of the mentioned
You can configure a Quartz SimpleTrigger object in Spring bean configuration file through:-
1. SimpleTrigger
2.SimpleTriggerBean
3.All of the mentioned
4.None of the mentioned
You can create a dom4j endpoint by extending the:-
1.AbstractDom4jPayloadEndpoint
2. AbstractDom4jPayload
3.AbstractDom4jEndpoint
4.None of the mentioned
You can implement the interface to send email notifications in case of errors.
1.Notify
2.Error
3.ErrorNotifier
4.None of the mentioned
You send the email by making a call to:-
1. Transport.send()
2. Transport.sendTo()
3. All of the mentioned
4.None of the mentioned