[JBoss JIRA] (JBIDE-13530) JBoss Perspective does not reload default views
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-13530?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-13530:
----------------------------------
Component/s: common
> JBoss Perspective does not reload default views
> -----------------------------------------------
>
> Key: JBIDE-13530
> URL: https://issues.redhat.com/browse/JBIDE-13530
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.0.0.Final
> Reporter: Michelle Murray
> Priority: Major
> Fix For: 4.1.0.Alpha1
>
>
> 1. Open JBDS or Eclipse.
> 2. Select JBoss Perspective.
> 3. Close some or all of the views (e.g., Servers, OpenShift Explorer, Palette, Project Explorer).
> 4. Select JBoss Perspective again and the closed views don't reopen.
> 5. Exit and restart JBDS or Eclipse and select JBoss Perspective again and still the closed views don't reopen.
> Perhaps this is intended behavior but I had assumed that some views were linked to JBoss Perspective and selecting JBoss Perspective would automatically open them. As a user I ran in to trouble as I closed lots of the views and then didn't know which were associated with JBoss Perspective but wanted a fresh JBoss Perspective again. The only resolution was to reinstall JBDS or JBoss Tools into Eclipse.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-13530) JBoss Perspective does not reload default views
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-13530?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-13530.
---------------------------------
Closing, nothing to do.
> JBoss Perspective does not reload default views
> -----------------------------------------------
>
> Key: JBIDE-13530
> URL: https://issues.redhat.com/browse/JBIDE-13530
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.0.0.Final
> Reporter: Michelle Murray
> Priority: Major
> Fix For: 4.1.0.Alpha1
>
>
> 1. Open JBDS or Eclipse.
> 2. Select JBoss Perspective.
> 3. Close some or all of the views (e.g., Servers, OpenShift Explorer, Palette, Project Explorer).
> 4. Select JBoss Perspective again and the closed views don't reopen.
> 5. Exit and restart JBDS or Eclipse and select JBoss Perspective again and still the closed views don't reopen.
> Perhaps this is intended behavior but I had assumed that some views were linked to JBoss Perspective and selecting JBoss Perspective would automatically open them. As a user I ran in to trouble as I closed lots of the views and then didn't know which were associated with JBoss Perspective but wanted a fresh JBoss Perspective again. The only resolution was to reinstall JBDS or JBoss Tools into Eclipse.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-16380) JBOSS 6.2 EAP doesnt print jdk logging.
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-16380?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-16380:
----------------------------------
Component/s: server
> JBOSS 6.2 EAP doesnt print jdk logging.
> ----------------------------------------
>
> Key: JBIDE-16380
> URL: https://issues.redhat.com/browse/JBIDE-16380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Vineela Gampa
> Priority: Major
> Labels: jboss
>
> We log request and response using com.sun.jersey.api.container.filter.LoggingFilter which uses java.util.logging.Logger . Application specific logs are getting printed with the below jboss-deployment-structure contents .
> <exclusions>
> <module name="org.apache.log4j" />
> <module name="org.slf4j.jcl-over-slf4j" />
> <module name="org.slf4j.impl" />
> <module name="org.slf4j" />
> <module name="org.slf4j.ext" />
> <module name="org.apache.commons.logging" />
> </exclusions>
> Debugged a lot but couldnt figure out why jdk logging is going to jboss server.log rather than the appender configured in log4j.properties.
> log4j.logger.com.sun.jersey.api.container.filter.LoggingFilter=INFO, RESTService
> log4j.additivity.com.sun.jersey.api.container.filter.LoggingFilter=false
> #requests to serve a log file
> log4j.appender.RESTService=com.macys.mobile.framework.logging.log4j.v1216.AsynchronousRollingFileAppender
> log4j.appender.RESTService.BufferSize=512
> log4j.appender.RESTService.Blocking=true
> log4j.appender.RESTService.File=${app.log.root}/rest.log
> log4j.appender.RESTService.DefaultConsoleThreshold=INFO
> log4j.appender.RESTService.ConsoleThreshold=INFO
> log4j.appender.RESTService.threshold=INFO
> # Maximum file size and no: of back up files can be configured as per the production environment requirement
> log4j.appender.RESTService.MaxFileSize=100MB
> log4j.appender.RESTService.MaxBackupIndex=10
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-16380) JBOSS 6.2 EAP doesnt print jdk logging.
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-16380?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-16380.
---------------------------------
Closing, nothing to do.
> JBOSS 6.2 EAP doesnt print jdk logging.
> ----------------------------------------
>
> Key: JBIDE-16380
> URL: https://issues.redhat.com/browse/JBIDE-16380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Vineela Gampa
> Priority: Major
> Labels: jboss
>
> We log request and response using com.sun.jersey.api.container.filter.LoggingFilter which uses java.util.logging.Logger . Application specific logs are getting printed with the below jboss-deployment-structure contents .
> <exclusions>
> <module name="org.apache.log4j" />
> <module name="org.slf4j.jcl-over-slf4j" />
> <module name="org.slf4j.impl" />
> <module name="org.slf4j" />
> <module name="org.slf4j.ext" />
> <module name="org.apache.commons.logging" />
> </exclusions>
> Debugged a lot but couldnt figure out why jdk logging is going to jboss server.log rather than the appender configured in log4j.properties.
> log4j.logger.com.sun.jersey.api.container.filter.LoggingFilter=INFO, RESTService
> log4j.additivity.com.sun.jersey.api.container.filter.LoggingFilter=false
> #requests to serve a log file
> log4j.appender.RESTService=com.macys.mobile.framework.logging.log4j.v1216.AsynchronousRollingFileAppender
> log4j.appender.RESTService.BufferSize=512
> log4j.appender.RESTService.Blocking=true
> log4j.appender.RESTService.File=${app.log.root}/rest.log
> log4j.appender.RESTService.DefaultConsoleThreshold=INFO
> log4j.appender.RESTService.ConsoleThreshold=INFO
> log4j.appender.RESTService.threshold=INFO
> # Maximum file size and no: of back up files can be configured as per the production environment requirement
> log4j.appender.RESTService.MaxFileSize=100MB
> log4j.appender.RESTService.MaxBackupIndex=10
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-2229) Hibernate Tools - JUnit tests has a lot of errors with Oracle test connection
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-2229?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-2229.
--------------------------------
Closing, nothing to do.
> Hibernate Tools - JUnit tests has a lot of errors with Oracle test connection
> -----------------------------------------------------------------------------
>
> Key: JBIDE-2229
> URL: https://issues.redhat.com/browse/JBIDE-2229
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Vitali Yemialyanchyk
> Assignee: Vitali Yemialyanchyk
> Priority: Minor
> Attachments: JBIDE-2229_20080529.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> 1) install Oracle 11g;
> 2) setup default db;
> 3) change etc/hibernate.properties:
> comment ## HypersonicSQL section,
> update ## Oracle section:
> hibernate.dialect org.hibernate.dialect.Oracle10gDialect
> hibernate.connection.driver_class oracle.jdbc.OracleDriver
> hibernate.connection.url jdbc:oracle:thin:@localhost:1521:orcl
> hibernate.connection.username SYSTEM
> hibernate.connection.password sa
> 4) add Oracle driver into the progect (on my computer it is "C:\app\Vitali\product\11.1.0\db_1\jdbc\lib\ojdbc5_g.jar")
> 5) Run ToolAllTests as JUnit test
> screenshot is example.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months