[JBoss JIRA] Created: (JBCOMMON-38) Use URI instead of URL in FileProtocolArchiveBrowserFactory
by Davide Baroncelli (JIRA)
Use URI instead of URL in FileProtocolArchiveBrowserFactory
-----------------------------------------------------------
Key: JBCOMMON-38
URL: http://jira.jboss.com/jira/browse/JBCOMMON-38
Project: JBoss Common
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Davide Baroncelli
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: 2.2.2.GA
Current code in FileProtocolArchiveBrowserFactory has problems when the URL coming from above contains escaped characters. E.g.: In an app. I'm writing, the class receives an URL coming from a ClassLoader.getResources method: resources in directories containing square brackets arrive to the class in escaped URLs such as the following:
file:/C:/Stratosfera/pos_back/%5BCARCON%5Dstratosfera-verifica-cartoline-concorso/war/WEB-INF/classes/
this form fails in the current implementation because of line 40:
File f = new File(url.getPath());
this results in a non existing file. Replacing the line with the following solves the problem:
File f;
try {
f = new File(url.toURI());
}
catch ( URISyntaxException e ) {
throw new RuntimeException( e );
}
this problems creates various compatibility problems in depending libraries (hibernate entitymanager for one).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBAS-3773) Empty baseCtxDN and rolesCtxDN adds a comma to the userDn and user roles
by Eric van Lydegraf (JIRA)
Empty baseCtxDN and rolesCtxDN adds a comma to the userDn and user roles
------------------------------------------------------------------------
Key: JBAS-3773
URL: http://jira.jboss.com/jira/browse/JBAS-3773
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Eric van Lydegraf
Assigned To: Scott M Stark
The LDAP server (Lotus Domino) has users organized along different CtxDN contexts, so for JNDI empty contexts are used and the filter sorts out the users and groups.
When Using LoginExtLoginModule, a sucessful retrieval of a User, has a full userDN but the code will append a comma expecting BaseCtxDN used in the search.
The same is true for group membership.
The solution I came up with is if the context is empty, no Ctx is appended and only the search result is preserved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (EJBTHREE-1406) i have the same pb : Circular dependance with EJBs
by Nouredine Goutal (JIRA)
i have the same pb : Circular dependance with EJBs
--------------------------------------------------
Key: EJBTHREE-1406
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1406
Project: EJB 3.0
Issue Type: Sub-task
Affects Versions: AS 4.2.2.GA
Environment: windows XP
Reporter: Nouredine Goutal
I have asked the last time the problem of circular dependencies between EJB, there is someone who responded me and telling me to use the annotation @IgnoreDependency to one of the instance of Ejb injection.
it solves the problem by half:
I explain: when I use default injecting dependance with @EJB without specifying the name attribute, Jboss solve reference, in this case @ IgnoreDependency works well. By when I specifie the name of reference( @EJB(name="ejb/someEJB"...) that does not work.
example:
Hello1Bean classe :
@EJBs(
{ @EJB(name="ejb/Hello2", beanInterface=Hello2.class, beanName="Hello2Bean")
})
public @Stateless class Hello1Bean implements Hello1 {
@IgnoreDependency
@EJB(name="ejb/Hello2")
private Hello2 hello;
and Hello2Bean Classe :
@EJBs(
{@EJB(name="ejb/Hello1", beanInterface=Hello1.class,beanName="Hello1Bean")
})
public @Stateless class Hello2LocalBean implements Hello2Local {
@IgnoreDependency
@EJB(name="ejb/Hello1")
private Hello1 hello;
with this case , i Have this probleme :
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:jar=cyclic.jar,name=Hello2Bean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:jar=cyclic.jar,name=Hello1Bean,service=EJB3
Depends On Me:
jboss.j2ee:jar=cyclic.jar,name=Hello1Bean,service=EJB3
ObjectName: jboss.j2ee:jar=cyclic.jar,name=Hello1Bean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
jboss.j2ee:jar=cyclic.jar,name=Hello2Bean,service=EJB3
Depends On Me:
jboss.j2ee:jar=cyclic.jar,name=Hello2Bean,service=EJB3
if someone has a solution, I currently work on the migration of a real application, and I have a major problem for progress.
Thank's a lot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBDEPLOY-62) error in deploy sample application jsfejb3.ear (taken from jboss org) in jboss-5.0.0.CR1
by Vjacheslav Korshakov (JIRA)
error in deploy sample application jsfejb3.ear (taken from jboss org) in jboss-5.0.0.CR1
----------------------------------------------------------------------------------------
Key: JBDEPLOY-62
URL: https://jira.jboss.org/jira/browse/JBDEPLOY-62
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Environment: Windows XP, JAVA JDK-1.5
Reporter: Vjacheslav Korshakov
2008-07-22 15:27:47,989 DEBUG [org.jboss.ejb3.deployers.PersistenceUnitParsingDeployer] (main) Error during deploy: vfszip:/C:/jboss-5.0.0.CR1/server/default/deploy/jsfejb3.ear/app.jar
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/jboss-5.0.0.CR1/server/default/deploy/jsfejb3.ear/app.jar
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1023)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:257)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:135)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:544)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=persistence
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:198)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329)
... 22 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=persistence
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:309)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 29 more
2008-07-22 15:27:47,989 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Parse: name=vfszip:/C:/jboss-5.0.0.CR1/server/default/deploy/jsfejb3.ear state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/jboss-5.0.0.CR1/server/default/deploy/jsfejb3.ear/app.jar
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1023)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:257)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:135)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:544)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=persistence
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:198)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329)
... 22 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=persistence
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:309)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 29 more
2008-07-22 15:27:48,036 DEBUG [org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper] (main) Parsing file: FileHandler(a)2417567[path=jbossws-container-beans.xml context=file:/C:/jboss-5.0.0.CR1/server/default/deploy/ real=file:/C:/jboss-5.0.0.CR1/server/default/deploy/jbossws-container-beans.xml] for type: interface org.jboss.kernel.spi.deployment.KernelDeployment
2008-07-22 15:27:48,036 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) Created parser: org.apache.xerces.jaxp.SAXParserImpl@1dc0d09, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBAS-4504) Container does not report invalid named query exception
by Radim Marek (JIRA)
Container does not report invalid named query exception
--------------------------------------------------------
Key: JBAS-4504
URL: http://jira.jboss.com/jira/browse/JBAS-4504
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.0.5.GA
Environment: java 5 update 11; jboss 4.0.5 GA
Reporter: Radim Marek
Assigned To: Carlo de Wolf
Priority: Minor
When entity manager is called to create non-existing named query (for example because of mistyping), container doesn't throw a persistence exception.
Code
Query query = entityManager.createNamedQuery("MarketingBatch.getBatches");
had been called from remote client and exception had appeared only on client as ClassNotFound: org.hibernate.MappingException. Other problems with named query are reported as expected.
I thought all exception not handled by session bean should be reported. It would be at least convenient.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBREFLECT-38) ValueConvertor.convertValue is swallowing too many exceptions
by Scott M Stark (JIRA)
ValueConvertor.convertValue is swallowing too many exceptions
-------------------------------------------------------------
Key: JBREFLECT-38
URL: https://jira.jboss.org/jira/browse/JBREFLECT-38
Project: JBoss Reflection
Issue Type: Bug
Reporter: Scott M Stark
ValueConvertor.convertValue(Class<Object>, Object, boolean, boolean) is swallowing too many exceptions. A bean like:
<bean name="JndiBindings" class="org.jboss.naming.BindingsInitializer">
<property name="ctx">
<inject bean="InitialContextFactory" property="ctx"/>
</property>
<property name="bindings">
<map keyClass="java.lang.String">
<entry>
<key>ints/1</key>
<value class="java.lang.Integer">1</value>
</entry>
<entry>
<key>strings/1</key>
<value class="java.lang.String">String1</value>
</entry>
<entry>
<key>bigint/1</key>
<value class="java.math.BigInteger">12345.6789</value>
</entry>
</map>
</property>
</bean>
Incorrectly creates a String value for the bigint/1 entry because the attempt to call BigInteger("12345.6789") fails with
an java.lang.reflect.InvocationTargetException/java.lang.NumberFormatException: For input string: "2345.6789"
in ReflectionUtils.newInstance(Constructor<?>, Object[]) line: 153
We need to look at differentiating between failures.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month