For anyone following this thread for info, I was able to set up the felix web console to run parallel to the gfv3 admin console during the prelude and promoted releases.
in the C:\glassfishv3-prelude\glassfish\felix\conf\config.properties add/alter the felix.auto.start.1 property to include the org.apache.felix.webconsole-1.0.1-SNAPSHOT.jar and dependent pieces. I also served it with the felix http jetty (org.apache.felix.http.jetty-0.9.0-SNAPSHOT.jar )
The felix.auto.start.1 ended up looking like
[code]
felix.auto.start.1= \
${com.sun.aas.installRootURI}/modules/javax.xml.stream-10.0-SNAPSHOT.jar \
${com.sun.aas.installRootURI}/modules/tiger-types-osgi-0.3.17.jar \
${com.sun.aas.installRootURI}/modules/auto-depends-0.3.17.jar \
${com.sun.aas.installRootURI}/modules/config-0.3.17.jar \
${com.sun.aas.installRootURI}/modules/hk2-core-0.3.17.jar \
${com.sun.aas.installRootURI}/modules/osgi-adapter-0.3.17.jar \
${com.sun.aas.installRootURI}/felix/bundle/org.osgi.core-1.3.0-SNAPSHOT.jar \
${com.sun.aas.installRootURI}/felix/bundle/org.osgi.compendium-1.3.0-SNAPSHOT.jar \
${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.shell.jar \
${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.shell.remote-1.0.1-SNAPSHOT.jar \
${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.http.jetty-0.9.0-SNAPSHOT.jar \
${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.scr-1.0.5-SNAPSHOT.jar \
${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.webconsole-1.0.1-SNAPSHOT.jar
# ${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.bundlerepository-1.1.0-SNAPSHOT.jar \
# ${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.shell.gui-0.9.0-SNAPSHOT.jar \
# ${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.shell.gui.plugin-0.9.0-SNAPSHOT.jar
# ${com.sun.aas.installRootURI}/felix/bundle/org.apache.felix.shell.tui.jar
[/code]
Put the above jars from a Felix build in the C:\glassfishv3-prelude\glassfish\felix\bundle folder.
Also add a property in config.properties for setting the port to something away from gf ports
org.osgi.service.http.port=5858
The other properties will be defaulted as listed in the configuration at
http://felix.apache.org/site/apache-felix-web-console.html but you could also set them to fit your scenario.
Start gfv3/felix with
java -jar .\modules\glassfish-10.0-SNAPSHOT.jar
[ Can also start with asadmin or netbeans and the shell-remote, shell.gui and or felix web console will come up. Only the shell.tui can only be reached with the java -jar .\modules\glassfish-10.0-SNAPSHOT.jar)
Browse to
http://localhost:5858/system/console for the felix web console.
The alternative telnet connection is at localhost 6666 via the rg.apache.felix.shell.remote-1.0.1-SNAPSHOT.jar for a backup connection.
You can use either shell to add in the fuji framework (JBI OSGi framework) C:\java.net\fuji\trunk\core\framework\target\framework-1.0-SNAPSHOT.jar after which you can add and run OpenESB components and your own composite app developments. Or if you know you are using fuji, its JBI OSGi framework can be added to the config.properties' felix.auto.start.1 above with:
${com.sun.aas.installRootURI}/felix/bundle/framework-1.0-SNAPSHOT.jar \
This also seems to satisfy a start level setting.
The Netbeans6.5 beta is not yet showing a way to deploy JBI and composite apps yet that I can see.
[Message sent by forum member 'rimartin7' (rimartin7)]
http://forums.java.net/jive/thread.jspa?messageID=297304