[JBoss JIRA] (AS7-5738) JNDI View doesn't work in domain mode
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-5738?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-5738:
-----------------------------
Issue Type: Bug (was: Feature Request)
> JNDI View doesn't work in domain mode
> --------------------------------------
>
> Key: AS7-5738
> URL: https://issues.jboss.org/browse/AS7-5738
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Fix For: 7.2.0.CR1
>
>
> Yields an exception on the server side:
> {noformat}
> [Server:server-one] Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.ManagementHome from [Module "org.jboss.as.naming:main" from local module loader @e49d67c (roots: /Users/hbraun/dev/prj/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)]
> [Server:server-one] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.3.GA]
> [Server:server-one] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5795) The Add/Remove buttons should always be placed in a consistent place on the pages.
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-5795?page=com.atlassian.jira.plugin.s... ]
Heiko Braun resolved AS7-5795.
------------------------------
Resolution: Done
> The Add/Remove buttons should always be placed in a consistent place on the pages.
> ----------------------------------------------------------------------------------
>
> Key: AS7-5795
> URL: https://issues.jboss.org/browse/AS7-5795
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console
> Reporter: Heiko Braun
> Assignee: Heiko Braun
> Labels: uxp
> Fix For: 7.2.0.CR1
>
> Attachments: Screen Shot 2012-10-19 at 10.48.58 AM.png, Screen Shot 2012-10-19 at 10.48.58 AM.png
>
>
> The Add/Remove buttons should always be placed in a consistent place on the pages. On some pages they are top aligned to the page, and other pages they are placed directly above the table. They should always be placed directly above the table the add/re- move is relevant to.
> See JCA>Bootstrap contexts for instance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6152) Content repository view broken?
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-6152?page=com.atlassian.jira.plugin.s... ]
Heiko Braun commented on AS7-6152:
----------------------------------
{noformat}
java.lang.NullPointerException
at org.jboss.as.console.client.domain.groups.deployment.ContentRepositoryView$3.getValue(ContentRepositoryView.java:134)
at org.jboss.as.console.client.domain.groups.deployment.ContentRepositoryView$3.getValue(ContentRepositoryView.java:1)
at com.google.gwt.user.cellview.client.Column.render(Column.java:165)
at com.google.gwt.user.cellview.client.AbstractCellTableBuilder.renderCell(AbstractCellTableBuilder.java:206)
at com.google.gwt.user.cellview.client.DefaultCellTableBuilder.buildRowImpl(DefaultCellTableBuilder.java:129)
at com.google.gwt.user.cellview.client.AbstractCellTableBuilder.buildRow(AbstractCellTableBuilder.java:87)
at com.google.gwt.user.cellview.client.AbstractCellTable.buildRowValues(AbstractCellTable.java:2347)
at com.google.gwt.user.cellview.client.AbstractCellTable.replaceAllChildren(AbstractCellTable.java:2148)
at com.google.gwt.user.cellview.client.AbstractHasData$View.replaceAllChildren(AbstractHasData.java:245)
at com.google.gwt.user.cellview.client.HasDataPresenter.resolvePendingState(HasDataPresenter.java:1351)
at com.google.gwt.user.cellview.client.HasDataPresenter.access$3(HasDataPresenter.java:1062)
at com.google.gwt.user.cellview.client.HasDataPresenter$2.execute(HasDataPresenter.java:984)
at com.google.gwt.core.client.impl.SchedulerImpl$Task$.executeScheduled$(SchedulerImpl.java:50)
at com.google.gwt.core.client.impl.SchedulerImpl.runScheduledTasks(SchedulerImpl.java:228)
at com.google.gwt.core.client.impl.SchedulerImpl.flushFinallyCommands(SchedulerImpl.java:327)
at com.google.gwt.core.client.impl.Impl.exit(Impl.java:266)
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:257)
at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:293)
at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:547)
at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364)
at java.lang.Thread.run(Thread.java:680)
{noformat}
> Content repository view broken?
> -------------------------------
>
> Key: AS7-6152
> URL: https://issues.jboss.org/browse/AS7-6152
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console
> Reporter: Heiko Braun
> Assignee: Harald Pehl
> Fix For: 7.2.0.CR1
>
>
> Might relate to the snapshot, but it doesn't display the contents
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6113) WS *AddStepHandlers are ignoring rollback callback
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/AS7-6113?page=com.atlassian.jira.plugin.s... ]
Richard Opalka resolved AS7-6113.
---------------------------------
Assignee: Richard Opalka (was: Alessio Soldano)
Resolution: Done
> WS *AddStepHandlers are ignoring rollback callback
> --------------------------------------------------
>
> Key: AS7-6113
> URL: https://issues.jboss.org/browse/AS7-6113
> Project: Application Server 7
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1
> Reporter: Ivo Studensky
> Assignee: Richard Opalka
>
> Webservice handlers from org.jboss.as.webservices.dmr package do not handle rollback of the context.restart/reloadRequired() call.
> According to Brian's comment at [1] the handlers need something like this:
> {code}
> protected void rollbackRuntime(OperationContext context, final ModelNode operation, final ModelNode model, List> controllers) {
> super.rollbackRuntime(context, operation, model, List>);
> if (!context.isBooting()) {
> context.revertReloadRequired();
> }
> }
> {code}
> [1] https://github.com/jbossas/jboss-as/pull/3588
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months