July 2012 - embjopr-issues - Jboss List Archives

[JBoss JIRA] (EMBJOPR-374) MySQL datasource type mapping should be present

by Larry O'Leary (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-374?page=com.atlassian.jira.plugi... ] Larry O'Leary moved JBPAPP-9474 to EMBJOPR-374: ----------------------------------------------- Project: Embedded Jopr (was: JBoss Enterprise Application Platform) Key: EMBJOPR-374 (was: JBPAPP-9474) Affects Version/s: 1.3.4.SP5 (was: EAP_EWP 5.1.2) Release Notes Docs Status: (was: Not Yet Documented) Release Notes Text: (was: Datasource type mapping property is now a text field allowing the input of a type mapping to use with a datasource.) Component/s: Plugin (was: Embedded Jopr) Security: (was: Public) Fix Version/s: 1.3.4.SP6 (was: EAP_EWP 5.1.3) Docs QE Status: (was: NEW) > MySQL datasource type mapping should be present > ----------------------------------------------- > > Key: EMBJOPR-374 > URL: https://issues.jboss.org/browse/EMBJOPR-374 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP5 > Environment: JBoss EAP 5.1.2 > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > From Bugzilla RHQ Project Bug 791142 - Jan Martiska 2012-02-16 05:21:47 EST > When creating a datasource in EAP 5.1.2 admin console, it was found out there was no choice 'MySQL' for type mapping. I wonder why this is not present currently? It is a supported database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-373) BRMS is not identified as a product by JBoss EAP plug-in

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-373?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated EMBJOPR-373: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=834360 (was: https://bugzilla.redhat.com/show_bug.cgi?id=838141) > BRMS is not identified as a product by JBoss EAP plug-in > -------------------------------------------------------- > > Key: EMBJOPR-373 > URL: https://issues.jboss.org/browse/EMBJOPR-373 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP6 > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Labels: admin-console, jopr > Fix For: 1.3.4.SP5 > > > BRMS gets its branding removed by the JBoss AS plug-in contained in admin-console. Specifically, the plug-in calls the BRMS server AS 5 instead of BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-373) BRMS is not identified as a product by JBoss EAP plug-in

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-373?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated EMBJOPR-373: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=838141 (was: https://bugzilla.redhat.com/show_bug.cgi?id=838141) > BRMS is not identified as a product by JBoss EAP plug-in > -------------------------------------------------------- > > Key: EMBJOPR-373 > URL: https://issues.jboss.org/browse/EMBJOPR-373 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP6 > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Labels: admin-console, jopr > Fix For: 1.3.4.SP5 > > > BRMS gets its branding removed by the JBoss AS plug-in contained in admin-console. Specifically, the plug-in calls the BRMS server AS 5 instead of BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-373) BRMS is not identified as a product by JBoss EAP plug-in

by Larry O'Leary (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-373?page=com.atlassian.jira.plugi... ] Larry O'Leary moved JBPAPP-9473 to EMBJOPR-373: ----------------------------------------------- Project: Embedded Jopr (was: JBoss Enterprise Application Platform) Key: EMBJOPR-373 (was: JBPAPP-9473) Affects Version/s: 1.3.4.SP6 (was: EAP_EWP 5.1.2) Component/s: Plugin (was: Embedded Jopr) Security: (was: Public) Fix Version/s: 1.3.4.SP5 (was: EAP_EWP 5.1.3) Docs QE Status: (was: NEW) > BRMS is not identified as a product by JBoss EAP plug-in > -------------------------------------------------------- > > Key: EMBJOPR-373 > URL: https://issues.jboss.org/browse/EMBJOPR-373 > Project: Embedded Jopr > Issue Type: Bug > Components: Plugin > Affects Versions: 1.3.4.SP6 > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Labels: admin-console, jopr > Fix For: 1.3.4.SP5 > > > BRMS gets its branding removed by the JBoss AS plug-in contained in admin-console. Specifically, the plug-in calls the BRMS server AS 5 instead of BRMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-372) rhq-core-domain.jar missing version attribute from persistence.xml

by Larry O'Leary (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-372?page=com.atlassian.jira.plugi... ] Larry O'Leary reassigned EMBJOPR-372: ------------------------------------- Assignee: (was: Heiko Braun) > rhq-core-domain.jar missing version attribute from persistence.xml > ------------------------------------------------------------------ > > Key: EMBJOPR-372 > URL: https://issues.jboss.org/browse/EMBJOPR-372 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.3.4.SP5 > Reporter: James Livingston > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > The persistence.xml file in rhq-core-domain.jar from admin-console.war is missing the version attribute, which causes an error from xml parsers in strict mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-372) rhq-core-domain.jar missing version attribute from persistence.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-372?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated EMBJOPR-372: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=797012 (was: https://bugzilla.redhat.com/show_bug.cgi?id=797012) > rhq-core-domain.jar missing version attribute from persistence.xml > ------------------------------------------------------------------ > > Key: EMBJOPR-372 > URL: https://issues.jboss.org/browse/EMBJOPR-372 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.3.4.SP5 > Reporter: James Livingston > Assignee: Heiko Braun > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > The persistence.xml file in rhq-core-domain.jar from admin-console.war is missing the version attribute, which causes an error from xml parsers in strict mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-372) rhq-core-domain.jar missing version attribute from persistence.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-372?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated EMBJOPR-372: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=797012 (was: https://bugzilla.redhat.com/show_bug.cgi?id=797012) > rhq-core-domain.jar missing version attribute from persistence.xml > ------------------------------------------------------------------ > > Key: EMBJOPR-372 > URL: https://issues.jboss.org/browse/EMBJOPR-372 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.3.4.SP5 > Reporter: James Livingston > Assignee: Heiko Braun > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > The persistence.xml file in rhq-core-domain.jar from admin-console.war is missing the version attribute, which causes an error from xml parsers in strict mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-372) rhq-core-domain.jar missing version attribute from persistence.xml

by Larry O'Leary (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-372?page=com.atlassian.jira.plugi... ] Larry O'Leary moved JBPAPP-9472 to EMBJOPR-372: ----------------------------------------------- Project: Embedded Jopr (was: JBoss Enterprise Application Platform) Key: EMBJOPR-372 (was: JBPAPP-9472) Affects Version/s: 1.3.4.SP5 (was: EAP_EWP 5.1.2) Component/s: (was: Embedded Jopr) Security: (was: Public) Fix Version/s: 1.3.4.SP6 (was: EAP_EWP 5.1.3) Docs QE Status: (was: NEW) > rhq-core-domain.jar missing version attribute from persistence.xml > ------------------------------------------------------------------ > > Key: EMBJOPR-372 > URL: https://issues.jboss.org/browse/EMBJOPR-372 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.3.4.SP5 > Reporter: James Livingston > Assignee: Heiko Braun > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > The persistence.xml file in rhq-core-domain.jar from admin-console.war is missing the version attribute, which causes an error from xml parsers in strict mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-358) In IE7, configuration tab under bindings page is blank, works fine in FF

by Larry O'Leary (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-358?page=com.atlassian.jira.plugi... ] Larry O'Leary updated EMBJOPR-358: ---------------------------------- Fix Version/s: 1.3.4.SP6 (was: 1.3.4) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=795918, https://bugzilla.redhat.com/show_bug.cgi?id=781116 (was: https://bugzilla.redhat.com/show_bug.cgi?id=795918, https://bugzilla.redhat.com/show_bug.cgi?id=781116) Affects Version/s: 1.3.4.SP5 (was: 1.3.4) > In IE7, configuration tab under bindings page is blank, works fine in FF > ------------------------------------------------------------------------ > > Key: EMBJOPR-358 > URL: https://issues.jboss.org/browse/EMBJOPR-358 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.3.4.SP5 > Environment: EAP5.1 running on Windows 2008, front-end by Apache. Accessed using IE7 > Reporter: Joel Tosi > Assignee: Larry O'Leary > Priority: Blocker > Fix For: 1.3.4.SP6 > > Attachments: embjopr-EMBJOPR-358.patch > > > Open up Admin console in IE7 - login as admin and go to Service Binding Manager, then choose Configuration tab. In IE7, screen is blank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (EMBJOPR-371) admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-371?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated EMBJOPR-371: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=795918, https://bugzilla.redhat.com/show_bug.cgi?id=751506 (was: https://bugzilla.redhat.com/show_bug.cgi?id=795918) > admin-console fails to load when unexploded EAR containing an EJB module JAR exists in the deploy directory > ----------------------------------------------------------------------------------------------------------- > > Key: EMBJOPR-371 > URL: https://issues.jboss.org/browse/EMBJOPR-371 > Project: Embedded Jopr > Issue Type: Bug > Affects Versions: 1.3.4.SP5 > Reporter: Larry O'Leary > Fix For: 1.3.4.SP6 > > > When an EAP instance has an EAR deployed to it which contains an EJB module JAR and the EAR is in an unexploded form (archived), attempting to access the admin-console results in the following exception: > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/admin-console]] (http-0.0.0.0-8080-1) Exception sending request initialized lifecycle event to listener instance of class org.jboss.on.embedded.LazyStartupListener > java.lang.RuntimeException: Error handling file /opt/jboss/jboss-eap-5.1/jboss-as/server/production/deploy/exolgan-legacy-ejb.ear/exolgan-legacy-ejb.jar > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:134) > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) > at org.jboss.seam.init.Initialization.create(Initialization.java:130) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) > at org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182) > at org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:180) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) > at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) > at java.lang.Thread.run(Thread.java:636) > Caused by: java.util.zip.ZipException: error in opening zip file > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:131) > at java.util.zip.ZipFile.<init>(ZipFile.java:148) > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) > ... 21 more > The issue can be resolved by adding the following files to admin-console.war/META-INF/ > Empty File (seam.properties) > seam-deployment.properties: > org.jboss.seam.deployment.scanners=org.jboss.seam.integration.jbossas.vfs.VFSScanner -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues July 2012