[JBoss JIRA] Created: (JBMICROCONT-184) Parsing more than one file
by Adrian Brock (JIRA)
Parsing more than one file
--------------------------
Key: JBMICROCONT-184
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-184
Project: JBoss MicroContainer
Issue Type: Task
Components: Deployment
Reporter: Adrian Brock
Fix For: JBossMC_2_0_0_CR1
The AbstractVFSParser has the following limitiation:
@Override
protected T parse(DeploymentUnit unit, String name, String suffix, T root) throws Exception
{
// Should we include the deployment
// The infrastructure will only check leafs anyway so no need to check here
if (name == null && isIncludeDeploymentFile())
name = unit.getName();
// Try to find the metadata
VFSDeploymentUnit vfsDeploymentUnit = (VFSDeploymentUnit) unit;
List<VirtualFile> files = vfsDeploymentUnit.getMetaDataFiles(name, suffix);
if (files.size() == 0)
return null;
// TODO remove this limitation
if (files.size() > 1)
throw new DeploymentException("Only one file is allowed, found=" + files);
VirtualFile file = files.get(0);
This is really also related to the "reparse" that is done for ejb-jar.xml/jboss.xml and [jboss-]web.xml
There should be parsing deployers that know how to parse multiple files into one object model.
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBAS-4189) @EJB doesn't work inside a servlet
by Juergen Zimmermann (JIRA)
@EJB doesn't work inside a servlet
----------------------------------
Key: JBAS-4189
URL: http://jira.jboss.com/jira/browse/JBAS-4189
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBossAS 4.2.0CR1, JDK 5.0_11, WinXP SP2, Eclipse WTP 1.5.3
Reporter: Juergen Zimmermann
Assigned To: Bill Burke
When a servlet tries to invoke a proxa referencing a stateless session bean I get a null pointer.
1) Stateless session bean:
@Stateless
@Local(EjbRefLocal.class)
public class EjbRefBean implements EjbRefLocal {
public String foo() {
return "ok";
}
}
2) Local interface
public interface EjbRefLocal {
String foo();
}
3) Servlet
public class MyServlet extends HttpServlet {
@EJB
private EjbRefLocal proxy;
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
final String result = proxy.foo();
System.out.println("RESULT = " + result);
}
}
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBRULES-1234) "mvn -Psolver clean install" results in 77 test errors. However, skipping tests apparently does result in a functional solver build.
by Martin S (JIRA)
"mvn -Psolver clean install" results in 77 test errors. However, skipping tests apparently does result in a functional solver build.
------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-1234
URL: http://jira.jboss.com/jira/browse/JBRULES-1234
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Solver
Affects Versions: 4.0.2
Environment: I am using maven 2.0.7, Java 1.6.0_02 on a single core XP3000+ Ubuntu Feisty Linux machine with 2GB of RAM.
Reporter: Martin S
Assigned To: Mark Proctor
"mvn -Psolver clean install" results in 77 test errors. However, skipping tests (mvn clean install -Psolver -Dmaven.test.skip) apparently does result in a functional solver build and seemingly working demos.
To produce the test failures I Checked out version Checked out revision 15451 by:
"svn checkout http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/ drools"
Then I attempted a build by: "mvn -Psolver clean install", resulting in:
Tests run: 17, Failures: 0, Errors: 17, Skipped: 0, Time elapsed: 81.56 sec <<< FAILURE!
Results :
Tests in error:
testListPackages(org.drools.repository.PackageItemTest)
testRulePackageItem(org.drools.repository.PackageItemTest)
testPackageCopy(org.drools.repository.PackageItemTest)
testPackageSnapshot(org.drools.repository.PackageItemTest)
testLoadRulePackageItem(org.drools.repository.PackageItemTest)
testPackageRuleVersionExtraction(org.drools.repository.PackageItemTest)
testIgnoreState(org.drools.repository.PackageItemTest)
testDuplicatePackageName(org.drools.repository.PackageItemTest)
testPackageInstanceWrongNodeType(org.drools.repository.PackageItemTest)
testLoadRulePackageItemByUUID(org.drools.repository.PackageItemTest)
testAddRuleRuleItem(org.drools.repository.PackageItemTest)
testGetRules(org.drools.repository.PackageItemTest)
testToString(org.drools.repository.PackageItemTest)
testRemoveRule(org.drools.repository.PackageItemTest)
testSearchByFormat(org.drools.repository.PackageItemTest)
testListArchivedAssets(org.drools.repository.PackageItemTest)
testMiscProperties(org.drools.repository.PackageItemTest)
testGetFormat(org.drools.repository.PackageItemTest)
testPackageCheckinConfig(org.drools.repository.PackageItemTest)
testTagItem(org.drools.repository.CategoryItemTest)
testCreateCateories(org.drools.repository.CategoryItemTest)
testGetChildTags(org.drools.repository.CategoryItemTest)
testGetChildTag(org.drools.repository.CategoryItemTest)
testGetFullPath(org.drools.repository.CategoryItemTest)
testRemoveCategoryUneeded(org.drools.repository.CategoryItemTest)
testFindArchivedAssets(org.drools.repository.ArchiveItemTest)
testArchiveBooleanFlag(org.drools.repository.ArchiveItemTest)
testLoadArchivedAsset(org.drools.repository.ArchiveItemTest)
testFindArchivedAssetsByCategory(org.drools.repository.ArchiveItemTest)
testLoadPackages(org.drools.repository.ArchiveItemTest)
testFindRulesByNameArchived(org.drools.repository.ArchiveItemTest)
testToString(org.drools.repository.AssetItemTest)
testGetFormat(org.drools.repository.AssetItemTest)
testAssetItemCreation(org.drools.repository.AssetItemTest)
testGetPackageItem(org.drools.repository.AssetItemTest)
testGetContent(org.drools.repository.AssetItemTest)
testUpdateContent(org.drools.repository.AssetItemTest)
testCategories(org.drools.repository.AssetItemTest)
testUpdateCategories(org.drools.repository.AssetItemTest)
testFindRulesByCategory(org.drools.repository.AssetItemTest)
testRemoveTag(org.drools.repository.AssetItemTest)
testGetTags(org.drools.repository.AssetItemTest)
testSetStateString(org.drools.repository.AssetItemTest)
testStatusStuff(org.drools.repository.AssetItemTest)
testGetLastModifiedOnCheckin(org.drools.repository.AssetItemTest)
testGetDateEffective(org.drools.repository.AssetItemTest)
testGetDateExpired(org.drools.repository.AssetItemTest)
testSaveAndCheckinDescriptionAndTitle(org.drools.repository.AssetItemTest)
testGetPrecedingVersionAndRestore(org.drools.repository.AssetItemTest)
testGetSucceedingVersion(org.drools.repository.AssetItemTest)
testGetSuccessorVersionsIterator(org.drools.repository.AssetItemTest)
testGetPredecessorVersionsIterator(org.drools.repository.AssetItemTest)
testHistoryIterator(org.drools.repository.AssetItemTest)
testGetTitle(org.drools.repository.AssetItemTest)
testDublinCoreProperties(org.drools.repository.AssetItemTest)
testAnonymousProperties(org.drools.repository.AssetItemTest)
testBinaryAsset(org.drools.repository.AssetItemTest)
testAddDirectories(org.drools.scm.jcr.JcrActionFactoryTest)
testAddFiles(org.drools.scm.jcr.JcrActionFactoryTest)
testUpdateFiles(org.drools.scm.jcr.JcrActionFactoryTest)
testDefaultPackage(org.drools.repository.RulesRepositoryTest)
testAddVersionARule(org.drools.repository.RulesRepositoryTest)
testFindRulesByName(org.drools.repository.RulesRepositoryTest)
testLoadRuleByUUIDWithConcurrentSessions(org.drools.repository.RulesRepositoryTest)
testAddRuleCalendarWithDates(org.drools.repository.RulesRepositoryTest)
testGetState(org.drools.repository.RulesRepositoryTest)
testGetTag(org.drools.repository.RulesRepositoryTest)
testListPackages(org.drools.repository.RulesRepositoryTest)
testCategoriesAndSnapshots(org.drools.repository.RulesRepositoryTest)
testMoveRulePackage(org.drools.repository.RulesRepositoryTest)
testCopyAsset(org.drools.repository.RulesRepositoryTest)
testRenameAsset(org.drools.repository.RulesRepositoryTest)
testRenamePackage(org.drools.repository.RulesRepositoryTest)
testCopyPackage(org.drools.repository.RulesRepositoryTest)
testListStates(org.drools.repository.RulesRepositoryTest)
testImportExport(org.drools.repository.RulesRepositoryTest)
testExportZippedRepository(org.drools.repository.RulesRepositoryTest)
Tests run: 104, Failures: 0, Errors: 77, Skipped: 0
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBRULES-1319) debug junit test as drools application without requiring main function on junit test class
by John Franey (JIRA)
debug junit test as drools application without requiring main function on junit test class
------------------------------------------------------------------------------------------
Key: JBRULES-1319
URL: http://jira.jboss.com/jira/browse/JBRULES-1319
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Affects Versions: 4.0.3
Environment: eclipse 3.3 x64, jrockit 6 x64, ubuntu linux 7.10 (gutsy gibbon)
Reporter: John Franey
Priority: Optional
It is not necessary to write main methods for junit test classes. Eclipse can run, debug or profile a 'main-less' junit test simply by right clicking on a junit test class in the package browser, selecting 'run as', 'debug as' or 'profile as' -> junit test. In general, main methods are not part of junit test classes. Even when run from command line, junit tests are not required to have main methods.
'Debug as drools application' is the only action in eclipse that lets me debug drools rules. 'Debug as drools application' is available only on java classes with main methods. Junit classes generally do not have main methods.
I would like to debug drools rules that a junit test is testing. In order to do so, I have to write a main method for the junit test case. Very easy to write, but I don't think it should be necessary.
Regards,
--
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
16 years, 10 months