Community
Participate
Working Groups
When searching for usages from Java properties editor (F3 or ctrl-click) it doesn't find property references used inside JavaDoc comments. Such properties are often used for JavaDoc-based annotations (e.g. with QDox or XDoclet tools) and it will be a good idea to see those references in the search results.
Can you give an example? The current support only covers NLS properties.
Ok. I have dozen of projects that has project.properties at the project root directory where we define all substitution variables (e.g. EJB pool sizes, JDNI names, etc). Our build is using XDoclet (btw, it is the same metadata generator as used by Eclipse WTP) and you can write something like this: /** * Mdb1Bean * * @ejb.bean * name="Mdb1Bean" * type="MDB" * destination-type="javax.jms.Queue" * transaction-type="Container" * * @ejb.transaction type="Required" * * @weblogic.transaction-descriptor * trans-timeout-seconds="${javatx.tx.timeout}" * * @weblogic.message-driven * initial-context-factory="${javatx.mdb1.icf}" * provider-url="${javatx.mdb1.url}" * connection-factory-jndi-name="${javatx.mdb1.qcf}" * destination-jndi-name="${javatx.mdb1.queue1}" * jms-polling-interval-seconds="${javatx.mdb1.pooling.interval}" * * @weblogic.pool * initial-beans-in-free-pool="${javatx.mdb1.pool.initial}" * max-beans-in-free-pool="${javatx.mdb1.pool.max}" * * @author Eugene Kuleshov */ public class Mdb1Bean extends BaseMdb { protected void onMessageImpl( Message message) { try { String messageId = message.getJMSMessageID(); logger.info( messageId+" : "+message); } catch( JMSException ex) { Locator.logError( "JMS error", ex); } } } Notice that all ${...} tokens will be substituted with values from propery file I mentioned above and then XDoclet will generate deployment descriptors from this JavaDoc metadata. Basically what I'm asking is that property usage search should find these substitutions.
So you're basically using it for any key/value pair unrelated to NLSing, right? Currently the whole support is built around property files that contain externalized strings. We have to investigate whether it's feasible to open this up.
Daniel, is there are any chance to address this in 3.2?
>Daniel, is there are any chance to address this in 3.2? Not for 3.2.
