Curious about:
java.lang.NoClassDefFoundError: org/jboss/metadata/process/chain/ProcessorChain
..or why you'd have to define the dependency upon jboss-metadata:1.0.0.CR5
manually? I'm getting:
[INFO] [dependency:tree]
| [INFO] org.jboss.ejb3:jboss-ejb3-embedded:jar:1.0.0-SNAPSHOT
| [INFO]
"ALRubinger" wrote : Sisepago, can I get a Unit Test for this...attached to a
JIRA filed under "EJBTHREE" in the "proxy" component?
Nevermind, I see this stems from the JNDI Server not being accessible. Have
you determined why?
S,
ALR
View the original post :
http://www.jboss.com/index.html?
Sisepago, can I get a Unit Test for this:
15:09:25,236 ERROR [AbstractKernelController] Error installing to Start:
name=jboss.j2ee:jar=classes
| ,name=HelloBean,service=EJB3 state=Create
| java.lang.RuntimeException: Could not bind Reference Class Name: Proxy for:
org.ormsys.ejb3.Hello
| T
"sisepago" wrote : ...
| but testing with mvn command "mvn test" doesn't work, because of
java.lang.NoClassDefFoundError: org/jboss/metadata/process/chain/ProcessorChain.
| here is the error trace:
|
| 12:39:59,564 INFO [HelloBeanTest] Test #1
| | 12:39:59,830 INFO [JBossEJBContaine
with this dependencies configuration on the pom.xml all thing work fine through
the comannd "mvn clean install". That means jboss-ejb3-embedded has a
dependency jboss-metadata-1.0.0.CR1 and maybe another dependencies have also
dependency jboss-metadata-1.0.0.CR5 and I do not know why?
http://ma
anonymous wrote : but testing with mvn command "mvn test" doesn't work, because
of java.lang.NoClassDefFoundError:
org/jboss/metadata/process/chain/ProcessorChain.
I noticed that error this morning while trying out few things. Here's what i
did:
- I have the EJB3 SVN repository on my local se
For now I can now compile my small test case:
env.: mac os x, Maven version: 2.0.9, Java version: 1.5.0_16
| /**
| * Unit test for simple App.
| */
| public class HelloBeanTest {
|
| private static final Logger log = Logger.getLogger(HelloBeanTest.class);
|
| private
I did a clean build and don't see this error. Which version of Maven do you
use? And does the following command throw any errors:
mvn clean install
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188368#4188368
Reply to the post :
http://www.jboss.com/index.
Here is my pom.xml
http://maven.apache.org/POM/4.0.0";
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
| xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
| 4.0.0
| org.orm-sys.ejb3
| ormsys-ejb31-embeddable
Please post your pom.xml file.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188356#4188356
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188356
___
jboss-user mailing list
Hi Carlo,
today, I tried one more time to see, if I can more experiment with EJB3.1
Embeddable but without sucess.
After a maven command call "mvn eclipse:clean eclipse:eclipse", I got this
error may you can know where is the matter here:
207b downloaded
| Downloading:
http://snapshots.jbos
I've upgraded embedded to use MC 2.0.0.CR5 and applied the workaround. For now
embedded is using core SNAPSHOT.
https://jira.jboss.org/jira/browse/EJBTHREE-1575[/url]
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188134#4188134
Reply to the post :
http://w
Carlo,
Could you please apply the workaround (constructor injection definition in
jboss-ejb3-embedded-1.0.0-SNAPSHOT.jar/embedded-bootstrap-beans.xml)
and place an updated EJB3 embedded snapshot build in the JBoss maven repository?
many thanks,
Karl
View the original post :
http://www.jboss.c
Update: I hadn't refreshed the page, so when i replied, i did not see Ales or
Carlo comments.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187371#4187371
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187371
_
At least MC should say that we entered a non-deterministic situation and throw
an exception.
I think it would be better to have an UndeterminedConstructorInfo which does
some extra work at the end.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187370#418737
I tried this on a sample project with EJB3.1 embedded and ran into the same
error:
---
| Test set: jaikiran.ejb3_1.client.EJBClientTestCase
|
--
Cool, thanks a lot
Karl
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187368#4187368
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187368
___
jboss-user mailing list
jboss-
https://jira.jboss.org/jira/browse/JBMICROCONT-380
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187367#4187367
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187367
___
jbos
The problem and fix are both quite simple. ;-)
Problem:
BeanMetaDataDeployer has 2 constructors.
The metadata provided in that xml is not enough to make exact/deterministic
decision about which constructor to chose.
In Carlo's case, he is just lucky that ConstructorInfo is ordered the way it is
Using JUnit instead of TestNG doesn't make a difference.
JDK: same behavior with JDK 1.6.0_10 and 1.5.0_15.
Karl
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187325#4187325
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
So far can't find anything different than my own setup except junit, which I
have as:
| junit
| junit
| [4,)
| test
|
What JDK are you using?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186776#4186776
Reply to the
Carlo,
thanks for responding.
Yes, 2.0.9, maven output is:
D:\sandbox\projects\green\EmbeddedEjbTest>mvn -Dverbose=true dependency:tree
| [INFO] Scanning for projects...
| [INFO] Searching repository for plugin with prefix: 'dependency'.
| [INFO]
--
Just to be sure: post the output of mvn -Dverbose=true dependency:tree here.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186484#4186484
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186484
__
It's not the exact same problem, but close.
Usually this indicates that Maven has chosen the wrong dependency somewhere.
Are you using Maven 2.0.9?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186483#4186483
Reply to the post :
http://www.jboss.com/index.
24 matches
Mail list logo
