[JBoss Tools] - enhance IntelliSense of hql-editor
by nimo stephan
nimo stephan [http://community.jboss.org/people/nimo22] created the discussion
"enhance IntelliSense of hql-editor"
To view the discussion, visit: http://community.jboss.org/message/560161#560161
--------------------------------------------------------------
I have found out that the intellisense of hql-editor does not contain all sql-statements.
For example: SQL Date and Time Functions (adapted from http://www.ibm.com/developerworks/data/library/techarticle/0211yip/0211yi... http://www.ibm.com/developerworks/data/library/techarticle/0211yip/0211yi...)
| DAYNAME | Returns a mixed case character string containing the name of the day (e.g., Friday) for the day portion of the argument. |
| DAYOFWEEK | Returns the day of the week in the argument as an integer value in the range 1-7, where 1 represents Sunday. |
| DAYOFWEEK_ISO | Returns the day of the week in the argument as an integer value in the range 1-7, where 1 represents Monday. |
| DAYOFYEAR | Returns the day of the year in the argument as an integer value in the range 1-366. |
| DAYS | Returns an integer representation of a date. |
| JULIAN_DAY | Returns an integer value representing the number of days from January 1, 4712 B.C. (the start of Julian date calendar) to the date value specified in the argument. |
| MIDNIGHT_SECONDS | Returns an integer value in the range 0 to 86 400 representing the number of seconds between midnight and the time value specified in the argument. |
| MONTHNAME | Returns a mixed case character string containing the name of month (e.g., January) for the month portion of the argument. |
| TIMESTAMP_ISO | Returns a timestamp value based on date, time or timestamp argument. |
| TIMESTAMP_FORMAT | Returns a timestamp from a character string that has been interpreted using a character template. |
| TIMESTAMPDIFF | Returns an estimated number of intervals of the type defined by the first argument, based on the difference between two timestamps. |
| TO_CHAR | Returns a character representation of a timestamp that has been formatted using a character template. TO_CHAR is a synonym for VARCHAR_FORMAT. |
| TO_DATE | Returns a timestamp from a character string that has been inter-preted using a character template. TO_DATE is a synonym for TIMESTAMP_FORMAT. |
| WEEK | Returns the week of the year of the argument as an integer value in range 1-54. The week starts with Sunday. |
| WEEK_ISO |
I guess, these are sql-functions independent from the database-provider. So would be nice to adapt these into the intellisense from hql-editor.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/560161#560161]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
[JBoss Remoting] - Re: Dynamic classloading issue
by v a
v a [http://community.jboss.org/people/hipa] created the discussion
"Re: Dynamic classloading issue"
To view the discussion, visit: http://community.jboss.org/message/560138#560138
--------------------------------------------------------------
Yes, I have read it. I have this line in jboss-app.xml:
> <loader-repository>org.test:loader=jboss-test.ear</loader-repository>
When I added just this part from the documentation to my deploy/ejb3-connectors-jboss-beans.xml:
> <bean name="remoting:serverConfiguration"
> class="org.jboss.remoting.ServerConfiguration">
> <property name="invokerLocatorParameters">
> <map keyClass="java.lang.String" valueClass="java.lang.String">
> <entry>
> <key>loaderport</key>
> <value>5544</value>
> </entry>
> </map>
> </property>
> <property name="serverParameters">
> <map keyClass="java.lang.String" valueClass="java.lang.Object">
> <entry>
> <key>remoteClassLoaders</key>
> <value>
> <list elementClass="java.lang.ClassLoader">
> <value>jboss-test.ear:classloader</value>
> </list>
> </value>
> </entry>
> </map>
> </property>
> ...
> </bean>
>
nothing happened. The only lines in log were:
> 13:28:59,808 TRACE [org.jboss.remoting.serialization.impl.java.JavaSerializationManager] Creating ObjectOutputStream
> 13:28:59,809 TRACE [org.jboss.remoting.serialization.impl.java.JavaSerializationManager] Creating ObjectInputStreamWithClassLoader
> 13:28:59,809 TRACE [org.jboss.remoting.transport.socket.SocketServerInvoker] passed through ServerSocketRefresh.release()
> 13:28:59,825 TRACE [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 60000
> 13:28:59,884 TRACE [org.jboss.remoting.transport.socket.ServerSocketWrapper] ServerSocketWrapper[Socket[addr=/ip,port=40042,localport=3873].bc9678] wrote CLOSING
> 13:28:59,885 TRACE [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/ip,port=40042,localport=3873].bc9678] closing socket
> 13:28:59,885 TRACE [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/ip,port=40042,localport=3873].bc9678] closed socket
> 13:28:59,885 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#20[10.0.4.75:40042] closed socketWrapper: ServerSocketWrapper[Socket[addr=/ip,port=40042,localport=3873].bc9678]
I also needed to add this (documentation has nothing about it):
> <bean name="org.jboss.ejb3.RemotingConnector"
> class="org.jboss.remoting.transport.Connector">
>
> <property name="invokerLocator">
>
> <value-factory bean="ServiceBindingManager"
> method="getStringBinding">
> ...
> <parameter>socket://${jboss.bind.address}:${port}?*loaderport=4873*</parameter>
> ...
> </value-factory>
>
> </property>
> <property name="serverConfiguration">
> <inject bean="ServerConfiguration" />
> </property>
> </bean>
Then log becames:
> 13:37:22,331 DEBUG [org.jboss.remoting.marshal.MarshallerLoaderHandler] MarshallerLoaderHandler received invocation with param of load_class and data type of null
> 13:37:22,331 DEBUG [org.jboss.remoting.marshal.MarshallerLoaderHandler] MarshallerLoaderHandler: loading class: *my interface*
> 13:37:22,331 TRACE [org.jboss.remoting.loading.ClassUtil] trying to load class: *my interface* from path: *my interface class file*
> 13:37:22,332 TRACE [org.jboss.remoting.loading.ClassByteClassLoader] getResourceAsStream =>*my interface* = null
> 13:37:22,332 DEBUG [org.jboss.remoting.marshal.MarshallerLoaderHandler] unable to load class *my interface*
> 13:37:22,332 DEBUG [org.jboss.remoting.marshal.MarshallerLoaderHandler] MarshallerLoaderHandler: returning class: *my interface*: ClassBytes [class=*my interface*,value=null]
Still confused why there is no any example of remote class loading in the documentation.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/560138#560138]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
[JBoss Messaging] - Using MDB running on Jboss 5.1.0 listening to remote destination located on Jboss 4.2.3
by Evgeny Tilman
Evgeny Tilman [http://community.jboss.org/people/EugenyT] created the discussion
"Using MDB running on Jboss 5.1.0 listening to remote destination located on Jboss 4.2.3"
To view the discussion, visit: http://community.jboss.org/message/560133#560133
--------------------------------------------------------------
Hello,
I'm trying to use MDB running on Jboss 5.1.0 GA, listening to remote destination deployed on Jboss 4.2.3 GA
and expiriencing the following error (MDB can not connect to destination):
,521 ERROR [org.jboss.messaging.util.ExceptionUtil] SessionEndpoint[1u-pc5bykdg-1-e9u4ykdg-e0hw43-f4y1k3] createQueue [2u-pc5bykdg-1-e9u4ykdg-e0hw43-f4y1k3]
javax.jms.JMSException: There is no administratively defined queue with name:MY_REMOTE_QUEUE
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createQueue(ServerSessionEndpoint.java:299)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createQueue$aop(SessionAdvised.java:105)
at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeTarget(SessionAdvised$createQueue_6431069199924553036.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.createQueue(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionCreateQueueRequest.serverInvoke(SessionCreateQueueRequest.java:74)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.remoting.Client.invoke(Client.java:617)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createQueue$aop(ClientSessionDelegate.java:319)
at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeTarget(ClientSessionDelegate$createQueue_6431069199924553036.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientSessionDelegate.createQueue(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossSession.createQueue(JBossSession.java:250)
at org.springframework.jms.support.destination.DynamicDestinationResolver.resolveQueue(DynamicDestinationResolver.java:101)
at org.springframework.jms.support.destination.DynamicDestinationResolver.resolveDestinationName(DynamicDestinationResolver.java:66)
at org.springframework.jms.support.destination.JmsDestinationAccessor.resolveDestinationName(JmsDestinationAccessor.java:100)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.createListenerConsumer(AbstractPollingMessageListenerContainer.java:219)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.initResourcesIfNecessary(DefaultMessageListenerContainer.java:1079)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1055)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1048)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)
at java.lang.Thread.run(Thread.java:619)
(*Same configuration , but MBD running on 4.2.3 GA works fine)
I'm using default jms ConnectionFactory.
- Can I use the combination of MDB running on 5.1,0 GA and destination on 4.2.3 GA at all?
- If yes , how I should configure jms ConnectionFactory to allow that , (or I'm missing some additional artifacts) ?
- Other thoughts?
Thanks a lot
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/560133#560133]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months
[jBPM] - Understanding Deployments & Executions
by Karoy Labs
Karoy Labs [http://community.jboss.org/people/obolabs] created the discussion
"Understanding Deployments & Executions"
To view the discussion, visit: http://community.jboss.org/message/560102#560102
--------------------------------------------------------------
Please read the following knowing that I am still only finding my way around JBPM as well as JBoss, although I've got some experience with weblogic and JEE in general.
Here I'm trying to wrap my mind around how the deploy and execution scenarios work together.
Consider this Ant-based deploy process:
<taskdef
name="jbpm-deploy"
classname="org.jbpm.pvm.internal.ant.*JbpmDeployTask*"
classpathref="jbpm.dependencies" />
<jbpm-deploy file="ProcessTester.bar" />
As far as I can tell, it parses the jbpm xml {for validation?} and writes the .bar file contents into the JBPM4_LOB table, as well as creating entries for the process in other deployment related tables.
This is done without needing anything from the JBoss+JBPM runtime, other than the support libraries.
Once running, BPM Console checks the DB for available deployments.
When a process is 'Start'-ed in the Console's Process Overview, its *.bar* is read from DB, reassembled and executed in place. In other words, the business archive does not have to be explicitly in the JBoss classpath.
Is that more or less it or are there missing bits in this description?
Also, I am fairly certain that you can also deploy processes from .bar files included in the classpath by simply putting the file into the deploy folder of the JBoss instance. However, I remember reading in another thread that JBPM 4.4 doesn't yet have a deployer, but one can use 4.1,2,3 deployers?
This method of deployment would result in the same DB artifacts being generated and the execution would be same.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/560102#560102]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 4 months