[JBoss JIRA] Created: (JBIDE-909) Publishing EAR and update failure
by Bernd Ahrens (JIRA)
Publishing EAR and update failure
---------------------------------
Key: JBIDE-909
URL: http://jira.jboss.com/jira/browse/JBIDE-909
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.0.0.Beta4
Environment: wtp-all-in-one-sdk-R-2.0-200706260303-win32.zip,JBossAS-Tools-200709180102-nightly.zip,JBossTools-Core-200709180102-nightly.zip, jdk1.5.0_12
Reporter: Bernd Ahrens
Hello,
I reproduced the behavior is with the new Nightly Build.
I am not sure, where and how to write a ?jira?, so here the steps for reprodducing:
I installed wtp-all-in-one-sdk-R-2.0-200706260303-win32.zip
with
JBossAS-Tools-200709180102-nightly.zip
and
JBossTools-Core-200709180102-nightly.zip
In an Eclipseextension folder.
Because with the Beta3 a got some erros in the preferences, like discussed in the forum.
Now I make a simple testear (EAR 1.4) Projekt and a testearWeb (Dynamic WebModule2.4) with a simple index.jsp.
In the EAR-Projekt under Properties / J2EE Module Dependencies I mark the "testearWeb" Projekt.
Publishing it to the local Server, the following structure is deployed:
c:\eclipse33\server\jboss-4.0.3SP1\server\default\deploy\testear.ear\testweb.war\index.jsp
Then I make a change on the index.jsp and push "Publish to the Server".
Now, there is a second folder for the war with only one file:
c:\eclipse33\server\jboss-4.0.3SP1\server\default\deploy\testearWeb.war\index.jsp
The first war-folder is still there, so you have two wars wih the same Context Root.
Why is there a second folder for the war?
Any ideas?
Could an Exploded Ear/War-Configuration help me? How is it configured?
( Before I make a Test with JBossAS-Tools-200709170536-nightly.zip, there was also a second folder for the war, but with more Content, I mean?)
Thanks for help!
Bernd
PS: I will try to live for once whith the slowly WTP-Deploy-Functions, maybe, with a faster Tomcat for the Webcontainer, maybe with Sysdeo. Have you other suggestions for Eclipse33?
--
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-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: (RHDS-186) Problems importing project created with RHDV beta 1 into new workspace in RHDS beta 1
by Y E (JIRA)
Problems importing project created with RHDV beta 1 into new workspace in RHDS beta 1
-------------------------------------------------------------------------------------
Key: RHDS-186
URL: http://jira.jboss.com/jira/browse/RHDS-186
Project: Red Hat Developer Studio
Issue Type: Bug
Components: visualeditor
Affects Versions: 1.0.0.beta1
Environment: Windows XP Enterprise,Red Hat Develoopoer Studio 1, jre 1.5.0_09
Reporter: Y E
Attachments: 1.log, 2.log
1.Generated WS Client project from a wsdl
2.Generated JSP to test the client
3. Closed the current workspace
4. Opened new workspace, copied the project to the new workspace and tried to import it.
5. No message is given, but the project is empty in package explorer ( see 1.log)
6.Closed RHDS
7.Opened RHDS
8.Message appears:
Initialising Java Tooling(Time of error ....)
Reason:
java.lang.NullPOinterException ( 2.log)
The same problem occurs if step 2 is skipped.
--
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