[JBoss OSGi Development] - Re: Change in manifest parser breaks symbolic name
by thomas.diesler＠jboss.com
| 2009-08-26 09:37:42,614 ERROR [org.jboss.osgi.plugins.metadata.QNameAttributeListValueCreator] Exception parsing parameters.
| org.jboss.osgi.plugins.metadata.ParseException: Encountered "jboss-osgi-common" at line 1, column 1.
| Was expecting:
| <QNAME> ...
|
| at org.jboss.osgi.plugins.metadata.HeaderValue.generateParseException(HeaderValue.java:962)
| at org.jboss.osgi.plugins.metadata.HeaderValue.jj_consume_token(HeaderValue.java:842)
| at org.jboss.osgi.plugins.metadata.HeaderValue.parameterInfo(HeaderValue.java:214)
| at org.jboss.osgi.plugins.metadata.HeaderValue.parseParameters(HeaderValue.java:122)
| at org.jboss.osgi.plugins.metadata.HeaderValue.parseParameters(HeaderValue.java:65)
| at org.jboss.osgi.plugins.metadata.HeaderValue.parseParameters(HeaderValue.java:87)
| at org.jboss.osgi.plugins.metadata.QNameAttributeListValueCreator.parseAttribute(QNameAttributeListValueCreator.java:39)
| at org.jboss.osgi.plugins.metadata.ParameterizedAttributeListValueCreator.useString(ParameterizedAttributeListValueCreator.java:39)
| at org.jboss.osgi.plugins.metadata.ParameterizedAttributeListValueCreator.useString(ParameterizedAttributeListValueCreator.java:1)
| at org.jboss.osgi.plugins.metadata.AbstractValueCreator.createValue(AbstractValueCreator.java:53)
| at org.jboss.osgi.plugins.metadata.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:272)
| at org.jboss.osgi.plugins.metadata.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:260)
| at org.jboss.osgi.plugins.metadata.AbstractOSGiMetaData.parseSymbolicName(AbstractOSGiMetaData.java:250)
| at org.jboss.osgi.plugins.metadata.AbstractOSGiMetaData.getBundleSymbolicName(AbstractOSGiMetaData.java:176)
| at org.jboss.osgi.plugins.facade.bundle.OSGiBundleState.getSymbolicName(OSGiBundleState.java:184)
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251712#4251712
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251712
16 years, 7 months
[Embedded JBoss Development] - Re: Archive Conversion Design Descussion
by johnbailey
To start with I will assume converting between storage types is the primary use case. I have started to prototype some archive conversion strategies for storage archives. Eventually we will need to allow converting the storage type in an existing container archive, but I am starting with the just the conversion of storage archives, as it is a prerequisite.
Below is an example syntax I have been prototyping for very basic conversion:
| MemoryMapArchive memoryMapArchive = new MemoryMapArchiveImpl("testArchive.jar");
|
| VfsArchive newArchive = ArchiveConverter.convert(memoryMapArchive).to(VfsArchive.class);
|
|
The above example is assuming there is a known implementation type for the VfsArchive, and it can be constructed using only the archive name. This relies on a very basic ArchiveFactory I have created to create Archive implementations. Once constructed all the content will be converted from the source archive to the newly created.
There will be Archive implementations that can not be constructed with only the name. For this there is an alternate conversion syntax that allows for custom conversion strategies.
Below is an example syntax for custom conversion:
|
| MemoryMapArchive memoryMapArchive = new MemoryMapArchiveImpl("testArchive.jar");
|
| VfsArchiveConverter converter = new VfsConverter();
| VfsConverterMetadata = metadata = new VfsConverterMetatdata(File root);
|
| VfsArchive newArchive = ArchiveConverter.convert(memoryMapArchive).using(converter, metadata);
|
| // or ....
|
| VfsArchive newArchive = ArchiveConverter.convert(memoryMapArchive).using(new VfsConverter(File root));
|
| // or ....
|
| VfsArchive newArchive = ArchiveConverter.convert(memoryMapArchive).using(new VfsConverter());
|
|
|
This example could then allow the conversion of any archive type using whatever strategy necessary to make the conversion.
This is not the slickest syntax ever, but something similar could be used to get an easily extensible conversion system in place. Then alternate conversion impls could be created to provide even nicer API/SPIs..
Below is where I could see it going:
| MemoryMapArchive memoryMapArchive = new MemoryMapArchiveImpl("testArchive.jar");
|
| VfsArchive newArchive = VfsArchiveConverter.convert(memoryMapArchive).toVfs(File root);
|
|
Which internally could make the call above with a custom converter and metadata.
Anyway, just throwing this out to get some thoughts on the syntax and overall design. I am not stuck on it, just the first design that I came up with.
What do you think?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251687#4251687
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251687
16 years, 7 months
[jBPM Development] - Re: Java Activity not using Interface
by jbpmjboss11
Tom, Thanks!
what could be the reason my execution is lost? It is immediate statement after i start process instance. Here is my code...
-----------------------------------------------------------------------------------
variables.put("input", new Holder(inputObj));
processInstance = executionService.startProcessInstanceByKey("myprocess",variables);
String pid = processInstance.getId();
System.out.println("PID is ... "+pid);
executionService.getVariableNames(pid);
String out = (String)executionService.getVariable(processInstance.getId(), "answer");
-----------------------------------------------------------------------------------
It throws exception on the last statement in the above code. I can very well get inside the method mentioned in jpdl with input arguments passing correctly.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251658#4251658
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251658
16 years, 7 months