[JBoss JIRA] Created: (JBIDE-837) A structured model client, FacesRendererFactory$MyEMF2DOMAdapterRoot(renderer,RendererTypeImpl) threw following exception during adapter notification
by Anton Klimkovich (JIRA)
A structured model client, FacesRendererFactory$MyEMF2DOMAdapterRoot(renderer,RendererTypeImpl) threw following exception during adapter notification
------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-837
URL: http://jira.jboss.com/jira/browse/JBIDE-837
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 2.0.0.Beta3
Reporter: Anton Klimkovich
Attachments: 111.txt
JSF project
1 Open faces-config.xml on tree tab.
2 Create new Render Kit (RenderKit)->Renderer -> Attribute
3 Click on Source tab
4 Add to source <facet><facet-name>FacetName</facet-name></facet> inside <attribute></attribute>
example:
<renderer>
<component-family/>
<renderer-type>renderer</renderer-type>
<renderer-class>RClass</renderer-class>
<attribute>
<facet>
<facet-name>FacetName</facet-name>
</facet>
<attribute-name>AtrName</attribute-name>
<attribute-class>AtrClass</attribute-class>
</attribute>
</renderer>
5 Delete string <facet><facet-name>FacetName</facet-name></facet>
6 Save changes.
Exception willbe occur
Log attached.
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBIDE-708) Seam gen->Generate Entities action is always use default connection parameters
by Denis Golovin (JIRA)
Seam gen->Generate Entities action is always use default connection parameters
------------------------------------------------------------------------------
Key: JBIDE-708
URL: http://jira.jboss.com/jira/browse/JBIDE-708
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Reporter: Denis Golovin
Assigned To: Max Andersen
Fix For: 2.0.0.Beta3
No matter where build.properties is placed: source folder, root project folder.
No matter if there are connection parameters in hibernate-console.properties or hibernate.properties.
It always says.
[hibernate] Executing Hibernate Tool with a JDBC Configuration (for reverse engineering)
[hibernate] 1. task: hbm2java (Generates a set of .java files)
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.cfg.Environment <clinit>
[hibernate] INFO: Hibernate 3.2.0.cr5
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.cfg.Environment <clinit>
[hibernate] INFO: hibernate.properties not found
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.cfg.Environment buildBytecodeProvider
[hibernate] INFO: Bytecode provider name : cglib
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.cfg.Environment <clinit>
[hibernate] INFO: using JDK 1.4 java.sql.Timestamp handling
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.connection.DriverManagerConnectionProvider configure
[hibernate] INFO: Using Hibernate built-in connection pool (not for production use!)
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.connection.DriverManagerConnectionProvider configure
[hibernate] INFO: Hibernate connection pool size: 20
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.connection.DriverManagerConnectionProvider configure
[hibernate] INFO: autocommit mode: false
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.connection.DriverManagerConnectionProvider configure
[hibernate] INFO: using driver: org.hsqldb.jdbcDriver at URL: jdbc:hsqldb:hsql://localhost:1701
[hibernate] Aug 13, 2007 9:54:11 PM org.hibernate.connection.DriverManagerConnectionProvider configure
[hibernate] INFO: connection properties: {user=sa, password=****}
[hibernate] Aug 13, 2007 9:54:12 PM org.hibernate.cfg.SettingsFactory buildSettings
[hibernate] WARNING: Could not obtain connection metadata
[hibernate] java.sql.SQLException: socket creation error
It looks like it tries to load hibernate.properties from resources available for ClassLoader.
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBIDE-626) Hibernate Reverse Engeneering File (Editor)
by Aliaksey Nis (JIRA)
Hibernate Reverse Engeneering File (Editor)
-------------------------------------------
Key: JBIDE-626
URL: http://jira.jboss.com/jira/browse/JBIDE-626
Project: JBoss Tools
Issue Type: Feature Request
Components: Hibernate
Environment: WindowsXP SP2
rhds-win32-1.0.0.alpha.jar
Red Hat Developer Studio
Version: 1.0.0
Build: build 20070711-nightly
JDK 1.5_08
Reporter: Aliaksey Nis
Assigned To: Max Andersen
Priority: Optional
1. Using Wizard - Ctrl+N > Hibernate Reverse Engeneering File
2. Selecting project, press "Next", selecting Console Configuration, press "Finish".
File reveng.xml opend not in Hibernate Reverse Engeneering Editor, but in simple xml editor. If manually select this file, it's also opens in xml editor. After i manually select "Open With" Hibernate Reverse Engeneering Editor, its start to work properly - reveng.xml files opens in reverse engeneering editor.
Maybe this is not an issue, but i think better to make those files opened with Reverse editor by default.
--
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
18 years, 6 months
[JBoss JIRA] Created: (JBIDE-807) Red Hat JSP Editor & JSF context help
by martin di bella (JIRA)
Red Hat JSP Editor & JSF context help
-------------------------------------
Key: JBIDE-807
URL: http://jira.jboss.com/jira/browse/JBIDE-807
Project: JBoss Tools
Issue Type: Feature Request
Components: JSF
Affects Versions: 2.0.0.Beta3
Environment: Window XP, eclipse europa
Reporter: martin di bella
Hi, I realized that when working with the h:commandButton, the ctrl + space and property analizer let you pick a method defined in a backing bean for the action and actionListener properties.
But when working with other libraries components (like icefaces ice:commandButton, for instance: tried with Ajax4JSF a4j:commandButton too, same result) you can only choose regular properties, no methods.
Dunno if it's possible to have methods available for choosing, but it would be nice to choose from any of the backing beans bindable properties (properties and methods).
--
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
18 years, 6 months
[JBoss JIRA] Created: (JBIDE-651) NullPointerException under MarkSweep Garbage Collection
by Steve Davidson (JIRA)
NullPointerException under MarkSweep Garbage Collection
-------------------------------------------------------
Key: JBIDE-651
URL: http://jira.jboss.com/jira/browse/JBIDE-651
Project: JBoss Tools
Issue Type: Bug
Components: JBoss Tools Core
Environment: SuSE 10.1
Linux gorky 2.6.16.27-0.9-default #1 Tue Feb 13 09:35:18 UTC 2007 i686 i686 i386 GNU/Linux
java -version
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
Reporter: Steve Davidson
Assigned To: Marshall Culpepper
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.core.packages.ProjectArchiveStorer.loadArchiveFrom(ProjectArchiveStorer.java:29)
at org.jboss.ide.eclipse.as.core.packages.ProjectArchiveStorer.getArchiveFor(ProjectArchiveStorer.java:24)
at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.getTopPackage(JstPublisher.java:146)
at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publish(JstPublisher.java:101)
at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:88)
at org.jboss.ide.eclipse.as.core.server.stripped.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:89)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:835)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
at org.jboss.tools.jst.web.ui.action.server.RunServerJob.run(RunServerActionDelegate.java:155)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x68c4376d, pid=4119, tid=3077134000
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode)
# Problematic frame:
# C [libxpcom.so+0xc976d] _ZN13nsCOMPtr_baseD2Ev+0x13
#
# An error report file with more information is saved as hs_err_pid4119.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
/usr/local/bin/eclipse: line 3: 4119 Aborted ./eclipse $ECLIPSE_OPTS -data /home/$USER/projects $@
Eclipse.ini file;
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
128M
-vmargs
-Xms256m
-Xmx768m
-XX:MaxPermSize=256m
-XX:PermSize=128m
-XX:+UseConcMarkSweepGC
-Dosgi.bundlefile.limit=200
-Steve
--
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
18 years, 6 months