July 2012 - embjopr-issues - Jboss List Archives

[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 commented on EMBJOPR-372: ------------------------------------------------- Stefan Negrea <snegrea(a)redhat.com> changed the Status of [bug 797012|https://bugzilla.redhat.com/show_bug.cgi?id=797012] from MODIFIED to ON_DEV > 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-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 reassigned EMBJOPR-373: ------------------------------------- Assignee: Stefan Negrea (was: Larry O'Leary) > 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.SP5 > Reporter: Larry O'Leary > Assignee: Stefan Negrea > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > 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-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 resolved EMBJOPR-374. ----------------------------------- Resolution: Done As per upstream RHQ project bug 791142 this has been committed and will be in 1.3.4.SP6 build: https://bugzilla.redhat.com/show_bug.cgi?id=791142#c2 Cherry-picked fixes for 743437 to AdminConsole_EAP_5_1 branch: http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commitdiff;h=40ba441 http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commitdiff;h=8e861e4 > 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: Stefan Negrea > 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-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 reassigned EMBJOPR-374: ------------------------------------- Assignee: Stefan Negrea (was: Larry O'Leary) > 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: Stefan Negrea > 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-366) Updating farmed EAR/WAR fails and un-farms app with error @Out attribute requires non-null value: updateBackingContentAction.packageType

by Larry O'Leary (JIRA)

Larry O'Leary created EMBJOPR-366: ------------------------------------- Summary: Updating farmed EAR/WAR fails and un-farms app with error @Out attribute requires non-null value: updateBackingContentAction.packageType Key: EMBJOPR-366 URL: https://issues.jboss.org/browse/EMBJOPR-366 Project: Embedded Jopr Issue Type: Bug Components: Plugin Affects Versions: 1.3.4 Environment: JBoss EAP 5.1.0 admin-console (1.3.4 SP1) Reporter: Larry O'Leary Fix For: 1.3.4 When attempting to update a deployed application (EAR/WAR) which has been deployed in the farm directory, the original application is removed from farm and the new version is deployed to the deploy directory and the following exception is being displayed in the UI: javax.el.ELException: org.jboss.seam.RequiredException: @Out attribute requires non-null value: updateBackingContentAction.packageType at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:339) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:280) at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59) at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:175) at org.jboss.seam.navigation.Page.preRender(Page.java:311) at org.jboss.seam.navigation.Pages.preRender(Pages.java:351) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:561) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:472) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:148) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:118) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:86) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:295) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:373) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:500) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 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:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) at java.lang.Thread.run(Thread.java:636) Caused by:org.jboss.seam.RequiredException: @Out attribute requires non-null value: updateBackingContentAction.packageType at org.jboss.seam.Component.outjectAttribute(Component.java:1767) at org.jboss.seam.Component.outjectAttributes(Component.java:1758) at org.jboss.seam.Component.outject(Component.java:1611) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:86) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:185) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:103) at org.jboss.on.embedded.ui.content.UpdateBackingContentAction_$$_javassist_seam_16.init(UpdateBackingContentAction_$$_javassist_seam_16.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:335) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:280) at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59) at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:175) at org.jboss.seam.navigation.Page.preRender(Page.java:311) at org.jboss.seam.navigation.Pages.preRender(Pages.java:351) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:561) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:472) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:148) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:118) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:86) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:295) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:373) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:500) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 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:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) at java.lang.Thread.run(Thread.java:636) The result is the application is un-deployed or removed from all nodes of the cluster and the new version is only being deployed to the single node. Additionally, the error displayed to the user is unexpected. -- 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

4
37
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 Larry O'Leary (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-371?page=com.atlassian.jira.plugi... ] Larry O'Leary reassigned EMBJOPR-371: ------------------------------------- Assignee: Stefan Negrea > 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 > Assignee: Stefan Negrea > 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

[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 updated EMBJOPR-373: ---------------------------------- Fix Version/s: 1.3.4.SP6 (was: 1.3.4.SP5) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=834360 (was: https://bugzilla.redhat.com/show_bug.cgi?id=834360) Affects Version/s: 1.3.4.SP5 (was: 1.3.4.SP6) > 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.SP5 > Reporter: Larry O'Leary > Assignee: Larry O'Leary > Labels: admin-console, jopr > Fix For: 1.3.4.SP6 > > > 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-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 commented on EMBJOPR-374: --------------------------------------- This was fixed in upstream RHQ project as part of https://bugzilla.redhat.com/show_bug.cgi?id=743437 and will be included in EmbJopr_1_3_4_SP6. > 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-374) MySQL datasource type mapping should be present

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-374?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated EMBJOPR-374: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=791142 (was: https://bugzilla.redhat.com/show_bug.cgi?id=791142) > 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-374) MySQL datasource type mapping should be present

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/EMBJOPR-374?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated EMBJOPR-374: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=791142 (was: https://bugzilla.redhat.com/show_bug.cgi?id=791142) > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues July 2012