<div dir="ltr">Hi Vineet,<div><br></div><div>Thanks for the answer. This time I am sorry that didn't find time to work on this issue the last week. I wanted to complete it during the Forge Hack Night, but I there was nobody from the Forge experts there.</div>
<div><br></div><div>Anyway, I will use this media to drive the open points cleared. I do want to go with option two. I went through the docs and compared them to the Forge implementation. I have to pass a Configuration object to the EntityWidgetBuilderConfig constructor upon creating EntityWidgetBuilder. Unfortunately I couldn't find a place where these constructors are invoked. Can you please guide me one step further? :)</div>
<div><br></div><div>Thanks,</div><div>Ivan</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 21, 2014 at 4:46 PM, Vineet Reynolds Pereira <span dir="ltr"><<a href="mailto:vpereira@redhat.com" target="_blank">vpereira@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hey Ivanov,<br>
<br>
Sorry about the late reply and thanks for taking this on. On reviewing the code, there are two ways to fix this:<br>
<br>
1. the Forge Configuration object for the project could be used to store the target directory provided by the user. This was the approach used in Forge 1, but was unfortunately missed out in Forge 2. The configuration being empty and unused is the root cause of this bug.<br>
2. the metawidget could be initialized in a programmatic manner like described in this section : <a href="http://metawidget.sourceforge.net/doc/reference/en/html/ch02s04.html#section-architecture-widgetbuilders-implementing-your-own" target="_blank">http://metawidget.sourceforge.net/doc/reference/en/html/ch02s04.html#section-architecture-widgetbuilders-implementing-your-own</a><br>
Currently the XML route is used, and this prevents variable information like the target directory from being passed onto the widget, except through some shared store (like the Forge Configuration in the above point).<br>
I'd recommend this way going forward, but I'm ok if you stick to resolving the issue through (1) instead of (2).<br>
<br>
Thanks,<br>
Vineet<br>
<div class=""><br>
<br>
----- Original Message -----<br>
> From: "Ivan St. Ivanov" <<a href="mailto:ivan.st.ivanov@gmail.com">ivan.st.ivanov@gmail.com</a>><br>
> To: "forge-dev List" <<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a>><br>
> Sent: Sunday, May 18, 2014 1:30:23 AM<br>
> Subject: [forge-dev] Passing parameters from command to a meta widget<br>
><br>
> Hey folks,<br>
><br>
</div>> I am working on <a href="https://issues.jboss.org/browse/FORGE-1787" target="_blank">https://issues.jboss.org/browse/FORGE-1787</a> . As you might<br>
<div class="">> read in the comments, I found that in order to adapt the outcome of a link,<br>
> I need to pass somehow the webroot from the command to the<br>
> EntityWidgetBuilder.<br>
><br>
> Does anybody know the way I can pass this info?<br>
><br>
> Thanks,<br>
> Ivan<br>
><br>
</div>> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote></div><br></div>