[JBoss JIRA] Updated: (JBIDE-332) Create a new splash image for JBossIDE 2.0
by Marshall Culpepper (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-332?page=all ]
Marshall Culpepper updated JBIDE-332:
-------------------------------------
Attachment: ide_spotlight_v3progress.jpg
OK, we got the new image that covers the new product name "JBossIDE for Eclipse" and includes good spacing/alignment for the progress bar and loading message. Check out the attached JPG.. looks nice and pretty =). Issue should now be considered resolved..
> Create a new splash image for JBossIDE 2.0
> ------------------------------------------
>
> Key: JBIDE-332
> URL: http://jira.jboss.com/jira/browse/JBIDE-332
> Project: JBoss IDE
> Issue Type: Feature Request
> Reporter: Marshall Culpepper
> Assigned To: James Cobb
> Fix For: 2.0.0.Beta2
>
> Attachments: JBossIDE-splash.xcf, new_splash_left_aligned.jpg
>
>
> We need a new splash screen for JBossIDE 2.0...
> Preferrably the size shouldn't be bigger than 455x295. I've attached the splash screen we were using for 1.5 and 1.6 (it's in Gimp/XCF format)
--
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
19 years, 8 months
[JBoss JIRA] Created: (JBCOMMON-7) Archive Browser does not support jar:file: url protocol
by Chris Mercer (JIRA)
Archive Browser does not support jar:file: url protocol
-------------------------------------------------------
Key: JBCOMMON-7
URL: http://jira.jboss.com/jira/browse/JBCOMMON-7
Project: JBoss Common
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core
Environment: jdk 1.5.8
jboss 4.0.4ga
hibernate 3.2cr2
hibernate entity manager 3.2.0.CR1
Using ejb3/entity manager annotations
Reporter: Chris Mercer
Assigned To: Dimitris Andreadis
Priority: Critical
We have a seperate jar file that contains all of our model/entity objects. This jar gets put in the WEB-INF/lib directory, since we are only using wars and not ears. Using the hibernate auto-discovery feature causes an exception to occur. In this configuration.
Caused by: java.lang.RuntimeException: NOT IMPLEMENTED
at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:42)
at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:541)
... 148 more
org.jboss.util.file.ArchiveBrowser.getBrowser(URL url, Filter filter) only supports URLS that have a protocol of "file". However, jars have a protocol of "jar:file:" and therefore it will throw a RuntimeException saying "NOT IMPLEMENTED" (at least according to my debugger). There is already a JarArchiveBrowser class, the ArchiveBrowser just needs to recognize the protocol and handle it.
This also affects Hibernate entity manager, since it gets included in the jboss-archive-browsing.jar in order to handle the auto-discovery of mapped entities feature.
I've marked this as critical, since it effects entity manager features (though its only advanced hibernate only functionality)
--
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
19 years, 8 months