Just throwing out a couple ideas. Some of these may already be in place, just not documented.
*Create a wiki-tag to embed uploaded attachment images/files.
image:myimg.jpg or image:Main/myimg.jpg instead of http://localhost:8080/wiki/Main/file:myimg.jpg (intent is to show image inline)
file:Main/samplesrc.java instead of manually creating a link to http://localhost:8080/wiki/Main/file:samplesrc.java (useful for future clustering attempts as well). Could also be useful if you use the image: tag for thumbnails and file: tag for downloading the actual image file (i.e. file: never embeds the image).
*Configuration option to allow or disallow embedding external images (i.e. if using the image: tag, only uploaded attachments and not external images). Policy or bandwidth reasons to not use external images for embedding into the page.
*Allow renaming of files on upload.
*Retain and come up with display options for the upload date and the 'uploader' for all attachments.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990190#3990190
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990190
I can look into that too. One option I guess is to load the jar into a byte array and have pointers into that array for the entries, returning BAIS, when needed. This seems like a memory hog though as you have to have the contents of the Jar in memory. I wonder if JarFile and the URLClassLoaders that use them are efficient in that regard? Using a stream interface so that they don't have to keep the raw bytes in memory. If not, then the bytearray approach probably works great.
I think thats sorta what you're already doing with the current implementation that is there.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990160#3990160
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990160
Some more:
| <artifactId>jboss-system</artifactId>
|
| All the ServerMBeanSupport extended MBean services are affected
|
Looks like jboss-system has a dependency on jboss-j2se, because removal of jboss-j2se makes ServerMBeanSupport unhappy due to dependence on org.jboss.mx.util.JBossNotificationBroadcasterSupport
| <artifactId>jnpserver</artifactId>
|
| All the naming provide context factories choke (org.jboss.security.jndi)
|
I do not think we need jboss.jar. so that can be removed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990157#3990157
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990157