Enter a Notebook expression: Notebook[{Cell[TextData["Hello world!"], "Text"]}] Cloud Base: Embed Notebook


Hillsong Worship (formerly Hillsong Live) is an Australian praise and worship group from Sydney, Australia, where they started making music in 1983 at Hillsong Church. Fifteen of their songs have appeared on the Billboard magazine charts in the US, with "What a Beautiful Name" (2016) representing their greatest success, reaching platinum in the US. This band is my personal favorite, especially since the songs are such a great inspiration to me. The band was originally formed in 1998, by close friends from within the youth ministry called "Powerhouse Youth", led by Hillsong Youth Pastors Phil and Lucinda Dooley for many years.[1] As the house band for the Powerhouse meetings, the group played original songs and rearranged popular radio tunes at their weekly meeting for local youth aged 16–25. Band members sometimes also contributed to the larger interdenominational ministry Youth Alive Australia and its albums. Most members of the band also attended Hillsong Church services.
Aftermath (stylized as 'aftər,maθ), formerly known as This Means Love, is the second studio album by Australian Contemporary Christian band Hillsong United.
A Beautiful Exchange is the nineteenth album in the live praise and worship series of contemporary worship by Hillsong Church.[4] [5] It was recorded at the Sydney Entertainment Centre.
Empires is the fourth studio album from Australian contemporary worship music band Hillsong United, a worship band from Hillsong Church. The album was released on 26 May 2015.
People is the fourteenth live album from Australian contemporary worship music band Hillsong United. The album was recorded on 18 November 2018 at Hills Campus in Sydney and released on 26 April 2019.
River Wild album was recorded during the 2015 Hillsong Conference at the Sydney SuperDome (currently named the Qudos Bank Arena) from 29 June until 3 July 2015 and was released on 16 October 2015, under Hillsong Music.
Zion is the third studio album by Australian contemporary worship music band Hillsong United. It was released on 22 February 2013 for Australia, and was released by 26 February 2013 internationally, under Hillsong Music and Sparrow Records
Jad was born and raised in New Zealand and at the age of 17 was leading the worship team in his local church. He was 21 when he moved to Sydney, Australia to pursue studies at Hillsong College and the harbour city quickly became home. Jad has been an integral part of the Hillsong UNITED team for over a decade.
Taya Gaukrodger hails from Lismore, a country town in the north of Australia. In 2010 she relocated to Sydney to pursue a career in music. Soon after arriving she began volunteering in the youth, young adult and creative ministries at Hillsong Church.
Joel Houston is a world renowned songwriter and worship leader. Songs such as The Stand, With Everything and Oceans to note, have been anthems of millions across the world. His desire is to see a generation across the earth awakened to the counter-cultural love of Christ, and see all people find hope in Him.
Having grown up in Hillsong Church, Matt Crocker spent most of his teenage years learning how to write songs as part of the youth ministry. Years on, his devotion to and investment into the worship team, songwriting and leading worship has resulted in songs that are sung all over the world.


LGBT Center of Raleigh
Location / Mailing Address
324 South Harrington Street
Raleigh, North Carolina 27603
(919)-832-4484
Email<EMAIL_ADDRESS>HoursMonday - Friday: 12:00 noon - 8:00pm
HIV/STD TestingMonday's and Thursday's | 6:00pm - 7:45pm
Street Parking is available and ranges from 30 minute spaces to 2 hour spaces.
Street Parking time limits ARE STRICTLY ENFORCED
There is dedicated parking behind the center. A parking permit is required to park here and you may obtain a pass from the front desk at the Center
While staffing the Center, volunteers will have access to dedicated parking behind the Center. These spaces require a parking permit that is available at the front desk and must be returned before your shift is complete
Special Events that occur during the week after 6pm (Monday-Thursday) and most of the time on weekends, you may park in the back gravel lot behind the Center. You will not be towed during these times. Please be sure to tell the attendant that you are "Going to an event at the LGBT Center."
Unless otherwise advised by James or Kelly, no one is to park in the back lot without a parking pass or outside of the designated times above. The Center is not responsible for your vehicle or fines/impoundment fees that result in deviation from these guidelines.


public interface JMSContext
extends java.lang.AutoCloseable
JMSContext
is the main interface in the simplified Jakarta Messaging API introduced for Jakarta Messaging 2.0. This combines in a
single object the functionality of two separate objects from the Java Message Service 1.1 API: a Connection
and a
Session
.
When an application needs to send messages it use the createProducer
method to create a JMSProducer
which provides methods to configure and send messages. Messages may be sent either synchronously or asynchronously.
When an application needs to receive messages it uses one of several createConsumer
or
createDurableConsumer
methods to create a JMSConsumer
. A JMSConsumer
provides methods to
receive messages either synchronously or asynchronously.
In terms of the Java Message Service 1.1 API a JMSContext
should be thought of as representing both a Connection
and a
Session
. Although the simplified API removes the need for applications to use those objects, the concepts of
connection and session remain important. A connection represents a physical link to the Jakarta Messaging server and a session
represents a single-threaded context for sending and receiving messages.
A JMSContext
may be created by calling one of several createContext
methods on a
ConnectionFactory
. A JMSContext
that is created in this way is described as being
application-managed. An application-managed JMSContext
must be closed when no longer needed by calling
its close
method.
Applications running in the Jakarta EE web and EJB containers may alternatively inject a JMSContext
into their
application using the @Inject
annotation. A JMSContext
that is created in this way is described as
being container-managed. A container-managed JMSContext
will be closed automatically by the container.
Applications running in the Jakarta EE web and EJB containers are not permitted to create more than one active session on a connection so combining them in a single object takes advantage of this restriction to offer a simpler API.
However applications running in a Java SE environment or in the Jakarta EE application client container are permitted to
create multiple active sessions on the same connection. This allows the same physical connection to be used in
multiple threads simultaneously. Such applications which require multiple sessions to be created on the same
connection should use one of the createContext
methods on the ConnectionFactory
to create the first
JMSContext
and then use the createContext
method on JMSContext
to create additional
JMSContext
objects that use the same connection. All these JMSContext
objects are application-managed
and must be closed when no longer needed by calling their close
method.
| Modifier and Type | Field and Description |
|---|---|
static int |
AUTO_ACKNOWLEDGE
With this session mode, the JMSContext's session automatically acknowledges a client's receipt of a message either
when the session has successfully returned from a call to
receive or when the message listener the session
has called to process the message successfully returns. |
static int |
CLIENT_ACKNOWLEDGE
With this session mode, the client acknowledges a consumed message by calling the message's
acknowledge
method. |
static int |
DUPS_OK_ACKNOWLEDGE
This session mode instructs the JMSContext's session to lazily acknowledge the delivery of messages.
|
static int |
SESSION_TRANSACTED
This session mode instructs the JMSContext's session to deliver and consume messages in a local transaction which
will be subsequently committed by calling
commit or rolled back by calling rollback . |
| Modifier and Type | Method and Description |
|---|---|
void |
acknowledge()
Acknowledges all messages consumed by the JMSContext's session.
|
void |
close()
Closes the JMSContext
|
void |
commit()
Commits all messages done in this transaction and releases any locks currently held.
|
QueueBrowser |
createBrowser(Queue queue)
Creates a
QueueBrowser object to peek at the messages on the specified queue. |
QueueBrowser |
createBrowser(Queue queue,
java.lang.String messageSelector)
Creates a
QueueBrowser object to peek at the messages on the specified queue using a message selector. |
BytesMessage |
createBytesMessage()
Creates a
BytesMessage object. |
JMSConsumer |
createConsumer(Destination destination)
Creates a
JMSConsumer for the specified destination. |
JMSConsumer |
createConsumer(Destination destination,
java.lang.String messageSelector)
Creates a
JMSConsumer for the specified destination, using a message selector. |
JMSConsumer |
createConsumer(Destination destination,
java.lang.String messageSelector,
boolean noLocal)
Creates a
JMSConsumer for the specified destination, specifying a message selector and the noLocal
parameter. |
JMSContext |
createContext(int sessionMode)
Creates a new
JMSContext with the specified session mode using the same connection as this JMSContext
and creating a new session. |
JMSConsumer |
createDurableConsumer(Topic topic,
java.lang.String name)
Creates an unshared durable subscription on the specified topic (if one does not already exist) and creates a
consumer on that durable subscription.
|
JMSConsumer |
createDurableConsumer(Topic topic,
java.lang.String name,
java.lang.String messageSelector,
boolean noLocal)
Creates an unshared durable subscription on the specified topic (if one does not already exist), specifying a message
selector and the
noLocal parameter, and creates a consumer on that durable subscription. |
MapMessage |
createMapMessage()
Creates a
MapMessage object. |
Message |
createMessage()
Creates a
Message object. |
ObjectMessage |
createObjectMessage()
Creates an
ObjectMessage object. |
ObjectMessage |
createObjectMessage(java.io.Serializable object)
Creates an initialized
ObjectMessage object. |
JMSProducer |
createProducer()
Creates a new
JMSProducer object which can be used to configure and send messages |
Queue |
createQueue(java.lang.String queueName)
Creates a
Queue object which encapsulates a specified provider-specific queue name. |
JMSConsumer |
createSharedConsumer(Topic topic,
java.lang.String sharedSubscriptionName)
Creates a shared non-durable subscription with the specified name on the specified topic (if one does not already
exist) and creates a consumer on that subscription.
|
JMSConsumer |
createSharedConsumer(Topic topic,
java.lang.String sharedSubscriptionName,
java.lang.String messageSelector)
Creates a shared non-durable subscription with the specified name on the specified topic (if one does not already
exist) specifying a message selector, and creates a consumer on that subscription.
|
JMSConsumer |
createSharedDurableConsumer(Topic topic,
java.lang.String name)
Creates a shared durable subscription on the specified topic (if one does not already exist), specifying a message
selector, and creates a consumer on that durable subscription.
|
JMSConsumer |
createSharedDurableConsumer(Topic topic,
java.lang.String name,
java.lang.String messageSelector)
Creates a shared durable subscription on the specified topic (if one does not already exist), specifying a message
selector, and creates a consumer on that durable subscription.
|
StreamMessage |
createStreamMessage()
Creates a
StreamMessage object. |
TemporaryQueue |
createTemporaryQueue()
Creates a
TemporaryQueue object. |
TemporaryTopic |
createTemporaryTopic()
Creates a
TemporaryTopic object. |
TextMessage |
createTextMessage()
Creates a
TextMessage object. |
TextMessage |
createTextMessage(java.lang.String text)
Creates an initialized
TextMessage object. |
Topic |
createTopic(java.lang.String topicName)
Creates a
Topic object which encapsulates a specified provider-specific topic name. |
boolean |
getAutoStart()
Returns whether the underlying connection used by this
JMSContext will be started automatically when a
consumer is created. |
java.lang.String |
getClientID()
Gets the client identifier for the JMSContext's connection.
|
ExceptionListener |
getExceptionListener()
Gets the
ExceptionListener object for the JMSContext's connection. |
ConnectionMetaData |
getMetaData()
Gets the connection metadata for the JMSContext's connection.
|
int |
getSessionMode()
Returns the session mode of the JMSContext's session.
|
boolean |
getTransacted()
Indicates whether the JMSContext's session is in transacted mode.
|
void |
recover()
Stops message delivery in the JMSContext's session, and restarts message delivery with the oldest unacknowledged
message.
|
void |
rollback()
Rolls back any messages done in this transaction and releases any locks currently held.
|
void |
setAutoStart(boolean autoStart)
Specifies whether the underlying connection used by this
JMSContext will be started automatically when a
consumer is created. |
void |
setClientID(java.lang.String clientID)
Sets the client identifier for the JMSContext's connection.
|
void |
setExceptionListener(ExceptionListener listener)
Sets an exception listener for the JMSContext's connection.
|
void |
start()
Starts (or restarts) delivery of incoming messages by the JMSContext's connection.
|
void |
stop()
Temporarily stops the delivery of incoming messages by the JMSContext's connection.
|
void |
unsubscribe(java.lang.String name)
Unsubscribes a durable subscription that has been created by a client.
|
static final int AUTO_ACKNOWLEDGE
receive
or when the message listener the session
has called to process the message successfully returns.static final int CLIENT_ACKNOWLEDGE
acknowledge
method. Acknowledging a consumed message acknowledges all messages that the session has consumed.
When this session mode is used, a client may build up a large number of unacknowledged messages while attempting to process them. A Jakarta Messaging provider should provide administrators with a way to limit client overrun so that clients are not driven to resource exhaustion and ensuing failure when some resource they are using is temporarily blocked.
Message.acknowledge()
,
Constant Field Valuesstatic final int DUPS_OK_ACKNOWLEDGE
static final int SESSION_TRANSACTED
commit
or rolled back by calling rollback
.JMSContext createContext(int sessionMode)
JMSContext
with the specified session mode using the same connection as this JMSContext
and creating a new session.
This method does not start the connection. If the connection has not already been started then it will be
automatically started when a JMSConsumer
is created on any of the JMSContext
objects for that
connection.
sessionMode
is set to JMSContext.SESSION_TRANSACTED
then the session will use a local
transaction which may subsequently be committed or rolled back by calling the JMSContext
's commit
or
rollback
methods.
sessionMode
is set to any of JMSContext.CLIENT_ACKNOWLEDGE
,
JMSContext.AUTO_ACKNOWLEDGE
or JMSContext.DUPS_OK_ACKNOWLEDGE
. then the session will be
non-transacted and messages received by this session will be acknowledged according to the value of
sessionMode
. For a definition of the meaning of these acknowledgement modes see the links below.
This method must not be used by applications running in the Jakarta EE web or EJB containers because doing so would
violate the restriction that such an application must not attempt to create more than one active (not closed)
Session
object per connection. If this method is called in a Jakarta EE web or EJB container then a
JMSRuntimeException
will be thrown.
sessionMode
- indicates which of four possible session modes will be used. The permitted values are
JMSContext.SESSION_TRANSACTED
, JMSContext.CLIENT_ACKNOWLEDGE
, JMSContext.AUTO_ACKNOWLEDGE
and
JMSContext.DUPS_OK_ACKNOWLEDGE
.JMSRuntimeException
- if the Jakarta Messaging provider fails to create the JMSContext due to
SESSION_TRANSACTED
,
CLIENT_ACKNOWLEDGE
,
AUTO_ACKNOWLEDGE
,
DUPS_OK_ACKNOWLEDGE
,
ConnectionFactory.createContext()
,
ConnectionFactory.createContext(int)
,
ConnectionFactory.createContext(java.lang.String, java.lang.String)
,
ConnectionFactory.createContext(java.lang.String, java.lang.String, int)
,
createContext(int)
JMSProducer createProducer()
JMSProducer
object which can be used to configure and send messagesJMSProducer
objectJMSProducer
java.lang.String getClientID()
This value is specific to the Jakarta Messaging provider. It is either preconfigured by an administrator in a
ConnectionFactory
object or assigned dynamically by the application by calling the setClientID
method.
JMSRuntimeException
- if the Jakarta Messaging provider fails to return the client ID for the JMSContext's connection due
to some internal error.void setClientID(java.lang.String clientID)
The preferred way to assign a Jakarta Messaging client's client identifier is for it to be configured in a client-specific
ConnectionFactory
object and transparently assigned to the Connection
object it creates.
Alternatively, a client can set the client identifier for the JMSContext's connection using a provider-specific
value. The facility to set its client identifier explicitly is not a mechanism for overriding the identifier that has
been administratively configured. It is provided for the case where no administratively specified identifier exists.
If one does exist, an attempt to change it by setting it must throw an IllegalStateRuntimeException
. If a
client sets the client identifier explicitly, it must do so immediately after it creates the JMSContext and before
any other action on the JMSContext is taken. After this point, setting the client identifier is a programming error
that should throw an IllegalStateRuntimeException
.
The purpose of the client identifier is to associate the JMSContext's connection and its objects with a state maintained on behalf of the client by a provider. The only such state identified by the Jakarta Messaging API is that required to support durable subscriptions.
If another connection with the same clientID
is already running when this method is called, the Jakarta Messaging provider
should detect the duplicate ID and throw an InvalidClientIDException
.
This method must not be used in a Jakarta EE web or EJB application. Doing so may cause a JMSRuntimeException
to
be thrown though this is not guaranteed.
This method must not be used if the JMSContext
is container-managed (injected). Doing so will cause a
IllegalStateRuntimeException
to be thrown.
clientID
- the unique client identifierInvalidClientIDRuntimeException
- if the Jakarta Messaging client specifies an invalid or duplicate client ID.IllegalStateRuntimeException
- JMSContext
is container-managed (injected).
JMSRuntimeException
- if the Jakarta Messaging provider fails to set the client ID for the JMSContext's connection for
one of the following reasons:
ConnectionMetaData getMetaData()
JMSRuntimeException
- if the Jakarta Messaging provider fails to get the connection metadataConnectionMetaData
ExceptionListener getExceptionListener()
ExceptionListener
object for the JMSContext's connection. Not every Connection
has an
ExceptionListener
associated with it.ExceptionListener
for the JMSContext's connection, or null if no ExceptionListener
is
associated with that connection.JMSRuntimeException
- if the Jakarta Messaging provider fails to get the ExceptionListener
for the JMSContext's
connection.Connection.setExceptionListener(jakarta.jms.ExceptionListener)
void setExceptionListener(ExceptionListener listener)
If a Jakarta Messaging provider detects a serious problem with a connection, it informs the connection's ExceptionListener
,
if one has been registered. It does this by calling the listener's onException
method, passing it a
JMSRuntimeException
object describing the problem.
An exception listener allows a client to be notified of a problem asynchronously. Some connections only consume messages, so they would have no other way to learn their connection has failed.
A connection serializes execution of its ExceptionListener
.
A Jakarta Messaging provider should attempt to resolve connection problems itself before it notifies the client of them.
This method must not be used in a Jakarta EE web or EJB application. Doing so may cause a JMSRuntimeException
to
be thrown though this is not guaranteed.
This method must not be used if the JMSContext
is container-managed (injected). Doing so will cause a
IllegalStateRuntimeException
to be thrown.
listener
- the exception listenerIllegalStateRuntimeException
- if the JMSContext
is container-managed (injected).JMSRuntimeException
- if the Jakarta Messaging provider fails to set the exception listener for one of the following
reasons:
void start()
start
on a
connection that has already been started is ignored. Also, it is normally not necessary for application to call this
method, since the underlying connection used by the JMSContext will be started automatically when a
consumer is created.
This method must not be used if the JMSContext
is container-managed (injected).
IllegalStateRuntimeException
- if the JMSContext
is container-managed (injected).JMSRuntimeException
- if the Jakarta Messaging provider fails to start message delivery due to some internal error.stop()
void stop()
start
method. When the connection is stopped, delivery to all the connection's message consumers is
inhibited: synchronous receives block, and messages are not delivered to message listeners.
Stopping a connection has no effect on its ability to send messages. A call to stop
on a connection that has
already been stopped is ignored.
A call to stop
must not return until delivery of messages has paused. This means that a client can rely on
the fact that none of its message listeners will be called and that all threads of control waiting for
receive
calls to return will not return with a message until the connection is restarted. The receive timers
for a stopped connection continue to advance, so receives may time out while the connection is stopped.
If message listeners are running when stop
is invoked, the stop
call must wait until all of them have
returned before it may return. While these message listeners are completing, they must have the full services of the
connection available to them.
However if the stop method is called from a message listener on its own JMSContext
, or any other
JMSContext
that uses the same connection, then it will either fail and throw a
jakarta.jms.IllegalStateRuntimeException
, or it will succeed and stop the connection, blocking until all other
message listeners that may have been running have returned.
Since two alternative behaviors are permitted in this case, applications should avoid calling stop
from a
message listener on its own JMSContext
, or any other JMSContext
that uses the same connection,
because this is not portable.
For the avoidance of doubt, if an exception listener for the JMSContext's connection is running when stop
is
invoked, there is no requirement for the stop
call to wait until the exception listener has returned before
it may return.
This method must not be used in a Jakarta EE web or EJB application. Doing so may cause a JMSRuntimeException
to
be thrown though this is not guaranteed.
This method must not be used if the JMSContext
is container-managed (injected).
IllegalStateRuntimeException
- JMSContext
is container-managed (injected).
JMSRuntimeException
- if the Jakarta Messaging provider fails to stop message delivery for one of the following reasons:
start()
void setAutoStart(boolean autoStart)
JMSContext
will be started automatically when a
consumer is created. This is the default behaviour, and it may be disabled by calling this method with a value of
false
.
This method does not itself either start or stop the connection.
This method must not be used if the JMSContext
is container-managed (injected). Doing so will cause a
IllegalStateRuntimeException
to be thrown.
autoStart
- Whether the underlying connection used by this JMSContext
will be automatically started when
a consumer is created.IllegalStateRuntimeException
- if the JMSContext
is container-managed (injected)getAutoStart()
boolean getAutoStart()
JMSContext
will be started automatically when a
consumer is created.JMSContext
will be started automatically when a
consumer is created.setAutoStart(boolean)
void close()
This closes the underlying session and any underlying producers and consumers. If there are no other active (not closed) JMSContext objects using the underlying connection then this method also closes the underlying connection.
Since a provider typically allocates significant resources outside the JVM on behalf of a connection, clients should close these resources when they are not needed. Relying on garbage collection to eventually reclaim these resources may not be timely enough.
Closing a connection causes all temporary destinations to be deleted.
When this method is invoked, it should not return until message processing has been shut down in an orderly fashion.
This means that all message listeners that may have been running have returned, and that all pending receives have
returned. A close terminates all pending message receives on the connection's sessions' consumers. The receives may
return with a message or with null, depending on whether there was a message available at the time of the close. If
one or more of the connection's sessions' message listeners is processing a message at the time when connection
close
is invoked, all the facilities of the connection and its sessions must remain available to those
listeners until they return control to the Jakarta Messaging provider.
However if the close method is called from a message listener on its own JMSContext
, then it will either fail
and throw a jakarta.jms.IllegalStateRuntimeException
, or it will succeed and close the JMSContext
. If
close
succeeds and the session mode of the JMSContext
is set to AUTO_ACKNOWLEDGE
, the current
message will still be acknowledged automatically when the onMessage call completes.
Since two alternative behaviors are permitted in this case, applications should avoid calling close from a message
listener on its own JMSContext
because this is not portable.
This method must not return until any incomplete asynchronous send operations for this JMSContext have been completed and any CompletionListener callbacks have returned. Incomplete sends should be allowed to complete normally unless an error occurs.
For the avoidance of doubt, if an exception listener for the JMSContext's connection is running when close
is
invoked, there is no requirement for the close
call to wait until the exception listener has returned before
it may return.
Closing a connection causes any of its sessions' transactions in progress to be rolled back. In the case where a
session's work is coordinated by an external transaction manager, a session's commit
and rollback
methods are not used and the result of a closed session's work is determined later by the transaction manager.
Closing a connection does NOT force an acknowledgment of client-acknowledged sessions.
Invoking the acknowledge
method of a received message from a closed connection's session must throw an
IllegalStateRuntimeException
. Closing a closed connection must NOT throw an exception.
A CompletionListener callback method must not call close on its own JMSContext. Doing so will cause an IllegalStateRuntimeException to be thrown.
This method must not be used if the JMSContext
is container-managed (injected). Doing so will cause a
IllegalStateRuntimeException
to be thrown.
close
in interface java.lang.AutoCloseable
IllegalStateRuntimeException
- JMSContext
is container-managed (injected)JMSRuntimeException
- if the Jakarta Messaging provider fails to close the JMSContext
due to some internal error.
For example, a failure to release resources or to close a socket connection can cause this exception to be thrown.BytesMessage createBytesMessage()
BytesMessage
object. A BytesMessage
object is used to send a message containing a stream of
uninterpreted bytes.BytesMessage
objectJMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.MapMessage createMapMessage()
MapMessage
object. A MapMessage
object is used to send a self-defining set of name-value
pairs, where names are String
objects and values are primitive values in the Java programming language.
The message object returned may be sent using any Session
or JMSContext
. It is not restricted to
being sent using the JMSContext
used to create it.
The message object returned may be optimised for use with the Jakarta Messaging provider used to create it. However it can be sent using any Jakarta Messaging provider, not just the Jakarta Messaging provider used to create it.
MapMessage
object.JMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.Message createMessage()
Message
object. The Message
interface is the root interface of all Jakarta Messaging messages. A
Message
object holds all the standard message header information. It can be sent when a message containing
only header information is sufficient.
The message object returned may be sent using any Session
or JMSContext
. It is not restricted to
being sent using the JMSContext
used to create it.
The message object returned may be optimised for use with the Jakarta Messaging provider used to create it. However it can be sent using any Jakarta Messaging provider, not just the Jakarta Messaging provider used to create it.
Message
object.JMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.ObjectMessage createObjectMessage()
ObjectMessage
object. An ObjectMessage
object is used to send a message that contains a
serializable Java object.
The message object returned may be sent using any Session
or JMSContext
. It is not restricted to
being sent using the JMSContext
used to create it.
The message object returned may be optimised for use with the Jakarta Messaging provider used to create it. However it can be sent using any Jakarta Messaging provider, not just the Jakarta Messaging provider used to create it.
ObjectMessage
object.JMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.ObjectMessage createObjectMessage(java.io.Serializable object)
ObjectMessage
object. An ObjectMessage
object is used to send a message that
contains a serializable Java object.
The message object returned may be sent using any Session
or JMSContext
. It is not restricted to
being sent using the JMSContext
used to create it.
The message object returned may be optimised for use with the Jakarta Messaging provider used to create it. However it can be sent using any Jakarta Messaging provider, not just the Jakarta Messaging provider used to create it.
object
- the object to use to initialize this messageObjectMessage
object.JMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.StreamMessage createStreamMessage()
StreamMessage
object. A StreamMessage
object is used to send a self-defining stream of
primitive values in the Java programming language.
The message object returned may be sent using any Session
or JMSContext
. It is not restricted to
being sent using the JMSContext
used to create it.
The message object returned may be optimised for use with the Jakarta Messaging provider used to create it. However it can be sent using any Jakarta Messaging provider, not just the Jakarta Messaging provider used to create it.
StreamMessage
object.JMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.TextMessage createTextMessage()
TextMessage
object. A TextMessage
object is used to send a message containing a
String
object.
The message object returned may be sent using any Session
or JMSContext
. It is not restricted to
being sent using the JMSContext
used to create it.
The message object returned may be optimised for use with the Jakarta Messaging provider used to create it. However it can be sent using any Jakarta Messaging provider, not just the Jakarta Messaging provider used to create it.
TextMessage
object.JMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.TextMessage createTextMessage(java.lang.String text)
TextMessage
object. A TextMessage
object is used to send a message containing
a String
.
The message object returned may be sent using any Session
or JMSContext
. It is not restricted to
being sent using the JMSContext
used to create it.
The message object returned may be optimised for use with the Jakarta Messaging provider used to create it. However it can be sent using any Jakarta Messaging provider, not just the Jakarta Messaging provider used to create it.
text
- the string used to initialize this messageTextMessage
object.JMSRuntimeException
- if the Jakarta Messaging provider fails to create this message due to some internal error.boolean getTransacted()
JMSRuntimeException
- if the Jakarta Messaging provider fails to return the transaction mode due to some internal error.int getSessionMode()
If a session mode was not specified when the JMSContext was created a value of JMSContext.AUTO_ACKNOWLEDGE will be returned.
JMSRuntimeException
- if the Jakarta Messaging provider fails to return the acknowledgment mode due to some internal
error.Connection.createSession(boolean, int)
void commit()
This method must not return until any incomplete asynchronous send operations for this JMSContext have been completed and any CompletionListener callbacks have returned. Incomplete sends should be allowed to complete normally unless an error occurs.
A CompletionListener callback method must not call commit on its own JMSContext. Doing so will cause an IllegalStateRuntimeException to be thrown.
This method must not be used if the JMSContext
is container-managed (injected).
IllegalStateRuntimeException
- JMSContext
is container-managed (injected)
TransactionRolledBackRuntimeException
- if the transaction is rolled back due to some internal error during
commit.JMSRuntimeException
- if the Jakarta Messaging provider fails to commit the transaction due to some internal errorvoid rollback()
This method must not return until any incomplete asynchronous send operations for this JMSContext have been completed and any CompletionListener callbacks have returned. Incomplete sends should be allowed to complete normally unless an error occurs.
A CompletionListener callback method must not call rollback on its own JMSContext. Doing so will cause an IllegalStateRuntimeException to be thrown.
This method must not be used if the JMSContext
is container-managed (injected).
IllegalStateRuntimeException
- JMSContext
is container-managed (injected)
JMSRuntimeException
- if the Jakarta Messaging provider fails to roll back the transaction due to some internal errorvoid recover()
All consumers deliver messages in a serial order. Acknowledging a received message automatically acknowledges all messages that have been delivered to the client.
Restarting a session causes it to take the following actions:
This method must not be used if the JMSContext
is container-managed (injected).
IllegalStateRuntimeException
- JMSContext
is container-managed (injected)
JMSRuntimeException
- if the Jakarta Messaging provider fails to stop and restart message delivery due to some internal
errorJMSConsumer createConsumer(Destination destination)
JMSConsumer
for the specified destination.
A client uses a JMSConsumer
object to receive messages that have been sent to a destination.
There is no need to explicitly call the start()
method as it is done automatically when the consumer
is created, unless the autoStart
property is set to false
with setAutoStart(boolean)
.
destination
- the Destination
to access.JMSConsumer
object.JMSRuntimeException
- if the session fails to create a JMSConsumer
due to some internal error.InvalidDestinationRuntimeException
- if an invalid destination is specified.JMSConsumer createConsumer(Destination destination, java.lang.String messageSelector)
JMSConsumer
for the specified destination, using a message selector.
A client uses a JMSConsumer
object to receive messages that have been sent to a destination.
There is no need to explicitly call the start()
method as it is done automatically when the consumer
is created, unless the autoStart
property is set to false
with setAutoStart(boolean)
.
destination
- the Destination
to accessmessageSelector
- only messages with properties matching the message selector expression are delivered. A value
of null or an empty string indicates that there is no message selector for the JMSConsumer
.JMSConsumer
object.JMSRuntimeException
- if the session fails to create a JMSConsumer
due to some internal error.InvalidDestinationRuntimeException
- if an invalid destination is specified.InvalidSelectorRuntimeException
- if the message selector is invalid.JMSConsumer createConsumer(Destination destination, java.lang.String messageSelector, boolean noLocal)
JMSConsumer
for the specified destination, specifying a message selector and the noLocal
parameter.
A client uses a JMSConsumer
object to receive messages that have been sent to a destination.
The noLocal
argument is for use when the destination is a topic and the JMSContext's connection is also being
used to publish messages to that topic. If noLocal
is set to true then the JMSConsumer
will not
receive messages published to the topic by its own connection. The default value of this argument is false. If the
destination is a queue then the effect of setting noLocal
to true is not specified.
There is no need to explicitly call the start()
method as it is done automatically when the consumer
is created, unless the autoStart
property is set to false
with setAutoStart(boolean)
.
destination
- the Destination
to accessmessageSelector
- only messages with properties matching the message selector expression are delivered. A value
of null or an empty string indicates that there is no message selector for the JMSConsumer
.noLocal
- if true, and the destination is a topic, then the JMSConsumer
will not receive messages
published to the topic by its own connectionJMSConsumer
object.JMSRuntimeException
- if the session fails to create a JMSConsumer
due to some internal error.InvalidDestinationRuntimeException
- if an invalid destination is specified.InvalidSelectorRuntimeException
- if the message selector is invalid.Queue createQueue(java.lang.String queueName)
Queue
object which encapsulates a specified provider-specific queue name.
The use of provider-specific queue names in an application may render the application non-portable. Portable
applications are recommended to not use this method but instead look up an administratively-defined Queue
object using JNDI.
Note that this method simply creates an object that encapsulates the name of a queue. It does not create the physical
queue in the Jakarta Messaging provider. Jakarta Messaging does not provide a method to create the physical queue, since this would be specific
to a given Jakarta Messaging provider. Creating a physical queue is provider-specific and is typically an administrative task
performed by an administrator, though some providers may create them automatically when needed. The one exception to
this is the creation of a temporary queue, which is done using the createTemporaryQueue
method.
queueName
- A provider-specific queue nameJMSRuntimeException
- if a Queue object cannot be created due to some internal errorTopic createTopic(java.lang.String topicName)
Topic
object which encapsulates a specified provider-specific topic name.
The use of provider-specific topic names in an application may render the application non-portable. Portable
applications are recommended to not use this method but instead look up an administratively-defined Topic
object using JNDI.
Note that this method simply creates an object that encapsulates the name of a topic. It does not create the physical
topic in the Jakarta Messaging provider. Jakarta Messaging does not provide a method to create the physical topic, since this would be specific
to a given Jakarta Messaging provider. Creating a physical topic is provider-specific and is typically an administrative task
performed by an administrator, though some providers may create them automatically when needed. The one exception to
this is the creation of a temporary topic, which is done using the createTemporaryTopic
method.
topicName
- A provider-specific topic nameJMSRuntimeException
- if a Topic object cannot be created due to some internal errorJMSConsumer createDurableConsumer(Topic topic, java.lang.String name)
noLocal
value of false
.
A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The Jakarta Messaging provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.
A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe
method.
This method may only be used with unshared durable subscriptions. Any durable subscription created using this method
will be unshared. This means that only one active (i.e. not closed) consumer on the subscription may exist at a time.
The term "consumer" here means a TopicSubscriber
, MessageConsumer
or JMSConsumer
object in
any client.
An unshared durable subscription is identified by a name specified by the client and by the client identifier, which must be set. An application which subsequently wishes to create a consumer on that unshared durable subscription must use the same client identifier.
If an unshared durable subscription already exists with the same name and client identifier, and the same topic,
message selector and noLocal
value has been specified, and there is no consumer already active (i.e. not
closed) on the durable subscription then this method creates a JMSConsumer
on the existing durable
subscription.
If an unshared durable subscription already exists with the same name and client identifier, and there is a consumer
already active (i.e. not closed) on the durable subscription, then a JMSRuntimeException
will be thrown.
If an unshared durable subscription already exists with the same name and client identifier but a different topic,
message selector or noLocal
value has been specified, and there is no consumer already active (i.e. not
closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a
new one.
A shared durable subscription and an unshared durable subscription may not have the same name and client identifier.
If a shared durable subscription already exists with the same name and client identifier then a
JMSRuntimeException
is thrown.
There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId. Such subscriptions would be completely separate.
topic
- the non-temporary Topic
to subscribe toname
- the name used to identify this subscriptionJMSConsumer
object.InvalidDestinationRuntimeException
- if an invalid topic is specified.IllegalStateRuntimeException
- if the client identifier is unsetJMSRuntimeException
- JMSConsumer
due to some internal
error
JMSConsumer createDurableConsumer(Topic topic, java.lang.String name, java.lang.String messageSelector, boolean noLocal)
noLocal
parameter, and creates a consumer on that durable subscription.
A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The Jakarta Messaging provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.
A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe
method.
This method may only be used with unshared durable subscriptions. Any durable subscription created using this method
will be unshared. This means that only one active (i.e. not closed) consumer on the subscription may exist at a time.
The term "consumer" here means a TopicSubscriber
, MessageConsumer
or JMSConsumer
object in
any client.
An unshared durable subscription is identified by a name specified by the client and by the client identifier, which must be set. An application which subsequently wishes to create a consumer on that unshared durable subscription must use the same client identifier.
If an unshared durable subscription already exists with the same name and client identifier, and the same topic,
message selector and noLocal
value has been specified, and there is no consumer already active (i.e. not
closed) on the durable subscription then this method creates a JMSConsumer
on the existing durable
subscription.
If an unshared durable subscription already exists with the same name and client identifier, and there is a consumer
already active (i.e. not closed) on the durable subscription, then a JMSRuntimeException
will be thrown.
If an unshared durable subscription already exists with the same name and client identifier but a different topic,
message selector or noLocal
value has been specified, and there is no consumer already active (i.e. not
closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a
new one.
If noLocal
is set to true then any messages published to the topic using this JMSContext
's
connection, or any other connection with the same client identifier, will not be added to the durable subscription.
A shared durable subscription and an unshared durable subscription may not have the same name and client identifier.
If a shared durable subscription already exists with the same name and client identifier then a
JMSRuntimeException
is thrown.
There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId. Such subscriptions would be completely separate.
This method is identical to the corresponding createDurableSubscriber
method except that it returns a
MessageConsumer
rather than a TopicSubscriber
to represent the consumer.
topic
- the non-temporary Topic
to subscribe toname
- the name used to identify this subscriptionmessageSelector
- only messages with properties matching the message selector expression are added to the
durable subscription. A value of null or an empty string indicates that there is no message selector for the durable
subscription.noLocal
- if true then any messages published to the topic using this session's connection, or any other
connection with the same client identifier, will not be added to the durable subscription.JMSConsumer
object.InvalidDestinationRuntimeException
- if an invalid topic is specified.InvalidSelectorRuntimeException
- if the message selector is invalid.IllegalStateRuntimeException
- if the client identifier is unsetJMSRuntimeException
- JMSConsumer
due to some internal
error
JMSConsumer createSharedDurableConsumer(Topic topic, java.lang.String name)
A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The Jakarta Messaging provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.
A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe
method.
This method may only be used with shared durable subscriptions. Any durable subscription created using this method
will be shared. This means that multiple active (i.e. not closed) consumers on the subscription may exist at the same
time. The term "consumer" here means a MessageConsumer
or JMSConsumer
object in any client.
A shared durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared durable subscription must use the same client identifier.
If a shared durable subscription already exists with the same name and client identifier (if set), and the same topic
and message selector has been specified, then this method creates a JMSConsumer
on the existing shared
durable subscription.
If a shared durable subscription already exists with the same name and client identifier (if set) but a different topic or message selector has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.
If a shared durable subscription already exists with the same name and client identifier (if set) but a different
topic or message selector has been specified, and there is a consumer already active (i.e. not closed) on the durable
subscription, then a JMSRuntimeException
will be thrown.
A shared durable subscription and an unshared durable subscription may not have the same name and client identifier
(if set). If an unshared durable subscription already exists with the same name and client identifier (if set) then a
JMSRuntimeException
is thrown.
If a message selector is specified then only messages with properties matching the message selector expression will be added to the subscription.
There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.
There is no need to explicitly call the start()
method as it is done automatically when the consumer
is created, unless the autoStart
property is set to false
with setAutoStart(boolean)
.
topic
- the non-temporary Topic
to subscribe toname
- the name used to identify this subscriptionJMSConsumer
object.InvalidDestinationRuntimeException
- if an invalid topic is specified.JMSRuntimeException
- MessageConsumer
due to some internal
error
JMSConsumer createSharedDurableConsumer(Topic topic, java.lang.String name, java.lang.String messageSelector)
A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it. The Jakarta Messaging provider retains a record of this durable subscription and ensures that all messages from the topic's publishers are retained until they are delivered to, and acknowledged by, a consumer on this durable subscription or until they have expired.
A durable subscription will continue to accumulate messages until it is deleted using the unsubscribe
method.
This method may only be used with shared durable subscriptions. Any durable subscription created using this method
will be shared. This means that multiple active (i.e. not closed) consumers on the subscription may exist at the same
time. The term "consumer" here means a MessageConsumer
or JMSConsumer
object in any client.
A shared durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared durable subscription must use the same client identifier.
If a shared durable subscription already exists with the same name and client identifier (if set), and the same topic
and message selector have been specified, then this method creates a JMSConsumer
on the existing shared
durable subscription.
If a shared durable subscription already exists with the same name and client identifier (if set), but a different topic or message selector has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one.
If a shared durable subscription already exists with the same name and client identifier (if set) but a different
topic or message selector has been specified, and there is a consumer already active (i.e. not closed) on the durable
subscription, then a JMSRuntimeException
will be thrown.
A shared durable subscription and an unshared durable subscription may not have the same name and client identifier
(if set). If an unshared durable subscription already exists with the same name and client identifier (if set) then a
JMSRuntimeException
is thrown.
There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.
There is no need to explicitly call the start()
method as it is done automatically when the consumer
is created, unless the autoStart
property is set to false
with setAutoStart(boolean)
.
topic
- the non-temporary Topic
to subscribe toname
- the name used to identify this subscriptionmessageSelector
- only messages with properties matching the message selector expression are added to the
durable subscription. A value of null or an empty string indicates that there is no message selector for the durable
subscription.JMSConsumer
object.InvalidDestinationRuntimeException
- if an invalid topic is specified.InvalidSelectorRuntimeException
- if the message selector is invalid.JMSRuntimeException
- JMSConsumer
due to some internal error
JMSConsumer createSharedConsumer(Topic topic, java.lang.String sharedSubscriptionName)
If a shared non-durable subscription already exists with the same name and client identifier (if set), and the same
topic and message selector has been specified, then this method creates a JMSConsumer
on the existing
subscription.
A non-durable shared subscription is used by a client which needs to be able to share the work of receiving messages
from a topic subscription amongst multiple consumers. A non-durable shared subscription may therefore have more than
one consumer. Each message from the subscription will be delivered to only one of the consumers on that subscription.
Such a subscription is not persisted and will be deleted (together with any undelivered messages associated with it)
when there are no consumers on it. The term "consumer" here means a MessageConsumer
or JMSConsumer
object in any client.
A shared non-durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared non-durable subscription must use the same client identifier.
If a shared non-durable subscription already exists with the same name and client identifier (if set) but a different
topic or message selector value has been specified, and there is a consumer already active (i.e. not closed) on the
subscription, then a JMSRuntimeException
will be thrown.
There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.
There is no need to explicitly call the start()
method as it is done automatically when the consumer
is created, unless the autoStart
property is set to false
with setAutoStart(boolean)
.
topic
- the Topic
to subscribe tosharedSubscriptionName
- the name used to identify the shared non-durable subscriptionJMSConsumer
object.JMSRuntimeException
- if the session fails to create the shared non-durable subscription and JMSContext
due to some internal error.InvalidDestinationRuntimeException
- if an invalid topic is specified.InvalidSelectorRuntimeException
- if the message selector is invalid.JMSConsumer createSharedConsumer(Topic topic, java.lang.String sharedSubscriptionName, java.lang.String messageSelector)
If a shared non-durable subscription already exists with the same name and client identifier (if set), and the same
topic and message selector has been specified, then this method creates a JMSConsumer
on the existing
subscription.
A non-durable shared subscription is used by a client which needs to be able to share the work of receiving messages
from a topic subscription amongst multiple consumers. A non-durable shared subscription may therefore have more than
one consumer. Each message from the subscription will be delivered to only one of the consumers on that subscription.
Such a subscription is not persisted and will be deleted (together with any undelivered messages associated with it)
when there are no consumers on it. The term "consumer" here means a MessageConsumer
or JMSConsumer
object in any client.
A shared non-durable subscription is identified by a name specified by the client and by the client identifier (which may be unset). An application which subsequently wishes to create a consumer on that shared non-durable subscription must use the same client identifier.
If a shared non-durable subscription already exists with the same name and client identifier (if set) but a different
topic or message selector has been specified, and there is a consumer already active (i.e. not closed) on the
subscription, then a JMSRuntimeException
will be thrown.
There is no restriction on durable subscriptions and shared non-durable subscriptions having the same name and clientId (which may be unset). Such subscriptions would be completely separate.
There is no need to explicitly call the start()
method as it is done automatically when the consumer
is created, unless the autoStart
property is set to false
with setAutoStart(boolean)
.
topic
- the Topic
to subscribe tosharedSubscriptionName
- the name used to identify the shared non-durable subscriptionmessageSelector
- only messages with properties matching the message selector expression are added to the shared
non-durable subscription. A value of null or an empty string indicates that there is no message selector for the
shared non-durable subscription.JMSConsumer
object.JMSRuntimeException
- if the session fails to create the shared non-durable subscription and
JMSConsumer
due to some internal error.InvalidDestinationRuntimeException
- if an invalid topic is specified.InvalidSelectorRuntimeException
- if the message selector is invalid.QueueBrowser createBrowser(Queue queue)
QueueBrowser
object to peek at the messages on the specified queue.queue
- the queue
to accessQueueBrowser
object.JMSRuntimeException
- if the session fails to create a browser due to some internal error.InvalidDestinationRuntimeException
- if an invalid destination is specifiedQueueBrowser createBrowser(Queue queue, java.lang.String messageSelector)
QueueBrowser
object to peek at the messages on the specified queue using a message selector.queue
- the queue
to accessmessageSelector
- only messages with properties matching the message selector expression are delivered. A value
of null or an empty string indicates that there is no message selector for the message consumer.QueueBrowser
object.JMSRuntimeException
- if the session fails to create a browser due to some internal error.InvalidDestinationRuntimeException
- if an invalid destination is specifiedInvalidSelectorRuntimeException
- if the message selector is invalid.TemporaryQueue createTemporaryQueue()
TemporaryQueue
object. Its lifetime will be that of the JMSContext's Connection
unless it
is deleted earlier.JMSRuntimeException
- if the session fails to create a temporary queue due to some internal error.TemporaryTopic createTemporaryTopic()
TemporaryTopic
object. Its lifetime will be that of the JMSContext's Connection
unless it
is deleted earlier.JMSRuntimeException
- if the session fails to create a temporary topic due to some internal error.void unsubscribe(java.lang.String name)
This method deletes the state being maintained on behalf of the subscriber by its provider.
A durable subscription is identified by a name specified by the client and by the client identifier if set. If the client identifier was set when the durable subscription was created then a client which subsequently wishes to use this method to delete a durable subscription must use the same client identifier.
It is erroneous for a client to delete a durable subscription while there is an active (not closed) consumer on that subscription, or while a consumed message is part of a pending transaction or has not been acknowledged in the session.
If the active consumer is represented by a JMSConsumer
then calling close
on either that object or
the JMSContext
used to create it will render the consumer inactive and allow the subscription to be deleted.
If the active consumer was created by calling setMessageListener
on the JMSContext
then calling
close
on the JMSContext
will render the consumer inactive and allow the subscription to be deleted.
If the active consumer is represented by a MessageConsumer
or TopicSubscriber
then calling
close
on that object or on the Session
or Connection
used to create it will render the
consumer inactive and allow the subscription to be deleted.
name
- the name used to identify this subscriptionJMSRuntimeException
- if the session fails to unsubscribe to the durable subscription due to some internal
error.InvalidDestinationRuntimeException
- if an invalid subscription name is specified.void acknowledge()
This method is for use when the session has an acknowledgement mode of CLIENT_ACKNOWLEDGE. If the session is transacted or has an acknowledgement mode of AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE calling this method has no effect.
This method has identical behaviour to the acknowledge
method on Message
. A client may individually
acknowledge each message as it is consumed, or it may choose to acknowledge messages as an application-defined group.
In both cases it makes no difference which of these two methods is used.
Messages that have been received but not acknowledged may be redelivered.
This method must not be used if the JMSContext
is container-managed (injected).
IllegalStateRuntimeException
- JMSContext
is closed.
JMSContext
is container-managed (injected)
JMSRuntimeException
- if the Jakarta Messaging provider fails to acknowledge the messages due to some internal errorSession.CLIENT_ACKNOWLEDGE
,
Message.acknowledge()


Event name is too short.
Event name is too long.
Event name is required.
Event Location is required.
Sathesh Kumar
<EMAIL_ADDRESS>+ Add more attendees
20 Feb 2016, 10:00am - 4:00pm
Venue: Hiton hotel, singapore


Explore your webpages
When you want to make a Helena program, first pick the website or websites from which you'll collect data. Look around the webpages you'll use so that you know where your information is located. For this tutorial, you'll be extracting data from
http://helena-lang.org/sample-data, so take a moment to play around with that page and its links. And remember, once you're doing a demonstration, everything that you do during the recording is also going to be done by your program; so now's the time to do any stray clicks, follow stray links, and generally figure out where your data lives.
Decide what data you want
Next decide what you want to include in your dataset - you should know exactly how your target dataset should look. Let's say we want to collect the following table:
| Scandal |
Awesome! |
| Buffy the Vampire Slayer |
Awesome! |
| Angel |
Not So Awesome |
So we want to know, for each TV show in the list, what's the title of the show and what's the extremely subjective quality rating. When we use Helena, we write a scraping program by demonstrating how we interact with the browser to collect the first row, so we'll want to demonstrate how to collect "Scandal" and "Awesome!" from the webpage. Then Helena will write a program for collecting all three rows.
Open the extension
Let's figure out how we demonstrate with Helena. Let's navigate to
http://helena-lang.org/sample-data, then open the extension. We open the extension by clicking on the icon at the upper right. This opens the control panel on the left:
And at the right, we see a new window, open to the URL we were using when we clicked on the Helena icon. This is the recoding window. Everything that we want to have recorded needs to happen in this window, because Helena isn't paying attention to any of the other Chrome windows we might have open. We recommend keeping both the control panel and the recording window visible throughout recording so that Helena can give you feedback about the data you're collecting.
Figure out what you can scrape
When you make a demonstration, your job is to show Helena how you'd collect the
first row of the dataset you want. We already decided that our first row is the title and subjective rating of the first show in our list, so "Scandal" and "Awesome!" from
http://helena-lang.org/sample-data. Let's figure out if we can scrape that. When you're doing a Helena demonstration, you can interact with the browser as usual, but you'll see a couple new things too. First, you can get hints about what kind of data Helena can collect for you. As you mouse over the page, you'll see a little white box following your mouse. That box shows the text Helena can collect from the element currently under your mouse.
Collect some cells
During a recording, the control pane shows directions for how to collect data from webpages, and the directions include a keyboard shortcut you can use. The particular shortcut varies based on what operating system you're using, but usually it's just the ALT key, so we'll just talk about using the ALT key, and you can look at the instructions if that isn't working for you. During a demonstration, when you hold down the ALT key, you'll see a red highlight following your mouse around when you mouse over webpages in the recording window; this red highlight lets you know which webpage elements you can add as news cells to your first row of data. When you're ready to add new cells to the first row of your target dataset, hold down the ALT key, click on all the elements you want to add to the first row, then let up the ALT key. Remember, our first row is "Scandal" and "Awesome!", so we'll collect those cells right now:
In the control pane, you'll see the first row growing as you add new cells:
Collect link cells
The normal keyboard shortcut collects the text of a webpage element, but if the webpage element is a link, you can also collect the URL/href associated with the link. Just hold down the normal keyboard shortcut plus the SHIFT key, then click. The preview pane at left will show the URL - if the element has one!
Stop recording
Once you've collected all the data you want in your first row, click on the 'Stop Recording' button. Helena will analyze the webpages you used to figure out if there are any relevant tables. For instance, we interacted with the first TV show in a table of TV shows, so it will guess that we want to collect information about all TV shows in the list. You can sit back and wait while the tool figures out what tables to use. Here's how this process looks in the tool:
In the control pane on the left, we see a representation of the program Helena has written. The purple blocks represent actions you took during your recording. The orange block adds a row of data to your output dataset. The yellow block is a loop, and it represents repeating actions for each row in a table. For instance, here the yellow block will cause us to repeat actions for each TV show in a table of TV shows. Helena may or may not have good names for the tables you use, depending on whether other Helena users have used the tables before. In this case, someone has used the TV shows table before and given it a descriptive name, so we see a nice name in our program.
Run a program
Now that Helena has written the program, let's run it. Just click the run button in the control pane. The control pane will show a preview of the dataset it's collecting. On the right you'll see the window Helena is using to access and collect all the data in the dataset.
Exercise 1: If you haven't been trying this process yourself so far, now's a great time to see if you can get this program up and running yourself.
Exercise 2: Try collecting this dataset instead:
| Scandal |
2012 |
2018 |
| Buffy the Vampire Slayer |
1996 |
2003 |
| Angel |
1999 |
2004 |
Use multiple tables
Let's get a little fancier. Say we want to collect multiple tables - say, information about each TV show and for each TV show, information about each character:
| Scandal |
Olivia Pope |
| Scandal |
Abby Whelan |
| Buffy the Vampire Slayer |
Buffy Summers |
| ... |
... |
We'll need to interact with the TV shows table but also a bunch of character tables. To collect this data, we'll do the same thing we did before - demonstrating how to collect the first row - but this time the first row will come from multiple webpages:
Notice the green highlights that Helena uses to indicate it's interacting with particular webpage elements. Remember, everything you do during a recording is also going to be done by your program, so keep your recording streamlined if you want to keep your program streamlined.
Exercise 3: Collect this dataset of TV shows and characters.
Download data
Once you've collected a dataset, you can use the download buttons to download the datset spreadsheets (in CSV format).
The button on the left, "Download Data (This Scrape)" downloads a CSV that includes all the data collected by the current program run - the rows in the current "Script Run" tab in the control pane. The button on the right, "Download Data (All Scrapes)" downloads a CSV that includes all the data ever collected by any run of the program.
Try a real website
Let's try a real website. Play around with the data available at Google Scholar, specifically at this webpage:
https://scholar.google.com/citations?hl=en&view_op=search_authors&mauthors=label%3Acomputer_science. Try to figure out how to collect this target dataset:
| Geoffrey Hinton |
Emeritus Prof. Comp Sci, U.Toronto & Engineering Fellow, Google |
| DEYWIS MORENO |
High Energy Physicist, Universidad Antonio Narino |
| ... |
... |
Did you figure it out? Here's how it goes:
Exercise 4: Collect this target dataset.
Try multiple tables from a real website
Let's scale up to a large dataset! We're going to start at
https://scholar.google.com/citations?hl=en&view_op=search_authors&mauthors=label%3Acomputer_science again. But this time our target dataset is this:
| Geoffrey Hinton |
Learning internal representations by error-propagation |
1986 |
| Geoffrey Hinton |
Learning representations by back-propagating errors |
1986 |
| ... |
... |
... |
| DEYWIS MORENO |
The ATLAS experiment at the CERN large hadron collider |
2008 |
| ... |
... |
... |
Notice we don't just want papers from the first author - we want to go through all the papers by author 1, then all the papers by author 2, and so on. Here's how we collect it:
Exercise 5: Collect this target dataset.


Hot Restaurant
Book Your Seat Before They Are All Gone!
View Tables
Make Reservation
API Table Link
| API Waitlist Link


This is a help page to help you to use our new search engine. It offers more type of reasearch than a mere search engine.
to run a search enter a keyword in the searchbar (1), and select your language (2). The results will automatically display under the search bar and will be classified in function of the search type (3).
ISI Search offers 4 different search types, each one is represented by a different tree.
The classical search is in the pink column. It has two parts :
The exotic search is in the purple column. It aims to guide your search in a less common search with a keywords list more or less linked to your search. To add one of these kewords to your search you just need to click on it.
The social search, it is to say a search trought social networks, you can access it with the "accès recherche via réseaux sociaux" button. It will open a new window in witch you can connect on some social networks. You can use the search bar to run a search throught those you are log on.
The media search is in the dark green column. It will return a media list (texts and sounds) wich correspond to you search from our database.
For image search you need to clic on the cat and on the "image" button in the new opened window. It will offer you two way for your search :
First, you can upload an image from your computer and it will return images with similar colors. You can filter black and/or white to ignore background colors.
Sencond, you can choose a color and an error range to get images which contains colors in this range.
By cliking on the cats you can upload texts and musics to enhance the test database.
All types of search are display by default. To show/hide one of them you just need to click on the correspondant tree. The tree of a hide research is colored in gray.
if you find a bug, have a question, use problem, suggestion, remark or anything else to communicate to the developpers, you can send a message whith the form on contact page or directly on our github page.
The MIT License (MIT)
Copyright (c) 2014 ISI students at the University of Strasbourg
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
"Apple tree" part :
"Bush" part :
"Willow" part :
"Fir tree" part :


Gets the scheduled tasks for the current computer.
Get-ScheduledTask [[-Name] <String>] [<CommonParameters>]
The Get-ScheduledTask
function gets the scheduled tasks on the current computer. It returns Carbon.TaskScheduler.TaskInfo
objects for each one.
With no parameters, Get-ScheduledTask
returns all scheduled tasks. To get a specific scheduled task, use the Name
parameter, which must be the full name of the task, i.e. path plus name. The name parameter accepts wildcards. If a scheduled task with the given name isn't found, an error is written.
This function has the same name as the built-in Get-ScheduledTask
function that comes on Windows 2012/8 and later. It returns objects with the same properties, but if you want to use the built-in function, use the ScheduledTasks
qualifier, e.g. ScheduledTasks\Get-ScheduledTask
.
| Name | Type | Description | Required? | Pipeline Input | Default Value |
|---|---|---|---|---|---|
| Name | String | The name of the scheduled task to return. Wildcards supported. This must be the full task name, i.e. the task's path/location and its name. |
false | false |
Carbon.TaskScheduler.TaskInfo.
Get-ScheduledTask
Demonstrates how to get all scheduled tasks.
Get-ScheduledTask -Name 'AutoUpdateMyApp'
Demonstrates how to get a specific task.
Get-ScheduledTask -Name '*Microsoft*'
Demonstrates how to get all tasks that match a wildcard pattern.
ScheduledTasks\Get-ScheduledTask
Demonstrates how to call the Get-ScheduledTask
function in the ScheduledTasks
module which ships on Windows 2012/8 and later.


Computational Linear Algebra
Table of Contents
Table of Contents
Target Boxes
Normalizing a vector
Matrix Addition
Matrix Subtraction
Matrix Multiplication
Matrix Transpose
Dot Product
Cross Product
Angle Between Vectors
Determinant
Adjugate
Inverse Matrices
Eigenvalues and Eigenvectors
Gaussian Elimination
Rank
Parametric Form of a Line
Implicit Form of a Line
Line Intersection


Harper is a simulated search and rescue robot that uses path planning algorithms, LiDAR and SLAM to rescue survivors.
Video coming soon! GitHub RepoHoward uses computer vision to detect lanes, stop at intersections, and go around obstacles.
Video GitHub Repo


VS Computer
Player 1
Submit
Player 1
Computer
Restart the Game
Play with Friend!
Home
Gameboard colors:
Red: Miss
Green: Hit
Orange: Selected
Yellow: Winner's remaining squares


class Point : ClusterItem
Class used to represent points on the Google Map. Implements ClusterItem
See Also
ClusterItem
| <init> |
Point()
Data constractor which initiates all the properties |
| getPosition |
fun getPosition(): LatLng |
| getSnippet |
fun getSnippet(): java.lang.String |
| getTitle |
fun getTitle(): java.lang.String |
| setLatitude |
fun setLatitude(): void |
| setLongitude |
fun setLongitude(): void |
| WIMSPoint |
class WIMSPoint : com.epimorphics.android.myrivers.data.Point
Data class storing water quality sample details found in Water Quality Data Archive(WIMS). Extends Point. |


This is an alternative universe where almost everything is the same except that almost everyone is the opposite gender from the original universe. Heck, your dog might even be a cat in this universe! Normally in a stock TV show episode, the main character gets stuck in this universe or vice versa. This is a very popular stock alternative universe for fanfics and fan art.
Sub-Trope of Distaff Counterpart and Bizarro Universe, where it's just the sexes of characters that are changed. See also Rule 63, which would only apply when this trope occurs in fanworks.
Not a Gender Bender sub-trope, as it's not an effect of sex-switching on a single person. This is a whole separate universe, full of Distaff Counterpart.
Examples:
open/close all folders
Anime & Manga
- One of the special chapters of Aria took place in an alternate universe where Undines are a male only profession. President Aria somehow got stuck in this universe and spent the whole day dealing with opposite sex versions of the whole cast.
- Maid-Sama!: "The Student Council President is a Butler!" omake flips everyone's gender.
- In Spirit Circle, looks like this is where Fuuko lives. Her life is explicitly stated to take place in an alternate universe of Fuuta's life, and she's the only one of his incarnations who is female. It also shows us her version of Fuuta's friends, all of which are also the opposite gender of their other incarnations.
- Urusei Yatsura: In one anime-original episode, Lum gets transported into a dimension where she briefly meets Gender-bent versions of Megane, the rest of the Lum stormtroopers, Ryuunouske and her(his) father(mother).
Comic Books
- One arc of The Authority saw the team visit an alternate universe where everyone had the opposite gender of their counterpart in the main Wildstorm universe, and where gender roles were reversed. Jack Hawksmoor walked away disturbed at the sight of his counterpart being heavily pregnant.
- In The Multiversity, the DC Universe's Earth-11 is basically "Earth-Gender Flip", with all the major characters swapped. (Oddly, the Green Lantern counterpart is not "Hannah Jordan" or whatever, but Carol Ferris as Star Sapphire. She's the only character who works like this.)
- The concept of a genderbend universe first appeared in Superman #349 (July 1980), which was created by Mr. Mxyzptlk to trick Superman into thinking he somehow ended up in another universe. It ends up failing because Superwoman and Clara Kent exists as separate people (and found that Mxy is still male in this world).
- In Web Warriors, one of the alternate universes is a world where everyone's gender, name, and moral alignment is opposite of their Earth-616 counterpart. It is the home of Octavia Otto.
- Exiles had this show up from time to time, though typically as one offs where the team jaunted through for a couple panels but didn't have a great deal of plot relevance.
Fan Works
- On a Cross and Arrow has one such universe parallel to Equestria.
Literature
- In the book series "The Magical States of America", there is an alternate universe where every person from "our" universe has a gender-swapped counterpart in a world that runs on magic instead of science.
- The Twilight one-shot book Life and Death: Twilight Reimagined is set in an alternate universe where the major characters are genderflipped; Bella Swan becomes Beaufort Swan, Edward Cullen becomes Edythe Cullen, Jacob Black becomes Julie Black, etc. Not everyone is genderflipped, though; Beaufort still moves to Forks to live with his father after his mother remarried.
Live-Action TV
- The Malcolm in the Middle episode "If Girls Were Boys" deconstructs this: while Lois fantasizes about how the problems would be far less common if she had all girls instead of boys (when she was pregnant with Jamie), by the end she realizes that both genders have their problems—if she had girls, she might wish they were boys instead.
- The Red Dwarf episode appropriately titled "Parallel Universe" featured gender-bent versions of most of the main characters (except for the cat; his parallel-universe equivalent was a dog). Also, in this parallel universe, men are the ones that can get pregnant, resulting in women being the dominant gender (Wilma Shakespeare was the most famous writer in that universe, while Nellie Armstrong was the first person to walk on the moon). However, the gender gap has closed since the 60s thanks to the efforts of masculists like Jeremy Greer.
- Sliders: The antagonist of the episode "Double Cross", Logan St. Claire, is revealed towards the end to be the double of main character Quinn Mallory. This is their first time encountering such a situation, as the Sliders' doubles have typically been just that, doubles.
Quinn: That's impossible. How can my double be a woman?
Arturo: It is the difference between an X- and Y-chromosome, Mr. Mallory.
Podcasts
- Red Panda Adventures: In "The World Next Door", the Red Panda and Flying Squirrel meet Baboon MacSmoothie, a traveler from an alternate timeline's future, there to steal something from the past without causing a paradox. During his visit, it's learned his world is vastly different from the main universe. Among other things, the Flying Squirrel was a teenage boy named Kent Baxter, rather than an adult woman named Kit Baxter. Kit tells the Panda that "Kent" would have been her name had she been a boy. A later reference to this world mentions a male villain called the "Necromator", who the Red Panda assumed is a gender flip of one of his own Rogues' Gallery villainess, Professor Zombie.
Tabletop Games
- Implied in Super Munchkin with the "alternate dimension version" card, which changes the sex of a player character.
Video Games
- A staple of the Fate series, which features genderbent versions of popular figures from history, folklore, and urban legend. Despite this, the trope is inverted with its signature character, Artoria Pendragon— our universe's "Arthur" is a female, but the male Arthur comes from a parallel world.
Web Animation
- Eddsworld had the episode "Mirror Mirror" in which there was a world with female versions of the main cast connected by Matt and Matilda's mirrors.
Web Comics
- Ennui GO! features a short run of strips in a gender-flipped alternate universe. The characters' roles and personalities were generally unchanged, although the feminine version of Noah had gigantic Gag Boobs instead of the regular Noah's Gag Penis, and the male version of Sarah had a thick mustache.
- Parodied in Val and Isaac.Val quickly got fed up of being "Girl Val" when the other Vals got together to solve a crisis (the other characters have a more or less even gender ratio across the multiverse).
Western Animation
- Adventure Time has a gender-bent universe that is the main setting of Ice King's stories. Examples include Fionna, a gender-bent Finn, and Cake who is a female cat that is the counterpart of Jake the Dog.
- Johnny Test: The episode "Johnny Alternative" revolves around Johnny and Dukey being sent to an alternate universe where everyone, including the duo, is the opposite gender (Johnny Test -> Joni West, Dukey -> Duchy, Eugene -> Eugenia, Susan Test -> Simon West, Mister Mittens -> Madame Mittens, etc.)
- Subverted in The Loud House episode "One of the Boys", where there seems to be a world where the Loud girls have turned into boys, Clyde, and Bobby into girls, and eventually Lincoln into a girl, but it turns out to be All Just a Dream.
- SheZow has Gal/DudePow, a Distaff Counterpart of Guy / SheZow from a alternate universe. There are also other characters in that alternate universe who are gender-flipped as well.
- In Ultimate Spider-Man, Spider-Man travels to an alternate universe where all the characters are gender-flipped. He meets his female counterpart, Petra Parker. This version of Earth is seemingly matriarchal, with Peter given a Stay in the Kitchen attitude from Petra. They still manage to work together to fight both his Green Goblin and her Green Goblin.


Weeknotes
31 May 2021
Work
- Testing toy code for viral infection data.
- Testing LD pruning in viral genomes.
- Writing results on viral association genetics.
- International collaboration call on host-pathogen interaction, hosted in Vanderbilt.
- Swiss Genomics Forum 2021 https://www.health2030genome.ch/swiss-genomics-forum/. Good talk from Nicholas Katsanis https://www.rescindotherapeutics.com/about and panel discussion.
Personal
- Website CSS building.
- Implementing Rake for webdev.
- Tech4Growth workshop.
Reading
-
The Honourable Schoolboy, John le Carré.
-
Zhang et al., 2021 AJHG. A computational approach for detecting physiological homogeneity in the midst of genetic heterogeneity.
- Accelerating Genomic Data Generation and Facilitating Genomic Data Access Using Decentralization, Privacy-Preserving Technologies and Equitable Compensation. Nublua, George Church et al. (See podcast below for related talk on smart contracts).
- Sergei Loznitsa’s monumental State Funeral.
- Yazz Ahmed - Polyhymnia
- Floating Points, Pharoah Sanders & The London Symphony Orchestra - Promises.
- Ana Vidović - in concert.
- Podcast - Lex Fridman Podcast, #181 – Sergey Nazarov: Chainlink, Smart Contracts, and Oracle Networks
Weeknotes
31 May 2021
Work
- Testing toy code for viral infection data.
- Testing LD pruning in viral genomes.
- Writing results on viral association genetics.
- International collaboration call on host-pathogen interaction, hosted in Vanderbilt.
- Swiss Genomics Forum 2021 https://www.health2030genome.ch/swiss-genomics-forum/. Good talk from Nicholas Katsanis https://www.rescindotherapeutics.com/about and panel discussion.
Personal
- Website CSS building.
- Implementing Rake for webdev.
- Tech4Growth workshop.
Reading
-
The Honourable Schoolboy, John le Carré.
-
Zhang et al., 2021 AJHG. A computational approach for detecting physiological homogeneity in the midst of genetic heterogeneity.
- Accelerating Genomic Data Generation and Facilitating Genomic Data Access Using Decentralization, Privacy-Preserving Technologies and Equitable Compensation. Nublua, George Church et al. (See podcast below for related talk on smart contracts).
- Sergei Loznitsa’s monumental State Funeral.
- Yazz Ahmed - Polyhymnia
- Floating Points, Pharoah Sanders & The London Symphony Orchestra - Promises.
- Ana Vidović - in concert.
- Podcast - Lex Fridman Podcast, #181 – Sergey Nazarov: Chainlink, Smart Contracts, and Oracle Networks


| deleteAllVisibleCookies |
|
|
| setTimeout |
100000 |
|
| open |
/vivo/ |
|
| assertTitle |
VIVO |
|
| clickAndWait |
link=Log in |
|
| assertTitle |
Log in to VIVO |
|
| type |
loginName |
<EMAIL_ADDRESS>|
| type |
loginPassword |
Password |
| clickAndWait |
loginForm |
|
| clickAndWait |
link=Index |
|
| clickAndWait |
link=Faculty Member |
|
| assertTitle |
Faculty Member |
|
| clickAndWait |
link=Furter, Frank |
|
| assertTitle |
Furter, Frank |
|
| clickAndWait |
link=Index |
|
| clickAndWait |
link=Faculty Member |
|
| assertTitle |
Faculty Member |
|
| clickAndWait |
link=Furter, Frank |
|
| assertTitle |
Furter, Frank |
|
| clickAndWait |
css=#relatedBy-Authorship > a.add-relatedBy > img.add-individual |
|
| assertTitle |
Edit |
|
| verifyTextPresent |
Create publication entry for Furter, Frank |
|
| verifyTextPresent |
Publication Type |
|
| select |
id=typeSelector |
label=Academic Article |
| type |
id=title |
One For the Road |
| clickAndWait |
id=submit |
|
| assertTitle |
Furter, Frank |
|
| clickAndWait |
link=One For the Road |
|
| assertTitle |
One For the Road |
|
| clickAndWait |
css=a.add-pageStart > img.add-individual |
|
| assertTitle |
Edit |
|
| waitForElementPresent |
tinymce |
|
| runScript |
tinyMCE.activeEditor.setContent('456') |
|
| clickAndWait |
id=submit |
|
| assertTitle |
One For the Road |
|
| clickAndWait |
css=a.add-pageEnd > img.add-individual |
|
| assertTitle |
Edit |
|
| waitForElementPresent |
tinymce |
|
| runScript |
tinyMCE.activeEditor.setContent('468') |
|
| clickAndWait |
id=submit |
|
| assertTitle |
One For the Road |
|
| clickAndWait |
css=a.add-dateTimeValue > img.add-individual |
|
| assertTitle |
Edit |
|
| type |
id=dateTimeField-year |
2008 |
| clickAndWait |
id=submit |
|
| assertTitle |
One For the Road |
|
| clickAndWait |
css=a.add-volume > img.add-individual |
|
| assertTitle |
Edit |
|
| waitForElementPresent |
tinymce |
|
| runScript |
tinyMCE.activeEditor.setContent('15') |
|
| clickAndWait |
id=submit |
|
| assertTitle |
One For the Road |
|
| clickAndWait |
css=a.add-issue > img.add-individual |
|
| assertTitle |
Edit |
|
| waitForElementPresent |
tinymce |
|
| runScript |
tinyMCE.activeEditor.setContent('8') |
|
| clickAndWait |
id=submit |
|
| assertTitle |
One For the Road |
|
| clickAndWait |
css=a.add-hasPublicationVenue > img.add-individual |
|
| assertTitle |
Edit |
|
| select |
id=typeOfNew |
label=Journal (bibo) |
| clickAndWait |
id=offerCreate |
|
| assertTitle |
Edit |
|
| type |
id=label |
DRINKY POOS |
| clickAndWait |
id=submit |
|
| assertTitle |
One For the Road |
|
| clickAndWait |
link=Index |
|
| clickAndWait |
link=Faculty Member |
|
| assertTitle |
Faculty Member |
|
| clickAndWait |
link=Furter, Frank |
|
| assertTitle |
Furter, Frank |
|
| verifyTextPresent |
Latest Alcohol Research. ALCOHOL RESEARCH & HEALTH. 23:990-994. 2009 |
|
| verifyElementPresent |
link=Latest Alcohol Research |
|
| verifyTextPresent |
One For the Road. DRINKY POOS. 15:456-468. 2008 |
|
| verifyElementPresent |
link=One For the Road |
|
| verifyTextPresent |
What should I drink?. Alcohol And Alcoholism. 55:345-367. 2007 |
|
| verifyElementPresent |
link=exact:What should I drink? |
|
| verifyTextPresent |
Alcohol Poisoning Treatment. Alcohol. 12:222-229. 2005 |
|
| verifyElementPresent |
link=Alcohol Poisoning Treatment |
|
| verifyTextPresent |
Dying for a Drink. Alcohol. 9:111-119. 2005 |
|
| verifyElementPresent |
link=Dying for a Drink |
|
| clickAndWait |
link=Map of Science |
|
| assertTitle |
Furter, Frank - Map of Science Visualization |
|
| click |
name=view-type |
|
| pause |
5000 |
|
| click |
id=first-filter |
|
| pause |
5000 |
|
| waitForTextPresent |
Explore activity |
|
| assertTitle |
Furter, Frank - Map of Science Visualization |
|
| pause |
10000 |
|
| verifyTextPresent |
Furter, Frank |
|
| verifyTextPresent |
Explore activity (4 publications) across 554 scientific subdisciplines |
|
| verifyTextPresent |
554 Subdisciplines |
|
| verifyTextPresent |
13 Disciplines |
|
| verifyTextPresent |
Neurotoxicology |
|
| verifyTextPresent |
4.0 |
|
| verifyTextPresent |
100.0 |
|
| verifyTextPresent |
mapped 100.00% of 4 publications |
|
| click |
id=second-filter |
|
| pause |
5000 |
|
| verifyTextPresent |
Brain Research |
|
| verifyTextPresent |
4.0 |
|
| click |
//tr[@id='DISCIPLINE-5']/td[3] |
|
| pause |
5000 |
|
| verifyTextPresent |
100.0 |
|
| click |
id=first-filter |
|
| pause |
5000 |
|
| click |
css=td..sorting_2 |
|
| pause |
5000 |
|
| verifyTextPresent |
Neurotoxicology |
|
| verifyTextPresent |
4.0 |
|
| verifyTextPresent |
100.0 |
|
| clickAndWait |
link=Home |
|
| clickAndWait |
link=Log out |
|
| assertTitle |
VIVO |
|


ms
Use this package to easily convert various time formats to milliseconds.
Examples
ms('2 days') // 172800000
ms('1d') // 86400000
ms('10h') // 36000000
ms('2.5 hrs') // 9000000
ms('2h') // 7200000
ms('1m') // 60000
ms('5s') // 5000
ms('1y') //<PHONE_NUMBER>0
ms('100') // 100
Convert from milliseconds
ms(60000) // "1m"
ms(2 * 60000) // "2m"
ms(ms('10 hours')) // "10h"
Time format written-out
ms(60000, { long: true }) // "1 minute"
ms(2 * 60000, { long: true }) // "2 minutes"
ms(ms('10 hours'), { long: true }) // "10 hours"
Features
- Works both in node and in the browser.
- If a number is supplied to
ms
, a string with a unit is returned. - If a string that contains the number is supplied, it returns it as a number (e.g.: it returns
100
for'100'
). - If you pass a string with a number and a valid unit, the number of equivalent ms is returned.
Caught a bug?
- Fork this repository to your own GitHub account and then clone it to your local device
- Link the package to the global module directory:
npm link
- Within the module you want to test your local development instance of ms, just link it to the dependencies:
npm link ms
. Instead of the default one from npm, node will now use your clone of ms!
As always, you can run the tests using: npm test


Survey Questionnaire
About You
Name
Photo Link
Question 1
Your mind is always buzzing with unexplored ideas and plans.
1
2
3
4
5
Question 2
Generally speaking, you rely more on your experience than your imagination.
1
2
3
4
5
Question 3
You find it easy to stay relaxed and focused even when there is some pressure.
1
2
3
4
5
Question 4
You rarely do something just out of sheer curiosity.
1
2
3
4
5
Question 5
People can rarely upset you.
1
2
3
4
5
Question 6
It is often difficult for you to relate to other people's feelings.
1
2
3
4
5
Question 7
In a discussion, truth should be more important than people's sensitivities.
1
2
3
4
5
Question 8
You rarely get carried away by fantasies and ideas.
1
2
3
4
5
Question 9
You think that everyone's views should be respected regardless of whether they are supported by facts or not.
1
2
3
4
5
Question 10
You feel more energetic after spending time with a group of people.
1
2
3
4
5
Submit
Closest Friend Match
Your Compatible Friend!
×


These select one of five synchronization modes for the {_sweep} generators:
| poly | Each voice has its own sweep generator. The initial phase when a voice is allocated is random, and it runs continuously even if the voice is retriggered. | |
| poly synced | Each voice has its own sweep generator. The phase starts at 0\d at the start of each note. | |
| mono | All voices share the same sweep phase computed by the virtual instrument, but each has its own amplitude control. This phase runs continuously, independent of the playing of notes. | |
| mono multiple | Like the mono mode, except that the phase is reset to 0\d whenever a key is pressed. | |
| mono single | Like the mono mode, except that the phase is reset to 0\d whenever the number of keys held goes from zero to one. |
These are contained in the {Sweep_rate_cluster Sweep rate clusters} within the {Sweep_section}.
These are contained in the SWEEP section of the right panel, under the following parameter number:
| {sw-8.png height=48} |
These appear in the display as Sweep Mode.
These are accessed via the following {_NRPN NRPNs}:
| A | 1,4 | |
| B | 2,4 |
| MIDI | display | ||
| 0 | poly | (default) | |
| 1 | poly synced | ||
| 2 | mono | ||
| 3 | mono multiple | ||
| 4 | mono single |


|
BitShares-Core
6.1.0
BitShares blockchain implementation and command-line interface software
|
A type describing the result of a restriction predicate. More...
#include <restriction_predicate.hpp>
Public Types | |
| enum | rejection_reason { predicate_was_false, null_optional, incorrect_variant_type } |
| Enumeration of the general reasons a predicate may reject. More... | |
| using | rejection_indicator = static_variant< size_t, vector< predicate_result >, rejection_reason > |
Public Member Functions | |
| operator bool () const | |
| predicate_result & | reverse_path () |
| Reverse the order of the rejection path. Returns a reference to this object. More... | |
Static Public Member Functions | |
| static predicate_result | Rejection (rejection_reason reason) |
| static predicate_result | Rejection (vector< predicate_result > branches) |
| static predicate_result | Success () |
Public Attributes | |
| bool | success = false |
| Whether or not the operation complied with the restrictions or not. More... | |
| vector< rejection_indicator > | rejection_path |
| Failure indicators, ordered from the outermost restriction to the innermost (the location of the rejection) More... | |
A type describing the result of a restriction predicate.
Definition at line 34 of file restriction_predicate.hpp.
| using graphene::protocol::predicate_result::rejection_indicator = static_variant<size_t, vector<predicate_result>, rejection_reason> |
An indicator of what rejection occurred at a particular restriction – either an index to a sub-restriction, a list of rejection results from the branches of a logical OR, or the immediate reason for rejection
Definition at line 47 of file restriction_predicate.hpp.
Enumeration of the general reasons a predicate may reject.
| Enumerator | |
|---|---|
| predicate_was_false | |
| null_optional | |
| incorrect_variant_type |
Definition at line 39 of file restriction_predicate.hpp.
|
inline |
Definition at line 55 of file restriction_predicate.hpp.
|
inlinestatic |
Definition at line 51 of file restriction_predicate.hpp.
|
inlinestatic |
Definition at line 52 of file restriction_predicate.hpp.
| predicate_result & graphene::protocol::predicate_result::reverse_path | ( | ) |
Reverse the order of the rejection path. Returns a reference to this object.
Definition at line 72 of file restriction_predicate.cpp.
|
inlinestatic |
Definition at line 53 of file restriction_predicate.hpp.
| vector<rejection_indicator> graphene::protocol::predicate_result::rejection_path |
Failure indicators, ordered from the outermost restriction to the innermost (the location of the rejection)
Definition at line 49 of file restriction_predicate.hpp.
| bool graphene::protocol::predicate_result::success = false |
Whether or not the operation complied with the restrictions or not.
Definition at line 36 of file restriction_predicate.hpp.