[
http://jira.jboss.com/jira/browse/JBMICROCONT-152?page=comments#action_12... ]
Wesley Hales commented on JBMICROCONT-152:
------------------------------------------
Is there a workaround?
I am getting this error and have no idea how to resolve it...I am brand spanking new to
the microcontainer and embedded-ejb but feel like I'm at the finish line with this
one. (attached is a sample app - just type "mvn jetty:run" to see the error)
Dependency names need to be validated earlier
---------------------------------------------
Key: JBMICROCONT-152
URL:
http://jira.jboss.com/jira/browse/JBMICROCONT-152
Project: JBoss MicroContainer
Issue Type: Bug
Components: Dependency
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossMC_2_0_0_CR1
Attachments: helloApp4.rar
I'm seeing an error like the following testing profileservice attachments overrides:
Caused by: java.lang.IllegalArgumentException: Null name
at
org.jboss.dependency.plugins.AbstractController.getContext(AbstractController.java:129)
at
org.jboss.kernel.plugins.dependency.AbstractKernelController.getContext(AbstractKernelController.java:101)
at
org.jboss.dependency.plugins.AbstractDependencyItem.resolve(AbstractDependencyItem.java:117)
at
org.jboss.dependency.plugins.AbstractDependencyInfo.resolveDependencies(AbstractDependencyInfo.java:128)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:595)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:531)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
at org.jboss.system.ServiceController.doInstall(ServiceController.java:638)
at org.jboss.system.ServiceController.install(ServiceController.java:271)
This error regarding the invalid dependency item name not showing up until there is an
attempt to resolve it makes it impossible to debug the problem as there is no context in
the dependency to understand why its null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira