[JBoss JIRA] (AS7-6196) Resolver environment may cache stale package capability
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-6196:
-----------------------------------
Summary: Resolver environment may cache stale package capability
Key: AS7-6196
URL: https://issues.jboss.org/browse/AS7-6196
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
The XEnvironment may incorrectly cache capabilities from already uninstalled bundles. This happens when the resolve attempt uses generic requirements with no namespace value.
--
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-6195) OSGi JPA integration does not export org.osgi.service.jpa
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-6195:
-----------------------------------
Summary: OSGi JPA integration does not export org.osgi.service.jpa
Key: AS7-6195
URL: https://issues.jboss.org/browse/AS7-6195
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
The JPA integration should contain and export the [org.osgi.service.jpa |http://www.osgi.org/javadoc/r4v42/org/osgi/service/jpa/package-summary.html] API
--
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-6194) Framework doe not consistently log ResolutionException
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-6194:
-----------------------------------
Summary: Framework doe not consistently log ResolutionException
Key: AS7-6194
URL: https://issues.jboss.org/browse/AS7-6194
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
When invoked implicitly as part of Bundle.start() they framework may not log a potential ResolutionException. This makes it hard to figure out why the Bundle could not get started
--
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-6169) CLI does not work on windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6169?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar resolved AS7-6169.
------------------------------
Resolution: Done
was fixed by upgrading ash to 0.27
> CLI does not work on windows
> ----------------------------
>
> Key: AS7-6169
> URL: https://issues.jboss.org/browse/AS7-6169
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, Windows 8, Windows Server 2008r2
> Reporter: Tomaz Cerar
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: cli, windows
> Fix For: 7.2.0.Alpha1
>
>
> Typing in CLI crashes with error below after any character is entered
> {noformat}
> [standalone@localhost:9999 /] ajava.lang.ArithmeticException: / by zero
> at org.jboss.aesh.console.Console.writeChar(Console.java:752)
> at org.jboss.aesh.console.Console.writeChars(Console.java:735)
> at org.jboss.aesh.console.Console.parseOperation(Console.java:432)
> at org.jboss.aesh.console.Console.read(Console.java:377)
> at org.jboss.aesh.console.Console.read(Console.java:331)
> at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171)
> at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1167)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> 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:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:294)
> {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-6186) Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations
by Marek Schmidt (JIRA)
[ https://issues.jboss.org/browse/AS7-6186?page=com.atlassian.jira.plugin.s... ]
Marek Schmidt updated AS7-6186:
-------------------------------
Attachment: AS7-6186-viewMap.war
(attaching reproducer of one of the Seam problems with Mojarra 2.1.16 with no Seam in it)
> Mojarra 2.1.16 upgrade breaks Seam2.3.0 conversations
> -----------------------------------------------------
>
> Key: AS7-6186
> URL: https://issues.jboss.org/browse/AS7-6186
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: 7.1.4.Final (EAP)
> Environment: Current 7.1.4.Final-SNAPSHOT (2012-12-15), Mojarra 2.1.16, Seam2.3.0.Final
> Reporter: Marek Schmidt
> Assignee: Stan Silvert
> Priority: Critical
> Attachments: AS7-6186-viewMap.war, seam-booking.ear
>
>
> Recent Mojarra upgrade seems to break Seam 2.3.0 conversations.
> Not exactly sure yet what has changed and whether it is a Mojarra bug or Seam depending on something it shouldn't.
--
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