Regular expression for key value pairs
by Vladimir Blagojevic
Hi,
What would be a regular expression for Java annotation key value pairs?
I want to compile this regex in Pattern class and then call method split
to get the the key value pairs. For example,
@RequestForEnhancement(
id = 2868724,
synopsis = "Enable time-travel",
engineer = "Mr. Peabody",
date = "4/1/3007"
)
Much appreciated,
Vladimir
14 years, 7 months
- 2
- 1
Migrating to JBoss Web 3
by Rémy Maucherat
Hi,
As part of the Servlet 3.0 development, AS trunk will have to be
switched to JBoss Web 3. Most is just a one time API change that is
not very difficult, and it should provide the same level of
functionality than JBW 2.1 (the new features need many deployer
updates), but the JSP changes are more intrusive.
Of particular interest is the new handling for tag library
descriptors, where instead of having Japser parse them "magically"
(and in a very hackish way ;) ) parse them, metadata will have to be
created in the container (Stan in particular asked for that ;) ). For
example, for JSTL and JSF, some deployer or listener could be
processing their taglibs using the new metadata classes and add them
to the Tomcat deployer as "shared" taglib metadata, which would then
be added to every webapps. This could be done by with the service that
would be looking for ServletConteainerInitializers in shared
libraries.
Given the amount of stuff that is involved, I don't see how to do the
thing in one pass, so I was posting to inquire about the development
strategy. Should this be done in trunk, accepting that JSP taglib
support is not going to be functional for a little while ? [note: it
might be possible to hack in a temporary solution by using Catalina's
taglib processing for now] In a separate branch of AS ? (but given the
rate of change, merging could be very difficult)
Comments ?
Rémy
14 years, 8 months
- 3
- 4
Problem running jboss-5.0.0.CR2
by Mamta Lohani
Hi,
Recently i have installed jboss-5.0.0.CR2 on fedora linux. I want to use
MySQL database for JBM Queue. Default JBM which is 1.4.1 runs fine with
MySQL, but I want to use messaging 2.0 with Jboss 5.0.0.CR2. I have
installed messaging 2.0 with JBoss, but when i run it as run.sh -c
all-with-jbm2 , it runs fine. It creates all JBM related tables in the
database, but when i try to send messages using our application it is
not inserting into those table, however my application pics up the data
from somewhere and operate on that accordingly.
Can any one tell me wjy is it so. Also when i run jboss it starts both
the messaging server i.e. JBoss Messaging Server version 2.0.0.BETA4
(maggot, 104) started
and [ServerPeer] JBoss Messaging 1.4.1.CR1 server [0] started.
Please help me out. Jboss log is as follows
=========================================================================
/opt/jboss-5.0.0.CR2/bin/run.sh -c all-with-jbm2
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss-5.0.0.CR2
JAVA: /usr/java/java-1.6.0-openjdk-1.6.0.0/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -Xms256m -Xmx1024m
-XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
-Djava.library.path=/opt/jboss-5.0.0.CR2/bin/META-INF/lib/linux2/x86
CLASSPATH: /opt/jboss-5.0.0.CR2/bin/run.jar:/usr/java/java-1.6.0-openjdk-1.6.0.0/lib/tools.jar
=========================================================================
09:18:41,762 INFO [ServerImpl] Starting JBoss (Microcontainer)...
09:18:41,763 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2
(build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)
09:18:41,765 INFO [ServerImpl] Home Dir: /opt/jboss-5.0.0.CR2
09:18:41,765 INFO [ServerImpl] Home URL: file:/opt/jboss-5.0.0.CR2/
09:18:41,765 INFO [ServerImpl] Library URL:
file:/opt/jboss-5.0.0.CR2/lib/
09:18:41,766 INFO [ServerImpl] Patch URL: null
09:18:41,766 INFO [ServerImpl] Server Name: all-with-jbm2
09:18:41,766 INFO [ServerImpl] Server Home
Dir: /opt/jboss-5.0.0.CR2/server/all-with-jbm2
09:18:41,766 INFO [ServerImpl] Server Home URL:
file:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/
09:18:41,766 INFO [ServerImpl] Server Data
Dir: /opt/jboss-5.0.0.CR2/server/all-with-jbm2/data
09:18:41,766 INFO [ServerImpl] Server Temp
Dir: /opt/jboss-5.0.0.CR2/server/all-with-jbm2/tmp
09:18:41,766 INFO [ServerImpl] Server Config URL:
file:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/conf/
09:18:41,766 INFO [ServerImpl] Server Library URL:
file:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/lib/
09:18:41,766 INFO [ServerImpl] Root Deployment Filename:
jboss-service.xml
09:18:42,703 INFO [ServerImpl] Starting Microcontainer,
bootstrapURL=file:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/conf/bootstrap.xml
09:18:43,801 INFO [CopyMechanism] VFS temp
dir: /opt/jboss-5.0.0.CR2/server/all-with-jbm2/tmp
09:18:43,858 INFO [ZipEntryContext] VFS force nested jars copy-mode is
enabled.
09:18:45,941 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems
Inc.
09:18:45,941 INFO [ServerInfo] Java VM: OpenJDK Server VM 1.6.0-b09,Sun
Microsystems Inc.
09:18:45,941 INFO [ServerInfo] OS-System: Linux 2.6.25-14.fc9.i686,i386
09:18:47,879 INFO [MetaDataAwareProfile] Using profile
root:/opt/jboss-5.0.0.CR2/server/all-with-jbm2
09:18:51,567 INFO [WebService] Using RMI server codebase:
http://127.0.0.1:8083/
09:19:02,308 WARN [HackClassloaderMetaDataDeployer] FIXME Using loader
repository config: jboss.console:sar=console-mgr.sar for
vfsfile:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/management/console-mgr.sar/ use classloading metadata not loader repository config
09:19:02,991 INFO [AspectDeployer] Deploying xml into
org.jboss.aop.AspectManager@1ddff76 for
BaseClassLoader@1b181f1{vfsfile:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/ejb3-interceptors-aop.xml}
09:19:03,096 INFO [AspectDeployer] Deploying AOP annotations into
org.jboss.aop.AspectManager@1ddff76 for
BaseClassLoader@d67f82{vfszip:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/cluster/jbossweb-cluster.aop}
09:19:03,101 INFO [AspectDeployer] Deploying xml into
org.jboss.aop.AspectManager@1ddff76 for
BaseClassLoader@d67f82{vfszip:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/cluster/jbossweb-cluster.aop}
09:19:10,527 INFO [UnifiedInvokerHA] Service name is
jboss:service=invoker,type=unifiedha
09:19:11,377 INFO [CorbaNamingService] CORBA Naming Started
09:19:13,555 INFO [JMXConnectorServerService] JMX Connector server:
service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
09:19:13,699 INFO [MailService] Mail Service bound to java:/Mail
09:19:15,195 INFO [SnmpAgentService] SNMP agent going active
09:19:16,197 INFO [DefaultPartition] Initializing partition
DefaultPartition
09:19:16,249 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:36385
-------------------------------------------------------
09:19:16,337 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:36385
-------------------------------------------------------
09:19:18,353 INFO [DefaultPartition] Number of cluster members: 1
09:19:18,353 INFO [DefaultPartition] Other members: 0
09:19:18,355 INFO [RPCManagerImpl] Received new cluster view:
[127.0.0.1:36385|0] [127.0.0.1:36385]
09:19:18,359 INFO [RPCManagerImpl] Cache local address is
127.0.0.1:36385
09:19:18,373 INFO [ComponentRegistry] JBoss Cache version: JBossCache
'Poblano' 2.2.0.GA
09:19:18,373 INFO [DefaultPartition] Fetching serviceState (will wait
for 30000 milliseconds):
09:19:18,373 INFO [DefaultPartition] State could not be retrieved (we
are the first member in group)
09:19:18,926 INFO [HANamingService] Started HAJNDI bootstrap;
jnpPort=1100, backlog=50, bindAddress=/127.0.0.1
09:19:18,931 INFO [DetachedHANamingService$AutomaticDiscovery]
Listening on /127.0.0.1:1102, group=230.0.0.4, HA-JNDI
address=127.0.0.1:1100
09:19:18,966 INFO [NativeServerConfig] JBoss Web Services - Stack
Native Core
09:19:18,966 INFO [NativeServerConfig] 3.0.3.GA
09:19:19,668 ERROR [STDERR] Sep 1, 2009 9:19:19 AM
org.jboss.messaging.core.logging.Logger info
INFO: live server is starting..
09:19:19,715 ERROR [STDERR] Sep 1, 2009 9:19:19 AM
org.jboss.messaging.core.logging.Logger warn
WARNING: It has been detected that the cluster admin user and password
which are used to replicate management operation from one node to the
other have not been changed from the installation default. Please see
the JBoss Messaging user guide for instructions on how to do this.
09:19:19,789 ERROR [STDERR] Sep 1, 2009 9:19:19 AM
org.jboss.messaging.core.logging.Logger info
INFO: AIO journal selected
09:19:19,958 ERROR [STDERR] Sep 1, 2009 9:19:19 AM
org.jboss.messaging.core.logging.Logger info
INFO: AIO loaded successfully
09:19:21,666 ERROR [STDERR] Sep 1, 2009 9:19:21 AM
org.jboss.messaging.core.logging.Logger warn
WARNING: There is no backup connector with name 'netty' deployed.
09:19:21,902 ERROR [STDERR] Sep 1, 2009 9:19:21 AM
org.jboss.messaging.core.logging.Logger info
INFO: JBoss Messaging Server version 2.0.0.BETA4 (maggot, 104) started
09:19:22,196 INFO [TransactionManagerService] JBossTS Transaction
Service (JTA version) - JBoss Inc.
09:19:22,197 INFO [TransactionManagerService] Setting up property
manager MBean and JMX layer
09:19:22,379 INFO [TransactionManagerService] Initializing recovery
manager
09:19:22,859 INFO [TransactionManagerService] Recovery manager
configured
09:19:22,859 INFO [TransactionManagerService] Binding
TransactionManager JNDI Reference
09:19:22,881 INFO [TransactionManagerService] Starting transaction
recovery manager
09:19:23,203 INFO [AprLifecycleListener] The Apache Tomcat Native
library which allows optimal performance in production environments was
not found on the
java.library.path: /opt/jboss-5.0.0.CR2/bin/META-INF/lib/linux2/x86
09:19:23,251 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on
http-127.0.0.1-8080
09:19:23,252 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on
ajp-127.0.0.1-8009
09:19:23,252 INFO [Catalina] Initialization processed in 168 ms
09:19:23,252 INFO [StandardService] Starting service jboss.web
09:19:23,254 INFO [StandardEngine] Starting Servlet Engine: JBoss
Web/2.1.1.CR7
09:19:23,300 INFO [Catalina] Server startup in 47 ms
09:19:23,355 INFO [TomcatDeployment] deploy, ctxPath=/invoker,
vfsUrl=httpha-invoker.sar/invoker.war
09:19:24,255 INFO [TomcatDeployment] deploy, ctxPath=/jbossws,
vfsUrl=jbossws.sar/jbossws-management.war
09:19:24,287 INFO [TomcatDeployment] deploy, ctxPath=/juddi,
vfsUrl=juddi-service.sar/juddi.war
09:19:24,322 INFO [RegistryServlet] Loading jUDDI configuration.
09:19:24,337 INFO [RegistryServlet] Resources loaded
from: /WEB-INF/juddi.properties
09:19:24,337 INFO [RegistryServlet] Initializing jUDDI components.
09:19:24,427 INFO [TomcatDeployment] deploy, ctxPath=/web-console,
vfsUrl=management/console-mgr.sar/web-console.war
09:19:24,706 INFO [RARDeployment] Required license terms exist, view
vfszip:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
09:19:24,719 INFO [RARDeployment] Required license terms exist, view
vfszip:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
09:19:24,820 INFO [RARDeployment] Required license terms exist, view
vfsfile:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/jms-ra.rar/META-INF/ra.xml
09:19:24,834 ERROR [STDERR] Sep 1, 2009 9:19:24 AM
org.jboss.messaging.core.logging.Logger info
INFO: JBoss Messaging resource adaptor started
09:19:24,876 INFO [ConnectionFactoryBindingService] Bound
ConnectionManager
'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name
'java:JmsXA'
09:19:24,883 INFO [RARDeployment] Required license terms exist, view
vfszip:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/mail-ra.rar/META-INF/ra.xml
09:19:24,905 INFO [RARDeployment] Required license terms exist, view
vfszip:/opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/quartz-ra.rar/META-INF/ra.xml
09:19:24,990 INFO [SimpleThreadPool] Job execution threads will use
class loader of thread: main
09:19:25,015 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
09:19:25,019 INFO [RAMJobStore] RAMJobStore initialized.
09:19:25,019 INFO [StdSchedulerFactory] Quartz scheduler
'DefaultQuartzScheduler' initialized from default resource file in
Quartz package: 'quartz.properties'
09:19:25,019 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
09:19:25,020 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_
$_NON_CLUSTERED started.
09:19:25,080 INFO [ConnectionFactoryBindingService] Bound
ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MysqlDS' to
JNDI name 'java:MysqlDS'
09:19:25,120 INFO [ConnectionFactoryBindingService] Bound
ConnectionManager 'jboss.jca:service=DataSourceBinding,name=SQLBOXDS' to
JNDI name 'java:SQLBOXDS'
09:19:25,143 INFO [ConnectionFactoryBindingService] Bound
ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS'
to JNDI name 'java:DefaultDS'
09:19:25,524 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE
QRTZ_JOB_DETAILS(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80)
NOT NULL, DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT
NULL, IS_DURABLE VARCHAR(1) NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL,
IS_STATEFUL VARCHAR(1) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL,
JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
09:19:25,572 INFO [SimpleThreadPool] Job execution threads will use
class loader of thread: main
09:19:25,573 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
09:19:25,574 INFO [JobStoreCMT] Using db table-based data access
locking (synchronization).
09:19:25,619 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
09:19:25,619 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
09:19:25,620 INFO [JobStoreCMT] JobStoreCMT initialized.
09:19:25,620 INFO [StdSchedulerFactory] Quartz scheduler
'JBossEJB3QuartzScheduler' initialized from an externally provided
properties instance.
09:19:25,620 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
09:19:25,638 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' /
'blocked' state.
09:19:25,640 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress
at the time of the last shut-down.
09:19:25,640 INFO [JobStoreCMT] Recovery complete.
09:19:25,640 INFO [JobStoreCMT] Removed 0 'complete' triggers.
09:19:25,640 INFO [JobStoreCMT] Removed 0 stale fired job entries.
09:19:25,643 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_
$_NON_CLUSTERED started.
09:19:25,731 WARN [JDBCPersistenceManager]
JBoss Messaging Warning: DataSource connection transaction isolation
should be READ_COMMITTED, but it is currently REPEATABLE_READ.
Using an isolation level less strict than
READ_COMMITTED may lead to data consistency problems.
Using an isolation level more strict than
READ_COMMITTED may lead to deadlock.
09:19:25,985 INFO [ServerPeer] JBoss Messaging 1.4.1.CR1 server [0]
started
09:19:26,054 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
09:19:26,084 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console,
vfsUrl=jmx-console.war
09:19:26,120 INFO [TomcatDeployment] deploy, ctxPath=/psms,
vfsUrl=psms.war
09:19:26,181 INFO [PsmsLogger] [log4j.properties
PATH] : /opt/jboss-5.0.0.CR2/server/all-with-jbm2/deploy/psms.war/WEB-INF/classes/log4j.properties
09:19:26,258 INFO [KannelRoute] INIT KANNELROUTE: 1
192.168.1.140:1223/cgi-bin/sendsms SMSC: fake
09:19:26,259 INFO [KannelRoute] INIT KANNELROUTE: 10
192.168.1.132:1223/cgi-bin/sendsms SMSC: fake1
09:19:26,282 INFO [CreditCache] SparseListMatrix Initialized.
09:19:26,287 INFO [JMSReceiver] Intializing JMS Receiver.
09:19:26,711 INFO [InitRoute] Queue initialized properly
09:19:26,746 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
http-127.0.0.1-8080
09:19:26,765 INFO [AjpProtocol] Starting Coyote AJP/1.3 on
ajp-127.0.0.1-8009
09:19:26,772 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR2
(build: SVNTag=JBoss_5_0_0_CR2 date=200809171139)] Started in 44s:998ms
Thanks!!
14 years, 8 months
- 2
- 1