Re: [forge-dev] Seam Persistence Plugin broken
by Daniel Sachse
Hey,
thanks for your answer! I changed it manually, but after updating my forge/core repo today with the latest commits I got the following error with forge when executing the following command: forge source-plugin ~/git/plugin-seam-persistence
Error message:
***SUCCESS*** Build successful.
***INFO*** Installing plugin artifact.
Wrote ~/.forge/plugins/org/jboss/forge/seam/persistence/plugin-seam-persistence/1.0.0-SNAPSHOT-3d85381d-bb06-493a-89c8-9f8edd08fc9a
Wrote ~/.forge/plugins/org/jboss/forge/seam/persistence/plugin-seam-persistence/1.0.0-SNAPSHOT-3d85381d-bb06-493a-89c8-9f8edd08fc9a/module.xml
***ERROR*** [forge source-plugin] Could not import XML from stream
org.jboss.forge.shell.exceptions.CommandExecutionException: Could not import XML from stream
at org.jboss.forge.shell.command.Execution.perform(Execution.java:153)
at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:125)
at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:63)
at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:811)
at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:834)
at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:624)
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:597)
at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
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:597)
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:106)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at org.jboss.forge.shell.command.Execution.perform(Execution.java:149)
... 31 more
Caused by: org.jboss.forge.parser.xml.XMLParserException: Could not import XML from stream
at org.jboss.forge.parser.xml.XMLParser.parse(XMLParser.java:116)
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.createModule(ForgePlugin.java:518)
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:483)
at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromLocalProject(ForgePlugin.java:371)
... 36 more
Caused by: java.lang.NullPointerException
at org.jboss.forge.parser.xml.XMLParser.parse(XMLParser.java:99)
... 39 more
I don't know if this also happens with other plugins too. Has anybody else encountered this?
Regards,
Daniel
Von: "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com>
Betreff: Re: [forge-dev] Seam Persistence Plugin broken
Datum: 16. Dezember 2011 17:20:20 MEZ
An: forge-dev List <forge-dev(a)lists.jboss.org>
Antwort an: forge-dev List <forge-dev(a)lists.jboss.org>
Yep, sorry about that. We had to update these APIs now or we wouldn't have a chance in the future. You can now use depFacet.addDirectDependency(), and can query using hasDirectDependency() or hasEffectiveDependency()
I think the new API is much easier to understand! Let me know if you have any thoughts.
We still need to go through and update all of the plugins to make sure they use the new APIs.
~Lincoln
On Thu, Dec 15, 2011 at 5:59 PM, Paul Bakker <paul.bakker.nl(a)gmail.com> wrote:
Hi Daniel,
This is caused by some refactoring after API reviews because Forge will soon move to a candidate release. This was our last change to improve those APIs. You will probably have this problem with some other plugins too, because many of them rely on the DependencyFacet. We will be fixing plugins in the next week(s). Sorry for the inconvenience.
Paul
On Dec 15, 2011, at 9:52 PM, Daniel Sachse wrote:
> Hey guys,
>
> the Seam Persistence Plugin is not building anymore, because the DependencyFacet doesn´t have the methods "hasDependency" and "addDependency" anymore.
> How can these methods be replaced?
>
> Regards,
>
> Daniel
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
12 years, 5 months
Creating Qualifier with Forge
by Daniel Sachse
Hey guys,
atm I am working on FORGE-372 and I need to create a Qualifier into the target project.
I made a method on my own which looks the following:
private JavaAnnotation createQualifier(String packageName, String interfaceName) {
JavaAnnotation javaAnnotation = JavaParser.create(JavaAnnotation.class).setName(interfaceName).setPackage(packageName);
javaAnnotation.addImport(Qualifier.class);
javaAnnotation.addImport(Target.class);
javaAnnotation.addImport(Retention.class);
javaAnnotation.addImport(Documented.class);
javaAnnotation.addAnnotation(Qualifier.class);
javaAnnotation.addAnnotation(Target.class).setEnumValue(TYPE).setEnumValue(METHOD).setEnumValue(PARAMETER).setEnumValue(FIELD);
javaAnnotation.addAnnotation(Retention.class).setEnumValue(RUNTIME);
javaAnnotation.addAnnotation(Documented.class);
return javaAnnotation;
}
As soon as I try to save it with "javaSourceFacet.saveJavaSource(createQualifier(packageName, "Forge"));", Forge throws the following error: "seam-persistence install-managed-persistence-context] Unknown JavaSource type."
Anyone any idea?
BTW:
If this createQualifier annotation doesn't exist already somewhere else, I would suggest to move into the core somewhere, as soon as it is finished and tested. Unfortunately I can't see the output atm.
Regards,
Daniel
12 years, 5 months
Seam Persistence Plugin broken
by Daniel Sachse
Hey guys,
the Seam Persistence Plugin is not building anymore, because the DependencyFacet doesn´t have the methods "hasDependency" and "addDependency" anymore.
How can these methods be replaced?
Regards,
Daniel
12 years, 5 months
Class Loading Error: ResourceLoadingException
by Ryan Bradley
Hi all,
I am trying to use seam-render in my plugin, for classes such as
TemplateCompiler. However, when I include it in the project and try to
build the plugin in Forge, I get a strange ResourceLoadingException
which suggests that the class is not being found. Can anyone shed some
light on this problem?
Thanks,
Ryan
12 years, 5 months
Testing new metawidget stuff
by Ivan St. Ivanov
Hi Lincoln, forge devs, :-)
On today's meeting you asked us to test the new metawidget stuff. So here
is what I did:
1) Pulled and built the latest forge tool
2) Created new project, a couple of new entities (Continent and Hurricane)
and a many-to-many relationship between them
3) Initiated scaffold from-entity on both entities
Everything passed successfully. Now what do we expect? :-)
Cheers!
Ivan
12 years, 5 months
