想了解Feature:Map/ReduceFeatureinTIS的新动态吗？本文将为您提供详细的信息，此外，我们还将为您介绍关于'RunAs'CucumberFeature不会为Eclipse中的C
想了解Feature: Map/Reduce Feature in TIS的新动态吗？本文将为您提供详细的信息，此外，我们还将为您介绍关于'Run As' Cucumber Feature 不会为 Eclipse 中的 Cucumber Feature 文件生成 Glue 代码、android – requestWindowFeature(Window.FEATURE_NO_TITLE);导致应用程序崩溃？、android – requestWindowFeature(Window.FEATURE_NO_TITLE);给出了例外、Arcgis Engine（ae）接口详解（3）：featureClass 的 feature 编辑和删除的新知识。
本文目录一览：- Feature: Map/Reduce Feature in TIS
- 'Run As' Cucumber Feature 不会为 Eclipse 中的 Cucumber Feature 文件生成 Glue 代码
- android – requestWindowFeature(Window.FEATURE_NO_TITLE);导致应用程序崩溃？
- android – requestWindowFeature(Window.FEATURE_NO_TITLE);给出了例外
- Arcgis Engine（ae）接口详解（3）：featureClass 的 feature 编辑和删除
Feature: Map/Reduce Feature in TIS
**This is for your reference only! Do not use this for commercial purpose!**
Map/Reduce Feature in TIS
There is a new feature Map/Reduce(M/R) in TIS. User can utilize the M/R feature to design a job that can run in Hadoop Map/Reduce framework.
Keypoint(M1):
1. Create a M/R job in Repository View with the same level as Job Design.
2. Implement some actions like editing M/R job properties, exporting/impoting job.
3. Seperate components by job type, only display the M/R components when M/R job editor is opened.
4. Run M/R job in Oozie View, which does not depend jars required by mapper/reducer method.
M2:
M3:
1. Convert between common job and M/R job.
2. Add cool bar and zoom actions.
3. Only components with the same type as process can be D&D to M/R editor.
RC1
1. Conversion by D&D and paste
2. Move "Hadoop Configuration" tab from Job View to Run view and support repository metadata.
(To be continued...)
'Run As' Cucumber Feature 不会为 Eclipse 中的 Cucumber Feature 文件生成 Glue 代码
如何解决''Run As'' Cucumber Feature 不会为 Eclipse 中的 Cucumber Feature 文件生成 Glue 代码？
''Run As'' Cucumber Feature 不会为 Eclipse 中的 Cucumber Feature 文件生成 glue 代码。
当我运行 Cucumber .feature 文件时，它不会为 Cucumber Feature 文件生成 glue 代码。 相反，它运行先前执行的 .feature 文件。 如何在 Eclipse 中解决此问题。
How to resolve this problem in Eclipse.
解决方法
暂无找到可以解决该程序问题的有效方法，小编努力寻找整理中！
如果你已经找到好的解决方法，欢迎将解决方案带上本链接一起发送给小编。
小编邮箱:dio#foxmail.com (将#修改为@）
android – requestWindowFeature(Window.FEATURE_NO_TITLE);导致应用程序崩溃？
添加此行时,应用程序崩溃
`requestwindowFeature(Window.FEATURE_NO_TITLE);
可能解决方案很简单,但我真的不知道该修复它的人.
Java代码：
public class GLSurfaceCameraSurfaceDemo2Activity extends Activity {
/** Called when the activity is first created. */
GLSurfaceView glSurfaceView;
FrameLayout fl01;
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
requestwindowFeature(Window.FEATURE_NO_TITLE);
}
}
XML文件：
<FrameLayout
android:id="@+id/fl01"
android:orientation="horizontal"
android:layout_width="fill_parent"
android:layout_height="fill_parent"/>
解决方法:
你必须调用requestwindowFeature(Window.FEATURE_NO_TITLE);在setContentView()之前……
public class GLSurfaceCameraSurfaceDemo2Activity extends Activity {
/** Called when the activity is first created. */
GLSurfaceView glSurfaceView;
FrameLayout fl01;
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
requestwindowFeature(Window.FEATURE_NO_TITLE);
setContentView(R.layout.main);
}
android – requestWindowFeature(Window.FEATURE_NO_TITLE);给出了例外
import android.content.pm.ActivityInfo;
import android.os.Bundle;
import android.preference.ListPreference;
import android.preference.Preference;
import android.preference.PreferenceActivity;
import android.util.Log;
import android.view.Window;
import android.view.WindowManager;
public class OptionsActivity extends PreferenceActivity {
private ListPreference mListPreference;
@Override
protected void onCreate (Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
requestwindowFeature(Window.FEATURE_NO_TITLE);
getwindow().addFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN);
getwindow().clearFlags(WindowManager.LayoutParams.FLAG_FORCE_NOT_FULLSCREEN);
addPreferencesFromresource(R.xml.options);
mListPreference = (ListPreference) findPreference("listpreference");
mListPreference.setPersistent(false);
}
}
Exception Stacktrace is given below:
01-27 12:35:51.920: ERROR/AndroidRuntime(615): FATAL EXCEPTION: main
01-27 12:35:51.920: ERROR/AndroidRuntime(615): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.game/com.android.game.OptionsActivity}: android.util.AndroidRuntimeException: requestFeature() must be called before adding content
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.ActivityThread.performlaunchActivity(ActivityThread.java:2663)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.ActivityThread.access$2300(ActivityThread.java:125)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.os.Handler.dispatchMessage(Handler.java:99)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.os.Looper.loop(Looper.java:123)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.ActivityThread.main(ActivityThread.java:4627)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at java.lang.reflect.Method.invokeNative(Native Method)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at java.lang.reflect.Method.invoke(Method.java:521)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at dalvik.system.NativeStart.main(Native Method)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): Caused by: android.util.AndroidRuntimeException: requestFeature() must be called before adding content
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at com.android.internal.policy.impl.PhoneWindow.requestFeature(PhoneWindow.java:172)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.Activity.requestwindowFeature(Activity.java:2719)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at com.android.game.OptionsActivity.onCreate(OptionsActivity.java:20)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): at android.app.ActivityThread.performlaunchActivity(ActivityThread.java:2627)
01-27 12:35:51.920: ERROR/AndroidRuntime(615): ... 11 more
解决方法
编辑：如下所述,我没有看到它使用了preferenceActivity.
只是为了您的理解,这是您使用super.onCreate()调用的PreferenceActivity.onCreate()：
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
requestwindowFeature(Window.FEATURE_NO_TITLE);
setContentView(com.android.internal.R.layout.preference_list_content);
mPreferenceManager = onCreatePreferenceManager();
getListView().setScrollBarStyle(View.SCROLLBARS_INSIDE_INSET);
}
如果在super.onCreate()中已经请求了FEATURE_NO_TITLE,为什么还要求它？有时,如果您深入了解Android源代码,这将非常有用.
Arcgis Engine（ae）接口详解（3）：featureClass 的 feature 编辑和删除
//由于测试数据不完善，featureClass在此要只设null值，真实功能要设实际的值
IFeatureClass featureClass = null;
//获取某个字段的索引，后面取字段值用到
int xxxFieldIdx = featureClass.FindField("xxx");
IFeatureCursor featureCursor = featureClass.Search(null, true);
IFeature feature = null;
//获取到IWorkspaceEdit接口，IWorkspaceEdit是编辑必须的接口
IWorkspaceEdit workspaceEdit = (featureClass as IDataset).Workspace as IWorkspaceEdit;
//开始编辑的两个重要方法，StartEditing第一个参数是是否允许Undo，Redo（重做，撤销），如果是后台数据处理功能一般关系不大
workspaceEdit.StartEditing(true);
//构成一个EditOperation有StartEditOperation和StopEditOperation方法，Undo，Redo是针对一个EditOperation的
workspaceEdit.StartEditOperation();
//这里加try的原因是，如果编辑时出错，需要调用IWorkspaceEdit的一些方法来回滚修改内容
//而且编辑出错几率比一般功能大
try
{
List<int> lstOid = new List<int>();
while ((feature = featureCursor.NextFeature()) != null)
{
//修改属性字段的字段值
feature.Value[xxxFieldIdx] = "sss";
IPoint point = new PointClass();
point.PutCoords(111, 222);
//修改几何字段的字段值
//因为几何字段只有一个，所以不需要字段索引
feature.Shape = point;
//保存要素的修改
feature.Store();
//保存oid是为了之后的删除要素功能
lstOid.Add(feature.OID);
}
System.Runtime.InteropServices.Marshal.FinalReleaseComObject(featureCursor);
//删除
//由于不能在遍历要素时删除要素，因此其中一种删除要素的方法：是在遍历时收集要删除要素的oid，遍历完后再通过oid进行删除
foreach (int oid in lstOid)
{
//先通过oid获取要素，然后调用要素的Delete方法删除
IFeature featureDelete = featureClass.GetFeature(oid);
featureDelete.Delete();
}
//保存编辑
//之前的feature.Store()和featureDelete.Delete()都是临时保存，下面两句才是真实的保存
workspaceEdit.StopEditOperation();
//参数1是是否保存，false就是不保存，也就是恢复到修改前的状态
workspaceEdit.StopEditing(true);
}
catch (Exception ex)
{
//编辑出错需要以下两句，大意是数据回滚
workspaceEdit.StopEditOperation();
workspaceEdit.StopEditing(false);
//此处不记录异常，把异常抛出让系统统一处理
throw new Exception("", ex);
}
我们今天的关于Feature: Map/Reduce Feature in TIS的分享就到这里，谢谢您的阅读，如果想了解更多关于'Run As' Cucumber Feature 不会为 Eclipse 中的 Cucumber Feature 文件生成 Glue 代码、android – requestWindowFeature(Window.FEATURE_NO_TITLE);导致应用程序崩溃？、android – requestWindowFeature(Window.FEATURE_NO_TITLE);给出了例外、Arcgis Engine（ae）接口详解（3）：featureClass 的 feature 编辑和删除的相关信息，可以在本站进行搜索。
本文标签：
