[JBoss JIRA] (FORGE-2223) Unable to create xhtml file
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2223?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2223.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.16.2.Final
Resolution: Done
XMLResource now supports XHTML files. Thanks!
> Unable to create xhtml file
> ---------------------------
>
> Key: FORGE-2223
> URL: https://issues.jboss.org/browse/FORGE-2223
> Project: …
[View More]Forge
> Issue Type: Bug
> Components: Addon Development
> Affects Versions: 2.13.0.Final
> Reporter: Michael Schwartz
> Assignee: George Gastaldi
> Fix For: 2.16.2.Final
>
>
> When creating a file with extension ".xhtml" with the following code the returned XMLResource is null. However creating the same file with extension "xml" works.
> XMLResource config = resourceFactory.create(XMLResource.class, new File(project.toString() + "/src/main/resources/" + filename));
> imho the create() method should produce an exception containing the cause of the error instead of returning null, it would simplify bugfixing.
> Furthermore the code getParent().mkdirs(); (2 occurences) in org.jboss.forge.addon.resource.AbstractFileResource may (and do) produce NullPointerExceptions.
> Is there any suggestion to get the base resource directory via code instead of hardcoding it to "project.toString() + "/src/main/resources"?
> thanks and regards from austria, Mike
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[View Less]
9 years, 10 months
[JBoss JIRA] (FORGE-2223) Unable to create xhtml file
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2223?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2223:
----------------------------------------
Hi Mike,
In order to return the resources path, you need to use the ResourcesFacet:
{code}
project.getFacet(ResourcesFacet.class).getResourceDirectory()
{code}
As for XHTML not being handled, you´re right. XHTML should be treated as a XMLResource.
Thanks for the feedback and sorry for missing this for some time.
> Unable to …
[View More]create xhtml file
> ---------------------------
>
> Key: FORGE-2223
> URL: https://issues.jboss.org/browse/FORGE-2223
> Project: Forge
> Issue Type: Bug
> Components: Addon Development
> Affects Versions: 2.13.0.Final
> Reporter: Michael Schwartz
>
> When creating a file with extension ".xhtml" with the following code the returned XMLResource is null. However creating the same file with extension "xml" works.
> XMLResource config = resourceFactory.create(XMLResource.class, new File(project.toString() + "/src/main/resources/" + filename));
> imho the create() method should produce an exception containing the cause of the error instead of returning null, it would simplify bugfixing.
> Furthermore the code getParent().mkdirs(); (2 occurences) in org.jboss.forge.addon.resource.AbstractFileResource may (and do) produce NullPointerExceptions.
> Is there any suggestion to get the base resource directory via code instead of hardcoding it to "project.toString() + "/src/main/resources"?
> thanks and regards from austria, Mike
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[View Less]
9 years, 10 months
[JBoss JIRA] (FORGE-2223) Unable to create xhtml file
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2223?page=com.atlassian.jira.plugin... ]
George Gastaldi edited comment on FORGE-2223 at 5/27/15 2:44 AM:
-----------------------------------------------------------------
Hi Mike,
In order to return the resources path, you need to use the ResourcesFacet:
{code:java}
project.getFacet(ResourcesFacet.class).getResourceDirectory()
{code}
As for XHTML not being handled, you´re right. XHTML should be treated as a XMLResource.
Thanks for the feedback and …
[View More]sorry for missing this for some time.
was (Author: gastaldi):
Hi Mike,
In order to return the resources path, you need to use the ResourcesFacet:
{code}
project.getFacet(ResourcesFacet.class).getResourceDirectory()
{code}
As for XHTML not being handled, you´re right. XHTML should be treated as a XMLResource.
Thanks for the feedback and sorry for missing this for some time.
> Unable to create xhtml file
> ---------------------------
>
> Key: FORGE-2223
> URL: https://issues.jboss.org/browse/FORGE-2223
> Project: Forge
> Issue Type: Bug
> Components: Addon Development
> Affects Versions: 2.13.0.Final
> Reporter: Michael Schwartz
>
> When creating a file with extension ".xhtml" with the following code the returned XMLResource is null. However creating the same file with extension "xml" works.
> XMLResource config = resourceFactory.create(XMLResource.class, new File(project.toString() + "/src/main/resources/" + filename));
> imho the create() method should produce an exception containing the cause of the error instead of returning null, it would simplify bugfixing.
> Furthermore the code getParent().mkdirs(); (2 occurences) in org.jboss.forge.addon.resource.AbstractFileResource may (and do) produce NullPointerExceptions.
> Is there any suggestion to get the base resource directory via code instead of hardcoding it to "project.toString() + "/src/main/resources"?
> thanks and regards from austria, Mike
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[View Less]
9 years, 10 months
[JBoss JIRA] (FORGE-2335) Enhancements on the Shell progress monitor
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2335?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2335:
-----------------------------------
Priority: Optional (was: Major)
> Enhancements on the Shell progress monitor
> ------------------------------------------
>
> Key: FORGE-2335
> URL: https://issues.jboss.org/browse/FORGE-2335
> Project: Forge
> Issue Type: Enhancement
> Components: UI …
[View More]- Shell
> Affects Versions: 2.16.1.Final
> Reporter: George Gastaldi
> Priority: Optional
> Labels: starter
> Fix For: 2.x Future
>
>
> The current output when using the UIProgressMonitor in shell is:
> {code}
> ***INFO*** Executing Rules: :Analyze Java(4%) Time until next Rule: 2 minutes, 7 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(8%) Time until next Rule: 1 minutes, 34 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(12%) Time until next Rule: 1 minutes, 7 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(16%) Time until next Rule: 1 minutes, 3 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(20%) Time until next Rule: 55 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(24%) Time until next Rule: 53 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(29%) Time until next Rule: 53 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(33%) Time until next Rule: 49 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(37%) Time until next Rule: 46 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(41%) Time until next Rule: 44 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(45%) Time until next Rule: 40 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(49%) Time until next Rule: 38 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(54%) Time until next Rule: 37 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(58%) Time until next Rule: 33 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(62%) Time until next Rule: 29 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(66%) Time until next Rule: 25 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(70%) Time until next Rule: 22 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(74%) Time until next Rule: 18 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(79%) Time until next Rule: 15 seconds [24/1229] ...
> ***INFO*** Executing Rules: :Analyze Java(83%) Time until next Rule: 12 seconds [24/1229] ...
> {code}
> This doesn't look so good in the UI. The following could be done:
> - add the loading spinner on each progress update
> - write the progress in a single line
> The loading spinner could appear by default on long-running tasks in the shell
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[View Less]
9 years, 10 months
[JBoss JIRA] (FORGE-253) Forge should provide development profiles API for datasources and other configs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-253?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-253.
---------------------------------
Fix Version/s: (was: 2.x Future)
Resolution: Out of Date
Afaik this is already accomplished by the database-tools addon. Closing it.
> Forge should provide development profiles API for datasources and other configs
> -------------------------------------------------------------------------------
>
> …
[View More]Key: FORGE-253
> URL: https://issues.jboss.org/browse/FORGE-253
> Project: Forge
> Issue Type: Feature Request
> Components: Plugin API
> Affects Versions: 1.0.0.Alpha3
> Reporter: Lincoln Baxter III
>
> lincolnthree
> It gives you what is in persistence.xml
> 11:22
> maxandersen
> it wasn't there a jbossworld
> 11:22
> lincolnthree
> that's been there from the beginning
> 11:22
> maxandersen
> yes - persistence.xml says datasources
> nothing about the actual connection info
> 11:23
> lincolnthree
> oh right
> well
> connection info is stored on the server
> forge doesn't know that
> unless it's in the persistence.xml
> 11:23
> maxandersen
> lincolnthree: exaactly - but it has to know that eventually.
> 11:23
> lincolnthree
> as properties
> 11:23
> maxandersen
> lincolnthree: it wont be
> lincolnthree: this is why tools like rails, hibernate tools and others have notion of "profiles" or simply just property overrides for use at design time and for use at runtime
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[View Less]
9 years, 10 months
[JBoss JIRA] (FURNACE-52) ClassCastException on application scoped beans
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FURNACE-52?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FURNACE-52:
-----------------------------------
Description: Having an addon with a class declared as an @ApplicationScoped bean, after reinstalling the same addon and calling the bean a ClassCastException is raised. (was: Having an addon with a class declared as an @ApplicationScoped bean, after reinstalling the same addon and calling the bean a ClassCastException should be raised. )
…
[View More]
> ClassCastException on application scoped beans
> ----------------------------------------------
>
> Key: FURNACE-52
> URL: https://issues.jboss.org/browse/FURNACE-52
> Project: Forge: Furnace
> Issue Type: Bug
> Components: Container - CDI, Runtime
> Affects Versions: 2.18.1.Final
> Reporter: George Gastaldi
> Fix For: 2.x Future
>
>
> Having an addon with a class declared as an @ApplicationScoped bean, after reinstalling the same addon and calling the bean a ClassCastException is raised.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[View Less]
9 years, 10 months