[JBoss JIRA] Created: (JBAS-8955) Injection of a WebServiceContext in an Interceptor fails when deployed.
by Peer Bech Hansen (JIRA)
Injection of a WebServiceContext in an Interceptor fails when deployed.
-----------------------------------------------------------------------
Key: JBAS-8955
URL: https://issues.jboss.org/browse/JBAS-8955
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.1.0.GA
Environment: Windows 7 US, JDK 1.6.22
Reporter: Peer Bech Hansen
Assignee: Carlo de Wolf
Fix For: 6.0.0.Final
http://community.jboss.org/message/589104
public class WebserviceLogInterceptor {
@Resource
private WebServiceContext wsc;
@AroundInvoke
public Object logCall(InvocationContext context) throws Exception {
try {
return context.proceed();
} catch (Exception e) {
throw e;
}
}
}
org.jboss.deployers.spi.DeploymentException: Error deploying Project-1.0-SNAPSHOT.jar: Exception while processing container metadata for EJB: DemoService in unit: Project-1.0-SNAPSHOT.jar
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:196)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:99)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.Exception: Exception while processing container metadata for EJB: DemoService in unit: Project-1.0-SNAPSHOT.jar
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:549)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189)
... 29 more
Caused by: java.lang.ArrayStoreException: org.jboss.injection.WebServiceContextPropertyInjector
at java.util.AbstractCollection.toArray(AbstractCollection.java:171)
at org.jboss.ejb3.interceptor.InterceptorInjector.(InterceptorInjector.java:42)
at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:610)
at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:418)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:527)
... 30 more
18:01:38,527 WARN Re: Bug: injecting WebServiceContext at AroundInvoke Failed to process changes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBRULES-2853) ResourceFactory.newClassPathResource(drlPath) behaves differently on different platforms (linux, windows): it parses the file with different encodings
by Geoffrey De Smet (JIRA)
ResourceFactory.newClassPathResource(drlPath) behaves differently on different platforms (linux, windows): it parses the file with different encodings
------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-2853
URL: https://issues.jboss.org/browse/JBRULES-2853
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Assignee: Mark Proctor
Priority: Critical
This really sucks for non English people :) English people write in pure ASCII, so they don't suffer from this problem.
French, Dutch etc mix in Latin-1 chars. Russian, Chinese use something else.
The root problem: There are 2 ways to create an InputStream:
- with encoding = GOOD, use encoding "UTF-8" and there are no problems.
- without encoding: use the default platform encoding = BAD
-- Linux: UTF-8, Windows in Belgium: Latin-1, Windows in China: Chinese-1, Windows in Sweden: Latin-2, ...
-- Java's InputStream should have just defaulted it on UTF-8
Proposition 1: Overloaded method which has an extra String encoding:
- ResourceFactory.newClassPathResource(drlPath, encoding)
- similar tactic as InputStream
Proposition 2: Keep it simple. We decide what a DRL file is.
Just like an XML file says to hell with the specified encoding, so can we.
Note: All XML files default to UTF-8 encoding, and you can overwrite it in a header in the XML file itself (= self-describing): no need to mess around in the java code.
Same principle: All DRL files are default UTF-8 encoding. Optionally we can define an encoding header later.
I strongly prefer proposition 2. The world has got enough encoding problems.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on AS7-3042:
---------------------------------------
Yes that would be a more worthwhile change - at the moment that page is a static page and we only see if the redirect can happen AFTER they click the link.
It would be better if the URL for the console was calculated as that page was displayed and the link removed, the redundant intermediate step to actually generate a redirect could also be removed.
> IPv6: Invalid redirect to Admin console (wrong IP address)
> ----------------------------------------------------------
>
> Key: AS7-3042
> URL: https://issues.jboss.org/browse/AS7-3042
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Darran Lofthouse
> Fix For: Open To Community
>
>
> This issue is some derivation from AS7-3040. Lets imagine starting server like this:
> {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code}
> So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990.
> This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1).
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)
by Jan Martiska (JIRA)
[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ]
Jan Martiska commented on AS7-3042:
-----------------------------------
In that case, why is the link to the admin console displayed on the welcome page at all, if it is not supposed to work at all times? In that case, the link should be removed completely.
> IPv6: Invalid redirect to Admin console (wrong IP address)
> ----------------------------------------------------------
>
> Key: AS7-3042
> URL: https://issues.jboss.org/browse/AS7-3042
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Darran Lofthouse
> Fix For: Open To Community
>
>
> This issue is some derivation from AS7-3040. Lets imagine starting server like this:
> {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code}
> So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990.
> This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1).
--
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
14 years, 2 months
[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on AS7-3042:
---------------------------------------
Is it really the correct URL that should be shared publicly? How do you know that the user that has connected through a firewall or reverse proxy can or even should be connecting to that address?
Whilst in your scenario that redirect would work there are plenty that will not and should not work.
> IPv6: Invalid redirect to Admin console (wrong IP address)
> ----------------------------------------------------------
>
> Key: AS7-3042
> URL: https://issues.jboss.org/browse/AS7-3042
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, Web
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Darran Lofthouse
> Fix For: Open To Community
>
>
> This issue is some derivation from AS7-3040. Lets imagine starting server like this:
> {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code}
> So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990.
> This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1).
--
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
14 years, 2 months