[JBoss Tools] - How to enable JBoss Tools content assist for JSF xhtml files
by Florian Minjat
Florian Minjat [http://community.jboss.org/people/wInddnIw] created the discussion
"How to enable JBoss Tools content assist for JSF xhtml files"
To view the discussion, visit: http://community.jboss.org/message/539247#539247
--------------------------------------------------------------
Hi,
I'm using IBM RAD 7.5 (based on eclipse 3.4.1) to develop JSF+Facelets+Richfaces applications.
I wanted to have the content assist for the xhtml JSF pages. I managed to do so using JSP Editor, adding jsp:root on every xhtml file and storing tlds in the WEB-INF folder, but it isn't very clean nor easy to add on an already existing project...
I saw that JBoss tools provides content assist, so I installed the "JBoss Tools RichFaces feature" from JBossTools-3.0.3.GA.zip. It installed without any errors, and I have new items for my WEB projects to "Add JSF capabilities..." and I can open the xhtml pages with JBoss Tools XML editor or JBoss Tools JSP editor. I didn't change anything nor used any wizard from JBoss Tools as my project are already working well and I don't want to change there configuration. But I still don't have any content assist in my JSF xhtml files, even with those. I still get the same error than without the JBoss Tools installed: "<ui:composition> has no known child tags".
I couln't find any documentation of forum discution on how to enable the content assist feature using JBoss Tools. Am I missing something or is it impossible ?
Regards,
Florian
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/539247#539247]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Microcontainer Development] - ClassPool bootstrap refactoring
by Kabir Khan
Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] created the discussion
"ClassPool bootstrap refactoring"
To view the discussion, visit: http://community.jboss.org/message/539242#539242
--------------------------------------------------------------
Following on from http://community.jboss.org/message/539041#539041 http://community.jboss.org/message/539041#539041 I have started refactoring how the ClassPools are initialized during bootstrap and moving code into the classpools project. The following (uncommitted, but working) test in ClassPools demonstrates how I see this working in the bootstrap.
/**
* Simulates the steps to be taken during AS bootstrap
*/
public void testBootstrap() throws Exception
{
//Initialize the config. This wires together the parts of the system
JBossClClassPoolConfig config = JBossClClassPoolConfig.getInstance();
assertNotNull(config.getClassPoolFactory());
assertNotNull(config.getClassPoolRepository());
assertNotNull(config.getDomainRegistry());
assertNotNull(config.getRegisterModuleCallback());
assertNull(config.getClassLoading());
//Check that the classpool factory works before we have deployed the classpool system
ClassLoader urlCl = createChildURLLoader(null, JAR_A_URL);
ClassPool urlPool = config.getClassPoolRepository().registerClassLoader(urlCl);
assertNotNull(urlPool);
CtClass aUrl = urlPool.get(CLASS_A);
CtClass stringUrl = urlPool.get(String.class.getName());
//Install the bean to get notified when ClassLoading is installed
BeanMetaDataBuilder builder = BeanMetaDataBuilder.createBuilder("JBossClClassPoolConfig", JBossClClassPoolConfig.class.getName());
builder.setFactoryClass(JBossClClassPoolConfig.class.getName());
builder.setFactoryMethod("getInstance");
ValueMetaData inject = builder.createContextualInject(null, null, AutowireType.BY_NAME, InjectOption.CALLBACK);
((AbstractInjectionValueMetaData)inject).setValue("ClassLoading");
builder.addPropertyMetaData("classLoading", inject);
getDelegate().deploy(builder.getBeanMetaData());
//Deploy the ClassLoading. This causes the RegistryModuleCallback
//to get installed as a module registry in ClassLoading
getDelegate().deployCommon();
assertNotNull(config.getClassLoading());
testScenario = new ClassPoolTestScenario<CLDeploymentBuilder>(getClassLoaderFactory(), config.getClassPoolRepository());
ClassPool poolA = testScenario.createLoader(new CLDeploymentBuilder("A", JAR_A_URL));
CtClass aDomain = poolA.get(CLASS_A);
assertNotSame(aUrl, aDomain);
assertSame(stringUrl, poolA.get(String.class.getName()));
ClassPool poolB = testScenario.createLoader(new CLDeploymentBuilder("B", JAR_B_URL));
assertSame(aDomain, poolB.get(CLASS_A));
}
The JBossClClassPoolConfig singleton wires together a lot of the things that are needed for running this in AS (getters ommitted)
public class JBossClClassPoolConfig
{
private static volatile JBossClClassPoolConfig config;
private final DomainRegistry domainRegistry;
private final RegisterModuleCallback registerModuleCallback;
private ClassLoading classLoading;
private JBossClDelegatingClassPoolFactory classPoolFactory;
private ClassPoolRepository classPoolRepository;
private JBossClClassPoolConfig(DomainRegistry domainRegistry, RegisterModuleCallback registerModuleCallback, JBossClDelegatingClassPoolFactory classPoolFactory)
{
this.domainRegistry = domainRegistry;
this.registerModuleCallback = registerModuleCallback;
this.classPoolFactory = classPoolFactory;
classPoolRepository = ClassPoolRepository.getInstance();
classPoolRepository.setClassPoolFactory(classPoolFactory);
}
public static JBossClClassPoolConfig getInstance()
{
if (config == null)
{
config = initialize();
}
return config;
}
private synchronized static JBossClClassPoolConfig initialize()
{
if (config != null)
return config;
DomainRegistry domainRegistry = new VFSClassLoaderDomainRegistry();
RegisterModuleCallback registerModuleCallback = new RegisterModuleCallback(domainRegistry);
JBossClDelegatingClassPoolFactory classPoolFactory = new JBossClDelegatingClassPoolFactory(domainRegistry, registerModuleCallback);
return new JBossClClassPoolConfig(domainRegistry, registerModuleCallback, classPoolFactory);
}
/**
* Set the classLoading. This should be set via a property
* by the MC
*
* @param cl the classLoading to set
*/
public void setClassLoading(ClassLoading cl)
{
if (cl != null)
cl.addModuleRegistry(registerModuleCallback);
else if (classLoading != null)
classLoading.removeModuleRegistry(registerModuleCallback);
classLoading = cl;
}
}
So basically all the AS bootstrap will need to do is to call JBossClClassPoolConfig.getInstance() to initialize the classpool parts, and then deploy the JBossClClassPoolConfig bean whose purpose is to add the RegisterModuleCallback as a module registry in ClassLoading once that is deployed.
With this in place and with a few small changes to how the aop classes work, what is in bootstrap/aop.xml will reuse things from JBossClClassPoolConfig where appropriate.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/539242#539242]
Start a new discussion in JBoss Microcontainer Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [jBPM] - JBPM 4.3 - org.jbpm.api.JbpmException: couldn't acquire block of ids
by Stefano Campanini
Stefano Campanini [http://community.jboss.org/people/campa] replied to the discussion
"JBPM 4.3 - org.jbpm.api.JbpmException: couldn't acquire block of ids"
To view the discussion, visit: http://community.jboss.org/message/539241#539241
--------------------------------------------------------------
It seems solved, changing my jbpm.cfg.xml to :
<jbpm-configuration spring="enabled">
<process-engine-context>
<repository-service />
<!-- <repository-cache /> -->
<object class="org.jbpm.pvm.internal.repository.RepositoryCacheImpl" />
<execution-service />
<history-service />
<management-service />
<identity-service />
<task-service />
<types resource="jbpm.variable.types.xml" />
<command-service name="newTxRequiredCommandService">
<retry-interceptor />
<environment-interceptor policy="requiresNew" />
<spring-transaction-interceptor policy="requiresNew" />
</command-service>
<!-- Default command service has a Spring transaction interceptor-->
<command-service name="txRequiredCommandService">
<retry-interceptor />
<environment-interceptor />
<spring-transaction-interceptor />
</command-service>
<deployer-manager>
<jpdl-deployer />
<object class="org.jbpm.pvm.internal.repository.RulesDeployer" />
</deployer-manager>
</process-engine-context>
<transaction-context>
<transaction type="spring" />
<hibernate-session current="true" />
<repository-session />
<db-session />
</transaction-context>
</jbpm-configuration>
Thanks guys for the support !!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/539241#539241]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years