Menu
▾
▴
jboss-dev-forums — The jboss development forum posts
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(157) |
May
(789) |
Jun
(608) |
Jul
(554) |
Aug
(868) |
Sep
(654) |
Oct
(994) |
Nov
(803) |
Dec
(982) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(1006) |
Feb
(1054) |
Mar
(1345) |
Apr
(1305) |
May
(1392) |
Jun
(1016) |
Jul
(265) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(8) |
Dec
(19) |
| 2007 |
Jan
(20) |
Feb
(10) |
Mar
(20) |
Apr
(8) |
May
(4) |
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
(6) |
Oct
(12) |
Nov
(7) |
Dec
(13) |
| 2008 |
Jan
(5) |
Feb
(4) |
Mar
(34) |
Apr
(32) |
May
(22) |
Jun
(21) |
Jul
(30) |
Aug
(18) |
Sep
(30) |
Oct
(23) |
Nov
(86) |
Dec
(51) |
| 2009 |
Jan
(25) |
Feb
(26) |
Mar
(34) |
Apr
(47) |
May
(38) |
Jun
(25) |
Jul
(36) |
Aug
(9) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(17) |
| 2010 |
Jan
(7) |
Feb
(9) |
Mar
(26) |
Apr
(49) |
May
(52) |
Jun
(48) |
Jul
(39) |
Aug
(27) |
Sep
(9) |
Oct
(14) |
Nov
(7) |
Dec
(10) |
| 2011 |
Jan
(12) |
Feb
(9) |
Mar
(17) |
Apr
(33) |
May
(39) |
Jun
(36) |
Jul
(29) |
Aug
(26) |
Sep
(29) |
Oct
(38) |
Nov
(35) |
Dec
(27) |
| 2012 |
Jan
(20) |
Feb
(34) |
Mar
(29) |
Apr
(33) |
May
(45) |
Jun
(46) |
Jul
(50) |
Aug
(35) |
Sep
(55) |
Oct
(68) |
Nov
(79) |
Dec
(45) |
| 2013 |
Jan
(67) |
Feb
(20) |
Mar
(55) |
Apr
(52) |
May
(25) |
Jun
(25) |
Jul
(34) |
Aug
(27) |
Sep
(21) |
Oct
(21) |
Nov
(19) |
Dec
(12) |
| 2014 |
Jan
(10) |
Feb
(8) |
Mar
(13) |
Apr
(18) |
May
(36) |
Jun
(26) |
Jul
(17) |
Aug
(19) |
Sep
(13) |
Oct
(8) |
Nov
(7) |
Dec
(5) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(13) |
Apr
(15) |
May
(7) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2016 |
Jan
(3) |
Feb
(5) |
Mar
(19) |
Apr
(34) |
May
(9) |
Jun
(10) |
Jul
(5) |
Aug
(10) |
Sep
(5) |
Oct
(11) |
Nov
(19) |
Dec
(7) |
| 2017 |
Jan
(4) |
Feb
(4) |
Mar
(8) |
Apr
(5) |
May
(12) |
Jun
(5) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <man...@jb...> - 2006-07-03 09:26:35
|
Hmm, that would involve rewriting the current set of cache loaders. I'm concerned about feasibility wrt. timescales here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954998#3954998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954998 |
|
From: apwalker <do-...@jb...> - 2006-07-03 08:46:18
|
This forum is for design and implementation discussions relating to the new JBoss messaging product. Please read this before posting to this forum. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=67598 I would suggest you take a look at the examples on the following wiki http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMQ. It should be as simple as reading/writing files to and from byte arrays and sending and receiving them as JMS byte messages (javax.jms.ByteMessage). If you need anymore details post a new message on the JBossMQ user forum and I'll address any specific questions you may have BUT look at the examples first. regards Aaron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954984#3954984 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954984 |
|
From: rish_pilgaon <do-...@jb...> - 2006-07-03 06:59:55
|
Warm Greetings!! My application needs to send and receive files using JBossMQ in P2P mode. Can any one help me out?? It would be great help if you could provide with som sample apps. Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954955#3954955 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954955 |
|
From: vickyk <do-...@jb...> - 2006-07-03 02:45:26
|
Yes, got it now!!!! I think my understanding about the usage of the MBeanProxyExt was wrong, I initilly though that this was used for optimization as I could see the invocation to getter/setter handled by simply invoking the corresponding attributes. Yes now I realize that this make code more readable/understandable than simply keeping the reflective calls in the code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954932#3954932 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954932 |
|
From: jplenhart <do-...@jb...> - 2006-07-02 23:57:24
|
Hi Mark,
Unfortunately - I tried that a bit earlier - and just tried now, the build is looking for the following directory:
Within the ESBCommon/build.xml - I guess I could put that directory and place those jars within that directory - unless there is something sooner on the way.
Thanks,
Jason
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954924#3954924
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954924
|
|
From: kukeltje <do-...@jb...> - 2006-07-02 22:22:19
|
point taken (with a lot of shame) btw, there should be an alternative association besides the fifa, one that dares to use cameras etc. Tennis, cycling, rugby etc use technology and what do they do in football? Give the refs a bionic ear which they in some cases do not even use... A frustrated sports fan. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954921#3954921 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954921 |
|
From: <mar...@jb...> - 2006-07-02 21:44:35
|
build.xml.root is not meant to be used (yet). Go into ESBCore and use the build.xml from there. We're refactoring the build system at the moment and build.xml.root will disappear soon. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954919#3954919 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954919 |
|
From: <mar...@jb...> - 2006-07-02 21:43:32
|
Jason, I'll create some JIRA issues for you tomorrow ;-) Thanks for the offer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954918#3954918 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954918 |
|
From: <mar...@jb...> - 2006-07-02 21:41:59
|
Being a member of both WS-R TC, I can say that OASIS WS-RM is pretty much dead. Despite having superior technology to WS-RX, the realities are that everyone (including Sun) is now looking to support WS-RX. JBossWS will eventually support WS-RX, though that's further down the roadmap. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954917#3954917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954917 |
|
From: <gal...@jb...> - 2006-07-02 17:55:55
|
Brian, you're right. Looking at the code in _setState, it seems like that: - The persistent state actually comes from calling CacheLoader.loadEntireState() or CacheLoader.loadState(). So the origing of the persistent state is the CacheLoader. - The transient(in-memory) state comes from marshalling the transient state (or marshall the associated state for PojoCache) generated inside the StateTransferGenerators. Therefore, we can control the in-memory state but we are can't really control the persistent state (with the current rules). In my opinion, rather than making both states consistent, the CacheLoader should be able to generate a persistent state given the in-memory state. However, in order for this to work, the structure of the in-memory state would need to be made public so that potential CacheLoader implementors could transform it into the persistent state that we're after. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954901#3954901 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954901 |
|
From: <koe...@jb...> - 2006-07-02 14:07:36
|
"kukeltje" wrote : ok, you asked for it..... | BELGIUM WASN'T EVEN AT THE WORLD CHAMPIONSHIP FOOTBALL | What is the point in getting qualified for the championship if you can't deliver a good game and are sent home with a sh**load of cards? :-PP At least we are able to concentrate on some good tennis and some great cyclists... Well at least one great cyclist that is ;-)) Cheers, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954886#3954886 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954886 |
|
From: jplenhart <do-...@jb...> - 2006-07-02 13:54:18
|
Hi, I tried to build the latest out of svn but am having some difficulty. Tried to build with the build.xml.root out of the 4_0_Alpha_1 directory - but it looks like this build file is not the correct version for building into a dist - there is no 'all' target. I have a post out regarding the database setup - but in the mean time - I would be happy to update the docs for building deploying jbossesb - however, I am not sure if my assumptions are correct in how I should be building the release. Thanks, Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954884#3954884 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954884 |
|
From: AlexFu.Novell <do-...@jb...> - 2006-07-02 01:38:48
|
No. It doesn't create a default HASingletonElectionPolicySimple. But it will use the old logic so the behavior should be equivalent to HASingletonElectionPolicySimple with position of 0. This situation is tested in the unit test. "bst...@jb..." wrote : If the user doesn't inject an HASingletonElectionPolicy, will HASingletonController default to creating an instance of HASingletonPolicySimple with a position of 0? | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954866#3954866 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954866 |
|
From: jplenhart <do-...@jb...> - 2006-07-02 00:39:00
|
Hi, Obviously I am new to this install - but I am a little confused. I created a database as the JBossESB-ds.xml would indicate: jdbc:postgresql://localhost:5432/JBossESB However when I run the script - it is creating a rosetta database. Should the url be something like: jdbc:postgresql://localhost:5432/rosetta Looks like the script is actually creating a database - not a dba by any stretch but a bit confused and will be happy to clear this up in a doc for future installers to read. Thanks, Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954864#3954864 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954864 |
|
From: <wes...@jb...> - 2006-07-01 21:44:10
|
I am moving what is currently in the connector project to the jboss-jca project. This is not in HEAD by default so you will have to cd src-dir cvs co jboss-jca Seems to be a better place for it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954857#3954857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954857 |
|
From: ddegroff <do-...@jb...> - 2006-07-01 20:59:33
|
anonymous wrote : I'm currently developing this 'off-line', so there is no website at all. Regarding the functionality, i'm focussing on the following items, ordered by priority | | 1: Full envelop compliancy (user messages and signal messages) | 2: Soap one-way MEP (one way push) | 3: Errorhandling | 4: Reliable messaging for this mep | 5: One way pull | 6: Reliable messaging for this mep | 7: Request response MEP | 8: Reliable messaging for this MEP | | After this basic functionality, I'll look into storing partner profiles, agreements etc. So on this part I am open to any requirements (I prefere to use LDAP though on the technical level) Only after this, I'll pay attention to persistent security aspects (signing etc) | | Reliability is the challenge, since there are two competing standards for it, both under OASIS (????? admired and hated by me cause of their flexibility. Speed ok, TWO protocols.... stupid) Maybe JBossWS will include one, I personally have a preference to use the SUN version, WS-Reliability) | Ah, this is what I was hoping for: More synergies than divergence. The basic functionality for the platform I envision has, at its root, a "hub and spoke" mentality. In my view, this can readily be adapted to a bus architecture, as I've come to understand ESB: 1. Trading Partner Management (maintenance of each endpoint's profile, including such things as formatting, security, transport). This could include entities as well as applications. 2. User Management (maintenance of each participant's profile, including security, level of access, etc.). 3. Routing (this capability can, especially as an ESB, involve routing intra-enterprise, as well as inter-enterprise). This would include application-specific adapters, enabling tight coupling with an entities' processing environment. 4. Transformation (each Trading Partner can have a "flavor" of "standard", according to their specific requirement). This portion of the functionality (as I see it today) must have the greatest level of flexibility to accommodate any-to-any, many-to-many endpoints. An "endpoint" might not necessarily be an "end", but an interim step. ESB design accommodates this nicely. 5. Tracking (each authorized user of the platform would have the ability of monitoring individual batch, message, transaction [pick your level of granularity] "in flight", that is, from point of delivery to the platform to point of delivery to desired recipient/application). 6. Security (I suspect JBoss AS/ESB provide most of what is required here, even to the message/transaction/batch level). This is what comes to mind, but makes a fair outline for a more fleshed-out functional spec. Dave View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954855#3954855 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954855 |
|
From: kukeltje <do-...@jb...> - 2006-07-01 19:41:15
|
David, (Since this is off-topic, which I as a jBPM forum moderator hate ;-), I'll for now respond one here. Maybe we should indeed start a new thread) I'm currently developing this 'off-line', so there is no website at all. Regarding the functionality, i'm focussing on the following items, ordered by priority 1: Full envelop compliancy (user messages and signal messages) 2: Soap one-way MEP (one way push) 3: Errorhandling 4: Reliable messaging for this mep 5: One way pull 6: Reliable messaging for this mep 7: Request response MEP 8: Reliable messaging for this MEP After this basic functionality, I'll look into storing partner profiles, agreements etc. So on this part I am open to any requirements (I prefere to use LDAP though on the technical level) Only after this, I'll pay attention to persistent security aspects (signing etc) Reliability is the challenge, since there are two competing standards for it, both under OASIS (????? admired and hated by me cause of their flexibility. Speed ok, TWO protocols.... stupid) Maybe JBossWS will include one, I personally have a preference to use the SUN version, WS-Reliability) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954852#3954852 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954852 |
|
From: ddegroff <do-...@jb...> - 2006-07-01 19:00:58
|
Ronald, I would be most interested. Having ebMS capability along with EDI would offer a pathway to the future of eCommerce. Your involvement in jBPM intrigues me, as well. I am of the opinion that BPM, along with data transformation, offers a powerful platform for extending a core capability to integrate an entity (public or private) within an ESB framework. Is there a website where I can learn more about your connector (from a functional description perspective)? I will be posting a functional description for the capability I've been describing. Most likely, I should create a new topic for this, so that those with similar interest/capabilities can merge their expertise. Agreed? ... and Thank You, Dave View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954850#3954850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954850 |
|
From: <ale...@jb...> - 2006-07-01 17:48:53
|
Here is the log that shows issue JBAS-993. Service controller complains about the EJB A while the EJB C is one that is guilty. 2006-07-01 19:41:43,091 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [5.0.0.Alpha (build: CVSTag=HEAD date=200606231301)] Started in 1m:13s:576ms | 2006-07-01 19:42:18,742 INFO [org.jboss.ejb.EjbModule] Deploying B | 2006-07-01 19:42:19,213 INFO [org.jboss.ejb.EjbModule] Deploying C | 2006-07-01 19:42:19,233 INFO [org.jboss.ejb.EjbModule] Deploying A | 2006-07-01 19:42:19,253 INFO [org.jboss.ejb.EjbModule] Deploying Facade | 2006-07-01 19:42:19,944 DEBUG [org.jboss.ejb.EntityContainer] Creating jboss.j2ee:jndiName=BLocal,service=EJB | 2006-07-01 19:42:20,044 DEBUG [org.jboss.ejb.EntityContainer] Created jboss.j2ee:jndiName=BLocal,service=EJB | 2006-07-01 19:42:20,064 DEBUG [org.jboss.ejb.EntityContainer] Creating jboss.j2ee:jndiName=CLocal,service=EJB | 2006-07-01 19:42:20,094 DEBUG [org.jboss.ejb.EntityContainer] Created jboss.j2ee:jndiName=CLocal,service=EJB | 2006-07-01 19:42:20,124 DEBUG [org.jboss.ejb.EntityContainer] Creating jboss.j2ee:jndiName=ALocal,service=EJB | 2006-07-01 19:42:20,164 DEBUG [org.jboss.ejb.EntityContainer] Created jboss.j2ee:jndiName=ALocal,service=EJB | 2006-07-01 19:42:20,265 DEBUG [org.jboss.ejb.EntityContainer] Starting jboss.j2ee:jndiName=BLocal,service=EJB | 2006-07-01 19:42:20,265 DEBUG [org.jboss.ejb.EntityContainer] Begin java:comp/env for EJB: B | 2006-07-01 19:42:20,275 DEBUG [org.jboss.ejb.EntityContainer] TCL: org.jboss.util.loading.DelegatingClassLoader@6972f1 | 2006-07-01 19:42:20,285 DEBUG [org.jboss.ejb.EntityContainer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered. | 2006-07-01 19:42:20,305 DEBUG [org.jboss.ejb.EntityContainer] End java:comp/env for EJB: B | 2006-07-01 19:42:20,325 INFO [org.jboss.ejb.plugins.local.BaseLocalProxyFactory] Bound EJB LocalHome 'B' to jndi 'BLocal' | 2006-07-01 19:42:21,086 DEBUG [org.jboss.ejb.EntityContainer] Started jboss.j2ee:jndiName=BLocal,service=EJB | 2006-07-01 19:42:21,096 DEBUG [org.jboss.ejb.EntityContainer] Starting jboss.j2ee:jndiName=CLocal,service=EJB | 2006-07-01 19:42:21,096 DEBUG [org.jboss.ejb.EntityContainer] Begin java:comp/env for EJB: C | 2006-07-01 19:42:21,106 DEBUG [org.jboss.ejb.EntityContainer] TCL: org.jboss.util.loading.DelegatingClassLoader@193b604 | 2006-07-01 19:42:21,116 DEBUG [org.jboss.ejb.EntityContainer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered. | 2006-07-01 19:42:21,146 DEBUG [org.jboss.ejb.EntityContainer] End java:comp/env for EJB: C | 2006-07-01 19:42:21,166 INFO [org.jboss.ejb.plugins.local.BaseLocalProxyFactory] Bound EJB LocalHome 'C' to jndi 'CLocal' | 2006-07-01 19:42:21,176 DEBUG [org.jboss.ejb.EntityContainer] Started jboss.j2ee:jndiName=CLocal,service=EJB | 2006-07-01 19:42:21,186 DEBUG [org.jboss.ejb.EntityContainer] Starting jboss.j2ee:jndiName=ALocal,service=EJB | 2006-07-01 19:42:21,196 DEBUG [org.jboss.ejb.EntityContainer] Begin java:comp/env for EJB: A | 2006-07-01 19:42:21,196 DEBUG [org.jboss.ejb.EntityContainer] TCL: org.jboss.util.loading.DelegatingClassLoader@12801c5 | 2006-07-01 19:42:21,206 DEBUG [org.jboss.ejb.EntityContainer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered. | 2006-07-01 19:42:21,236 DEBUG [org.jboss.ejb.EntityContainer] End java:comp/env for EJB: A | 2006-07-01 19:42:21,256 INFO [org.jboss.ejb.plugins.local.BaseLocalProxyFactory] Bound EJB LocalHome 'A' to jndi 'ALocal' | 2006-07-01 19:42:22,638 ERROR [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.C#findAll] Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | | org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.generateParseException(EJBQLParser.java:4360) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.jj_consume_token(EJBQLParser.java:4237) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.IdentificationVariable(EJBQLParser.java:2256) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.SelectClause(EJBQLParser.java:515) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.EJBQL(EJBQLParser.java:172) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.parse(EJBQLParser.java:65) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.compileEJBQL(JDBCEJBQLCompiler.java:167) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.<init>(JDBCEJBQLQuery.java:57) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:75) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:286) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:505) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:396) | at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172) | at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:355) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy56.start(Unknown Source) | at org.jboss.ejb.EjbModule.startService(EjbModule.java:409) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy27.start(Unknown Source) | at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:662) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) | at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124) | at org.jboss.security.auth.login.LoginConfigInterceptor.start(LoginConfigInterceptor.java:173) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) | at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy28.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | 2006-07-01 19:42:23,559 DEBUG [org.jboss.ejb.EntityContainer] Starting failed jboss.j2ee:jndiName=ALocal,service=EJB | org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement for EJB 'C': select object(o) from C oo; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | ) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.<init>(JDBCEJBQLQuery.java:66) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:75) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:286) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:505) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:396) | at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172) | at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:355) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy56.start(Unknown Source) | at org.jboss.ejb.EjbModule.startService(EjbModule.java:409) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy27.start(Unknown Source) | at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:662) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) | at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124) | at org.jboss.security.auth.login.LoginConfigInterceptor.start(LoginConfigInterceptor.java:173) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) | at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy28.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | Caused by: org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.generateParseException(EJBQLParser.java:4360) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.jj_consume_token(EJBQLParser.java:4237) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.IdentificationVariable(EJBQLParser.java:2256) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.SelectClause(EJBQLParser.java:515) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.EJBQL(EJBQLParser.java:172) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.parse(EJBQLParser.java:65) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.compileEJBQL(JDBCEJBQLCompiler.java:167) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.<init>(JDBCEJBQLQuery.java:57) | ... 97 more | 2006-07-01 19:42:24,511 WARN [org.jboss.system.ServiceController] Problem starting service jboss.j2ee:jndiName=ALocal,service=EJB | org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement for EJB 'C': select object(o) from C oo; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | ) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.<init>(JDBCEJBQLQuery.java:66) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:75) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:286) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:505) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:396) | at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172) | at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:355) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy56.start(Unknown Source) | at org.jboss.ejb.EjbModule.startService(EjbModule.java:409) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy27.start(Unknown Source) | at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:662) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) | at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124) | at org.jboss.security.auth.login.LoginConfigInterceptor.start(LoginConfigInterceptor.java:173) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) | at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy28.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | Caused by: org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.generateParseException(EJBQLParser.java:4360) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.jj_consume_token(EJBQLParser.java:4237) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.IdentificationVariable(EJBQLParser.java:2256) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.SelectClause(EJBQLParser.java:515) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.EJBQL(EJBQLParser.java:172) | at org.jboss.ejb.plugins.cmp.ejbql.EJBQLParser.parse(EJBQLParser.java:65) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.compileEJBQL(JDBCEJBQLCompiler.java:167) | at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.<init>(JDBCEJBQLQuery.java:57) | ... 97 more | 2006-07-01 19:42:25,532 INFO [org.jboss.proxy.ejb.ProxyFactory] Bound EJB Home 'Facade' to jndi 'Facade' | 2006-07-01 19:42:25,542 INFO [org.jboss.ejb.EJBDeployer] Deployed: file:/E:/cvsroot/jboss-head/build/output/jboss-5.0.0.Alpha/server/default/deploy/test-ejb.jar | 2006-07-01 19:42:25,652 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing: | | --- MBeans waiting for other MBeans --- | ObjectName: jboss.j2ee:jndiName=ALocal,service=EJB | State: FAILED | Reason: org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement for EJB 'C': select object(o) from C oo; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | ) | | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | ObjectName: jboss.j2ee:jndiName=ALocal,service=EJB | State: FAILED | Reason: org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement for EJB 'C': select object(o) from C oo; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o" at line 1, column 15. | Was expecting: | <IDENTIFICATION_VARIABLE> ... | ) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954847#3954847 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954847 |
|
From: kukeltje <do-...@jb...> - 2006-07-01 17:08:14
|
Dave, Would you be interested in a ebMS 3.0 B2B connector? I'm working on one that should be fairly easy to integrate with JBESB. I hope to have it ready by Q4 2006. To be as backwardscompatible as possible I hope to have a ebMS2.0 version available in Q1 2007. I see lots of opportunities for this in Europe as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954844#3954844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954844 |
|
From: jplenhart <do-...@jb...> - 2006-07-01 15:56:30
|
Hi, I have been going through and installing the 4.0 Alpha 1 release and thought I would create a simple doc for installing PostgreSQL on OS X. I know that this doc will probably get dated very quickly but thought I would document a set of steps that took me some time to arrive too. http://web.mac.com/jasonlenhart/iWeb/Site/OS_X_PostgresSQL_Install_JBossESB.pdf Feel free to assign me some documentation tasks in Jira (jplenhart) :-D Thanks, Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954839#3954839 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954839 |
|
From: ddegroff <do-...@jb...> - 2006-07-01 15:35:49
|
anonymous wrote : Dave, do you need this for something real?? Boy, Tom, the short answer is "yes". The long answer is a bit more involved. My objective is to deliver an eCommerce infrastructure based on JBESB. In truth, this concept is applicable cross-industry. My main focus/passion is US healthcare, certainly. My experience, in fact, has been in multiple industry environments, including international. The infrastructure of which I speak would apply for X12 (cross-industry, including healthcare, retail, manufacturing, logistics, etc.), EDIFACT, SWIFT, on and on. Now, I can get off my "soap box'. If your question relates to timescales/existing client, the short answer is: no existing client--yet; but I would like to see this "generic" infrastructure in place by Q1 2007. In the interim, I seek a client to partner for early adoption/alpha and beta testing, etc. Maybe my reach exceeds my grasp, but I see enormous potential for this. Dave View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954831#3954831 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954831 |
|
From: <sco...@jb...> - 2006-07-01 13:17:49
|
Ok. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954811#3954811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954811 |
|
From: <ale...@jb...> - 2006-07-01 12:14:50
|
The more I think about it the more I get convinced that to depend on a specific EJB is not a good idea. The right service to depend on would be the EjbModule. Suppose there is an EJB module that contains to EJBs A and B. The startService will be called on one of them first then on the other one. So, if A returns from its startService but the B's startService hasn't yet been called, can we assume that the A bean is usable? The may have CMR or call each other, etc So, I think, it's ok to assume that in EjbModule.startService we can use the DataSource. And so, we can complete the initialization of all the PMs before starting the EJB containers. What do you think about this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954804#3954804 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954804 |
|
From: <sco...@jb...> - 2006-07-01 11:31:06
|
I would have to see an example deployment that illustrates the 993 issue and why these exceptions cannot be collected in the EjbModule or elsewhere for latter reporting. The 993 issue could also be handle by logging and a summary see the log exception. Breaking the service lifecycle for this 993 issue is not worth it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954798#3954798 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954798 |
1965 messages has been excluded from this view by a project administrator.
